LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
Reload this Page Router Crashing every 15 minutes
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 07-18-2005, 03:56 PM   #1
djgenesis
LQ Newbie
 
Registered: Jul 2005
Location: UK
Distribution: Ubuntu Hoary Hedgehog.
Posts: 18

Rep: Reputation: 0
Router Crashing every 15 minutes

Hello all, although this is my first post i'll skip the intro cause it might be considered boring. Let me just say that i am
glad i am part of this community and i appreciate those who, in times of trouble, give me a hand to think clearer.

I am running Fedora Core 3 and i am sharing a cable internet connection from telewest broadband.
Recently i bought a wireless router from AHAtpe modelnumber: AT-WBR402G
It is running SecureSOHO


I had problems setting it up but i finaly did it and managed to get an IP issued from the DHCP.
Buyt the problem i am facing now is that it keeps crashing after 15 minutes.
The first day i set it up , it was fine and remained fine for a couple of days. But now after ~15 minutes of operation, it
just hungs. The LAN seems to be working ok but i can't ping 192.168.1.254 which is the IP of the router. I lose internet
connectivity and the routers webpage is not loading. This only happens when the router is connected on the Internet.When its
running without the cable modem, it does not cause any problems and runs for ages!

I reset it to factory settings but still no luck.
I am trying to find a firmware update for it but the manufacturers website is crap. (redsonic.com)
I googled for SecureSOHO but i don't seem to find any info of updates. From the system log I found a piece of software it is
running but i can't inderstand if i need to upgrade it.

Here is the syslog when the router is running only on LAN after restoring factory settings

Code:
Jan 1 00:00:14 Router daemon.info dhcpd:
 
Jan 1 00:00:14 Router daemon.info dhcpd:
  Please contribute if you find this software useful.
Jan 1 00:00:14 Router daemon.info dhcpd:
  For info, please visit h**p://***.isc.org/dhcp-contrib.html
Jan 1 00:00:14 Router daemon.info dhcpd:
 
Jan 1 00:00:14 Router daemon.info dhcpd:
  Listening on LPF/br0/00:0a:e9:09:ec:46/192.168.1.0
Jan 1 00:00:14 Router daemon.info dhcpd:
  Sending on LPF/br0/00:0a:e9:09:ec:46/192.168.1.0
Jan 1 00:00:14 Router daemon.info dhcpd:
  Sending on Socket/fallback/fallback-net
Jan 1 00:00:14 Router user.notice ONSOFTWARE:
  : dhcp: LAN DHCPd Started
Jan 1 00:00:18 Router daemon.info dhcpd:
  DHCPREQUEST for 192.168.1.1 from 00:50:fc:51:43:50 via br0
Jan 1 00:00:18 Router daemon.info dhcpd:
  DHCPACK on 192.168.1.1 to 00:50:fc:51:43:50 via br0
Jan 1 00:00:18 Router daemon.info dhcpd:
  DHCPREQUEST for 192.168.1.3 from 00:10:b5:0f:92:78 via br0
Jan 1 00:00:18 Router daemon.info dhcpd:
  DHCPACK on 192.168.1.3 to 00:10:b5:0f:92:78 via br0
Jan 1 00:00:19 Router daemon.info dhcpd:
  DHCPREQUEST for 192.168.1.2 from 00:10:dc:63:fe:d5 via br0
Jan 1 00:00:19 Router daemon.info dhcpd:
  DHCPACK on 192.168.1.2 to 00:10:dc:63:fe:d5 via br0
Jan 1 08:00:20 Router daemon.info klogd:
  br0: port 2(eth0) entering learning state
Jan 1 08:00:20 Router daemon.info klogd:
  br0: port 1(wlan0) entering learning state
Jan 1 08:00:35 Router daemon.info klogd:
  br0: port 2(eth0) entering forwarding state
Jan 1 08:00:35 Router daemon.info klogd:
  br0: topology change detected, propagating
Jan 1 08:00:35 Router daemon.info klogd:
  br0: port 1(wlan0) entering forwarding state
