Billion BiPAC 7700N

This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram.
DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version onto it! See 4/32 warning for details.

1) This device does not have sufficient resources (flash and/or RAM) to provide secure and reliable operation.
This means that even setting a password or changing simple network settings might not be possible any more, rendering the device effectively useless. See OpenWrt on 4/32 devices what you can do now.

2) OpenWrt support for this device has ended in 2022.
19.07.10 was the last official build for 4/32 devices.

Devices with Broadcom WiFi chipsets have limited OpenWrt supportability (due to limited FLOSS driver availability for Broadcom chips). Consider this when choosing a device to buy, or when deciding to flash OpenWrt on your device because it is listed as supported. See Broadcom WiFi for details.

DSL will not work at all on devices with BCM63xx DSL chipset (due to unavailability of FLOSS driver for Broadcom chips). Consider this when choosing a device to buy, or when deciding to flash OpenWrt on your device because it is listed as supported.
See Broadcom DSL, Unsupported: DSL modem and Broadcom BCM63xx for details.

BiPAC 7700N

The Billion BiPAC 7700N Wireless-N ADSL2+ Firewall Router is an ADSL2+ Router that offers an integrated 802.11n Access Point, supports data rates up to 300Mbps and incorporates VLAN support capable of establishing reliable high-speed transmissions for wide bandwidth applications.

The BiPAC 7700N is compliant with worldwide ADSL standards, and supports download rates of up to 12 / 24Mbps using ADSL2 / 2+, 8Mbps using ADSL and an upload rate of up to 1Mbps. The integrated Annex M standard supports ADSL2 / 2+ for higher uploads by doubling the upload data rate. The 4-port Ethernet Switch incorporated into the BiPAC 7700N enables users to connect to multiple computers or wired-Ethernet devices easily.

The R2 model has two detachable antennas as the only difference to this model. The 7700 R4 is a different device to this.

The BiPAC 7700N has a similar CPU and wireless platform as the Sagem F@ST2704 V2 but has 32MB of RAM installed instead of 64MB and does not provide a USB port.

None yet but development snapshots are available.

The 7700N does not provide a JTAG interface. So installation via JTAG is not possible. → Install OpenWrt (generic explanation)

You can flash the device to OpenWrt from the web configuration or the emergency firmware mode if the device is running firmware bipac-7700n-vb038_n28_gh_uk-00-4300 (other firmwares are untested.)

cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00010000 00010000 "CFE"
mtd1: 00010000 00010000 "nvram"
mtd2: 007e0000 00010000 "linux"
mtd3: 0015d780 00010000 "kernel"
mtd4: 00682780 00010000 "rootfs"
mtd5: 00420000 00010000 "rootfs_data"
cat /sys/class/mtd/mtd*/offset

This section describes actions that might damage your device or firmware. Proceed with care!

Please ensure that you verify the downloaded OpenWrt firmware binary file (.bin) before proceeding to flash the device.
Note: Resetting the device to factory defaults before continuing is highly recommended.

  1. Browse to and login to the manufacturer's web configuration software
  2. Access the firmware update\upgrade page via the menu on the left hand side
  3. Upload the correct OpenWrt firmware .bin file for the device, using the device's upgrade page
  4. Wait for the process to complete and the device to reboot
  5. Browse to via a web browser and configure LuCI
  6. Establish an ssh connection into and set the root password

NOTE: If you experience Wi-Fi problems (random disconnection or connected but no data) try disabling “WMM Mode” in wifi settings.

NOTE: This is the recommended way to install OpenWrt onto this device.

Set your TCP/IP V4 protocol connection settings to:

  1. IP Address:
  2. Netmask:
  3. Gateway:
  4. DNS: (optional, can be blank)


  1. Power off the router
  2. Press the reset button under the device
  3. Keep the reset button held down while powering up (for approximately 20+ seconds)
  4. Access via a web browser and upload the OpenWrt .bin file
  5. Wait for the process to complete and for the device to then reboot
  6. Browse to via a web browser and configure LuCI
  7. Establish an ssh connection into and set the root password

