Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: 8800nl errors (Plusnet)  (Read 3258 times)

hr21

  • Member
  • **
  • Posts: 14
8800nl errors (Plusnet)
« on: May 30, 2015, 05:18:08 PM »

Hi all,

I have had the 8800nl for about a month now, it was very stable on my talktalk line but I recently changed to Plusnet and it has been fine, but the quantity of errors seems to have dramatically increased.

This morning my internet had essentially stopped working and I had to reboot the 8800nl.

I decided to update the firmware to d39 since then,

Now it has been synced for the past 30 minutes since updating and it has the following error readout.

HEC Errors         114   0
OCD Errors   0   0
LCD Errors   0   0
Total Cells   134285110   0
Data Cells   1695407   0
Bit Errors   0   0
Total ES   58   2
Total SES   0   0
Total UAS   28   28

My downstream is 42578 upstream is 12504

This has dropped from 48mbps since the line went live.

I read through the entire 8800nl thread and noticed this chipset does produce more errors, so was considering going for the openreach modem in bridge mode with a router connected - do I have any reason to pursue this?

Further info:

Line Coding (Trellis)   On   On
SNR Margin (dB)   6.1   6.1
Attenuation (dB)     20.1   0.0
Output Power (dBm)   13.3   6.9
Attainable Rate (Kbps)   49906   12692


Any help appreciated.
Thanks
Logged

les-70

  • Kitizen
  • ****
  • Posts: 1254
Re: 8800nl errors (Plusnet)
« Reply #1 on: May 30, 2015, 05:55:54 PM »

My impression is that on many lines there is not much difference in error rates between the HG612 and 8800Nl. However on my line which has odd large noise events giving bursts of CRC's the HG612  has about 50% less errors.  Some others had similar results, I would guess that if your CRC errors are only individually a few per minute then there won't be much difference but if you get odd big CRC error spikes then the HG612 may be better at keeping the DLM at bay.  I found the 8800NL the best for errors of the various devices with the 63168 chipset but things may have altered with subsequent firmware updates.
Logged

underzone

  • Reg Member
  • ***
  • Posts: 442
Re: 8800nl errors (Plusnet)
« Reply #2 on: May 30, 2015, 07:30:47 PM »

Try the DH65 firmware. I posted the link earlier this week.
Logged

hr21

  • Member
  • **
  • Posts: 14
Re: 8800nl errors (Plusnet)
« Reply #3 on: July 23, 2015, 09:21:39 PM »

Hi, I know this is an old post but I've gone back to my 8800nl after using the hg612 for a while but was having similar drops/ disconnects with that in fairness.

I've posted some info over at billion forums but wouldn't mind an additional opinion here - cheers.

Hi, getting disconnects in the middle of the night - wondering if anyone had any ideas why? Here is my log.