Jan 1 08:00:35 Router daemon.info klogd:
  br0: topology change detected, propagating
Jan 1 00:00:36 Router daemon.info dnsmasq[212]:
  reading /var/state/dhcpd.leases



This is what the system log has after the restart from the crash (Note the time settings have been lost :S)


Code:
Jan 1 01:01:11 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=220.189.251.10 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=105 ID=38862 DF PROTO=TCP SPT=61469 DPT=10154 WINDOW=65535 RES=0x00 SYN URGP=0
Jan 1 01:01:11 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=68.83.185.242 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=112 ID=39375 DF PROTO=TCP SPT=4413 DPT=10154 WINDOW=65535 RES=0x00 SYN URGP=0
Jan 1 01:01:11 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=68.83.185.242 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=112 ID=39375 DF PROTO=TCP SPT=4413 DPT=10154 WINDOW=65535 RES=0x00 SYN URGP=0
Jan 1 01:01:12 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=212.122.120.118 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=116 ID=11846 DF PROTO=TCP SPT=2104 DPT=9172 WINDOW=16384 RES=0x00 SYN URGP=0
Jan 1 01:01:12 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=212.122.120.118 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=116 ID=11846 DF PROTO=TCP SPT=2104 DPT=9172 WINDOW=16384 RES=0x00 SYN URGP=0
Jan 1 01:01:12 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=220.189.251.10 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=105 ID=38886 DF PROTO=TCP SPT=61469 DPT=10154 WINDOW=65535 RES=0x00 SYN URGP=0
Jan 1 01:01:12 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=220.189.251.10 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=105 ID=38886 DF PROTO=TCP SPT=61469 DPT=10154 WINDOW=65535 RES=0x00 SYN URGP=0
Jan 1 01:01:14 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=212.122.120.118 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=116 ID=11906 DF PROTO=TCP SPT=2104 DPT=9172 WINDOW=16384 RES=0x00 SYN URGP=0
Jan 1 01:01:14 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=212.122.120.118 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=116 ID=11906 DF PROTO=TCP SPT=2104 DPT=9172 WINDOW=16384 RES=0x00 SYN URGP=0
Jan 1 01:01:16 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=212.122.120.118 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=116 ID=11972 DF PROTO=TCP SPT=2104 DPT=9172 WINDOW=16384 RES=0x00 SYN URGP=0
Jan 1 01:01:16 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=212.122.120.118 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=116 ID=11972 DF PROTO=TCP SPT=2104 DPT=9172 WINDOW=16384 RES=0x00 SYN URGP=0
Jan 1 01:01:21 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=200.83.117.217 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=115 ID=12557 DF PROTO=TCP SPT=4795 DPT=9172 WINDOW=64240 RES=0x00 SYN URGP=0
Jan 1 01:01:21 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=200.83.117.217 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=115 ID=12557 DF PROTO=TCP SPT=4795 DPT=9172 WINDOW=64240 RES=0x00 SYN URGP=0
Jan 1 01:01:22 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=200.83.117.217 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=115 ID=12608 DF PROTO=TCP SPT=4795 DPT=9172 WINDOW=64240 RES=0x00 SYN URGP=0
Jan 1 01:01:22 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=200.83.117.217 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=115 ID=12608 DF PROTO=TCP SPT=4795 DPT=9172 WINDOW=64240 RES=0x00 SYN URGP=0
Jan 1 01:01:24 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=200.83.117.217 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=115 ID=12666 DF PROTO=TCP SPT=4795 DPT=9172 WINDOW=64240 RES=0x00 SYN URGP=0
Jan 1 01:01:24 x1-6-00-65-74-68-2d-31 daemon.warn klogd:
  Invalid packet: IN=eth1 OUT= MAC=00:65:74:68:2d:31:00:0b:fc:43:e4:8d:08:00 SRC=200.83.117.217 DST=82.35.***.*** LEN=48 