If you intend to to use the Wi-Fi, it is recommended that you proceed to create a Wi-Fi configuration and then move on to the section entitled basic configuration.

Please first ensure that your configuration is backed up.

Due to the 4/32 warning (unoptimised use of flash, RAM and CPU in official OpenWrt builds,) upgrading the entire flash using a full sized image is the only way to use future OpenWrt builds and snapshots.
Flashing an updated release of OpenWrt can be done via luci or the command prompt via an ssh connection.

(If you would like to understand the 4/32 issue, please observe the amount of memory consumed by luci and the http daemon used to deliver luci's pages. It is almost one fifth of the total RAM the device has.
Include with that : two dhcp servers, an ssh daemon, an ipv6 stack running on all interfaces - which the device was never designed to handle and the device is fast approaching it's limits.)

Once you have an OpenWrt release installed, you can install a snapshot.
Installing a snapshot allows you to run the bleeding edge version of OpenWrt, test out new features and test for regressions or bug fixes.
Running a snapshot is not recommended unless:

  • You are familiar enough with OpenWrt to configure it completely via an ssh connection (luci is not present in snapshots, you can install luci yourself, however.)
  • You are testing a new feature, trying to check for a regression or other bug or feature.
  • You check the sha256 checksum of the firmware download before flashing the device.
  • You are confident you understand the risk involved in flashing a bleeding edge development version of OpenWrt.
  • You are prepared to re-install any extra packages you have installed via opkg.

The following steps will allow you to download, check and install an OpenWrt snapshot from within an Internet connected device running OpenWrt. This is commonly performed while logged in via an ssh connection.

cd /tmp
rm -r /tmp/opkg-lists/
sync && echo 3 > /proc/sys/vm/drop_caches
wget -O snapshot.bin
grep "FAST2704V2" sha256sums
sha256sum snapshot.bin
# Compare the two checksums which appear
# Confirm that they both match exactly - do not continue, if not.
rm -f sha256sums
sysupgrade -v /tmp/snapshot.bin

The device will reboot as per the usual sysupgrade method of installation and should come back online with the new version of the software installed.
The -v switch of the sysupgrade command means that the existing configuration should be preserved.
It's recommended to finally remote in via ssh and install any software which is not present inside of the default image, which the device requires to do it's job, as a final step.


A serial connection can be created using the pin outs on the board.
Please see the installation instructions to learn how to put the device into emergency flash mode.

Basic configuration After flashing, proceed with this.

By default the Wi-Fi adapter will not work. To enable the Wi-Fi, use luci to create the connection, then manually add the MAC address to the configuration and disable wmm.

You can find the MAC Address on a sticker on the back of the unit. But any MAC address will work. Just ensure that it is unique within your network.
Once you have a MAC address, You can then ssh into the device and use the command prompt to do the following:

wifi down
uci set wireless.@wifi-iface[-1].macaddr=1F:48:1A:1D:E0:E9
uci set wireless.@wifi-iface[-1].wmm=0
uci commit wireless
wifi up

Ensure that macaddr= is set to the MAC address you want to use.

You can check the new configuration using:

uci get wireless.@wifi-iface[-1].wmm
uci get wireless.@wifi-iface[-1].macaddr

Proceed to the User Guide when you are ready to further configure your running instance of OpenWrt.
If you require further assistance; there is a guide to help with Internet connectivity and troubleshooting if you are experiencing problems.

You can make the same changes by instead modifying the file /etc/config/wireless and reloading the Wi-Fi :

config wifi-iface
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'OpenWrt'
        option encryption 'none'
        option macaddr '2c:e4:XX:XX:XX:XX' # ADD THIS LINE AND USE YOUR OWN MAC ADDRESS
	option wmm '0' # ADD THIS

Edit the file by logging into your device via ssh and using the command:

vi /etc/config/wireless

Once you have added the MAC address and saved the file, reload the Wi-Fi stack using:

wifi reload

For Wi-Fi stability, you absolutely must also disable WMM. Otherwise you may experience a problem where data stops (you are connected but there is no data flow.)

If you change the Wi-Fi configuration via luci at all, you should check that option wmm has not been removed from /etc/config/wireless.
There is not currently anyway to disable WMM via luci. It can only be done using the above two methods.

The default network configuration is:

Interface Name Description Default configuration
br-lan LAN & WiFi
eth0 VLAN containing LAN ports (1 to 4) None
eth0.1 LAN port 1 DHCP
eth0.2 LAN port 2 DHCP
eth0.3 LAN port 3 DHCP
eth0.4 LAN port 4 DHCP
lo Local Loopback None
wlan0 Wi-Fi None and missing it's MAC address
Port Switch port
Internet (WAN) eth0
LAN 1 eth0.1
LAN 2 eth0.2
LAN 3 eth0.3
LAN 4 eth0.4

hardware.button on howto use and configure the hardware button(s). Here, we merely name the buttons, so we can use them in the above Howto.

The Billion BiPAC 7700N has the following buttons:

WPS wps
WIFI wifi
RESET reset

BiPAC 7700N

BiPAC 7700N

Main PCB:
BiPAC 7700N

Note: This will void your warranty!

To open the device and access the main circuit board:

  1. Flip the device onto it's back
  2. Use a pin or the blade of a sharp knife to carefully prise up the black foam rubber feet (one in each corner)
  3. Remove the four Phillips head screws (which you have now revealed,) by using a normal sized Phillips head screw driver
  4. Flip the whole unit back over and then lift the top cover straight up vertically and it should come away cleanly from the rest of the body in one single piece
  5. The circuit board can finally be accessed and even carefully lifted out if desired

Reassemble in the reverse order.

port.serial general information about the serial port, serial port cable, etc.

How to connect to the Serial Port of this specific device:

Be aware that you should not connect the VCC pin or the CPU will receive too much voltage when the DC power supply is connected. This will likely brick it.
o o o o

Only connect GND, TX and RX.


The 7700N is the same platform board type as the Sagem F@ST2704 V2. So any mod which works on the F@ST2704 V2, should within reason stand a fairly good chance of working on the 7700N.
The Sagem F@ST2704 V2 has twice as much RAM (64M.) So if you are handy with soldering SoC\BGA then you may be able to increase the 7700N's memory by replacing the 32MB chip with 64MB.
The Sagem F@ST2704 V2 has a USB port, so in theory it may be possible to add (via soldering) a USB port to the circuit board to add USB functionality to the 7700N.

[ 0.000000] Linux version 4.14.108 (buildbot@slashdirt-03) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r9745-b0395cf)) #0 Thu Mar 28 14:20:58 2019 [ 0.000000] Detected Broadcom 0x6328 CPU revision b0 [ 0.000000] CPU frequency is 320 MHz [ 0.000000] 32MB of RAM installed [ 0.000000] board_bcm963xx: Boot address 0xb8000000 [ 0.000000] board_bcm963xx: CFE version: 1.0.37-106.5 [ 0.000000] bootconsole [early0] enabled [ 0.000000] CPU0 revision is: 0002a075 (Broadcom BMIPS4350) [ 0.000000] board: board name: F@ST2704V2 [ 0.000000] MIPS: machine is Sagem F@ST2704V2 [ 0.000000] Determined physical RAM map: [ 0.000000] memory: 02000000 @ 00000000 (usable) [ 0.000000] Initrd not found or empty - disabling initrd [ 0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 16 bytes. [ 0.000000] Primary data cache 32kB, 2-way, VIPT, cache aliases, linesize 16 bytes [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000000000000-0x0000000001ffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x0000000001ffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000001ffffff] [ 0.000000] On node 0 totalpages: 8192 [ 0.000000] free_area_init_node: node 0, pgdat 805230c0, node_mem_map 810056b0 [ 0.000000] Normal zone: 64 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 8192 pages, LIFO batch:0 [ 0.000000] random: get_random_bytes called from start_kernel+0x80/0x488 with crng_init=0 [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 8128 [ 0.000000] Kernel command line: rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200 [ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes) [ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Memory: 25600K/32768K available (4046K kernel code, 195K rwdata, 960K rodata, 1320K init, 209K bss, 7168K reserved, 0K cma-reserved) [ 0.000000] SLUB: HWalign=16, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS: 256 [ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11945377789 ns [ 0.000017] sched_clock: 32 bits at 160MHz, resolution 6ns, wraps every 13421772796ns [ 0.008126] Calibrating delay loop... 319.74 BogoMIPS (lpj=639488) [ 0.050488] pid_max: default: 32768 minimum: 301 [ 0.055744] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.062600] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.078194] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.088254] futex hash table entries: 256 (order: -1, 3072 bytes) [ 0.094717] pinctrl core: initialized pinctrl subsystem [ 0.103001] NET: Registered protocol family 16 [ 0.351568] registering PCI controller with io_map_base unset [ 0.396764] PCI host bridge to bus 0000:00 [ 0.401025] pci_bus 0000:00: root bus resource [mem 0x10f00000-0x10ffffff] [ 0.408088] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0] [ 0.415072] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0] [ 0.422059] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff] [ 0.430272] pci 0000:00:00.0: [14e4:6328] type 01 class 0x060400 [ 0.430419] pci 0000:00:00.0: PME# supported from D0 D3hot [ 0.430862] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.439466] pci 0000:01:00.0: [14e4:a8d8] type 00 class 0x028000 [ 0.439571] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit] [ 0.439656] pci 0000:01:00.0: enabling Extended Tags [ 0.444907] pci 0000:01:00.0: supports D1 D2 [ 0.445315] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 0.445353] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 01 [ 0.445419] pci 0000:00:00.0: BAR 8: assigned [mem 0x10f00000-0x10ffffff] [ 0.452447] pci 0000:01:00.0: BAR 0: assigned [mem 0x10f00000-0x10f03fff 64bit] [ 0.459985] pci 0000:00:00.0: PCI bridge to [bus 01] [ 0.465078] pci 0000:00:00.0: bridge window [mem 0x10f00000-0x10ffffff] [ 0.480245] clocksource: Switched to clocksource MIPS [ 0.488212] NET: Registered protocol family 2 [ 0.494635] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [ 0.501924] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [ 0.508522] TCP: Hash tables configured (established 1024 bind 1024) [ 0.515617] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 0.521735] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 0.528722] NET: Registered protocol family 1 [ 0.533342] PCI: CLS 0 bytes, default 16 [ 0.542521] Crashlog allocated RAM at address 0x1f00000 [ 0.551779] workingset: timestamp_bits=30 max_order=13 bucket_order=0 [ 0.571084] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.577128] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.616421] io scheduler noop registered [ 0.620462] io scheduler deadline registered (default) [ 0.627338] bcm6328-pinctrl registered at mmio b0000080 [ 0.636589] PCI: Enabling device 0000:00:00.0 (0000 -> 0002) [ 0.643374] 10000100.serial: ttyS0 at MMIO 0x10000100 (irq = 36, base_baud = 1562500) is a bcm63xx_uart [ 0.653124] console [ttyS0] enabled [ 0.660274] bootconsole [early0] disabled [ 0.687008] m25p80 spi1.0: mx25l6405d (8192 Kbytes) [ 0.692883] 3 fixed-partitions partitions found on MTD device spi1.0 [ 0.699442] Creating 3 MTD partitions on "spi1.0": [ 0.704365] 0x000000000000-0x000000010000 : "cfe" [ 0.710889] 0x000000010000-0x0000007f0000 : "linux" [ 0.721805] parser_imagetag: rootfs: CFE image tag found at 0x0 with version 6, board type F@ST2704V2 [ 0.731344] parser_imagetag: Partition 0 is kernel offset 100 and length 1a7180 [ 0.738850] parser_imagetag: Partition 1 is rootfs offset 1a7280 and length 638d80 [ 0.746638] parser_imagetag: Spare partition is offset 3d0004 and length 40fffc [ 0.754238] 2 bcm963xx-imagetag partitions found on MTD device linux [ 0.760791] Creating 2 MTD partitions on "linux": [ 0.765639] 0x000000000100-0x0000001a7280 : "kernel" [ 0.772572] 0x0000001a7280-0x0000007e0000 : "rootfs" [ 0.779246] mtd: device 3 (rootfs) set to be root filesystem [ 0.788919] 1 squashfs-split partitions found on MTD device rootfs [ 0.795330] 0x0000003d0000-0x0000007e0000 : "rootfs_data" [ 0.802566] 0x0000007f0000-0x000000800000 : "nvram" [ 0.811399] libphy: Fixed MDIO Bus: probed [ 0.861332] b53_common: found switch: BCM63xx, rev 0 [ 0.867077] bcm63xx-wdt bcm63xx-wdt: started, timer margin: 30 sec [ 0.876592] PCI: Enabling device 0000:01:00.0 (0000 -> 0002) [ 0.882502] bcma-pci-bridge 0000:01:00.0: bus0: Found chip with id 43225, rev 0x01 and package 0x0A [ 0.891875] bcma-pci-bridge 0000:01:00.0: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x22, class 0x0) [ 0.902854] bcma-pci-bridge 0000:01:00.0: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x17, class 0x0) [ 0.913937] bcma-pci-bridge 0000:01:00.0: bus0: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x0F, class 0x0) [ 1.048958] bcma-pci-bridge 0000:01:00.0: bus0: Invalid SPROM read from the PCIe card, trying to use fallback SPROM [ 1.059699] bcma-pci-bridge 0000:01:00.0: bus0: Using fallback SPROM failed (err -2) [ 1.067665] bcma-pci-bridge 0000:01:00.0: bus0: No SPROM available [ 1.091586] bcma-pci-bridge 0000:01:00.0: bus0: Bus registered [ 1.100064] NET: Registered protocol family 10 [ 1.112490] Segment Routing with IPv6 [ 1.116440] NET: Registered protocol family 17 [ 1.121099] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 1.134452] 8021q: 802.1Q VLAN Support v1.8 [ 1.145902] random: fast init done [ 1.153016] VFS: Mounted root (squashfs filesystem) readonly on device 31:3. [ 1.177883] Freeing unused kernel memory: 1320K [ 1.182553] This architecture does not have kernel memory protection. [ 2.346121] init: Console is alive [ 2.350015] init: - watchdog - [ 4.161061] kmodloader: loading kernel modules from /etc/modules-boot.d/* [ 4.347989] usbcore: registered new interface driver usbfs [ 4.353877] usbcore: registered new interface driver hub [ 4.359585] usbcore: registered new device driver usb [ 4.381621] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 4.391482] ehci-platform: EHCI generic platform driver [ 4.504306] ehci-platform ehci-platform: EHCI Host Controller [ 4.510298] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 [ 4.518807] ehci-platform ehci-platform: irq 50, io mem 0xb0002500 [ 4.540280] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00, overcurrent ignored [ 4.550380] hub 1-0:1.0: USB hub found [ 4.555027] hub 1-0:1.0: 1 port detected [ 4.568926] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 4.578321] ohci-platform: OHCI generic platform driver [ 4.583967] ohci-platform ohci-platform: Generic Platform OHCI controller [ 4.591038] ohci-platform ohci-platform: new USB bus registered, assigned bus number 2 [ 4.599360] ohci-platform ohci-platform: irq 49, io mem 0xb0002600 [ 4.670069] hub 2-0:1.0: USB hub found [ 4.674690] hub 2-0:1.0: 1 port detected [ 4.681770] kmodloader: done loading kernel modules from /etc/modules-boot.d/* [ 4.699960] init: - preinit - [ 6.491870] random: jshn: uninitialized urandom read (4 bytes read) [ 6.726954] random: jshn: uninitialized urandom read (4 bytes read) [ 6.990255] random: jshn: uninitialized urandom read (4 bytes read) [ 7.708139] urandom_read: 2 callbacks suppressed [ 7.708153] random: procd: uninitialized urandom read (4 bytes read) [ 7.734809] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 7.741078] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on Port 1, 100Mbps, full-duplex [ 7.741304] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on Port 2, 10Mbps, full-duplex [ 7.757526] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready [ 7.764286] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready [ 8.740286] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 11.402549] jffs2: notice: (388) jffs2_build_xattr_subsystem: complete building xattr subsystem, 8 of xdatum (3 unchecked, 5 orphan) and 38 of xref (5 dead, 0 orphan) found. [ 11.424215] mount_root: switching to jffs2 overlay [ 11.471859] overlayfs: upper fs does not support tmpfile. [ 11.500495] urandom-seed: Seeding with /etc/urandom.seed [ 11.781021] procd: - early - [ 11.784100] procd: - watchdog - [ 12.528010] procd: - watchdog - [ 12.531806] procd: - ubus - [ 12.603885] random: ubusd: uninitialized urandom read (4 bytes read) [ 12.616744] random: ubusd: uninitialized urandom read (4 bytes read) [ 12.624024] random: ubusd: uninitialized urandom read (4 bytes read) [ 12.632558] procd: - init - [ 13.512161] random: crng init done [ 13.515613] random: 1 urandom warning(s) missed due to ratelimiting [ 13.614003] kmodloader: loading kernel modules from /etc/modules.d/* [ 13.638464] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 13.681533] Bridge firewalling registered [ 13.689615] Loading modules backported from Linux version v4.19.23-0-g67d52fae61c1 [ 13.697449] Backport generated by backports.git v4.19.23-1-0-g480a925a [ 13.711534] ip_tables: (C) 2000-2006 Netfilter Core Team [ 13.742108] nf_conntrack version 0.5.0 (1024 buckets, 4096 max) [ 13.879250] xt_time: kernel timezone is -0000 [ 14.036338] PPP generic driver version 2.4.2 [ 14.046244] NET: Registered protocol family 24 [ 14.097883] b43-phy0: Broadcom 43225 WLAN found (core revision 23) [ 14.105574] b43-phy0: Found PHY: Analog 8, Type 4 (N), Revision 6 [ 14.111885] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2056, Revision 11, Version 0 [ 14.120765] Broadcom 43xx driver loaded [ Features: PNL ] [ 14.133562] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 14.275830] kmodloader: done loading kernel modules from /etc/modules.d/* [ 28.032545] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on Port 1, 100Mbps, full-duplex [ 28.040731] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on Port 2, 10Mbps, full-duplex [ 28.056026] br-lan: port 1(eth0.1) entered blocking state [ 28.061630] br-lan: port 1(eth0.1) entered disabled state [ 28.067723] device eth0.1 entered promiscuous mode [ 28.072696] device eth0 entered promiscuous mode [ 28.094761] br-lan: port 1(eth0.1) entered blocking state [ 28.100357] br-lan: port 1(eth0.1) entered listening state [ 28.106322] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready [ 30.116324] br-lan: port 1(eth0.1) entered learning state [ 32.132677] br-lan: port 1(eth0.1) entered forwarding state [ 32.138405] br-lan: topology change detected, propagating [ 32.235249] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) [ 32.450927] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 32.457409] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready [ 36.449326] wlan0: authenticate with 48:xx:36:xx:58:xx [ 36.515298] wlan0: send auth to 48:xx:36:xx:58:xx (try 1/3) [ 36.525348] wlan0: authenticated [ 36.536387] wlan0: associate with 48:xx:36:xx:58:xx (try 1/3) [ 36.558609] wlan0: RX AssocResp from 48:xx:36:xx:58:xx (capab=0x411 status=0 aid=1) [ 36.584641] wlan0: associated [ 36.639953] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready BusyBox v1.30.1 () built-in shell (ash) _______ ________ __ | |.-----.-----.-----.| | | |.----.| |_ | - || _ | -__| || | | || _|| _| |_______|| __|_____|__|__||________||__| |____| |__| W I R E L E S S F R E E D O M ----------------------------------------------------- OpenWrt SNAPSHOT, r9745-b0395cf -----------------------------------------------------

