'Link Down' - what is it?

On Oct 8th, by ADSL stopped working. Looked at the router info and it said 'Link down': not something I've seen before. There was no information at all showing for the usual stats.
Normally, the 'disconnect' button has changed to 'connect' if it's gone down for some reason.
Then I saw that in the log, it wasn't trying to reconnect at all. Info stopped after it reported the loss of connection.
It was a fine, sunny day.

After an hour, I called my ISP and they could find no reason for it, nor were there any BT faults reported. I was told to call back if it wasn't back up in 2 hours.
It came back up almost two hours later.

Today, the very same thing happened at 3.30pm - 'link down' and the log showing no attempts to reconnect.
It came back up at 5.30.
Again, at the time it was a fine sunny day. (Changed at 7pm though)

I've had higher down noise margins since some thundery weather at the end of August caused it to disconnect briefly, and despite those two 'link down' episodes this month, it's still high today: 9.3down 6.0up
This is how it looks now (we have a thunderstorm just moving away):
Operational Mode ADSL2+
Upstream 1136
Downstream 8480
SNR Margin(Upstream) 6.1
SNR Margin(Downstream) 6.1
Line Attenuation(Upstream) 27.0
Line Attenuation(Downstream) 46.5

If your router isn't trying to auto reconnect, the first thing I'd suggest you do is swap it out.

Link down usually refers to there being no AdSL link.

Modem is seeing no response to the initial are there calls to the exchange, hence no sync speeds.

You say that whilst the link was down you called your ISP- was this using the same line that the modem is connected to?

Just to confirm that the line to the exchange hadn't suffered some sort of fault.

Thanks Zarjaz - On both occasions, the router (7800n) reconnected fine once whatever the problem was had cleared. System up remained, just the ADSL was showing 'Link down'.
Just as on the 8th, after some hours, it briefly lost adsl at around 1.34am last night but I didn't even notice it.

'course, it could have been the other end of things. When it was down, was whichever light indicates sync on the router, blinking mournfully ?

Thanks Mr Saffron - these two incidents aren't something I've noticed before. Normally if it goes down, the router button changes from 'Disconnect' to 'Connect' and the log shows it trying to reconnect by itself.

Thanks Bill - yes, the same line. Phone working perfectly and no noise on the line.

No BT fault showed up on the lists either.
My connection is usually quite stable and ISP tech could see no reaon for it being down.

Perhaps a fault somewhere on the ISP's equipment?

Yes, all lights were on but the 'internet' one was indeed blinking rather sadly.

Hmm, so since the router seemed to be telling you it couldn't find anything to talk too, I still say it's your router or the CP's port in the exchange. One is going to be a lot easier to rule out than the other.

If it happens again, I'll copy the log to see if it shows anything unusual or points to the source of the problem.

I don't have a spare router apart from an old Netgear one that developed a fault and caused problems. The Billion is 22 months old, but I do realise they can develop a fault at any time.

In reply to a post by TrishaH:

Yes, all lights were on but the 'internet' one was indeed blinking rather sadly.

It's a while since I used a combined modem/router (separate on FTTC), but iirc that usually meant that you'd got sync to the exchange but not authorisation to your ISP.

OTOH, in your OP you said there were no stats available, which would imply no sync.

I'm inclined to agree with Zarjaz and suspect the router.


edit- I see you don't have a spare... bad move

Edited by billford (Sun 20-Oct-13 12:11:11)

True, there weren't any stats there at all ..just 'link down' in each space.

If I did get a new router, would it be best to stick with the 7800n? - is has been very good on what used to be an awful connection, and I find it easy to use too.

It lives under my desk, so although I do like smart things with pretty lights, I'd hardly ever notice it really.

In those cases suspect it is seeing some hardware at the other end and starts negotiating sync speed and then the authentication

I've had that with routers: a blinking "internet" light can be a indication of an ISP pinging the router, red internet light = PPP link down, and no internet light can mean the router has given up trying to connect, especially if one intervenes and attempts to manually connect from the GUI. Fortunately, as you say, changing to a different router usually cures the later problem

In reply to a post by TrishaH:

If I did get a new router, would it be best to stick with the 7800n?

You'll probably get a different answer in each reply to that one

My feeling would be to say "yes", unless there's a good reason to switch to a different make.

