Excellent downstream sync, assuming the initial noise margin was 6dB. That may show up in the system log for connection time.

Error rates pretty low. Unusual to see upstream interleaving. (The D 4 figure). That's probably a result of the history and may revert to Fast Path (D 1).

Edited by RobertoS (Mon 21-Oct-13 20:52:14)

The stats I fist saw showed 9.1 down and 6.8 up. (They've been pretty much like that, (dropping in the evening) since late august.
I've had interleaving since summer 2012. I think that was when I got moved for the Olympics/London internet access.

The system log doesn't seem to give the same wording on the info as the 7800n did. I don't understand most of it :

Oct 21 16:58:27 daemon info kernel: br0: bridge group port 5(wl0) entering disabled state
Oct 21 16:58:27 daemon info kernel: device wl0 left promiscuous mode
Oct 21 16:58:27 daemon info kernel: br0: bridge group port 5(wl0) entering disabled state
Oct 21 16:58:27 daemon info kernel: device wl0 entered promiscuous mode
Oct 21 16:58:27 daemon info kernel: br0: bridge group port 5(wl0) entering forwarding state
Oct 21 16:58:29 daemon info kernel: br0: bridge group port 5(wl0) entering disabled state
Oct 21 16:58:29 daemon info kernel: device wl0 left promiscuous mode
Oct 21 16:58:29 daemon info kernel: br0: bridge group port 5(wl0) entering disabled state
Oct 21 16:58:29 daemon info kernel: device wl0 entered promiscuous mode
Oct 21 16:58:29 daemon info kernel: br0: bridge group port 5(wl0) entering forwarding state
Oct 21 16:58:29 daemon info WLAN Schedule: WLAN Schedule Control on wl0 exit
Oct 21 16:58:30 daemon info kernel: br0: bridge group port 5(wl0) entering disabled state
Oct 21 16:58:30 daemon info kernel: device wl0 left promiscuous mode
Oct 21 16:58:30 daemon info kernel: br0: bridge group port 5(wl0) entering disabled state
Oct 21 16:58:30 daemon info kernel: device wl0 entered promiscuous mode
Oct 21 16:58:30 daemon info kernel: br0: bridge group port 5(wl0) entering forwarding state
Oct 21 16:58:35 daemon info WLAN Schedule: WLAN Schedule Control on wl0 start
Oct 21 16:58:45 daemon info kernel: br0: bridge group port 6(wl1) entering disabled state
Oct 21 16:58:45 daemon info kernel: device wl1 left promiscuous mode
Oct 21 16:58:45 daemon info kernel: br0: bridge group port 6(wl1) entering disabled state
Oct 21 16:58:45 daemon info kernel: device wl1 entered promiscuous mode
Oct 21 16:58:45 daemon info kernel: br0: bridge group port 6(wl1) entering forwarding state
Oct 21 16:58:47 daemon info kernel: br0: bridge group port 6(wl1) entering disabled state
Oct 21 16:58:47 daemon info kernel: device wl1 left promiscuous mode
Oct 21 16:58:47 daemon info kernel: br0: bridge group port 6(wl1) entering disabled state
Oct 21 16:58:47 daemon info kernel: device wl1 entered promiscuous mode
Oct 21 16:58:47 daemon info kernel: br0: bridge group port 6(wl1) entering forwarding state
Oct 21 16:58:48 daemon info WLAN Schedule: WLAN Schedule Control on wl1 exit
Oct 21 16:58:48 daemon info kernel: br0: bridge group port 6(wl1) entering disabled state
Oct 21 16:58:49 daemon info kernel: device wl1 left promiscuous mode
Oct 21 16:58:49 daemon info kernel: br0: bridge group port 6(wl1) entering disabled state
Oct 21 16:58:49 daemon info kernel: device wl1 entered promiscuous mode
Oct 21 16:58:49 daemon info kernel: br0: bridge group port 6(wl1) entering forwarding state
Oct 21 16:58:53 daemon info WLAN Schedule: WLAN Schedule Control on wl1 start
Oct 21 18:46:24 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:46:25 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:46:40 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:46:41 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:49:08 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:49:09 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:49:41 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:49:42 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:51:20 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:51:21 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:51:44 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38
Oct 21 18:51:45 daemon warn kernel: bcmxtmcfg: OAM loopback response not received on VCC 1.0.38

Edited by deleted (Mon 21-Oct-13 21:07:19)

All the 16:58 log entries appear to be the device's Wi-Fi (re)initialising - the wireless interfaces are being placed into promiscuous mode and bridged to the local network in order that traffic can flow.

OAM loopback is like a ping, but at a lower level in the protocol stack. Those messages indicate potential loss of connectivity between the router's WAN port and the DSLAM.

Thanks. I'm thinking it isn't as problematic as it looks to me.

I have my router wired, but did wonder if I'd done something wrong with the wireless. The wording isn't the same as on the 7800n, and that one showed that the Wireless was enabled and also that it was secure. Can't see that shown anywhere with this one, so I'll need to find out if it's OK.

As for the loopback parts - is this a big problem ..and if so, how do I fix it please?

The severity level of these messages tells you they're basically background noise: "info" and "warn".

The OAM loopback message might well be the loss of a single packet, which may just be the DSLAM being too busy to respond before your router gave up waiting. Unless you noticed any corresponding loss of connectivity, it's just meaningless noise.

In reply to a post by TrishaH:

As for the loopback parts - is this a big problem ..and if so, how do I fix it please?

As David_W said, those messages don't look like a problem.

It may be that the easiest way to fix them is to have a good look around the menu system and see if you can reduce what's recorded in the log

There's usually an option to only report events above some degree of severity... sometimes it's called verbosity level.

Ah - thanks David. The last one was fairly straightforward in most ways, and I could more or less understand it.
This even has a Log for Security which is showing some sort of intrusion attempts - this is the last one:
Oct 21 22:11:21 daemon alert kernel: Intrusion -> TCP packet from [pppoa0] 198.20.69.98:33618

This router obviously shows more things that I want to see!

I did know where to put the wireless 'shared key' password with the last one, but don't see where to put it with this one.
There's 2 occasional family members with iPhones, and myself with a notebook that are/were registered to the wireless on the old one. I did see something called WPA/WAPI Passphrase that had a default password in it which is actually on the base of the router. Do you know if this is what I can change to my own password?

Thanks Bill - I'll take a look.
Think it'll be in the config part somewhere.
I used to use the log info on the old one to see when any disconnects had happened and how long it took to re-connect. This one looks completely different

I do see two tall blue spikes on the BQM that aren't usual, but it hasn't lost the connection at all. Perhaps just settling down!

In reply to a post by TrishaH:

Oct 21 22:11:21 daemon alert kernel: Intrusion -> TCP packet from [pppoa0] 198.20.69.98:33618

This router obviously shows more things that I want to see!

That looks like an incoming packet hitting the firewall and being dropped. Such is life on the Internet. There's plenty of innocent explanations, and some not so innocent explanations - but so long as unwanted traffic is not getting onto your network, you have nothing to fear.

In reply to a post by TrishaH:

I did know where to put the wireless 'shared key' password with the last one, but don't see where to put it with this one.
There's 2 occasional family members with iPhones, and myself with a notebook that are/were registered to the wireless on the old one. I did see something called WPA/WAPI Passphrase that had a default password in it which is actually on the base of the router. Do you know if this is what I can change to my own password?

That's the setting you're looking for.

For optimum security, you should use 63 random characters, including upper case, lower case and punctuation. You will probably only ever enter it once per device, so this is hardly too onerous.


Other wireless security recommendations are to turn off WPS (one button wireless pairing), disable TKIP and set WPA2 only mode (which may be a "mixed mode" setting that you should turn off). Don't worry if you haven't got or can't find these settings - the long, random passphrase is the important part.

In reply to a post by TrishaH:

I did see something called WPA/WAPI Passphrase that had a default password in it which is actually on the base of the router. Do you know if this is what I can change to my own password?

Yes but it only works if you Tipex it out smoothly and print the new one on that with a black ballpoint.

Seriously, yes that is the wireless key and you should be able to find that entry in the menus. You should also change the Security mode to WPA2 from WPA, WPA2-PSK is very common. If you find any of your kit cannot cannot connect with that, (unlikely) you may have to select WPA-PSK + WPA2-PSK (mixed mode).