To configure the vlans on the 7700N use swconfig.

The model used for testing exhibited a Wi-Fi overheating or b43 driver issue which could be triggered by opening multiple encrypted connections via a web browser. The issue appeared to be related to hardware encryption overloading the device and appeared to be solved by disabling ipv6 for the Wi-Fi connection and disabling wmm. The 7700N is from an era before ipv6 began being pushed towards mass adoption and when ssl connection handling was not a default.
There is a Wi-Fi bug in OpenWrt 18.06.2. So it's recommended to use an up to date snapshot (where it is fixed) for now, until the next release.

The hardware Wi-Fi button is not enabled by default. Enabling the Wi-Fi button should be possible. kmod-gpio-button-hotplug is installed.
The same may be the case for the WPS button. It was untested.

The reason the Wi-Fi does not work without manually setting the MAC address, is because the device reports it's MAC address as 00:00:00:00:00:00 when probed via software.
This can be observed by using the command:

cat /sys/class/ieee80211/phy0/macaddress

I can recommend hardening your installation of OpenWrt, once installed.
But not installing luci-ssl due to memory constraints. In fact, You may need to remove luci and uhttpd altogether to free up memory and CPU cycles.
Removing luci and uhttpd reduces memory usage by around 20%. OpenWrt snapshots do not contain luci and this makes them ideal.

