Frequent Disconnections - Router or Phone Line?
Posted: Fri Oct 25, 2013 9:44 pm
Hello,
I purchased a Billion BiPAC 7800DXL at the end of July this year.
For the first 4-6 weeks it performed very well. It now suffers from disconnections; over the past couple of months, the longest 'Connection Time' I have seen is just over 3 days. The connection usually goes down once every 3-4 hours, today it has been going down every 8 - 30 minutes.
I upgraded from firmware 2.32b to 2.32c today, it hasn't fixed the problem.
What I'm trying to establish, is whether this is a phone line problem, or a router problem.
Any help with this would be greatly appreciated.
The error log for my most recent disconnection is below:
Oct 25 20:59:42 daemon crit kernel: Line 0: ADSL link down
Oct 25 20:59:42 daemon warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = DOWN, Service Support = ATM
Oct 25 20:59:42 daemon warn kernel: bcmxtmrt: DSD(8a435c1c) - 128
Oct 25 20:59:42 daemon warn kernel: HOST XTM tx ch 0 disabled.
Oct 25 20:59:42 daemon warn kernel: bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0
Oct 25 20:59:44 daemon crit kernel: Line 0: xDSL G.994 training
Oct 25 20:59:45 daemon notice syslog: pppd:Terminating on signal 20.
Oct 25 20:59:45 daemon crit syslog: Clear IP addresses. PPP connection DOWN.
Oct 25 20:59:45 daemon crit syslog: Clear IP addresses. Connection DOWN.
Oct 25 20:59:55 daemon crit kernel: Line 0: ADSL G.992 started
Oct 25 21:00:00 daemon crit kernel: Line 0: ADSL G.992 channel analysis
Oct 25 21:00:06 daemon crit kernel: Line 0: ADSL G.992 message exchange
Oct 25 21:00:07 daemon crit kernel: Line 0: ADSL link down
Oct 25 21:00:10 daemon crit kernel: Line 0: xDSL G.994 training
Oct 25 21:00:21 daemon crit kernel: Line 0: ADSL G.992 started
Oct 25 21:00:26 daemon crit kernel: Line 0: ADSL G.992 channel analysis
Oct 25 21:00:32 daemon crit kernel: Line 0: ADSL G.992 message exchange
Oct 25 21:00:32 daemon crit kernel: Line 0: ADSL link up, Bearer 0, us=1272, ds=15259
Oct 25 21:00:32 daemon warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = ATM
Oct 25 21:00:32 daemon warn kernel: bcmxtmrt: MAC address: 00 04 ed f4 7a 58
Oct 25 21:00:32 daemon warn kernel: [DoCreateDeviceReq.3244]: register_netdev
Oct 25 21:00:32 daemon warn kernel: [DoCreateDeviceReq.3246]: register_netdev done
Oct 25 21:00:32 daemon warn kernel: [FAP0] xtmCreateDevice : devId 0, encapType 1, headerLen 0
Oct 25 21:00:32 daemon warn kernel: bcmxtmrt: DSD(8ab1845c) - 128
Oct 25 21:00:32 daemon warn kernel: XTM Init: 400 tx BDs at 0xaa428000
Oct 25 21:00:32 daemon warn kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1272000, DS=15259000
Oct 25 21:00:32 daemon warn kernel: [FAP0] xtmLinkUp : devId 0, matchId 0
Oct 25 21:00:33 daemon notice syslog: pppd:cms logging initialized.
Oct 25 21:00:33 daemon notice syslog: pppd:PPPoATM setdevname_pppoatm
Oct 25 21:00:33 daemon notice syslog: pppd:PPPoATM setdevname_pppoatm - SUCCESS
Oct 25 21:00:33 daemon notice syslog: pppd 2.4.1 started by admin, uid 0
Oct 25 21:00:33 daemon notice syslog: PPP: Start to connect ...
Oct 25 21:00:33 daemon warn kernel: netdev path : pppoa0 -> atm0
Oct 25 21:00:33 daemon notice syslog: pppd:Using interface pppoa0
Oct 25 21:00:33 daemon notice syslog: pppd:Connect: pppoa0 <-->
Oct 25 21:00:36 daemon crit syslog: PPP LCP UP.
Oct 25 21:00:36 daemon notice syslog: pppd:Remote message: CHAP authentication success, unit 455
Oct 25 21:00:36 daemon notice syslog: pppd:local IP address 86.161.122.55
Oct 25 21:00:36 daemon notice syslog: pppd:remote IP address 217.32.142.194
Oct 25 21:00:36 daemon notice syslog: pppd:primary DNS address 217.32.171.22
Oct 25 21:00:36 daemon notice syslog: pppd:secondary DNS address 213.120.234.50
Oct 25 21:00:36 daemon crit syslog: Received valid IP address from server. Connection UP.
Oct 25 21:00:40 daemon warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache flushing the flows^[[0m
I purchased a Billion BiPAC 7800DXL at the end of July this year.
For the first 4-6 weeks it performed very well. It now suffers from disconnections; over the past couple of months, the longest 'Connection Time' I have seen is just over 3 days. The connection usually goes down once every 3-4 hours, today it has been going down every 8 - 30 minutes.
I upgraded from firmware 2.32b to 2.32c today, it hasn't fixed the problem.
What I'm trying to establish, is whether this is a phone line problem, or a router problem.
Any help with this would be greatly appreciated.
The error log for my most recent disconnection is below:
Oct 25 20:59:42 daemon crit kernel: Line 0: ADSL link down
Oct 25 20:59:42 daemon warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = DOWN, Service Support = ATM
Oct 25 20:59:42 daemon warn kernel: bcmxtmrt: DSD(8a435c1c) - 128
Oct 25 20:59:42 daemon warn kernel: HOST XTM tx ch 0 disabled.
Oct 25 20:59:42 daemon warn kernel: bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0
Oct 25 20:59:44 daemon crit kernel: Line 0: xDSL G.994 training
Oct 25 20:59:45 daemon notice syslog: pppd:Terminating on signal 20.
Oct 25 20:59:45 daemon crit syslog: Clear IP addresses. PPP connection DOWN.
Oct 25 20:59:45 daemon crit syslog: Clear IP addresses. Connection DOWN.
Oct 25 20:59:55 daemon crit kernel: Line 0: ADSL G.992 started
Oct 25 21:00:00 daemon crit kernel: Line 0: ADSL G.992 channel analysis
Oct 25 21:00:06 daemon crit kernel: Line 0: ADSL G.992 message exchange
Oct 25 21:00:07 daemon crit kernel: Line 0: ADSL link down
Oct 25 21:00:10 daemon crit kernel: Line 0: xDSL G.994 training
Oct 25 21:00:21 daemon crit kernel: Line 0: ADSL G.992 started
Oct 25 21:00:26 daemon crit kernel: Line 0: ADSL G.992 channel analysis
Oct 25 21:00:32 daemon crit kernel: Line 0: ADSL G.992 message exchange
Oct 25 21:00:32 daemon crit kernel: Line 0: ADSL link up, Bearer 0, us=1272, ds=15259
Oct 25 21:00:32 daemon warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = ATM
Oct 25 21:00:32 daemon warn kernel: bcmxtmrt: MAC address: 00 04 ed f4 7a 58
Oct 25 21:00:32 daemon warn kernel: [DoCreateDeviceReq.3244]: register_netdev
Oct 25 21:00:32 daemon warn kernel: [DoCreateDeviceReq.3246]: register_netdev done
Oct 25 21:00:32 daemon warn kernel: [FAP0] xtmCreateDevice : devId 0, encapType 1, headerLen 0
Oct 25 21:00:32 daemon warn kernel: bcmxtmrt: DSD(8ab1845c) - 128
Oct 25 21:00:32 daemon warn kernel: XTM Init: 400 tx BDs at 0xaa428000
Oct 25 21:00:32 daemon warn kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1272000, DS=15259000
Oct 25 21:00:32 daemon warn kernel: [FAP0] xtmLinkUp : devId 0, matchId 0
Oct 25 21:00:33 daemon notice syslog: pppd:cms logging initialized.
Oct 25 21:00:33 daemon notice syslog: pppd:PPPoATM setdevname_pppoatm
Oct 25 21:00:33 daemon notice syslog: pppd:PPPoATM setdevname_pppoatm - SUCCESS
Oct 25 21:00:33 daemon notice syslog: pppd 2.4.1 started by admin, uid 0
Oct 25 21:00:33 daemon notice syslog: PPP: Start to connect ...
Oct 25 21:00:33 daemon warn kernel: netdev path : pppoa0 -> atm0
Oct 25 21:00:33 daemon notice syslog: pppd:Using interface pppoa0
Oct 25 21:00:33 daemon notice syslog: pppd:Connect: pppoa0 <-->
Oct 25 21:00:36 daemon crit syslog: PPP LCP UP.
Oct 25 21:00:36 daemon notice syslog: pppd:Remote message: CHAP authentication success, unit 455
Oct 25 21:00:36 daemon notice syslog: pppd:local IP address 86.161.122.55
Oct 25 21:00:36 daemon notice syslog: pppd:remote IP address 217.32.142.194
Oct 25 21:00:36 daemon notice syslog: pppd:primary DNS address 217.32.171.22
Oct 25 21:00:36 daemon notice syslog: pppd:secondary DNS address 213.120.234.50
Oct 25 21:00:36 daemon crit syslog: Received valid IP address from server. Connection UP.
Oct 25 21:00:40 daemon warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache flushing the flows^[[0m