8800AXL R2 5GHz channel stops working

Discussions for BiPAC 8800 series: 8800NL, 8800NLR2, 8800AXL, 8800AXLR2
Post Reply
ajwtucker
Posts: 4
Joined: Sat Jan 20, 2018 8:42 am

8800AXL R2 5GHz channel stops working

Post by ajwtucker »

Hi,
3 days ago I bought a 8800AXL R2 to replace a 5 year old 7800DXL that had failed.

I've set it up similarly to the 7800DXL, but I seem to be experiencing a bizarre issue with the 5GHz wireless channel. It works perfectly, but probably around once a day it seems to stop accepting connections on the 5GHz channel and drops all existing connections on that channel.

Ethernet and 2.4GHz wireless still work perfectly, and any attempts to connect over 5GHz produce 'authentication errors' from the clients. If I restart the router, then everything returns to normal and it works. I never had to restart my old 7800DXL even once during the 5 years that I used it.

I've only got around 6 or 7 clients connecting over 5Ghz, so well within the 16 device limit that's been set, and I'm at a loss to explain what's happening.

Restarting the router on a daily basis is not workable for me, and if I can't get to the bottom of this issue then I'll have to return the router and try something else. Does anyone have any ideas?
Top
ajwtucker
Posts: 4
Joined: Sat Jan 20, 2018 8:42 am

Re: 8800AXL R2 5GHz channel stops working

Post by ajwtucker »

This has continued to happen. Sometimes it's manifested as authentication issues, and other times it's manifested as the signal strength 'disappearing' the moment I try to connect.

I've found someone on one of the Australian Billion forums who was having similar issues and was advised to switch away from 5GHz channel 38. I've changed the 5GHz spectrum to another channel. For some bizarre reason, this seems to have worked for the last 24 hours. I will see if it continues...
Top
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8800AXL R2 5GHz channel stops working

Post by billion_fan »

ajwtucker wrote: ↑Mon Jan 22, 2018 8:50 am This has continued to happen. Sometimes it's manifested as authentication issues, and other times it's manifested as the signal strength 'disappearing' the moment I try to connect.

I've found someone on one of the Australian Billion forums who was having similar issues and was advised to switch away from 5GHz channel 38. I've changed the 5GHz spectrum to another channel. For some bizarre reason, this seems to have worked for the last 24 hours. I will see if it continues...
Keep us posted,
Top
ajwtucker
Posts: 4
Joined: Sat Jan 20, 2018 8:42 am

Re: 8800AXL R2 5GHz channel stops working

Post by ajwtucker »

I thought that this change had resolved things, as it had been ticking along for 4 days without incident.

However, today I couldn't connect on either the 5GHz or the 2.4GHz interfaces, so I plugged a cable in and tried connecting over Ethernet. Still no joy - I couldn't connect at all.

However, devices that were already connected to the router were working OK - I managed to connect remotely to a web server and an FTP server that were both connected to the router via Ethernet. I rebooted the router via the hardware switch and everything was fine again.

