Well I seem to be having major problems with my connection and its driving me up the wall.
Ever since having the BB put in to this address it seems the longest connection time without dropping is about 10 hours.
Wondering if there is something wrong at my end, ID Net end or BT end.
Anyway thats enough of the rant now on to the specifics.
Tonight has been terrible and so far I have had 14 disconnects in the last 30 minutes.
I am using a Belkin N1 high performance router - seems to be fairly comprehensive.
But from the security logs I have recovered the following:
Jul 10 21:10:39 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 64.233.177.99 attempting to remotely manage the Router 155
Jul 10 21:10:40 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 64.233.177.99 attempting to remotely manage the Router 155
Jul 10 21:10:42 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 64.233.177.99 attempting to remotely manage the Router 155
Jul 10 21:10:46 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 64.233.177.99 attempting to remotely manage the Router 155
Jul 10 21:10:54 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 64.233.177.99 attempting to remotely manage the Router 155
Jul 10 21:19:02 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 212.135.93.136 attempting to remotely manage the Router 156
Jul 10 21:19:03 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 212.135.93.136 attempting to remotely manage the Router 156
Jul 10 21:19:04 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 212.135.93.136 attempting to remotely manage the Router 156
Jul 10 21:23:39 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 60.172.220.10 116
Jul 10 21:23:39 (none) user.alert kernel: SYNFLOODIN=ppp_0_38_1 OUT= MAC= attack detected from 60.172.220.10 114
Jul 10 21:23:39 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 60.172.220.10 attempting to remotely manage the Router 155
Jul 10 21:25:01 (none) user.alert kernel: LANDATTACKIN=ppp_0_38_1 OUT= MAC= attack detected from 219.148.119.2 116
Jul 10 21:25:01 (none) user.alert kernel: SYNFLOODIN=ppp_0_38_1 OUT= MAC= attack detected from 219.148.119.2 114
Jul 10 21:25:01 (none) user.alert kernel: RemoteAccess: IN=ppp_0_38_1 OUT= MAC= RemoteAccess : 219.148.119.2 attempting to remotely manage the Router 155
I imagine that this is not helping the situation but is it the root cause? If it is how do I go about fixing the problem? I have ran full scans (virus/malware) using 3 different programs (zonealarm pro / ad aware / spybot) and the PC is clean.
On the router homepage it gives the following information:
ADSL
Type Interleave
Status No Defect
Downstream Upstream
Date rate(Kbps)
5632 448
Noise margin (dB)
15.8 28.0
Output power (dBm)
19.8 11.9
Attenuation (dB)
29.0 16.5
I am getting to my wits end as I am trying to do some work but with the connection dropping I do not know what I can do.
Any help would be very much appreciated.
Kind Regards,
Matt
Hi Matt, welcome to the forum.
Quote from: MattBHC on Jul 10, 2007, 21:29:52
Wondering if there is something wrong at my end, ID Net end or BT end.
Well, that's three ends! Joking aside, your problem is due to either the BT wiring from your exchange to your house (owned by BT), or the wiring within your own house.
Quote from: MattBHC on Jul 10, 2007, 21:29:52
Noise margin (dB)
15.8 28.0
The 15.8db figure here is a clue. The default target figure, set by BT, is 6db. However, if BT's equipment detect a series of faults/disconnects the target noise margin will rise in 3db steps. This is what has happened here and I would guess that your target has been increased to either 15db or 18db.
The first thing I recommend you do is read through the part of the FAQ here (http://www.idnetters.co.uk/forums/index.php/topic,1904.msg31528.html#msg31528). Note where it says everything connected to a phone socket must do so through a filter, this means everything. Absolutely no exceptions! It does sound like you could have a dodgy filter, so try swapping these about as one of the first things you do.
Once you have gone through that, feel free to post further questions and to ask for more help and clarification!
Hope this helps,
Lance
Hi Matt and welcome to Idnetters,
The router log is showing the dross that bounces around the Net,
64.233.177.99 is a Google .com bot
212.135.93.136 is an IP from Newnet (UK)
60.172.220.10 is China net
219.148.119.2 is also China net.
I would think the last 3 are worm activity that your router is seeing as an attack rather than 3 seperate hacker attacks.
the connection dropping I think will be due to high noise/interference on the line,you have interleaving on and the down stream snr is raised.
Do the checks that Lance suggests and post back.