8800NL - Wireless/VDSL issues

Discussions for BiPAC 8800 series: 8800NL, 8800NLR2, 8800AXL, 8800AXLR2
Post Reply
neradi
Posts: 2
Joined: Sat Jul 01, 2017 10:48 pm

8800NL - Wireless/VDSL issues

Post by neradi »

Hello to all,

I'm new here and need your help.

I have BiPAC 8800NL but having all kinds of issues.

I'm using VDSL but it seems for some reason my connection is dropping and because of that wireless is not stable at all.

Another strange thing is that my ISP from which i get this router/modem upgraded with 2.51.d1 version and i've seen that latest version is 2.32. And it says: Model Name BiPAC 8800NL.

As temporary solution i used another router for wifi connected over "wan" port to avoid using bipac 8800nl wifi which i turned off using button.

It is happening that after dsl connection is down (it happens random) wifi becomes unstable and i can connect to some wifi network - only to open wifi networks but not protected ones. And, biggest issue is that DHCP does not assign ip address and gateway after DSL connection was dropped and i need to set static ip address for my laptop wireless adapter and then it works.

Anyway, it happened now again after turning off wireless and using another router for wifi but this time it just dropped and i need to wait ~10 seconds for connection and everything worked fine again.

Sorry for my English it is not best ;)

I will c/p my log here, if you need anything else please let me know:

(this log is only for latest dsl drop, i've done clear before it)

Jul 1 23:37:18 kern crit kernel: Line 0: xDSL link down
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = DOWN(2), Service Support = PTM(2)
Jul 1 23:37:18 kern warn kernel: HOST XTM tx ch 0 disabled.
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 0
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = DISABLED
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: xDSL G.Fast Mode = DISABLED
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: ATM Bonding configured in system. Fallback mode = Enabled
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: Bonding State is DATA_IDLE
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: SID MODE SET to 12 BIT MODE
Jul 1 23:37:19 kern warn kernel: *** BcmXdslCoreMaintenanceTask: Resetting XdslCore
Jul 1 23:37:19 kern warn kernel: lmemhdr[2]=0x100CE000, pAdslLMem[2]=0x100CE000
Jul 1 23:37:19 kern warn kernel: pSdramPHY=0xA7FFFFF8, 0x1B7851 0xDEADBEEF
Jul 1 23:37:19 kern warn kernel: *** XfaceOffset: 0x5FF90 => 0x5FF90 ***
Jul 1 23:37:19 kern warn kernel: *** PhySdramSize got adjusted: 0xF3AAC => 0x127ED0 ***
Jul 1 23:37:19 kern warn kernel: AdslCoreSharedMemInit: shareMemSize=41232(41232)
Jul 1 23:37:19 kern warn kernel: AdslCoreHwReset: pLocSbSta=85a60000 bkupThreshold=3072
Jul 1 23:37:19 kern warn kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA7FB2560
Jul 1 23:37:19 kern warn kernel: VersionInfo: A2pv6F039p.d26e
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered disabled state
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered forwarding state
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered forwarding state
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered disabled state
Jul 1 23:37:21 kern info kernel: device ptm0.2 left promiscuous mode
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered disabled state
Jul 1 23:37:22 kern info kernel: device ptm0.3 left promiscuous mode
Jul 1 23:37:22 kern info kernel: br0: port 5(ptm0.3) entered disabled state
Jul 1 23:37:24 daemon notice syslog: pppd:Terminating on signal 20.
Jul 1 23:37:25 kern crit kernel: Line 0: xDSL G.994 training
Jul 1 23:37:29 kern info kernel: device ptm0 left promiscuous mode
Jul 1 23:37:29 kern info kernel: device ptm0 entered promiscuous mode
Jul 1 23:37:29 kern info kernel: device ptm0 left promiscuous mode
Jul 1 23:37:37 kern crit kernel: Line 0: VDSL G.993 started
Jul 1 23:37:46 kern crit kernel: Line 0: VDSL G.993 channel analysis
Jul 1 23:37:47 kern crit kernel: Line 0: VDSL2 link up, Bearer 0, us=1134, ds=17023
Jul 1 23:37:47 kern crit kernel: Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = ENABLED
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: xDSL G.Fast Mode = DISABLED
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP(1), Service Support = PTM(2)
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 2
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
Jul 1 23:37:47 kern warn kernel: bcmxtmrt: TxPAF Status = Disabled
Jul 1 23:37:47 kern warn kernel: bcmxtmrt: MAC address: 60 03 47 0c 47 ac
Jul 1 23:37:47 kern warn kernel: [DoCreateDeviceReq.710]: register_netdev
Jul 1 23:37:47 kern warn kernel: [DoCreateDeviceReq.712]: register_netdev done
Jul 1 23:37:47 kern warn kernel: [FAP0] xtmCreateDevice : devId 0, encapType 0, headerLen 0
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: Reserve TxQueueIdx=0 for vcid 0
Jul 1 23:37:47 kern warn kernel: XTM Init: Ch:0 - 400 tx BDs at 0xa3dcc000
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1134000, DS=17023000
Jul 1 23:37:47 kern warn kernel: [FAP1] xtmCreateDevice : devId 0, encapType 0, headerLen 0
Jul 1 23:37:47 kern warn kernel: [FAP0] xtmLinkUp : devId 0, matchId 0
Jul 1 23:37:47 kern warn kernel: [FAP1] xtmLinkUp : devId 0, matchId 0
Jul 1 23:37:47 kern warn kernel: [FAP0] xtmLinkUp : devId 0, matchId 1
Jul 1 23:37:47 kern warn kernel: [FAP1] xtmLinkUp : devId 0, matchId 1
Jul 1 23:37:47 kern warn kernel: ptm0.1 MAC address set to 60:03:47:0C:47:AD
Jul 1 23:37:47 kern warn kernel: netdev path : ptm0.1 -> ptm0
Jul 1 23:37:47 kern warn kernel: BCMVLAN : ptm0 mode was set to RG
Jul 1 23:37:47 kern info kernel: device ptm0 entered promiscuous mode
Jul 1 23:37:47 kern warn kernel: netdev path : ptm0.2 -> ptm0
Jul 1 23:37:47 kern warn kernel: BCMVLAN : ptm0 mode was set to RG
Jul 1 23:37:48 kern info kernel: device ptm0.2 entered promiscuous mode
Jul 1 23:37:48 kern info kernel: br1: port 1(ptm0.2) entered forwarding state
Jul 1 23:37:48 kern info kernel: br1: port 1(ptm0.2) entered forwarding state
Jul 1 23:37:49 kern warn kernel: netdev path : ptm0.3 -> ptm0
Jul 1 23:37:49 kern warn kernel: BCMVLAN : ptm0 mode was set to RG
Jul 1 23:37:50 kern info kernel: device ptm0.3 entered promiscuous mode
Jul 1 23:37:50 kern info kernel: br0: port 5(ptm0.3) entered forwarding state
Jul 1 23:37:50 kern info kernel: br0: port 5(ptm0.3) entered forwarding state
Jul 1 23:37:52 kern warn kernel: ptm0.4 MAC address set to 60:03:47:0C:47:AE
Jul 1 23:37:52 kern warn kernel: netdev path : ptm0.4 -> ptm0
Jul 1 23:37:52 kern warn kernel: BCMVLAN : ptm0 mode was set to RG
Jul 1 23:37:52 daemon notice syslog: pppd:cms logging initialized.
Jul 1 23:37:52 daemon notice syslog: pppd 2.4.1 started by admin, uid 0
Jul 1 23:37:57 daemon notice syslog: PPP: Start to connect ...
Jul 1 23:37:57 daemon crit syslog: session disconnect pppoe.oldsession=4c00827b63c1/017e
Jul 1 23:38:01 daemon crit syslog: PPP server detected.
Jul 1 23:38:01 daemon crit syslog: PPP session established.
Jul 1 23:38:01 kern warn kernel: netdev path : ppp1.4
Jul 1 23:38:01 kern info kernel: -> ptm0.4 ->
Jul 1 23:38:01 daemon notice syslog: pppd:Using interface ppp1.4
Jul 1 23:38:01 kern info kernel: ptm0
Jul 1 23:38:01 daemon notice syslog: pppd:Connect: ppp1.4 <--> ptm0.4
Jul 1 23:38:01 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Jul 1 23:38:01 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jul 1 23:38:01 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jul 1 23:38:01 daemon crit syslog: PPP LCP UP.
Jul 1 23:38:01 daemon notice syslog: pppd:local IP address 85.94.(masked to be safe)
Jul 1 23:38:01 daemon notice syslog: pppd:remote IP address 85.94.(masked to be safe)
Jul 1 23:38:01 daemon notice syslog: pppd:primary DNS address 212.39.(masked to be safe)
Jul 1 23:38:01 daemon notice syslog: pppd:secondary DNS address 212.39.(masked to be safe)
Jul 1 23:38:01 daemon crit syslog: Received valid IP address from server. Connection UP.
Jul 1 23:38:01 daemon notice syslog: connect count=0 ...
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8800NL - Wireless/VDSL issues

Post by billion_fan »

neradi wrote:Hello to all,

I'm new here and need your help.

I have BiPAC 8800NL but having all kinds of issues.

I'm using VDSL but it seems for some reason my connection is dropping and because of that wireless is not stable at all.

Another strange thing is that my ISP from which i get this router/modem upgraded with 2.51.d1 version and i've seen that latest version is 2.32. And it says: Model Name BiPAC 8800NL.

As temporary solution i used another router for wifi connected over "wan" port to avoid using bipac 8800nl wifi which i turned off using button.

It is happening that after dsl connection is down (it happens random) wifi becomes unstable and i can connect to some wifi network - only to open wifi networks but not protected ones. And, biggest issue is that DHCP does not assign ip address and gateway after DSL connection was dropped and i need to set static ip address for my laptop wireless adapter and then it works.

Anyway, it happened now again after turning off wireless and using another router for wifi but this time it just dropped and i need to wait ~10 seconds for connection and everything worked fine again.

Sorry for my English it is not best ;)