I've got an external Syslog server connected, and that didn't appear to log anything untoward. It seems to have a few blocked packet notifications (due to firewall rules that I've put in place for my FTP server) and nothing else for today until I restarted it:

<6>1 2018-01-25T13:22:15+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 178.168.129.146:63454
<6>1 2018-01-25T13:22:21+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 178.168.129.146:63454
<6>1 2018-01-25T13:22:33+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 178.168.129.146:63454
<6>1 2018-01-25T17:31:57+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:52371
<6>1 2018-01-25T17:32:00+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:52371
<6>1 2018-01-25T17:32:06+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:52371
<6>1 2018-01-25T17:32:18+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:52371
<6>1 2018-01-25T17:32:18+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:53230
<6>1 2018-01-25T17:32:21+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:53230
<6>1 2018-01-25T17:32:27+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:53230
<6>1 2018-01-25T17:32:39+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:53230
<2>1 2018-01-01T00:00:37+00:00 192.168.1.254 kernel - - - kernel: eth2 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
<6>1 2018-01-01T00:00:37+00:00 192.168.1.254 kernel - - - kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
<6>1 2018-01-01T00:00:37+00:00 192.168.1.254 kernel - - - kernel: br0: port 3(eth2) entered forwarding state
<6>1 2018-01-01T00:00:37+00:00 192.168.1.254 kernel - - - kernel: br0: port 3(eth2) entered forwarding state
<2>1 2018-01-01T00:00:38+00:00 192.168.1.254 kernel - - - kernel: eth3 (Ext switch port: 4) (Logical Port: 12) Link UP 1000 mbps full duplex
<6>1 2018-01-01T00:00:38+00:00 192.168.1.254 kernel - - - kernel: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
<6>1 2018-01-01T00:00:38+00:00 192.168.1.254 kernel - - - kernel: br0: port 4(eth3) entered forwarding state
<6>1 2018-01-01T00:00:38+00:00 192.168.1.254 kernel - - - kernel: br0: port 4(eth3) entered forwarding state
<6>1 2018-01-01T00:00:40+00:00 192.168.1.254 kernel - - - kernel: device wl0 entered promiscuous mode
<6>1 2018-01-01T00:00:40+00:00 192.168.1.254 kernel - - - kernel: br0: port 6(wl0) entered forwarding state
<6>1 2018-01-01T00:00:40+00:00 192.168.1.254 kernel - - - kernel: br0: port 6(wl0) entered forwarding state
<4>1 2018-01-01T00:00:40+00:00 192.168.1.254 kernel - - - kernel: No device name wl0 found in Ethernet driver
<30>1 2018-01-01T00:00:40+00:00 WLAN Schedule - - - Schedule: WLAN Schedule Control on wl0 start
<14>1 2018-01-01T00:00:40+00:00 192.168.1.254 syslog - - - syslog: WLAN Schedule Control on wl1 exit
<6>1 2018-01-01T00:00:48+00:00 192.168.1.254 kernel - - - kernel: device wl1 entered promiscuous mode
<6>1 2018-01-01T00:00:48+00:00 192.168.1.254 kernel - - - kernel: br0: port 7(wl1) entered forwarding state
<6>1 2018-01-01T00:00:48+00:00 192.168.1.254 kernel - - - kernel: br0: port 7(wl1) entered forwarding state
<4>1 2018-01-01T00:00:48+00:00 192.168.1.254 kernel - - - kernel: No device name wl1 found in Ethernet driver
<30>1 2018-01-01T00:00:49+00:00 WLAN Schedule - - - Schedule: WLAN Schedule Control on wl1 start
<2>1 2018-01-01T00:00:56+00:00 192.168.1.254 kernel - - - kernel: Line 0: VDSL G.993 channel analysis
<2>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: Line 0: VDSL2 link up, Bearer 0, us=9886, ds=52182
<2>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: SILI Start - UtopiaCfg - 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: DS xDSL G.inp Mode = ENABLED
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: xDSL G.Fast Mode = DISABLED
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: xDSL ADSL Mode = DISABLED
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP(1), Service Support = PTM(2)
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 2
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: SILI End - UtopiaCfg - 10
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmrt: TxPAF Status = Disabled
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmrt: MAC address: 60 03 47 39 88 9d
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [DoCreateDeviceReq.775]: register_netdev
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [DoCreateDeviceReq.777]: register_netdev done
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP0] xtmCreateDevice : devId 0, encapType 0, headerLen 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP1] xtmCreateDevice : devId 0, encapType 0, headerLen 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: Reserve TxQueueIdx=0 for vcid 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: NON-CO4 DSLAM based operations for PTM CRC & ENET FCS.
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP0] xtmLinkUp : devId 0, matchId 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP1] xtmLinkUp : devId 0, matchId 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP0] xtmLinkUp : devId 0, matchId 1
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP1] xtmLinkUp : devId 0, matchId 1
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: XTM Init: Ch:0 - 400 tx BDs at 0xa2648000
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=9886000, DS=52182000
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: ptm0.1 MAC address set to 60:03:47:39:88:9E
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: netdev path : ptm0.1
<6>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: -> ptm0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: BCMVLAN : ptm0 mode was set to RG
<6>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: device ptm0 entered promiscuous mode
<29>1 2018-01-01T00:00:58+00:00 192.168.1.254 syslog - - - syslog: pppd:cms logging initialized.
<29>1 2018-01-01T00:00:58+00:00 192.168.1.254 syslog - - - syslog: pppd 2.4.1 started by admin, uid 0
<29>1 2018-01-01T00:00:58+00:00 192.168.1.254 syslog - - - syslog: PPP: Start to connect ...
<27>1 2018-01-01T00:01:22+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
<29>1 2018-01-01T00:01:22+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
<29>1 2018-01-01T00:01:22+00:00 192.168.1.254 syslog - - - syslog: pppd:Doing disconnect
<29>1 2018-01-01T00:01:25+00:00 192.168.1.254 syslog - - - syslog: PPP: Start to connect ...
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: PPP server detected.
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: PPP session established.
<4>1 2018-01-01T00:01:27+00:00 192.168.1.254 kernel - - - kernel: netdev path : ppp1.1
<6>1 2018-01-01T00:01:27+00:00 192.168.1.254 kernel - - - kernel: ->
<6>1 2018-01-01T00:01:27+00:00 192.168.1.254 kernel - - - kernel: ptm0.1 ->
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Using interface ppp1.1
<6>1 2018-01-01T00:01:27+00:00 192.168.1.254 kernel - - - kernel: ptm0
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Connect: ppp1.1 <--> ptm0.1
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MTU to 1500.
<27>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MRU to 1500
<27>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MRU to 1500
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: PPP LCP UP.
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MTU to 1500.
<27>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MRU to 1500
<27>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MRU to 1500
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: PPP LCP UP.
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:local IP address <removed>
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:remote IP address <removed>
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:primary DNS address 212.159.6.9
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:secondary DNS address 212.159.6.10
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: Received valid IP address from server. Connection UP.
Top
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8800AXL R2 5GHz channel stops working

Post by billion_fan »

ajwtucker wrote: ↑Thu Jan 25, 2018 7:55 pm I thought that this change had resolved things, as it had been ticking along for 4 days without incident.

However, today I couldn't connect on either the 5GHz or the 2.4GHz interfaces, so I plugged a cable in and tried connecting over Ethernet. Still no joy - I couldn't connect at all.

However, devices that were already connected to the router were working OK - I managed to connect remotely to a web server and an FTP server that were both connected to the router via Ethernet. I rebooted the router via the hardware switch and everything was fine again.

I've got an external Syslog server connected, and that didn't appear to log anything untoward. It seems to have a few blocked packet notifications (due to firewall rules that I've put in place for my FTP server) and nothing else for today until I restarted it:

<6>1 2018-01-25T13:22:15+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 178.168.129.146:63454
<6>1 2018-01-25T13:22:21+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 178.168.129.146:63454
<6>1 2018-01-25T13:22:33+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 178.168.129.146:63454
<6>1 2018-01-25T17:31:57+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:52371
<6>1 2018-01-25T17:32:00+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:52371
<6>1 2018-01-25T17:32:06+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:52371
<6>1 2018-01-25T17:32:18+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:52371
<6>1 2018-01-25T17:32:18+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:53230
<6>1 2018-01-25T17:32:21+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:53230
<6>1 2018-01-25T17:32:27+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:53230
<6>1 2018-01-25T17:32:39+00:00 192.168.1.254 kernel - - - kernel: PacketFilter: Drop TCP packet from [br0] 192.168.1.77:21 to 117.199.75.208:53230
<2>1 2018-01-01T00:00:37+00:00 192.168.1.254 kernel - - - kernel: eth2 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
<6>1 2018-01-01T00:00:37+00:00 192.168.1.254 kernel - - - kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
<6>1 2018-01-01T00:00:37+00:00 192.168.1.254 kernel - - - kernel: br0: port 3(eth2) entered forwarding state
<6>1 2018-01-01T00:00:37+00:00 192.168.1.254 kernel - - - kernel: br0: port 3(eth2) entered forwarding state
<2>1 2018-01-01T00:00:38+00:00 192.168.1.254 kernel - - - kernel: eth3 (Ext switch port: 4) (Logical Port: 12) Link UP 1000 mbps full duplex
<6>1 2018-01-01T00:00:38+00:00 192.168.1.254 kernel - - - kernel: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
<6>1 2018-01-01T00:00:38+00:00 192.168.1.254 kernel - - - kernel: br0: port 4(eth3) entered forwarding state
<6>1 2018-01-01T00:00:38+00:00 192.168.1.254 kernel - - - kernel: br0: port 4(eth3) entered forwarding state
<6>1 2018-01-01T00:00:40+00:00 192.168.1.254 kernel - - - kernel: device wl0 entered promiscuous mode
<6>1 2018-01-01T00:00:40+00:00 192.168.1.254 kernel - - - kernel: br0: port 6(wl0) entered forwarding state
<6>1 2018-01-01T00:00:40+00:00 192.168.1.254 kernel - - - kernel: br0: port 6(wl0) entered forwarding state
<4>1 2018-01-01T00:00:40+00:00 192.168.1.254 kernel - - - kernel: No device name wl0 found in Ethernet driver
<30>1 2018-01-01T00:00:40+00:00 WLAN Schedule - - - Schedule: WLAN Schedule Control on wl0 start
<14>1 2018-01-01T00:00:40+00:00 192.168.1.254 syslog - - - syslog: WLAN Schedule Control on wl1 exit
<6>1 2018-01-01T00:00:48+00:00 192.168.1.254 kernel - - - kernel: device wl1 entered promiscuous mode
<6>1 2018-01-01T00:00:48+00:00 192.168.1.254 kernel - - - kernel: br0: port 7(wl1) entered forwarding state
<6>1 2018-01-01T00:00:48+00:00 192.168.1.254 kernel - - - kernel: br0: port 7(wl1) entered forwarding state
<4>1 2018-01-01T00:00:48+00:00 192.168.1.254 kernel - - - kernel: No device name wl1 found in Ethernet driver
<30>1 2018-01-01T00:00:49+00:00 WLAN Schedule - - - Schedule: WLAN Schedule Control on wl1 start
<2>1 2018-01-01T00:00:56+00:00 192.168.1.254 kernel - - - kernel: Line 0: VDSL G.993 channel analysis
<2>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: Line 0: VDSL2 link up, Bearer 0, us=9886, ds=52182
<2>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: SILI Start - UtopiaCfg - 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: DS xDSL G.inp Mode = ENABLED
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: xDSL G.Fast Mode = DISABLED
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: xDSL ADSL Mode = DISABLED
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP(1), Service Support = PTM(2)
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 2
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: SILI End - UtopiaCfg - 10
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmrt: TxPAF Status = Disabled
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmrt: MAC address: 60 03 47 39 88 9d
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [DoCreateDeviceReq.775]: register_netdev
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [DoCreateDeviceReq.777]: register_netdev done
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP0] xtmCreateDevice : devId 0, encapType 0, headerLen 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP1] xtmCreateDevice : devId 0, encapType 0, headerLen 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: Reserve TxQueueIdx=0 for vcid 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: NON-CO4 DSLAM based operations for PTM CRC & ENET FCS.
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP0] xtmLinkUp : devId 0, matchId 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP1] xtmLinkUp : devId 0, matchId 0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP0] xtmLinkUp : devId 0, matchId 1
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: [FAP1] xtmLinkUp : devId 0, matchId 1
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: XTM Init: Ch:0 - 400 tx BDs at 0xa2648000
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=9886000, DS=52182000
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: ptm0.1 MAC address set to 60:03:47:39:88:9E
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: netdev path : ptm0.1
<6>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: -> ptm0
<4>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: BCMVLAN : ptm0 mode was set to RG
<6>1 2018-01-01T00:00:58+00:00 192.168.1.254 kernel - - - kernel: device ptm0 entered promiscuous mode
<29>1 2018-01-01T00:00:58+00:00 192.168.1.254 syslog - - - syslog: pppd:cms logging initialized.
<29>1 2018-01-01T00:00:58+00:00 192.168.1.254 syslog - - - syslog: pppd 2.4.1 started by admin, uid 0
<29>1 2018-01-01T00:00:58+00:00 192.168.1.254 syslog - - - syslog: PPP: Start to connect ...
<27>1 2018-01-01T00:01:22+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
<29>1 2018-01-01T00:01:22+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
<29>1 2018-01-01T00:01:22+00:00 192.168.1.254 syslog - - - syslog: pppd:Doing disconnect
<29>1 2018-01-01T00:01:25+00:00 192.168.1.254 syslog - - - syslog: PPP: Start to connect ...
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: PPP server detected.
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: PPP session established.
<4>1 2018-01-01T00:01:27+00:00 192.168.1.254 kernel - - - kernel: netdev path : ppp1.1
<6>1 2018-01-01T00:01:27+00:00 192.168.1.254 kernel - - - kernel: ->
<6>1 2018-01-01T00:01:27+00:00 192.168.1.254 kernel - - - kernel: ptm0.1 ->
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Using interface ppp1.1
<6>1 2018-01-01T00:01:27+00:00 192.168.1.254 kernel - - - kernel: ptm0
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Connect: ppp1.1 <--> ptm0.1
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MTU to 1500.
<27>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MRU to 1500
<27>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MRU to 1500
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: PPP LCP UP.
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MTU to 1500.
<27>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MRU to 1500
<27>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:Couldn't increase MRU to 1500
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: PPP LCP UP.
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:local IP address <removed>
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:remote IP address <removed>
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:primary DNS address 212.159.6.9
<29>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: pppd:secondary DNS address 212.159.6.10
<26>1 2018-01-01T00:01:27+00:00 192.168.1.254 syslog - - - syslog: Received valid IP address from server. Connection UP.
Can you try loading the latest firmware attached (with this firmware please upgrade your device and then reset back to factory default settings to ensure all changes within the firmware are implemented correctly)
You do not have the required permissions to view the files attached to this post.
Top
ajwtucker
Posts: 4
Joined: Sat Jan 20, 2018 8:42 am

Re: 8800AXL R2 5GHz channel stops working

Post by ajwtucker »

Many thanks.

I've downloaded and installed the attached firmware, together with a factory reset. I've set it all up again now, so let's see how it goes. I will keep you posted...
Top
Post Reply

Return to “BiPAC 8800 series”