It has the advantage that if it turns out that the current router is OK and the problem is at the exchange then you've got a spare identical router ready for when it does go wrong (which it will), if it is the router at fault then you use the new one and have a look around eBay for a cheap and cheerful <any brand> to use as a swap-out when in due course the new one goes wrong. Which it will

That's my approach to spares... others may differ.

I'd rather have it covered than have to go and buy whatever local stores had available in the event it died altogether.

I see that Billion have a newer model: 7800DXL
Reviews seem very good, and the only thing I see is this in one review:
There seem to be fewer options for the ADSL side of things compared to the 7800N, though I can't identify what's missing from memory
Seeing I know very little about settings, I doubt this will be a problem for me.
As long as it's easy to set up, I should be OK

I use mine wired, but the 7800n wireless seems to work well for any registered visitors, and my notebook connects wirelessly too in another room. Can't say I've used the wireless much myself but I hear no complaints. I assume if I got the newer model it would work the same.

I still see no BT faults/repairs showing for my phone code, nor were there any on 8th when it happened before.
Looks like Zarjaz and yourself could be right about it being the router at fault.

So - 7800n or DXL. Any reason not to go with the newer model?

In reply to a post by TrishaH:

So - 7800n or DXL. Any reason not to go with the newer model?

I had a quick look at the spec for the DXL- most of the improvements seem to be wireless and cable (fibre) related, so could be viewed as overkill if you don't use wireless much and haven't got fibre, otoh it's not much dearer so yes, I'd suggest going for the newer one.

As for setting up- iirc Billions use a wizard to get you initially connected (given your login details), then you just have to sort out any twiddly bits you need. So that shouldn't be a problem.

In my opinion it's also marginally prettier than the 7800N but let's face it- that wouldn't be difficult

Thanks Bill - I appreciate you looking.

I originally got the 7800n because I intended going to fibre, but once I had a new master socket and then the 7800n, things had improved so much in those two steps, I had all I needed so didn't go to fibre.
I do still have the option should the need arise though.

I do agree, the 7800n is probably the ugliest of them all - quite shocked when I first saw it The new one does indeed look considerably better, if not nearly as snazzy as some others.
Quality of performance is more important to me than looks for something like this, so for not a huge lot more, the newer model is probably worth having.

I have screenshots of all my passwords etc, so shouldn't have a problem getting it working, especially with a wizard.

Thanks so much everyone for pointing me in what may likely be the right direction.

The Billion 7800DXL router arrived today.
I've never set one up totally by myself, but the install wizard seems good and I think I did it OK at least for the ADSL. A few things have slightly different terminology though.
There's a couple of things I'm not quite understanding yet, so may try the DSL Hardware section to see if anyone else has one.
So far so good - time will tell if it's solved the problem.

These are the stats from the new router after it had been up for 2.5hours - do they look OK. There's a lot more info under the first couple of paragraphs - more than there was on my 7800n, and I don't know if it's all pretty much alright:

xDSL
Bonding Line Selection line 0 line 1
Mode ADSL_2plus
Traffic Type ATM
Status Up
Link Power State L0

Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.8 6.0
Attenuation (dB) 44.5 26.1
Output Power (dBm) 0.0 12.5
Attainable Rate (Kbps) 9256 1176

Rate (Kbps) 8562 1168