TOS=0x00 PREC=0x00 TTL=115 ID=12666 DF PROTO=TCP SPT=4795 DPT=9172 WINDOW=64240 RES=0x00 SYN URGP=0

I am trying to find out whats wrong and i am breaking my head.

Can anybody help?

Thanks you guys.
Last edited by djgenesis; 07-18-2005 at 03:58 PM.
 
Old 07-18-2005, 04:45 PM   #2
demian
Member
 
Registered: Apr 2001
Location: Bremen, Germany
Distribution: Debian
Posts: 303

Rep: Reputation: 30
The messages you posted after the router crashes are just iptables log messages. Nothing wrong there. I wouldn't worry about this anyway: You said you recently bought it and it crashes every 15minutes. Take it back to the store and have them replace it.
 
Old 07-19-2005, 08:18 AM   #3
djgenesis
LQ Newbie
 
Registered: Jul 2005
Location: UK
Distribution: Ubuntu Hoary Hedgehog.
Posts: 18

Original Poster
Rep: Reputation: 0
I have installed another router but it does exactly the same
I was thinking that it might be the cable modem but it works fine and for hours when I connect it to a PC.

Could it be a buffer overflow from the routers side? If i set any strict firewall rules will that combat the problem at any level?
 
Old 07-19-2005, 10:42 AM   #4
demian
Member
 
Registered: Apr 2001
Location: Bremen, Germany
Distribution: Debian
Posts: 303

Rep: Reputation: 30
Hard to say what really causes this. Can you try and find the log messages just before the router crashes? Maybe connect through a serial console and tail the messages.
 
Old 07-19-2005, 10:45 AM   #5
slackhack
Senior Member
 
Registered: Jun 2004
Distribution: Arch, Debian, Slack
Posts: 1,016

Rep: Reputation: 47
bring it back and get a linksys.
 
Old 07-20-2005, 04:02 AM   #6
djgenesis
LQ Newbie
 
Registered: Jul 2005
Location: UK
Distribution: Ubuntu Hoary Hedgehog.
Posts: 18

Original Poster
Rep: Reputation: 0
I can't post the logs, everytime it crashes, it just resets and clears the logs. It is definatelly not hardware, everything else is working fine.
Does anyone know where to find the firmware upgrade?
 
Old 07-20-2005, 12:16 PM   #7
Kropotkin
Member
 
Registered: Oct 2004
Location: /usr/home
Distribution: Mint, Ubuntu server, FreeBSD, Android
Posts: 362

Rep: Reputation: 32
Like the other users have said, take it back, and get one from a reputable manufacturer.

I had a cheapo wireless router/DSL modem which crashed on average about once everything three days, the wireless component more often. After a couple of months, I finally ditched it and got a Linksys.
 
Old 07-20-2005, 12:35 PM   #8
demian
Member
 
Registered: Apr 2001
Location: Bremen, Germany
Distribution: Debian
Posts: 303

Rep: Reputation: 30
Quote:
Originally posted by djgenesis
I can't post the logs, everytime it crashes, it just resets and clears the logs.
That's why I suggested connecting via serial cable.
 
Old 07-21-2005, 04:31 AM   #9
djgenesis
LQ Newbie
 
Registered: Jul 2005
Location: UK
Distribution: Ubuntu Hoary Hedgehog.
Posts: 18

Original Poster
Rep: Reputation: 0
Quote:
That's why I suggested connecting via serial cable.
There is no serial cable connector on the router.

I guess you are right . I'm taking it back and i am getting one from a better company.
Thank you for all your help you guys.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Server looking up its own hostname every 2 minutes tunasashimi SUSE / openSUSE 8 07-04-2005 04:02 AM
HD not writeable after few minutes Cyber Maid Linux - Hardware 2 02-25-2005 05:33 PM
Crontab every 10 minutes Neorio Linux - General 1 11-18-2003 11:46 PM
9.2: Standby after five minutes! dominik81 Mandriva 2 11-13-2003 03:35 PM
Linux freezes after 10 minutes boots147 General 1 01-24-2002 04:26 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 08:00 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration