78--N lan dies. unplug eithernet to reset and adsl dies

[raymie]

I want to use the 7800N to replace my normal routers but it has a huge issue

After a number of hours it seems to die and all local ethernet traffic ceases but the adsl remains up

Pulling the ETHERNET cable (in ewan and lan1 ports) and putting it back in again fixes the local lan issue but when I do that the adsl connection resets (somethin I try to avoid).

Last occurrence was around 19:47 and the log showed

Jul 15 18:58:05 syslog -- MARK --
Jul 15 19:15:40 daemon DHCP SERVER: DHCP request from 00:0d:0b:7a:f3:ee
Jul 15 19:15:44 daemon DHCP SERVER: DHCP request from 00:0d:0b:7a:f3:ee
Jul 15 19:15:48 daemon DHCP SERVER: DHCPDISCOVER from 00:0d:0b:7a:f3:ee via br0
Jul 15 19:15:48 daemon DHCP SERVER: DHCPDISCOVER from 00:0d:0b:7a:f3:ee via br0
Jul 15 19:15:48 daemon DHCP SERVER: already acking lease 192.168.1.154
Jul 15 19:15:49 daemon DHCP SERVER: DHCP offer to 00:0d:0b:7a:f3:ee
Jul 15 19:15:49 daemon DHCP SERVER: DHCP request from 00:0d:0b:7a:f3:ee
Jul 15 19:15:49 daemon DHCP SERVER: DHCP ack to 00:0d:0b:7a:f3:ee
Jul 15 19:47:42 user kernel: eth0 Link DOWN.
Jul 15 19:47:42 user kernel: br0: port 1(eth0) entering disabled state
Jul 15 19:47:42 user kernel: br0: port 1(eth0) entering disabled state
Jul 15 19:47:46 user kernel: eth0 Link UP.
Jul 15 19:47:46 user kernel: br0: port 1(eth0) entering learning state
Jul 15 19:47:46 user kernel: br0: topology change detected, propagating
Jul 15 19:47:46 user kernel: br0: port 1(eth0) entering forwarding state
Jul 15 19:47:59 user kernel: Line 0: ADSL link down
Jul 15 19:48:00 user syslog: tc qdisc del dev ppp_0_0_38_1 root 2>/dev/null
Jul 15 19:48:00 daemon pppd[2216]: Terminating connection due to link down.
Jul 15 19:48:03 user kernel: Line 0: xDSL G.994 training
Jul 15 19:48:09 user kernel: Line 0: ADSL G.992 started
Jul 15 19:48:12 user kernel: Line 0: ADSL G.992 channel analysis
Jul 15 19:48:16 user kernel: Line 0: ADSL G.992 message exchange
Jul 15 19:48:16 user kernel: Line 0: ADSL link up, interleaved, us=256, ds=1856
Jul 15 19:48:18 daemon pppd[2216]: PPPoE: Terminating on signal 15.
Jul 15 19:48:18 daemon pppd[2216]: Clear IP addresses. Connection DOWN.
Jul 15 19:48:18 daemon pppd[2216]: Clear IP addresses.
Jul 15 19:48:18 daemon pppd[2216]: Couldn't increase MTU to 1500.
Jul 15 19:48:18 daemon pppd[2216]: Connection terminated.
Jul 15 19:48:18 daemon pppd[2216]: Connect time 224.6 minutes.
Jul 15 19:48:18 daemon pppd[2216]: Sent 128091557 bytes, received 1288812132 bytes.
Jul 15 19:48:18 user kernel: dev_shutdown, dec ppp device refcnt, dev->refcnt=4
Jul 15 19:48:18 user kernel: unregister_netdevice: waiting for ppp_0_0_38_1 to become free. Usage count = -1
Jul 15 19:48:18 user kernel: dev->name = ppp_0_0_38_1, dev->refcnt=-1
Jul 15 19:48:18 user kernel: after reset to 0, dev->refcnt=0
Jul 15 19:48:18 daemon pppd[2216]: Exit.
Jul 15 19:48:18 daemon pppd[3142]: PPPoATM setdevname_pppoatm
Jul 15 19:48:18 daemon pppd[3142]: PPPoATM setdevname_pppoatm - SUCCESS
Jul 15 19:48:18 daemon pppd[3142]: pppd 2.4.1 started by admin, uid 0
Jul 15 19:48:18 daemon pppd[3142]: PPP: Start to connect ...
Jul 15 19:48:18 daemon pppd[3142]: Using interface ppp0_0_38_1
Jul 15 19:48:18 daemon pppd[3142]: Connect: ppp_0_0_38_1 <-->
Jul 15 19:48:18 daemon pppd[3142]: Couldn't increase MTU to 1500.
Jul 15 19:48:24 daemon pppd[3142]: PPP LCP UP.
Jul 15 19:48:25 daemon pppd[3142]: local IP address xxxxxxxxxxxxx
Jul 15 19:48:25 daemon pppd[3142]: remote IP address xxxxxxxxxxxxxx
Jul 15 19:48:25 daemon pppd[3142]: primary DNS address 217.32.171.21
Jul 15 19:48:25 daemon pppd[3142]: secondary DNS address 213.120.234.2
Jul 15 19:48:25 daemon dnsmasq[92]: using nameserver 213.120.234.2#53
Jul 15 19:48:25 daemon dnsmasq[92]: using nameserver 217.32.171.21#53
Jul 15 19:48:25 daemon pppd[3142]: Received valid IP address from server. Connection UP.
Jul 15 19:48:25 user syslog: begin: interface: ppp_0_0_38_1 go to up
Jul 15 19:48:26 daemon dnsmasq[92]: using nameserver 213.120.234.2#53
Jul 15 19:48:26 daemon dnsmasq[92]: using nameserver 217.32.171.21#53
Jul 15 19:48:26 daemon UPNPD[2471]: received signal 15, good-bye
Jul 15 19:48:28 daemon UPNPD[3317]: HTTP listening on port 2800
Jul 15 19:48:30 user syslog: end: interface: ppp_0_0_38_1 go to up
Jul 15 19:56:02 user syslog: wps_btn&
Jul 15 19:56:02 user syslog: WSCScan&
Jul 15 19:56:05 user kernel: Net device ra0 going down....
Jul 15 19:56:05 user kernel: rlk_inic_mbss_close --->
Jul 15 19:56:05 user kernel: setup MBSS[0] success
Jul 15 19:56:05 user kernel: all interfaces closed.
Jul 15 19:56:05 user kernel: rlk_inic_mbss_close <---
Jul 15 19:56:05 user kernel: iNIC Closing
Jul 15 19:56:05 user kernel: Delete HeartBeatTimer ....
Jul 15 19:56:05 user kernel: iNIC Closed
Jul 15 19:56:05 user kernel: br0: port 3(ra0) entering disabled state
Jul 15 19:58:05 syslog -- MARK --