The following modules can be removed if you have no intention of hacking the USB header:


You may get an error like:

Collected errors:
 * pkg_run_script: Internal error: kmod-usb2 has a NULL tmp_unpack_dir.
 * opkg_remove_pkg: not removing package "kmod-usb2", prerm script failed

but keep going and all of them can be uninstalled via luci's package manager or opkg.

Not enabling ipv6 appears to bring resource (memory and CPU) usage down. Don't attempt to do so on the lan interface as it will take down the internal network unless you uninstall odhcpd-ipv6only and restart the network.
You can remove ipv6 dhcp from OpenWrt by removing odhcpd-ipv6only via opkg.

opkg update && opkg remove odhcpd-ipv6only
rm -r /tmp/opkg-lists/
uci del network.globals

Alternatively, you could replace replace dnsmasq completely.

You may want to apply the following patch to /etc/init.d/sysctl to ensure an out of memory (oom killer) crash does not occur as a result of memory over utilisation.

        if [ "$mem" -gt 65536 ]; then # 128M
        elif [ "$mem" -gt 32768 ]; then # 64M
        elif [ "$mem" -gt 28672 ]; then # 32M
        elif [ "$mem" -gt 12288 ]; then # 16M
        else # 8M
                frag_low_thresh=393216 # Depreciated after 4.17