Jul 23 03:45:39 daemon crit kernel: Line 0: VDSL2 link down
Jul 23 03:45:39 daemon warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = DOWN, Service Support = PTM
Jul 23 03:45:39 daemon warn kernel: HOST XTM tx ch 0 disabled.
Jul 23 03:45:39 daemon warn kernel: bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0
Jul 23 03:45:39 daemon warn kernel: TxLineRateTimer=0
Jul 23 03:45:39 daemon warn kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 0
Jul 23 03:45:39 daemon warn kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
Jul 23 03:45:42 daemon notice syslog: pppd:Terminating on signal 20.
Jul 23 03:45:42 daemon crit syslog: Clear IP addresses. PPP connection DOWN.
Jul 23 03:45:42 daemon crit syslog: Clear IP addresses. Connection DOWN.
Jul 23 03:45:42 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Jul 23 03:45:42 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jul 23 03:45:47 daemon info kernel: device ptm0 left promiscuous mode
Jul 23 03:45:47 daemon info kernel: device ptm0 entered promiscuous mode
Jul 23 03:45:47 daemon info kernel: device ptm0 left promiscuous mode
Jul 23 03:45:49 daemon crit kernel: Line 0: VDSL G.993 started
Jul 23 03:46:07 daemon crit kernel: Line 0: VDSL2 link up, Bearer 0, us=12280, ds=34999
Jul 23 03:46:07 daemon warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = PTM
Jul 23 03:46:07 daemon warn kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 2
Jul 23 03:46:07 daemon warn kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
Jul 23 03:46:07 daemon warn kernel: TxLineRateTimer=2606
Jul 23 03:46:07 daemon warn kernel: bcmxtmrt: MAC address: 60 03 47 0d 63 0f
Jul 23 03:46:07 daemon warn kernel: [DoCreateDeviceReq.3087]: register_netdev
Jul 23 03:46:07 daemon warn kernel: [DoCreateDeviceReq.3089]: register_netdev done
Jul 23 03:46:07 daemon warn kernel: [FAP0] xtmCreateDevice : devId 0, encapType 0, headerLen 0
Jul 23 03:46:07 daemon warn kernel: bcmxtmcfg: Reserve PTM vcid=0 ptmPri=1 port=0 bondingPort=4
Jul 23 03:46:07 daemon warn kernel: bcmxtmcfg: Reserve PTM vcid=1 ptmPri=2 port=0 bondingPort=4
Jul 23 03:46:07 daemon warn kernel: bcmxtmcfg: Reserve TxQueueIdx=0 for vcid 0
Jul 23 03:46:07 daemon warn kernel: bcmxtmcfg: Reserve MP group=0 priority=0 weight=1
Jul 23 03:46:07 daemon warn kernel: XTM Init: Ch:0 - 400 tx BDs at 0xa47c8000
Jul 23 03:46:07 daemon warn kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=12280000, DS=34999000
Jul 23 03:46:07 daemon warn kernel: [FAP1] xtmCreateDevice : devId 0, encapType 0, headerLen 0
Jul 23 03:46:07 daemon warn kernel: [FAP0] xtmLinkUp : devId 0, matchId 0
Jul 23 03:46:07 daemon warn kernel: [FAP1] xtmLinkUp : devId 0, matchId 0
Jul 23 03:46:07 daemon warn kernel: [FAP0] xtmLinkUp : devId 0, matchId 1
Jul 23 03:46:07 daemon warn kernel: [FAP1] xtmLinkUp : devId 0, matchId 1
Jul 23 03:46:07 daemon warn kernel: ptm0.1 MAC address set to 60:03:47:0D:63:10
Jul 23 03:46:07 daemon warn kernel: netdev path : ptm0.1
Jul 23 03:46:07 daemon info kernel: -> ptm0
Jul 23 03:46:07 daemon warn kernel: BCMVLAN : ptm0 mode was set to RG
Jul 23 03:46:07 daemon info kernel: device ptm0 entered promiscuous mode
Jul 23 03:46:07 daemon notice syslog: pppd:cms logging initialized.
Jul 23 03:46:07 daemon notice syslog: pppd 2.4.1 started by admin, uid 0
Jul 23 03:46:07 daemon notice syslog: PPP: Start to connect ...
Jul 23 03:46:34 daemon err syslog: pppd:Couldn't get channel number: Transport endpoint is not connected
Jul 23 03:46:34 daemon notice syslog: pppd:Couldn't reset tty to normal line discipline: Inappropriate ioctl for device
Jul 23 03:46:34 daemon notice syslog: pppd:Doing disconnect
Jul 23 03:46:37 daemon notice syslog: PPP: Start to connect ...
Jul 23 03:46:42 daemon crit syslog: PPP server detected.
Jul 23 03:46:42 daemon crit syslog: PPP session established.
Jul 23 03:46:42 daemon warn kernel: netdev path : ppp0.1 -> ptm0.1 -> ptm0
Jul 23 03:46:42 daemon notice syslog: pppd:Using interface ppp0.1
Jul 23 03:46:42 daemon notice syslog: pppd:Connect: ppp0.1 <--> ptm0.1
Jul 23 03:46:42 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Jul 23 03:46:42 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jul 23 03:46:42 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jul 23 03:46:42 daemon crit syslog: PPP LCP UP.
Jul 23 03:46:42 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Jul 23 03:46:42 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jul 23 03:46:42 daemon err syslog: pppd:Couldn't increase MRU to 1500
Jul 23 03:46:42 daemon crit syslog: PPP LCP UP.
Jul 23 03:46:43 daemon notice syslog: pppd:local IP address 87.112.30.221
Jul 23 03:46:43 daemon notice syslog: pppd:remote IP address 195.166.128.183
Jul 23 03:46:43 daemon notice syslog: pppd:primary DNS address 212.159.6.9
Jul 23 03:46:43 daemon notice syslog: pppd:secondary DNS address 212.159.6.10
Jul 23 03:46:43 daemon crit syslog: Received valid IP address from server. Connection UP.
Jul 23 03:46:45 daemon warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache flushing the flows^[[0m

and

Having more issues tonight.

We were streaming from amazon instant video this evening and basically the streaming came to a complete halt, and the hec errors were multiplying by the thousands every second. My log was displaying these messages...

Jul 23 21:14:30 daemon err syslog: dhcpd:sending OFFER of 192.168.1.100
Jul 23 21:14:30 daemon err syslog: dhcpd:sending ACK to 192.168.1.100
Jul 23 21:14:38 daemon err syslog: dhcpd:sending OFFER of 192.168.1.101
Jul 23 21:14:38 daemon err syslog: dhcpd:sending ACK to 192.168.1.101

I have changed around cables and homeplugs and it has happened before already. Seems to happen around this time of day.

Any insight?

Thanks
Logged