[billion_fan]

Can you submit a ticket on our esupport found here

http://www.billion.uk.com/esupport/inde ... ets/Submit

Please restart the router, login to the router and submit your full system log, showing the start up process of the router.

[raymie]

I raised a support ticket last night but I cannot get another log at this time since the router failed again overnight and I had to switch it out for the original one at the moment,

[raymie]

This is the startup of the router but MINUS it being attached to the adsl (since I can't lose my current connection at the moment)

Jan 01 00:00:07 syslog syslogd started:
Jan 01 00:00:07 user kernel: klogd started:
Jan 01 00:00:07 user kernel: OS #1 Thu Dec 8 15:30:22 CST 2011
Jan 01 00:00:07 user kernel: Parallel flash device: name MX29LV320AB, id 0x22a8, size 4096KB
Jan 01 00:00:07 user kernel: CPU revision is: 0002a010
Jan 01 00:00:07 user kernel: Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Jan 01 00:00:07 user kernel: Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 01 00:00:07 user kernel: Memory: 29768k/32384k available (1757k kernel code, 2572k reserved, 234k data, 76k init, 0k highmem)
Jan 01 00:00:07 user kernel: Total Flash size: 4096K with 71 sectors
Jan 01 00:00:07 user kernel: MPPE/MPPC encryption/compression module registered
Jan 01 00:00:07 user kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
Jan 01 00:00:07 user kernel: TCP: Hash tables configured (established 2048 bind 4096)
Jan 01 00:00:07 user kernel: Initializing IPsec netlink socket
Jan 01 00:00:07 user kernel: 6WIND/LSIIT IPv6 multicast forwarding 0.1 plus PIM-SM/SSM with *BSD API
Jan 01 00:00:07 user kernel: IPv6 over IPv4 tunneling driver
Jan 01 00:00:07 user kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 01 00:00:07 user kernel: Freeing unused kernel memory: 76k freed
Jan 01 00:00:07 user kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 01 00:00:07 user kernel: atmapi: module license 'Proprietary' taints kernel.
Jan 01 00:00:07 user kernel: adsl: adsl_init entry
Jan 01 00:00:07 user kernel: Config Internal PHY Through MDIO
Jan 01 00:00:07 user kernel: ENET: 100 MB Full-Duplex (auto-neg)
Jan 01 00:00:07 user kernel: eth0: MAC Address: 00:04:ED:D2:AA:6E
Jan 01 00:00:07 user kernel: Config Ethernet Switch Through MDIO Pseudo PHY Interface
Jan 01 00:00:07 user kernel: ethsw: found bcm5395!
Jan 01 00:00:07 user kernel: dgasp: kerSysRegisterDyingGaspHandler: eth1 registered
Jan 01 00:00:07 user kernel: eth1: MAC Address: 00:04:ED:D2:AA:6E
Jan 01 00:00:07 user kernel: eth1 Link UP.
Jan 01 00:00:07 user kernel: rt2880_iNIC: falsely claims to have parameter csumoff
Jan 01 00:00:07 user kernel: RT2880iNIC: 802.11n WLAN PCI driver v2.2.0.1 (Aug. 10, 2009)
Jan 01 00:00:07 user kernel: RT2880iNIC: pci dev 0000:00:01.0 (id 1814:0801 rev 00)
Jan 01 00:00:07 user kernel: PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
Jan 01 00:00:07 user kernel: rt->regs = b0100000
Jan 01 00:00:07 user kernel: Update MAC(0)=00:04:ed:65:7c:8f
Jan 01 00:00:07 user kernel: ============= Init Thread ===================
Jan 01 00:00:07 user kernel: RacfgTaskThread pid = 74
Jan 01 00:00:07 user kernel: RacfgBacklogThread pid = 75
Jan 01 00:00:07 user kernel: ra0: Ralink iNIC at 0xb0100000, 00:04:ed:65:7c:8f, IRQ 39
Jan 01 00:00:07 user kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64
Jan 01 00:00:07 user kernel: eth0 Link UP.
Jan 01 00:00:07 daemon dnsmasq[90]: using nameserver 8.8.4.4#53
Jan 01 00:00:07 daemon dnsmasq[90]: using nameserver 8.8.8.8#53
Jan 01 00:00:07 user kernel: BcmAdsl_Initialize=0xC006F7D8, g_pFnNotifyCallback=0xC0091A04
Jan 01 00:00:07 user kernel: pSdramPHY=0xA1FFFFF8, 0xF04FF00F 0xF00FF00F
Jan 01 00:00:08 user kernel: AdslCoreSharedMemInit: shareMemAvailable=19296
Jan 01 00:00:08 user kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA1FF02DC
Jan 01 00:00:08 user kernel: dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered
Jan 01 00:00:08 user kernel: ATM proc init !!!
Jan 01 00:00:08 user kernel: KLOB extended to 2 pools
Jan 01 00:00:09 user kernel: BRCM NAT Caching v0.1 Jul 3 2007 10:16:19
Jan 01 00:00:09 user kernel: BRCM NAT Cache: Hooking hit function @ c006cc48
Jan 01 00:00:13 user kernel: ip6_tables: (C) 2000-2002 Netfilter core team
Jan 01 00:00:14 user kernel: ip6_conntrack version 0.1 (253 buckets, 2024 max) - 208 bytes per conntrack
Jan 01 00:00:16 user syslog: ifconfig eth0 up
Jan 01 00:00:16 user syslog: ifconfig br0 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255 up
Jan 01 00:00:16 user syslog: ifconfig eth0 up 2>/dev/null
Jan 01 00:00:16 user syslog: brctl addif br0 eth0 2>/dev/null
Jan 01 00:00:16 user kernel: device eth0 entered promiscuous mode
Jan 01 00:00:16 user kernel: br0: port 1(eth0) entering learning state
Jan 01 00:00:16 user kernel: br0: topology change detected, propagating
Jan 01 00:00:16 user kernel: br0: port 1(eth0) entering forwarding state
Jan 01 00:00:16 user syslog: ifconfig eth1 up
Jan 01 00:00:16 user syslog: ifconfig eth1 up 2>/dev/null
Jan 01 00:00:16 user syslog: brctl addif br0 eth1 2>/dev/null
Jan 01 00:00:16 user kernel: device eth1 entered promiscuous mode
Jan 01 00:00:16 user kernel: br0: port 2(eth1) entering learning state
Jan 01 00:00:16 user kernel: br0: topology change detected, propagating
Jan 01 00:00:16 user kernel: br0: port 2(eth1) entering forwarding state
Jan 01 00:00:17 user kernel: br0: port 1(eth0) entering disabled state
Jan 01 00:00:20 user syslog: wps_btn&
Jan 01 00:00:21 user syslog: WSCScan&
Jan 01 00:00:21 user syslog: ifconfig ra0 down 2>/dev/null
Jan 01 00:00:21 user syslog: brctl addif br0 ra0 2>/dev/null
Jan 01 00:00:21 user kernel: device ra0 entered promiscuous mode
Jan 01 00:00:22 user syslog: ethctl eth0 vport query 2>/var/vcfgerr
Jan 01 00:00:22 user syslog: rm /var/vcfgerr
Jan 01 00:00:22 user syslog: ethctl eth1 vport query 2>/var/vcfgerr
Jan 01 00:00:22 user syslog: rm /var/vcfgerr
Jan 01 00:00:22 user syslog: rmmod vnet 2>/dev/null
Jan 01 00:00:22 user kernel: br0: port 2(eth1) entering disabled state
Jan 01 00:00:22 user kernel: br0: port 2(eth1) entering learning state
Jan 01 00:00:22 user kernel: br0: topology change detected, propagating
Jan 01 00:00:22 user kernel: br0: port 2(eth1) entering forwarding state
Jan 01 00:00:22 user kernel: br0: port 1(eth0) entering learning state
Jan 01 00:00:22 user kernel: br0: topology change detected, propagating
Jan 01 00:00:22 user kernel: br0: port 1(eth0) entering forwarding state
Jan 01 00:00:23 daemon dnsmasq[90]: using nameserver 8.8.4.4#53
Jan 01 00:00:23 daemon dnsmasq[90]: using nameserver 8.8.8.8#53
Jan 01 00:00:23 daemon UPNPD[536]: HTTP listening on port 2800
Jan 01 00:00:23 daemon UPNPD[536]: uuidvalue=uuid:0004edd2-aa6e-0004-edd2-aa6e0000048
Jan 01 00:00:24 daemon pppd[547]: PPPoATM setdevname_pppoatm
Jan 01 00:00:24 daemon pppd[547]: PPPoATM setdevname_pppoatm - SUCCESS
Jan 01 00:00:24 daemon dnsmasq[90]: using nameserver 8.8.4.4#53
Jan 01 00:00:24 daemon dnsmasq[90]: using nameserver 8.8.8.8#53
Jan 01 00:00:24 daemon pppd[547]: pppd 2.4.1 started by admin, uid 0
Jan 01 00:00:29 user syslog: web: ::ffff:192.168.1.21 login

[billion_fan]

Hi Raymie

Can you leave the router on for around for a day or so, (you don't need a ADSL connection while you do this) and then send us another updated log.

Edit, - Also is the WLAN light on, on the front of the router, or the wireless option showing within the web interface?

Thanks

[craigae]

Sorry to reply to an old thread, but I think I'm having the same problem.

I upgraded from a Billion 7300g (still working fine, but I wanted faster lan and wireless), updated the 7800n to the latest g firmware, and everything seemed to be initially working fine.

However, when left with nothing to do, the wired LAN ports just seem to stop working after a while. First thing in the morning or when I come back home after work, all the ports are dead. Wireless and ADSL will still be working fine. To resolve the situation, I can log in to the web admin via wifi and reset the box. (This to me suggests it's a software or component problem, and not faulty wiring or the box overheating).

I checked the logs this morning when it happened again, and saw nothing but the usual DHCP requests from wireless stuff (iphones and ipads seem to request frequently). I checked DHCP page and had around 10 devices registered (from about 12 hours previous, when I had last restarted), however only wireless things in the ARP page. The "Physical Port Status" had "Ethernet" ticked, and the lights on the front we on as expected.

Nothing has really changed since I switched to the 7800 from the 7300, so I don't think it's any configuration conflict. I have tried to turn off a few features in the admin (like disable IPV6, time schedules etc) but nothing has helped so far.

This is a major problem because the majority of my equipment is connected via wired port to a switch in another part of the house (although to confirm, equipment connected to all ports fail).

I was hoping someone might have some advice before I have to return it.

[billion_fan]

Sorry to reply to an old thread, but I think I'm having the same problem.

I upgraded from a Billion 7300g (still working fine, but I wanted faster lan and wireless), updated the 7800n to the latest g firmware, and everything seemed to be initially working fine.

However, when left with nothing to do, the wired LAN ports just seem to stop working after a while. First thing in the morning or when I come back home after work, all the ports are dead. Wireless and ADSL will still be working fine. To resolve the situation, I can log in to the web admin via wifi and reset the box. (This to me suggests it's a software or component problem, and not faulty wiring or the box overheating).

I checked the logs this morning when it happened again, and saw nothing but the usual DHCP requests from wireless stuff (iphones and ipads seem to request frequently). I checked DHCP page and had around 10 devices registered (from about 12 hours previous, when I had last restarted), however only wireless things in the ARP page. The "Physical Port Status" had "Ethernet" ticked, and the lights on the front we on as expected.

Nothing has really changed since I switched to the 7800 from the 7300, so I don't think it's any configuration conflict. I have tried to turn off a few features in the admin (like disable IPV6, time schedules etc) but nothing has helped so far.

This is a major problem because the majority of my equipment is connected via wired port to a switch in another part of the house (although to confirm, equipment connected to all ports fail).

I was hoping someone might have some advice before I have to return it.

So the computers connected to the router using a wired connection get 'Limited or No connectivity with a IP address starting with 169 is this correct??

Have you tired to use the EWAN port and connect your hub to this port??

[craigae]

Thanks for the reply.

It just happened again now, and I've only been out the house 3-4 hours today. There is literally nothing in the system log but a few syslog lines of -- MARK -- while I was out and the DHCP stuff for my desktop turning on. Unfortunately, I couldn't copy and paste the log 'cos I had to use my phone to restart.

It seems my PC had gotten a valid IP address in the right range seconds before the ethernet ports stopped working (192.168.1.101). I tried accessing 192.168.1.254 but the request timed out.

On the 4 ports I have an 8 port switch, a security cam, my desktop PC and file server. They all seem to stop working.

Using the EWAN would defeat the purpose of upgrading from a 7300 (speed!)

[billion_fan]

Thanks for the reply.

It just happened again now, and I've only been out the house 3-4 hours today. There is literally nothing in the system log but a few syslog lines of -- MARK -- while I was out and the DHCP stuff for my desktop turning on. Unfortunately, I couldn't copy and paste the log 'cos I had to use my phone to restart.

It seems my PC had gotten a valid IP address in the right range seconds before the ethernet ports stopped working (192.168.1.101). I tried accessing 192.168.1.254 but the request timed out.

On the 4 ports I have an 8 port switch, a security cam, my desktop PC and file server. They all seem to stop working.

Using the EWAN would defeat the purpose of upgrading from a 7300 (speed!)

I know the speed of the EWAN port is 100mbps, I just wanted you to test a device connected to the EWAN port, so we know if the unit is suffering from a sort of LAN failure on ports 1-4.

Maybe you can plug your hub switch the port, this should help to verify the issue.

[craigae]

I know the speed of the EWAN port is 100mbps, I just wanted you to test a device connected to the EWAN port, so we know if the unit is suffering from a sort of LAN failure on ports 1-4.

Maybe you can plug your hub switch the port, this should help to verify the issue.

I finally got around to plugging the switch into the EWAN port. The problem still occurred, but the devices attached to the EWAN port continued to work, while none of the LAN ports did. Hopefully this helps get to the bottom of the problem?

I've noticed it happens pretty much every 7 hours (if that figure is significant somehow?)

I suspected for a little while it was DHCP related, or perhaps an IP clash. I've since tried using longer leases (72 hours) and much shorter ones (4-8 hours) with no better results. Currently I've set 90% of my devices to have a static-ish IP via the DHCP fixed hosts option, so I'm pretty sure the problem is not DHCP related.