Depending upon the configuration of your OpenWrt instance, it may be appropriate to add

option flow_offloading '1'

to the

config defaults

section of the file /etc/config/firewall as doing so appeared to offer a slight improvement in performance.

You may want to install nano if you do lots of manual config editing via ssh.
The unit is a prime candidate for testing luci2.
Turning off Allow legacy 802.11b rates might be of use.
Lowering the dbm to 5 from 20 (depending upon connected client distance) might be of help to you: dBm
You may want to set the device's ntp pool to ones closer to your locality.
Some speedtest results for this device attached to this wiki page would be useful.

The following is a collection of diagnostic output collected from the BiPAC 7700N:

cat /proc/cmdline
rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
cat /proc/cpuinfo
system type             : bcm63xx/F@ST2704V2 (0x6328/0xB0)
machine                 : Sagem F@ST2704V2
processor               : 0
cpu model               : Broadcom BMIPS4350 V7.5
BogoMIPS                : 319.74
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : yes
hardware watchpoint     : no
isa                     : mips1 mips2 mips32r1
ASEs implemented        :
shadow register sets    : 1
kscratch registers      : 0
package                 : 0
core                    : 0
VCED exceptions         : not available
VCEI exceptions         : not available
cat /proc/meminfo
MemTotal:          27856 kB
MemFree:            6176 kB
MemAvailable:      14664 kB
Buffers:            2332 kB
Cached:             8872 kB
SwapCached:            0 kB
Active:             8252 kB
Inactive:           4148 kB
Active(anon):       1800 kB
Inactive(anon):       28 kB
Active(file):       6452 kB
Inactive(file):     4120 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:          1204 kB
Mapped:             2104 kB
Shmem:               632 kB
Slab:               5076 kB
SReclaimable:       1464 kB
SUnreclaim:         3612 kB
KernelStack:         328 kB
PageTables:          200 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:       13928 kB
Committed_AS:       4100 kB
VmallocTotal:    1032116 kB
VmallocUsed:           0 kB
VmallocChunk:          0 kB
cat /proc/devices
Character devices:
  1 mem
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
 10 misc
 90 mtd
