[SOLVED] Unsure of what the problem may be

[alzakiel]

Hello Everyone!

For quite a few months i've seen many problem arise with what i believe the problem to be the rooter. It will work entirely fine for 2 weeks if not more like it did till now for the last 16 days. But then all a sudden i would loose connection to the internet multiple times in a row for a varying amount of time.

It kinda look like this

------------------
Jan 29 11:16:23 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:16:13 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:16:04 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:15:54 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:15:43 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:15:33 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:15:23 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:15:13 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:15:03 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:14:54 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:14:43 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:14:33 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:14:23 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:14:13 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:14:03 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:13:54 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:13:44 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:13:33 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:13:23 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:13:10 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:13:00 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:12:50 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:12:41 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:12:30 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:12:20 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:12:10 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:12:00 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:11:50 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:11:41 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:11:31 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:11:26 info * RIPD start
Jan 29 11:11:24 info compile time options: IPv6 GNU-getopt no-ISC-leasefile no-DBus no-I18N no-TFTP
Jan 29 11:11:24 info started, version 2.41 cachesize 150
Jan 29 11:11:22 info exiting on receipt of SIGTERM
Jan 29 11:11:20 info Lease of ..100.20 obtained, lease time 20
Jan 29 11:11:20 info Sending discover...
Jan 29 11:11:02 info Sending discover...
Jan 29 11:11:00 info Sending discover...
Jan 29 11:10:58 info Sending discover...
Jan 29 11:10:54 info DHCP Release WAN IP address = 0.0.0.0
Jan 29 11:10:54 info Unicasting a release of ...171 to ...85
Jan 29 11:10:28 notice Blocked incoming TCP SynAck packet from ...17:443 to ...171:54527 with unexpected sequence
Jan 29 11:09:44 info * RIPD start
Jan 29 11:09:43 info using nameserver ..**.16#53
Jan 29 11:09:43 info using nameserver ..**.17#53
Jan 29 11:09:43 info using nameserver ..**.13#53
Jan 29 11:09:43 info compile time options: IPv6 GNU-getopt no-ISC-leasefile no-DBus no-I18N no-TFTP
Jan 29 11:09:43 info started, version 2.41 cachesize 150
Jan 29 11:09:41 info exiting on receipt of SIGTERM
Jan 29 11:09:41 info using nameserver ..**.16#53
Jan 29 11:09:41 info using nameserver ..**.17#53
Jan 29 11:09:41 info using nameserver ..**.13#53
Jan 29 11:09:39 info Lease of ..**.171 obtained, lease time 83716
Jan 29 11:09:39 info Sending discover...
Jan 29 11:09:18 info Lease of ..**.20 obtained, lease time 20
Jan 29 11:09:08 info Lease of ..**.20 obtained, lease time 20
Jan 29 11:08:58 info Lease of ..**.20 obtained, lease time 20
Jan 29 11:08:53 info * RIPD start
Jan 29 11:08:51 info compile time options: IPv6 GNU-getopt no-ISC-leasefile no-DBus no-I18N no-TFTP
Jan 29 11:08:51 info started, version 2.41 cachesize 150
Jan 29 11:08:49 info exiting on receipt of SIGTERM
Jan 29 11:08:48 info Lease of .100.20 obtained, lease time 20
Jan 29 11:08:48 info Sending discover...
Jan 29 11:08:30 info Sending discover...
Jan 29 11:08:28 info Sending discover...
Jan 29 11:08:26 info Sending discover...
Jan 29 11:08:20 info DHCP Release WAN IP address = 0.0.0.0
Jan 29 11:08:20 info Unicasting a release of ...171 to ...85
Jan 29 11:03:48 notice Blocked incoming TCP SynAck packet from ...169:443 to ...171:54442 with unexpected sequence
Jan 29 10:33:09 notice Blocked incoming TCP SynAck packet from ...56:443 to ...171:54302 with unexpected sequence
Jan 29 10:29:19 notice Blocked incoming TCP SynAck packet from ...82:80 to ...171:49149 with unexpected sequence
Jan 29 10:23:00 info using nameserver ..**.16#53
Jan 29 10:23:00 info using nameserver ..**.17#53
Jan 29 10:23:00 info using nameserver ..**.13#53
Jan 29 10:22:58 info Lease of ..**.171 obtained, lease time 86400
Jan 29 10:13:00 notice Blocked incoming TCP SynAck packet from ...220:443 to ...171:54132 with unexpected sequence
Jan 29 09:42:38 notice Blocked incoming TCP SynAck packet from ...222:443 to ...171:53972 with unexpected sequence
Jan 29 09:32:28 notice Blocked incoming TCP SynAck packet from ...220:443 to ...171:53907 with unexpected sequence
Jan 29 09:02:11 notice Blocked incoming TCP SynAck packet from ...219:443 to ...171:53755 with unexpected sequence
Jan 29 08:52:03 notice Blocked incoming TCP SynAck packet from ...185:443 to ...171:53713 with unexpected sequence
Jan 29 08:29:20 notice Blocked incoming TCP SynAck packet from ...121:80 to ...171:60379 with unexpected sequence
Jan 29 08:29:19 notice Blocked incoming TCP SynAck packet from ...82:80 to ...171:47913 with unexpected sequence
Jan 29 07:29:19 notice Blocked incoming TCP SynAck packet from...121:80 to ...171:50872 with unexpected sequence
------------------

