Billion UK Forum

I manually rebooted the box with FW 2.50a.d13.
not sure if there are any pointers or anything useful that may be line or environment related to be seen here:

Jan 1 00:00:14 kern warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache registered with netdev chain^[[0m
Jan 1 00:00:14 kern warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache learning via BLOG enabled.^[[0m
Jan 1 00:00:14 kern warn kernel: flwStatsThread created
Jan 1 00:00:14 kern warn kernel: ^[[0;36;44mConstructed Broadcom Packet Flow Cache v2.2 Jul 19 2016 15:19:44^[[0m
Jan 1 00:00:14 kern warn kernel: bcmxtmcfg: bcmxtmcfg_init entry
Jan 1 00:00:14 kern warn kernel: adsl: adsl_init entry
Jan 1 00:00:14 kern warn kernel: Broadcom BCM63381B0 Ethernet Network Device v0.1 Jul 19 2016 15:20:00
Jan 1 00:00:14 kern warn kernel: dgasp: kerSysRegisterDyingGaspHandler: bcmsw registered
Jan 1 00:00:14 kern warn kernel: eth0: <Int sw port: 0> <Logical : 00> PHY_ID <0x00000001 : 0x01> MAC : 60:03:XX:XX:XX:XX
Jan 1 00:00:14 kern warn kernel: eth1: <Int sw port: 1> <Logical : 01> PHY_ID <0x00000002 : 0x02> MAC : 60:03:XX:XX:XX:XX
Jan 1 00:00:14 kern warn kernel: eth2: <Int sw port: 2> <Logical : 02> PHY_ID <0x00000003 : 0x03> MAC : 60:03:XX:XX:XX:XX
Jan 1 00:00:14 kern warn kernel: eth3: <Int sw port: 3> <Logical : 03> PHY_ID <0x00000004 : 0x04> MAC : 60:03:XX:XX:XX:XX
Jan 1 00:00:14 kern warn kernel: eth4: <Int sw port: 4> <Logical : 04> PHY_ID <0x05180018 : 0x18> MAC : 60:03:XX:XX:XX:XX
Jan 1 00:00:14 kern warn kernel: Ethernet Auto Power Down and Sleep: Enabled
Jan 1 00:00:14 kern info kernel: NComm TMS V6.80 Kernel Module loaded.
Jan 1 00:00:14 kern info kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan 1 00:00:14 kern warn kernel: PCI: Enabling device 0000:00:0a.0 (0000 -> 0002)
Jan 1 00:00:14 kern debug kernel: ehci_hcd 0000:00:0a.0: setting latency timer to 64
Jan 1 00:00:14 kern info kernel: ehci_hcd 0000:00:0a.0: EHCI Host Controller
Jan 1 00:00:14 kern info kernel: ehci_hcd 0000:00:0a.0: new USB bus registered, assigned bus number 1
Jan 1 00:00:14 kern warn kernel: ehci_hcd 0000:00:0a.0: Enabling legacy PCI PM
Jan 1 00:00:14 kern info kernel: ehci_hcd 0000:00:0a.0: irq 113, io mem 0x1000c300
Jan 1 00:00:14 kern info kernel: ehci_hcd 0000:00:0a.0: USB f.f started, EHCI 1.00
Jan 1 00:00:14 kern info kernel: hub 1-0:1.0: 1 port detected
Jan 1 00:00:14 kern info kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan 1 00:00:14 kern warn kernel: PCI: Enabling device 0000:00:09.0 (0000 -> 0002)
Jan 1 00:00:14 kern debug kernel: ohci_hcd 0000:00:09.0: setting latency timer to 64
Jan 1 00:00:14 kern info kernel: ohci_hcd 0000:00:09.0: OHCI Host Controller
Jan 1 00:00:14 kern info kernel: ohci_hcd 0000:00:09.0: new USB bus registered, assigned bus number 2
Jan 1 00:00:14 kern info kernel: ohci_hcd 0000:00:09.0: irq 112, io mem 0x1000c400
Jan 1 00:00:14 kern info kernel: hub 2-0:1.0: USB hub found
Jan 1 00:00:14 kern info kernel: hub 2-0:1.0: 1 port detected
Jan 1 00:00:14 kern info kernel: usbcore: registered new interface driver usblp
Jan 1 00:00:14 kern info kernel: Initializing WLCSM Module
Jan 1 00:00:14 kern info kernel: WLCSM Module loaded successfully
Jan 1 00:00:14 kern warn kernel: --SMP support
Jan 1 00:00:14 kern warn kernel: wl: dsl_tx_pkt_flush_len=338
Jan 1 00:00:14 kern warn kernel: wl: norm_wmark_tot=1417, pktc_wmark_tot=1417
Jan 1 00:00:14 kern warn kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
Jan 1 00:00:14 kern warn kernel: wl: passivemode=1
Jan 1 00:00:14 kern info kernel: wl0: creating kthread wl0-kthrd
Jan 1 00:00:14 kern warn kernel: wl: napimode=0
Jan 1 00:00:14 kern warn kernel: initvars_cis_pci: Not CIS format
Jan 1 00:00:14 kern warn kernel: Neither SPROM nor OTP has valid image
Jan 1 00:00:14 kern warn kernel: wl:srom/otp not programmed, using main memory mapped srom info(wombo board)
Jan 1 00:00:14 kern warn kernel: wl: ID=pci/2/0/
Jan 1 00:00:14 kern warn kernel: wl: ID=pci/2/0/
Jan 1 00:00:14 kern warn kernel: wl: loading /etc/wlan/bcm43217_map.bin
Jan 1 00:00:14 kern warn kernel: srom rev:8
Jan 1 00:00:14 kern warn kernel: wl: reading /etc/wlan/bcmcmn_nvramvars.bin, file size=32
Jan 1 00:00:14 kern warn kernel: wl0: allocskbmode=1 currallocskbsz=256
Jan 1 00:00:14 kern warn kernel: wl0: Broadcom BCM43227 802.11 Wireless Controller 7.14.43.21.cpe4.16L02A.0-kdb
Jan 1 00:00:14 kern warn kernel: dgasp: kerSysRegisterDyingGaspHandler: wl0 registered
Jan 1 00:00:14 kern warn kernel: p8021ag: p8021ag_init entry
Jan 1 00:00:14 kern info kernel: Broadcom 802.1Q VLAN Interface, v0.1
Jan 1 00:00:14 kern warn kernel: Host MIPS Clock divider pwrsaving is enabled
Jan 1 00:00:14 kern info kernel: Netfilter messages via NETLINK v0.30.
Jan 1 00:00:16 kern warn kernel: br_netlink_mcpd.c: Setting registration type 0 pid to 474
Jan 1 00:00:16 kern info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:16 kern info kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:17 kern info kernel: device eth0 entered promiscuous mode
Jan 1 00:00:17 kern info kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 1 00:00:20 kern info kernel: device eth1 entered promiscuous mode
Jan 1 00:00:20 kern info kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jan 1 00:00:23 kern info kernel: device eth2 entered promiscuous mode
Jan 1 00:00:23 kern info kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jan 1 00:00:26 kern info kernel: device eth3 entered promiscuous mode
Jan 1 00:00:26 kern info kernel: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jan 1 00:00:29 kern info kernel: device eth4 entered promiscuous mode
Jan 1 00:00:29 kern info kernel: ADDRCONF(NETDEV_UP): eth4: link is not ready
Jan 1 00:00:32 kern warn kernel: *** dslThread dslPid=929
Jan 1 00:00:32 kern warn kernel: BcmAdsl_Initialize=0xC0137050, g_pFnNotifyCallback=0xC0170E90
Jan 1 00:00:33 kern warn kernel: pSdramPHY=0xA3FFFFF8, 0x1B77B2 0xDEADBEEF
Jan 1 00:00:33 kern warn kernel: *** XfaceOffset: 0x4FF90 => 0x4FF90 ***
Jan 1 00:00:33 kern warn kernel: *** PhySdramSize got adjusted: 0xF50C4 => 0x122FF8 ***
Jan 1 00:00:33 kern warn kernel: AdslCoreSharedMemInit: shareMemSize=61408(61408)
Jan 1 00:00:33 kern warn kernel: AdslCoreHwReset: pLocSbSta=814d8000 bkupThreshold=3072
Jan 1 00:00:33 kern warn kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA3FB4AD4
Jan 1 00:00:33 kern warn kernel: VersionInfo: A2pvI042c.d26e
Jan 1 00:00:33 kern warn kernel: ***BcmDiagsMgrRegisterClient: 0 ***
Jan 1 00:00:33 kern warn kernel: dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered
Jan 1 00:00:33 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = DISABLED
Jan 1 00:00:33 kern warn kernel: XTM Init: Ch:0 - 499 rx BDs at 0xa366b000
Jan 1 00:00:33 kern warn kernel: XTM Init: Ch:1 - 16 rx BDs at 0xa3683180
Jan 1 00:00:33 kern warn kernel: bcmxtmrt: PTM/ATM Non-Bonding Mode configured in system
Jan 1 00:00:33 kern warn kernel: bcmxtmcfg: Out of sequence call to XTM_ASM_HANDLER::Uninitialize(). Recovering.
Jan 1 00:00:33 kern warn kernel: bcmxtmcfg: ATM Bonding configured in system. Fallback mode = Enabled
Jan 1 00:00:33 kern warn kernel: bcmxtmcfg: Bonding State is DATA_IDLE
Jan 1 00:00:33 kern warn kernel: bcmxtmcfg: SID MODE SET to 12 BIT MODE
Jan 1 00:00:33 kern warn kernel: bcmxtmcfg: ATM Bonding Mgmt Log Area = 8345b504
Jan 1 00:00:33 kern info kernel: nf_conntrack version 0.5.0 (923 buckets, 3692 max)
Jan 1 00:00:34 kern info kernel: xt_time: kernel timezone is -0000
Jan 1 00:00:35 kern info kernel: monitor task is initialized pid= 430
Jan 1 00:00:37 kern warn kernel: Energy Efficient Ethernet: Enabled
Jan 1 00:00:38 user info syslog: WLAN Schedule Control on wl0 exit
Jan 1 00:00:38 kern crit kernel: eth4 (Int switch port: 4) (Logical Port: 4) Link UP 1000 mbps full duplex
Jan 1 00:00:38 kern info kernel: ADDRCONF(NETDEV_CHANGE): eth4: link becomes ready
Jan 1 00:00:38 kern info kernel: br0: port 5(eth4) entered forwarding state
Jan 1 00:00:38 kern info kernel: br0: port 5(eth4) entered forwarding state
Jan 1 00:01:06 kern crit kernel: Line 0: VDSL G.993 channel analysis
Jan 1 00:01:08 kern crit kernel: Line 0: VDSL2 link up, Bearer 0, us=19903, ds=71059
Jan 1 00:01:08 kern crit kernel: Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
Jan 1 00:01:08 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = ENABLED
Jan 1 00:01:08 kern warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP(1), Service Support = PTM(2)
Jan 1 00:01:08 kern warn kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 2
Jan 1 00:01:08 kern warn kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
Jan 1 00:01:08 kern warn kernel: bcmxtmrt: TxPAF Status = Disabled
Jan 1 00:01:08 kern warn kernel: bcmxtmrt: MAC address: 60 03 XX XX XX XX XX
Jan 1 00:01:08 kern warn kernel: [DoCreateDeviceReq.710]: register_netdev
Jan 1 00:01:08 kern warn kernel: [DoCreateDeviceReq.712]: register_netdev done
Jan 1 00:01:08 kern warn kernel: bcmxtmcfg: Reserve TxQueueIdx=0 for vcid 0
Jan 1 00:01:08 kern warn kernel: XTM Init: Ch:0 - 400 tx BDs at 0xa0800000
Jan 1 00:01:08 kern warn kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=19903000, DS=71059000
Jan 1 00:01:08 kern warn kernel: ptm0.1 MAC address set to 60:03:XX:XX:XX:XX
Jan 1 00:01:08 kern warn kernel: netdev path : ptm0.1
Jan 1 00:01:08 kern info kernel: -> ptm0
Jan 1 00:01:08 kern warn kernel: BCMVLAN : ptm0 mode was set to RG
Jan 1 00:01:08 kern info kernel: device ptm0 entered promiscuous mode
Jan 1 00:01:08 daemon notice syslog: pppd:cms logging initialized.
Jan 1 00:01:08 daemon notice syslog: pppd 2.4.1 started by admin, uid 0
Jan 1 00:01:08 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:01:31 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jan 1 00:01:31 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jan 1 00:01:31 daemon notice syslog: pppd:Doing disconnect
Jan 1 00:01:34 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:01:57 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jan 1 00:01:57 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jan 1 00:01:57 daemon notice syslog: pppd:Doing disconnect
Jan 1 00:02:00 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:02:23 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jan 1 00:02:23 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jan 1 00:02:23 daemon notice syslog: pppd:Doing disconnect
Jan 1 00:02:26 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:02:49 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jan 1 00:02:49 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jan 1 00:02:49 daemon notice syslog: pppd:Doing disconnect
Jan 1 00:02:52 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:03:15 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jan 1 00:03:15 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jan 1 00:03:15 daemon notice syslog: pppd:Doing disconnect
Jan 1 00:03:18 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:03:41 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jan 1 00:03:41 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jan 1 00:03:41 daemon notice syslog: pppd:Doing disconnect
Jan 1 00:03:44 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:04:07 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jan 1 00:04:07 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jan 1 00:04:07 daemon notice syslog: pppd:Doing disconnect
Jan 1 00:04:10 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:04:33 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jan 1 00:04:33 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jan 1 00:04:33 daemon notice syslog: pppd:Doing disconnect
Jan 1 00:04:36 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:04:59 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jan 1 00:04:59 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jan 1 00:04:59 daemon notice syslog: pppd:Doing disconnect
Jan 1 00:05:02 daemon notice syslog: PPP: Start to connect ...
Jan 1 00:05:10 daemon crit syslog: PPP server detected.
Jan 1 00:05:10 daemon crit syslog: PPP session established.
Jan 1 00:05:10 kern warn kernel: netdev path :
Jan 1 00:05:10 kern info kernel: ppp1.1
Jan 1 00:05:10 kern info kernel: ->
Jan 1 00:05:10 kern info kernel: ptm0.1
Jan 1 00:05:10 kern info kernel: -> ptm0
Jan 1 00:05:10 daemon notice syslog: pppd:Using interface ppp1.1
Jan 1 00:05:10 daemon notice syslog: pppd:Connect: ppp1.1 <--> ptm0.1
Jan 1 00:05:10 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Jan 1 00:05:10 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jan 1 00:05:11 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jan 1 00:05:11 daemon crit syslog: PPP LCP UP.
Jan 1 00:05:11 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Jan 1 00:05:11 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jan 1 00:05:11 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jan 1 00:05:11 daemon crit syslog: PPP LCP UP.
Jan 1 00:05:11 daemon notice syslog: pppd:local IP address XXX.XXX.XXX.XXX
Jan 1 00:05:11 daemon notice syslog: pppd:remote IP address XXX.XXX.XXX.XXX
Jan 1 00:05:11 daemon notice syslog: pppd:primary DNS address XXX.XXX.XXX.XXX
Jan 1 00:05:11 daemon notice syslog: pppd:secondary DNS address XXX.XXX.XXX.XXX
Jan 1 00:05:11 daemon crit syslog: Received valid IP address from server. Connection UP.

First post but thought I could add my experience with 2.52.d10 firmware.

Model Name - BiPAC 8800NL R2
System Up-Time - 112D 18H 34M 15S
Software Version - 2.52.d10

Router was pre-configured from IDNET with a 2.5x version (other than 2.52.d10) and I carried out the update myself along with factory reset as per the update instructions.

**Edit**
Running everything as normal apart from Wifi is switched off.

No problems so far.

Model Name BiPAC 8800NL R2
System Up-Time 7D 17H 10M 50S
Software Version 2.52.d10

I followed the upgrade instructions and set up 2.52.d10 on a clean install - and it worked fine until I screwed a networking setting - unfortunately I can't recall what it is now. Might have been NAT, might have been LAN or WAN settings.

Boom. Reboot after reboot. Undid whatever I'd messed up, and it was perfect afterward. This firmware's definitely fragile on something - but it was definitely provoked by a misconfiguration *I* had made.

alanfleming wrote: ↑Sun Jun 24, 2018 12:39 pm I followed the upgrade instructions and set up 2.52.d10 on a clean install - and it worked fine until I screwed a networking setting - unfortunately I can't recall what it is now. Might have been NAT, might have been LAN or WAN settings.

Boom. Reboot after reboot. Undid whatever I'd messed up, and it was perfect afterward. This firmware's definitely fragile on something - but it was definitely provoked by a misconfiguration *I* had made.

If anyone else is experiencing rebooting on 2.52.d10, PM me if you are happy to help debug the issue with our engineers.

Any update on this problem?

Earlier in the year I used my 8800NL R2 on a BT ADSL connection with the supplied 2.52.d4, it was quite stable and ipV6 was also working. Last month I upgraded to Infinity 1, initially I used the supplied BT Hub 6 which worked OK but rebooted every 2 weeks, a Hub 'feature'. Line very stable at 39Mbs.

Last week I decided to try the 8800NL on the Infinity line. Connection fine, with IPv6 as well, but quickly noticed it would reboot once or twice a day. Following suggestions on here upgraded the firmware to 2.52.d10. Initially hopes high but see that has also rebooted after 18 hours or so - and I seem to have lost IPv6 connectivity even though I am sure it is set up as it was before.

It looks like I shall have to revert to the BT Hub and put up with its 14 day reboots.

didn't have a reboot issue with 2.52 d10 but had issue mentioned re snr dropping,went very low at times and feared I would get drops(imagine the earache if it dropped when missus was bidding for something on ebay!),so reverted to the 2.50 d13 version,no drops (ever) ipv6 works fine,no issues and snr never falter more than about .1 db.
not sure if the version I am using lacks a few frills but if it does they are frills I don't seem to need so will stick with this version until I have any issues with it,don't try and fix problems that aren't really there,bit like first creating a solution then looking for a problem it may fix!

Strange that this topic has been bumped.

I have been using 2.52.d10 for what seems ages and had no rebooting issues.

In the last week or so, I have now seen that my router has randomly rebooted at least 2 or 3 times.

I've not done or changed any setting since the update so I have no explanation as to why it's doing the reboots. I might hazard a guess that this may be hardware related (PSU on the way out?) but the whole device is only just 9 months old (supplied new when I signed up to IDnet).

If it happens again over the next few weeks I might go back to IDnet and ask about getting a replacement under warranty first.

**Edit** Just seen my first post above, had this router with the same firmware running for 112 days without issue. Same settings, same devices etc. connected to it.

ZicoUK wrote: ↑Sun Sep 09, 2018 11:56 am Strange that this topic has been bumped.

I have been using 2.52.d10 for what seems ages and had no rebooting issues.

In the last week or so, I have now seen that my router has randomly rebooted at least 2 or 3 times.

I've not done or changed any setting since the update so I have no explanation as to why it's doing the reboots. I might hazard a guess that this may be hardware related (PSU on the way out?) but the whole device is only just 9 months old (supplied new when I signed up to IDnet).

If it happens again over the next few weeks I might go back to IDnet and ask about getting a replacement under warranty first.

**Edit** Just seen my first post above, had this router with the same firmware running for 112 days without issue. Same settings, same devices etc. connected to it.

I will be trying to debug the issue with a customer, I'll drop a update once we have more information

We have four BiPAC 8800NL R2s here in a temperature controlled computer room with UPS. One ISP. They go through phases of being rock solid for weeks/months and then we get a spate of reboots. For example at the moment they all have the same up time to within around 10 minutes.

They all had 2.52 d3 and I updated one to 2.52 d10 yesterday but no effect. I have just enabled debug level logging from all four to my PC.