108 ppp
128 ptm
136 pts
180 usb
189 usb_device
253 watchdog
254 gpiochip
Block devices:
259 blkext
 31 mtdblock
ls /sys/devices/platform
Fixed MDIO bus.0       b53-switch             bcm63xx_enet_shared.0  bcm63xx_udc            gpio-keys-polled       leds-gpio.0            regulatory.0           uevent
alarmtimer             bcm63xx-wdt            bcm63xx_enetsw.0       ehci-platform          gpio-leds              ohci-platform          ubus@10000000
uci show wireless
cat /sys/class/ieee80211/phy0/macaddress
iw phy0 info
Wiphy phy0
        max # scan SSIDs: 4
        max scan IEs length: 2285 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 1:
                        * 2412 MHz [1] (20.0 dBm)
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)
                        * 2467 MHz [12] (20.0 dBm) (no IR)
                        * 2472 MHz [13] (20.0 dBm) (no IR)
                        * 2484 MHz [14] (20.0 dBm) (no IR)
        interface combinations are not supported
        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
ls -l /sys/class/net
lrwxrwxrwx    1 root     root             0 Mar  2 11:48 br-lan -> ../../devices/virtual/net/br-lan
lrwxrwxrwx    1 root     root             0 Jan  1  1970 eth0 -> ../../devices/platform/bcm63xx_enetsw.0/net/eth0
lrwxrwxrwx    1 root     root             0 Mar  2 11:48 eth0.1 -> ../../devices/virtual/net/eth0.1
lrwxrwxrwx    1 root     root             0 Jan  1  1970 lo -> ../../devices/virtual/net/lo
lrwxrwxrwx    1 root     root             0 Mar  2 14:57 wlan0 -> ../../devices/pci0000:00/0000:00:00.0/0000:01:00.0/bcma0:1/net/wlan0
(install pciutils to be able to lspci)
lspci -vnn -d 14e4:
00:00.0 PCI bridge [0604]: Broadcom Limited Device [14e4:6328] (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 31
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 00000000-00000fff [size=4K]
        Memory behind bridge: 10f00000-10ffffff [size=1M]
        Prefetchable memory behind bridge: None
        Capabilities: [48] Power Management version 3
        Capabilities: [ac] Express Root Port (Slot-), MSI 00
        Capabilities: [100] Advanced Error Reporting
        Kernel driver in use: pcieport
lspci: Unable to load libkmod resources: error -12
01:00.0 Network controller [0280]: Broadcom Limited BCM43224/5 Wireless Network Adapter [14e4:a8d8] (rev 01)
        Subsystem: Broadcom Limited BCM43224/5 Wireless Network Adapter [14e4:a8d8]
        Flags: bus master, fast devsel, latency 0, IRQ 31
        Memory at 10f00000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [58] Vendor Specific Information: Len=78 <?>
        Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [d0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel
        Capabilities: [160] Device Serial Number 00-00-00-ff-ff-00-00-00
        Capabilities: [16c] Power Budgeting <?>
        Kernel driver in use: bcma-pci-bridge
This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2024/02/12 11:13
  • by