And this is one of the logs i saved. I do not own the rooter and hence i don't have access to anything else. But i am beginning to wonder if i should ask my renter if we should probably get a new one ? It's an old Linksys DIR-825 dating from 2012. But unless i know if it's dying or not, i doubt she will buy a new one.

Hence i decided to ask some question about what the hell is going to cause this problem every now and then where the rooter seem to be restarting itself constantly for a while. Im more than at ease when it come to building PC, but when it come to networking im at a lost.

Thanks for you time!

 

[bill001g]

Could be a issue with the internet connection. It appears to be having some issue obtaining a IP address from the ISP. The router is not actually restarting but the either the connection is dropping or it is having a issue sending traffic over the connection. This could be a router issue but it could also be a circuit issue. If there is a modem in front of this maybe you can see if that also has logs.

You could call the ISP and maybe get lucky and they have some log. Most times they just test and say its working fine now because the bug or whatever did not happen at that instance. All depends if the person you talk to know how to get to the logs. Things like cable modems send the same messages you see to the ISP, DSL connections they should get messages from the device on their end of the circuit.

 

[alzakiel]

Anyway to confirm if the modem is connected to the rooter via the linksys setting page accessed by the network ip ? Or do i need access to the modem to do this ? If i have to i'll ask my renter if i can get access to it and check if there is any logs.

Otherwise yeah, i'll have to ask her to call Vidéotron to see if they can come and check this up. But like you said, if the problem isn't happening when they come, they'll probably do nothing lol. Which is kinda annoying.

I had the admin password before. But it might have been changed or resetted because the password my renter had given me doesn't work anymore. So i can't really do much outside looking at some logs.

 

[bill001g]

They don't actually have to come out they can check it from their side of the connection.

It depends on the modem you can try 192.168.100.1 there generally is no userid or password. This works for arris and a number of other cable modems. Sometime thought the router does not allow it to pass through. There are other brands of cable modems and they may use different ip addresses.

This assumes you have a cable tv connection things like fiber or dsl the modem work differently.

 

[alzakiel]

Well i have access to this. Otherwise not much i can do over here since the password isn't working anymore. This is where i took my logs.

 

[bill001g]

Pretty standard router status screen, does not tell much from what I can tell. It is very blurry and written in french which us americans have no clue about.

 

[alzakiel]

Haha yeah my bad about the french. I totally forgot to switch it to english (Yeah i just realised you could switch between french and english on the login screen).

But yeah overall it's just IP adress, mac adress, subnet mask, wireless and connected devices to the network. With all the sections for logs/stats/internet session and ect on the left.