I will c/p my log here, if you need anything else please let me know:

(this log is only for latest dsl drop, i've done clear before it)

Jul 1 23:37:18 kern crit kernel: Line 0: xDSL link down
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = DOWN(2), Service Support = PTM(2)
Jul 1 23:37:18 kern warn kernel: HOST XTM tx ch 0 disabled.
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 0
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = DISABLED
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: xDSL G.Fast Mode = DISABLED
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: ATM Bonding configured in system. Fallback mode = Enabled
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: Bonding State is DATA_IDLE
Jul 1 23:37:18 kern warn kernel: bcmxtmcfg: SID MODE SET to 12 BIT MODE
Jul 1 23:37:19 kern warn kernel: *** BcmXdslCoreMaintenanceTask: Resetting XdslCore
Jul 1 23:37:19 kern warn kernel: lmemhdr[2]=0x100CE000, pAdslLMem[2]=0x100CE000
Jul 1 23:37:19 kern warn kernel: pSdramPHY=0xA7FFFFF8, 0x1B7851 0xDEADBEEF
Jul 1 23:37:19 kern warn kernel: *** XfaceOffset: 0x5FF90 => 0x5FF90 ***
Jul 1 23:37:19 kern warn kernel: *** PhySdramSize got adjusted: 0xF3AAC => 0x127ED0 ***
Jul 1 23:37:19 kern warn kernel: AdslCoreSharedMemInit: shareMemSize=41232(41232)
Jul 1 23:37:19 kern warn kernel: AdslCoreHwReset: pLocSbSta=85a60000 bkupThreshold=3072
Jul 1 23:37:19 kern warn kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA7FB2560
Jul 1 23:37:19 kern warn kernel: VersionInfo: A2pv6F039p.d26e
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered disabled state
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered forwarding state
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered forwarding state
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered disabled state
Jul 1 23:37:21 kern info kernel: device ptm0.2 left promiscuous mode
Jul 1 23:37:21 kern info kernel: br1: port 1(ptm0.2) entered disabled state
Jul 1 23:37:22 kern info kernel: device ptm0.3 left promiscuous mode
Jul 1 23:37:22 kern info kernel: br0: port 5(ptm0.3) entered disabled state
Jul 1 23:37:24 daemon notice syslog: pppd:Terminating on signal 20.
Jul 1 23:37:25 kern crit kernel: Line 0: xDSL G.994 training
Jul 1 23:37:29 kern info kernel: device ptm0 left promiscuous mode
Jul 1 23:37:29 kern info kernel: device ptm0 entered promiscuous mode
Jul 1 23:37:29 kern info kernel: device ptm0 left promiscuous mode
Jul 1 23:37:37 kern crit kernel: Line 0: VDSL G.993 started
Jul 1 23:37:46 kern crit kernel: Line 0: VDSL G.993 channel analysis
Jul 1 23:37:47 kern crit kernel: Line 0: VDSL2 link up, Bearer 0, us=1134, ds=17023
Jul 1 23:37:47 kern crit kernel: Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = ENABLED
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: xDSL G.Fast Mode = DISABLED
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP(1), Service Support = PTM(2)
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 2
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
Jul 1 23:37:47 kern warn kernel: bcmxtmrt: TxPAF Status = Disabled
Jul 1 23:37:47 kern warn kernel: bcmxtmrt: MAC address: 60 03 47 0c 47 ac
Jul 1 23:37:47 kern warn kernel: [DoCreateDeviceReq.710]: register_netdev
Jul 1 23:37:47 kern warn kernel: [DoCreateDeviceReq.712]: register_netdev done
Jul 1 23:37:47 kern warn kernel: [FAP0] xtmCreateDevice : devId 0, encapType 0, headerLen 0
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: Reserve TxQueueIdx=0 for vcid 0
Jul 1 23:37:47 kern warn kernel: XTM Init: Ch:0 - 400 tx BDs at 0xa3dcc000
Jul 1 23:37:47 kern warn kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1134000, DS=17023000
Jul 1 23:37:47 kern warn kernel: [FAP1] xtmCreateDevice : devId 0, encapType 0, headerLen 0
Jul 1 23:37:47 kern warn kernel: [FAP0] xtmLinkUp : devId 0, matchId 0
Jul 1 23:37:47 kern warn kernel: [FAP1] xtmLinkUp : devId 0, matchId 0
Jul 1 23:37:47 kern warn kernel: [FAP0] xtmLinkUp : devId 0, matchId 1
Jul 1 23:37:47 kern warn kernel: [FAP1] xtmLinkUp : devId 0, matchId 1
Jul 1 23:37:47 kern warn kernel: ptm0.1 MAC address set to 60:03:47:0C:47:AD
Jul 1 23:37:47 kern warn kernel: netdev path : ptm0.1 -> ptm0
Jul 1 23:37:47 kern warn kernel: BCMVLAN : ptm0 mode was set to RG
Jul 1 23:37:47 kern info kernel: device ptm0 entered promiscuous mode
Jul 1 23:37:47 kern warn kernel: netdev path : ptm0.2 -> ptm0
Jul 1 23:37:47 kern warn kernel: BCMVLAN : ptm0 mode was set to RG
Jul 1 23:37:48 kern info kernel: device ptm0.2 entered promiscuous mode
Jul 1 23:37:48 kern info kernel: br1: port 1(ptm0.2) entered forwarding state
Jul 1 23:37:48 kern info kernel: br1: port 1(ptm0.2) entered forwarding state
Jul 1 23:37:49 kern warn kernel: netdev path : ptm0.3 -> ptm0
Jul 1 23:37:49 kern warn kernel: BCMVLAN : ptm0 mode was set to RG
Jul 1 23:37:50 kern info kernel: device ptm0.3 entered promiscuous mode
Jul 1 23:37:50 kern info kernel: br0: port 5(ptm0.3) entered forwarding state
Jul 1 23:37:50 kern info kernel: br0: port 5(ptm0.3) entered forwarding state
Jul 1 23:37:52 kern warn kernel: ptm0.4 MAC address set to 60:03:47:0C:47:AE
Jul 1 23:37:52 kern warn kernel: netdev path : ptm0.4 -> ptm0
Jul 1 23:37:52 kern warn kernel: BCMVLAN : ptm0 mode was set to RG
Jul 1 23:37:52 daemon notice syslog: pppd:cms logging initialized.
Jul 1 23:37:52 daemon notice syslog: pppd 2.4.1 started by admin, uid 0
Jul 1 23:37:57 daemon notice syslog: PPP: Start to connect ...
Jul 1 23:37:57 daemon crit syslog: session disconnect pppoe.oldsession=4c00827b63c1/017e
Jul 1 23:38:01 daemon crit syslog: PPP server detected.
Jul 1 23:38:01 daemon crit syslog: PPP session established.
Jul 1 23:38:01 kern warn kernel: netdev path : ppp1.4
Jul 1 23:38:01 kern info kernel: -> ptm0.4 ->
Jul 1 23:38:01 daemon notice syslog: pppd:Using interface ppp1.4
Jul 1 23:38:01 kern info kernel: ptm0
Jul 1 23:38:01 daemon notice syslog: pppd:Connect: ppp1.4 <--> ptm0.4
Jul 1 23:38:01 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Jul 1 23:38:01 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jul 1 23:38:01 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jul 1 23:38:01 daemon crit syslog: PPP LCP UP.
Jul 1 23:38:01 daemon notice syslog: pppd:local IP address 85.94.(masked to be safe)
Jul 1 23:38:01 daemon notice syslog: pppd:remote IP address 85.94.(masked to be safe)
Jul 1 23:38:01 daemon notice syslog: pppd:primary DNS address 212.39.(masked to be safe)
Jul 1 23:38:01 daemon notice syslog: pppd:secondary DNS address 212.39.(masked to be safe)
Jul 1 23:38:01 daemon crit syslog: Received valid IP address from server. Connection UP.
Jul 1 23:38:01 daemon notice syslog: connect count=0 ...

Who is your ISP?? (who provided you with the firmware upgrade etc)

The UK the latest firmware is 2.32e for the Bipac 8800NL (white unit that stands ups)
neradi
Posts: 2
Joined: Sat Jul 01, 2017 10:48 pm

Re: 8800NL - Wireless/VDSL issues

Post by neradi »

billion_fan wrote:
Who is your ISP?? (who provided you with the firmware upgrade etc)

The UK the latest firmware is 2.32e for the Bipac 8800NL (white unit that stands ups)
It is ISP from Bosnia and Herzegovina actually (Eronet/HT). Don't know really how they can have newer firmware that doesn't even exist. I will write them too but not sure if i will get right answer as it is hard to talk with real person who knows something more than just tehnician. And, yes, it is white standing unit.
After logging in admin panel there is custom header with their logo so i guess some customizations are done but unreal software version it seems to be used. I need someone to read this log that i attached to see why drop outs are happening. Maybe weirdest thing is that when there is thunder far far away from me that dsl drops every time even thunderstorm is not even close to me.
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8800NL - Wireless/VDSL issues

Post by billion_fan »

neradi wrote:
billion_fan wrote:
Who is your ISP?? (who provided you with the firmware upgrade etc)

The UK the latest firmware is 2.32e for the Bipac 8800NL (white unit that stands ups)
It is ISP from Bosnia and Herzegovina actually (Eronet/HT). Don't know really how they can have newer firmware that doesn't even exist. I will write them too but not sure if i will get right answer as it is hard to talk with real person who knows something more than just tehnician. And, yes, it is white standing unit.
After logging in admin panel there is custom header with their logo so i guess some customizations are done but unreal software version it seems to be used. I need someone to read this log that i attached to see why drop outs are happening. Maybe weirdest thing is that when there is thunder far far away from me that dsl drops every time even thunderstorm is not even close to me.
The routers logs won't tell you why the line has dropped, as you have custom firmware, you will have to contact your ISP and report the issue, to try and get it resolved, I can't really comment on custom firmware, or line conditions in Bosnia sorry
7800nUser
Posts: 56
Joined: Mon May 05, 2014 9:21 pm

Re: 8800NL - Wireless/VDSL issues

Post by 7800nUser »

neradi are you sure it's not the 8800NL R2 unit you have? I noticed the log mentioned G.Fast which the original 8800NL doesn't support. Can you post an image of the unit you have if you can please.
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8800NL - Wireless/VDSL issues

Post by billion_fan »

7800nUser wrote:neradi are you sure it's not the 8800NL R2 unit you have? I noticed the log mentioned G.Fast which the original 8800NL doesn't support. Can you post an image of the unit you have if you can please.
"yes, it is white standing unit" meaning 8800NL, the grey unit is the 8800NL R2, I think the mention on g.fast is a option within the OS on the new BCM code base, but the hardware needs to support it also
Post Reply