MSGc (# of bytes in overhead channel message) 59 10
B (# of bytes in Mux Data Frame) 133 26
M (# of Mux Data Frames in FEC Data Frame) 1 8
T (Mux Data Frames over sync bytes) 2 6
R (# of check bytes in FEC Data Frame) 10 6
S (ratio of FEC over PMD Data Frame length) 0.4989 5.8807
L (# of bits in PMD Data Frame) 2309 302
D (interleaver depth) 64 4
Delay (msec) 8 6
INP (DMT symbol) 1.00 0.00

Super Frames 733340 663914
Super Frame Errors 76 73
RS Words 95334032 3790947
RS Correctable Errors 42005 508
RS Uncorrectable Errors 967 0

HEC Errors 539 52
OCD Errors 0 0
LCD Errors 0 0
Total Cells 240133847 32701723
Data Cells 797358 125515
Bit Errors 0 4895

Total ES 34 57
Total SES 0 0
Total UAS 50 50

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).

In reply to a post by David_W:

- but so long as unwanted traffic is not getting onto your network, you have nothing to fear.

I thought unwanted traffic was getting in! Thanks for the reassurance.

In reply to a post by TrishaH:

Do you know if this is what I can change to my own password?

That's the setting you're looking for.

Good- thanks

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.

Well, my key was less complex than that. Must think again!

WPS is disabled, and the setting currently for Network authentication is WPA2-PSK ...is it better to change this to just plain WPA2?
TKIP is the only one I can't find ..yet.

Thanks for the help.

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

But .....I'd never be able to get 63 characters written in that tiny space!

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).

Right! - I see both yourself and David advising WPA2 only so I'll give it a try in the morning. If WPA2 doesn't work, is the mixed selection better than how it currently is? ..had enough of poking around in it for today

In reply to a post by TrishaH:

In reply to a post by David_W:

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.

Well, my key was less complex than that. Must think again!

The password should also include numbers as well (my fault) - so 63 characters of random upper case, lower case, numbers and punctuation. There are web sites that will generate such a password using Javascript, so the actual key is generated locally in your browser. You can copy and paste the output into the router's configuration interface and into a text file to squirrel away. If you can get the text file onto the client device somehow, you can copy and paste your 63 characters into the wireless configuration screen - otherwise it's a a few minutes of discovering where all those weird symbols are on your phone or tablet's keyboard!

In reply to a post by TrishaH:

WPS is disabled, and the setting currently for Network authentication is WPA2-PSK ...is it better to change this to just plain WPA2?
TKIP is the only one I can't find ..yet.

The problem is that there's no standardisation for the names of the various settings in the various user interfaces.

WPA2-PSK is the one you want - WPA2 with a passphrase, sometimes called WPA2-Personal.

WPA2 will be WPA2 with RADIUS authentication, sometimes called WPA2-Enterprise. This is stronger than WPA2-Personal, but requires you to run a RADIUS server. If you have a local Linux / *BSD computer that is always on, that's a good choice - but installing and configuring FreeRADIUS is not for the faint hearted. (All the wireless here is WPA2-Enterprise, but I have some FreeBSD servers on site that I use to run FreeRADIUS).

A home RADIUS server would be an ideal job for a Raspberry Pi, if only someone would produce a nice web-driven user interface to the appropriate FreeRADIUS functionality. I'd do this myself, but there's already so much on my "to do" list.


Leave WPS disabled - you don't want that. Like many convenience features, it is a potential security hole.


What Bob and I are both driving at is that if all your devices have full support for WPA2, you can disable any fall-back support for WPA ("mixed mode", "WPA and WPA2" or similar) and its associated weak encryption (TKIP, which is the old and broken WEP encryption with dynamically changing keys to keep a little way ahead of the hackers).

Adopting the "if in doubt, check the manual" approach, you want "Network Authentication" set to "WPA2-PSK" (mixed mode is another option in that list) and "WPA/WAPI Encryption" set to "AES" for optimum security. Only use "Mixed WPA/WPA2-PSK" and/or "TKIP+AES" if you have a device that refuses to work on the optimum settings.


Don't forget to make the same changes to the 5GHz wireless as the 2.4GHz. I'd argue the best option is to operate both wireless bands using the exactly same settings, then devices can move from one radio to the other seamlessly. 5GHz is less congested and typically allows faster operation, but not every device supports 5GHz operation and the higher frequency 5GHz signal is rapidly attenuated by distance and building structure.

I'll give it a try in the morning ..had enough of poking around in it for today

Just been taking a look (woke with a migraine type thing today, so a bit slow).

This is how I've got the wireless set now - 5&2.4 GHz - underlined is actual setting used, brackets shows the options:

Wireless Security:
WPS Enable - Disable (Current: Disable)
Manual Setup AP:
Select SSID - Billion-AP-2.4g (Billion-Guest1-2.4g Billion-Guest2-2.4g Billion-Guest3-2.4g )
Network Authentication - WPA2 -PSK (Open Shared 802.1X WPA WPA-PSK WPA2 Mixed WPA2/WPA Mixed WPA2/WPA -PSK )
WPA/WAPI passphrase - Click here to display
WPA Group Rekey Interval - 3600 [0-2147483647)
WPA/WAPI Encryption - [u]AES (TKIP+AES)

I took screenshots of each 'page' on the old one, and apart from Network Authentication being WPA/WPA2-PSK on the old 'n' one, these 'DXL' settings are the same.

For the time being, I've used the same pass key. Eldest son set the wireless up on their phones and my notebook, so I'll leave it to him to sort out next time he's here.

Edited by deleted (Tue 22-Oct-13 15:24:57)

That looks good to me (I can see you attempted to mark "AES" in the encryption line - it's just the underline closing tag that's missing).

I hope it's working well now.

Thanks David - I really appreciate the help I've had from you all.

It seems fine. I did prefer being able to see the tick for wireless enabled and a padlock for the security being set (as shown on the old one), but if it looks good to you, I'm happy.
I'll get a better pass key sorted out soon.

As for the AES underline thing - I just tried to edit it twice and it just won't change!

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.

I did look at that too, and set it at 'Notice' hoping that would be the right one - it had been on 'Informational'. Not sure if the 'Mode' setting should be 'Both' instead of just 'Local' ?
Settings used are underlined, options in brackets:

Log
Configure Log:
Parameters
Log - Enable (Disable)
Log Level - Notice (Emergency, Alert, Critical, Error, Warning, Informational, Debugging )
Display Level - Notice (Emergency, Alert, Critical, Error, Warning, Informational, Debugging)
Mode - Local (Remote, Both)

This is what the log is showing right now (nothing since I switched the computer on this morning):
Oct 22 01:23:57 syslog emerg Router started: BusyBox v1.17.2
Oct 22 01:23:57 daemon notice kernel: klogd started: BusyBox v1.17.2 (2013-07-31 17:16:52 CST)
Oct 22 03:03:00 daemon crit kernel: eth3 (switch port: 1) Link DOWN.
Oct 22 03:03:03 daemon crit kernel: eth3 (switch port: 1) Link UP 10 mbps full duplex
Oct 22 10:58:42 daemon crit kernel: eth3 (switch port: 1) Link DOWN.
Oct 22 10:58:46 daemon crit kernel: eth3 (switch port: 1) Link UP 1000 mbps full duplex

It seems the option to configure the logs only applies to the standard one, and not the security log which is still showing intrusions (attempted intrusions I assume).

A setting of "Notice" sounds about right. It doesn't indicate where in the list it lives, I'd guess between "Warning" and "Error"?

In reply to a post by TrishaH:

Not sure if the 'Mode' setting should be 'Both' instead of just 'Local' ?

I would think that the "Mode" setting of Local means that it will only report possible problems within your own network- those eth3 messages indicate something going on with one of the Ethernet ports. (Probably nothing to worry about- it looks like a speed change, maybe a brief burst of interference from somewhere.)

If that's right, it won't report events on the link to the exchange, which is probably the more useful one! I don't think the "Local" setting would show loss of sync etc.

Try setting it to "Both" and see what it comes up with.

That's a nice set of logging options... my Asus, which is broadly the same class of router, gives me practically no useful options at all- it's about the only thing I dislike about it

A setting of "Notice" sounds about right. It doesn't indicate where in the list it lives, I'd guess between "Warning" and "Error"?

It's between 'Warning' & 'Informational'

I would think that the "Mode" setting of Local means that it will only report possible problems within your own network- those eth3 messages indicate something going on with one of the Ethernet ports. (Probably nothing to worry about- it looks like a speed change, maybe a brief burst of interference from somewhere.)

If that's right, it won't report events on the link to the exchange, which is probably the more useful one! I don't think the "Local" setting would show loss of sync etc.

Try setting it to "Both" and see what it comes up with.

Tried that - The config screen showed two more boxes when I'd selected 'Both', and I didn't know what to put in the 'Server IP Address':
Parameters
Log - Enable ( Disable )
Log Level - Notice (Emergency, Alert, Critical, Error, Warning, Informational, Debugging,)
Display Level -Notice (Emergency, Alert, Critical, Error, Warning, Informational, Debugging,)
Mode - Both (Local, Remote)
Server IP Address - that's showing 0.0.0.0 and it asks for correct IP address
Server UDP Port - that's showing 514

That's a nice set of logging options... my Asus, which is broadly the same class of router, gives me practically no useful options at all- it's about the only thing I dislike about it

I think you'd like this then ..seems to have lots of 'stuff' I haven't seen before! All serves to puzzle me, but for someone who knows what they're looking at, probably very useful.
With things like this, too much information means I have to start asking questions in case I'm seeing a problem

In reply to a post by TrishaH:

It's between 'Warning' & 'Informational'

OK, that should be fine. There isn't really a "correct" setting, it depends what you're doing- if you get too much in the log that's of no interest, move it up a notch .

The config screen showed two more boxes when I'd selected 'Both', and I didn't know what to put in the 'Server IP Address':

Right, that means it doesn't do what I thought it did- "Remote" means it will send logged events to another computer on the network, mine will do that. It can be useful at times, but it's unlikely you'll need it (I'm not even sure if Windows machines can handle it) so put it back to "Local".

I think you'd like this then ..seems to have lots of 'stuff' I haven't seen before!

Maybe... there's a couple of setup pages on mine that I leave severely alone

OK, that should be fine. There isn't really a "correct" setting, it depends what you're doing- if you get too much in the log that's of no interest, move it up a notch .

OK. Seems fine as it is ..I think

Right, that means it doesn't do what I thought it did- "Remote" means it will send logged events to another computer on the network, mine will do that. It can be useful at times, but it's unlikely you'll need it (I'm not even sure if Windows machines can handle it) so put it back to "Local".

OK - I'd thought it meant wireless events!

Maybe... there's a couple of setup pages on mine that I leave severely alone

I saw one yesterday that I decideed to ignore! It's in the Advanced part, and is a set of diagnostic pages:
Advanced Setup

Test the connection to your local network --- pppoa_0_0_38
Test LAN Connection ( P4/EWAN ) FAIL Help
Test LAN Connection ( P3 ) FAIL Help
Test LAN Connection ( P2 ) FAIL Help
Test LAN Connection ( P1 ) PASS Help
Test your Wireless Connection PASSPASS Help

Test the connection to your DSL service provider
Test ADSL Synchronization PASS Help
Test ATM OAM F5 segment ping FAIL Help
Test ATM OAM F5 end-to-end ping FAIL Help

Test the connection to your Internet service provider
Test PPP server session PASS Help
Test authentication with ISP PASS Help
Test the assigned IP address PASS Help
Ping default gateway PASS Help
Ping primary Domain Name Server PASS Help

The 'Fails' on the ATM sections give info that if you are connected to the internet, then it doesn't apply.

The ones on the LAN show this for the first P4/EWAN fail:

Ethernet Connection Test
Fail Indicates that the Broadband Router does not detect the Ethernet interface on your computer.
Follow the troubleshooting procedures listed below and rerun the diagnostics tests by clicking on the Rerun Diagnostic Tests button at the bottom of this page.

If all the tests pass, close and restart your Web browser to access the Internet.

Troubleshooting
If you are not able to access this page, verify that the Ethernet cable from your computer or your hub is connected to the LAN port on DSL Router. Reseat the cable by unplugging both ends and reconnecting them to their respective ports.

Turn off the Broadband Router, wait 10 seconds and turn it back ON.

Make sure you are using the Ethernet cable supplied with your DSL Router

With the router on, press the reset button on the Broadband Router for at least five seconds and release it. This resets the Broadband Router to its default settings. Wait for the Broadband Router to initialize, then close and restart your Web browser. To reconfigure the router, type your DSL Account username and password.

Don't think I could face doing all the re-starting and set up stuff again ..it seems to be working OK.
Not a section I'll be looking at with any fequency.

That looks like a very competent router... but I think I'll stick with the Asus- I like it and I've got to know it!

I can see one problem though:

Troubleshooting
If you are not able to access this page...

... how do you read the instructions?

..it seems to be working OK.

A very sound principle- if it ain't broke, don't fix it

That looks like a very competent router... but I think I'll stick with the Asus- I like it and I've got to know it!

Don't blame you - I liked the 7800n because I got used to it fairly quickly - expected a very similar interface with this one, so got a shock by all the additional stuff

I can see one problem though:

Troubleshooting
If you are not able to access this page...

... how do you read the instructions?

To tell the truth, I scanned through the paragraph, saw about re-entering everything and thought "Pass on that one then!"

A very sound principle- if it ain't broke, don't fix it

Yes, usually my thoughts with most things. (I still miss the last Gigabit phone we had - a few features were far better than the Panasonic we now have)

Son called in a few minutes ago, and when he got up off the floor after hearing I'd set up the router myself ...he tried his iPhone, re-entered the pass key, and there it was! Glad I got that one sorted ..I did tell him I'd had help understanding it properly though

The old router wasn't runing hot - more like moderately warm - but this one is just gently warm!
I saw in a review how someone uses a tablet stand for it to allow air underneath too.

By the way, Natoora have some quince. They're sold in 2's this year rather than by the Kg.

Hi ... just a thought & an other opinion (of course i can be wrong) ... if you still have disconnections can you try change the adsl filter just in case
How ever my opinion about the night time disconnections ... seems they doing some work at the dslam or exchange ... i had this at rear cases the time i was in UK (night time disconnections & my isp did not showed any fault at the area status) ... i bet after few days or very soon your disconnection issues will disappear (perhaps when they will finish working)

EDIT

if you know you can telnet at the modem and see the retrain reason because if someone knows the retrain codes can light up the reason of the disconnection

the command with the 7800 i do also have is "adsl info --stats" ... not sure if is the same with your new modem

example from my stats
> adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 1115 Kbps, Downstream rate = 15856 Kbps
Path: 0, Upstream rate = 1023 Kbps, Downstream rate = 13779 Kbps

Edited by deleted (Tue 22-Oct-13 19:37:27)

In reply to a post by TrishaH:

By the way, Natoora have some quince. They're sold in 2's this year rather than by the Kg.

That should confuse a few people reading this thread but thanks, I'll go take a look



later- ouch, not at that price... I'll have a look locally.

Edited by billford (Tue 22-Oct-13 20:05:58)

Thanks - the long disconnections were during the day on both occasions, and it was a total loss of the link, yet the system remained up.
ISP did tests and we changed the filter & tried the test socket too, plus there were no faults/outages on either occasion. Also, ISP has a page that shows all BT's current and planned work or faults, and none showed up for those days on my phone code.
Their tech said it could be the router as there was nothing else apparent.
The second time, the general opinion here was that it pointed to the router too, so for the time being, I'm hoping it was.

Time will tell I suppose

By the way, Natoora have some quince. They're sold in 2's this year rather than by the Kg.

That should confuse a few people reading this thread but thanks, I'll go take a look

True! ...not many routers run on quince juice these days

later- ouch, not at that price... I'll have a look locally.

Thought you'd say that!
I bought them for far less there when they sold them by the Kg. Could never find them anywhere else.

Got some lovely photographic reference with leaves/stalks attached from the dozen we grew this year. Plenty of reference for work in the coming year
Son will be making something with them as soon as they've ripened properly for a couple of weeks.
Sometimes, farmers markets get them, and it's usually around this time of year.

Perhaps a silly question, but with this new router, on the BQM I see one or two 'active'? periods of 2 hours during the night or early morning when the computer is off.

It's done this every night since I got it (almost 5 days), and I'm wondering what that is as I never got that with the old Billion router. It always showed a flat line right through until the computer was switched on again.

You mean that one between about 4:15 and 6? Strange.

Yes, and also the shorter one between 9.30 and 10.30am. The tallest spike just after that shorter one was (I assume) me turning the computer on.

I've had one or two of these spells each night/early morning since it was connected.
On 21st, it ws 4am-6am, and on the 25th approx 2am -4am plus approx 7.30-9.30am.
(I didn't make a note of the other days).

The log shows it as off from 2.20am until 10.59am this morning when I turned the computer on.

Update on that oddity on the BQM:
2 days ago, the computer engineer was poking around via TeamViewer and did a few bits of sorting out. I'd had two days of the system freezing up and shutting down, so they tried to isolate the problem.

It's been working fine since whatever he did, but in the process, he installed IE11 (I'd been using 9), and on the nights since, there has been no sign of any 'activity' showing on the BQM during the night when the computer is off.

Anyway, that new router is going back on Monday because the wireless was very poor, and I've bought another 7800n. Only just got it set up, so not yet sure if the wireless is working properly now.

I haven't re-read the whole thread, but you haven't got any smartphones or tablets connecting have you? Or outsiders?

I upgraded from Win 8 to 8.1 a couple of days ago. That automatically upped me from IE10 to IE11.

Last night I set up a new ASUS RT-N66U instead of the PlusNet 582n. Looking good so far.

It was a few posts back, on 26th Oct.
That new router was showing 1.2-2 hours of activity once or twice through the night, and after the IE upgrade, it stopped.

The wireless connection was secure. Sons both have iPhones, but neither were here at night, and I have a notebook but it was turned off completely.
None of them would hold the Wi-Fi connection on that router, hence it going back.

Irrelevant now though because it's back in it's box ready to go back on Monday.

The new 7800n seems OK so far! Hope your new Asus stays 'good'