dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1211

kocheroni
join:2002-05-12

kocheroni

Member

My SMC7004VBR is having random "hangups"

I know that this could go in the SMC forum, but unfortunately not many people visit it and therefore I selected this one, because I'm thinking it could be an easy problem for someone to diagnose.

Right now I'm running, 1 on comp on win xp, 1 on 98, and 1 on 2000 to my SMC 7004VBR. Then, the forth port of the router is plugged into a befw11s4, however that is having no problems.

Recently, w/in the past day I should say, It has basically stopped detecting the WAN. Although the light is still lit up on both the router and the modem, I can not access anything outside of the router. At first I thought it might be random outages by my internet service provider, but when I would unplug just the router and replug it in and let both the router and modem sync, everything would come back to normal. Does anyone have a solution to this, or no one the potential problem might be? I recently did some more port forwarding to one computer, however I don't think that should be a problem for it.

cliff notes: My router loses the internet connection, although shows it as still active, unplugging and replugging power resyncs it.

pleekmo
Triptoe Through The Tulips
Premium Member
join:2001-09-14
Manchester, CT

pleekmo

Premium Member

I have also experienced these issues. I'm running an Efficient Networks Speedstream 5260 (5660) into it. I'd originally bought the Barracade because my SS had been experiencing that issue as well (loss of WAN connectivity) which I'd attributed to it being a "small memory" hacked router. But, looking over the threads here, it appears that SMC retail products seem to mostly be POS and unstable. There are several firmwares available if you want to try different firmwares. I have been able to find v1.0, v1.05b, v1.20 (European), v1.20a. If you are very good at searching through the forum you may be able to find the thread in which I show where to access all these firmwares.

Some people have had success with a particular firmware. Some have been able to relieve the problem by turning off the router's firewall. Some have been able to stabilize the unit by physically modifying it to include a heat sink over the main processor.

My suggestion would be to go out and buy some other router to replace the Barracade.

I'd recently found that perhaps a particular application had been causing my original issues with the Speedstream, but today I have found that perhaps I was not correct. Contemplating reverting to my setup of Internet > SS 5260 (5660) > SMC 7004VBR > 4 computers. That setup appears to be a bit more stable than the naked Speedstream still.

russr
join:2000-07-25
Hillsborough, NJ

russr to kocheroni

Member

to kocheroni
This might be a rather obvious question, but have you installed the latest firmware from SMC's website? If not, install the firmware and do a reset of the router.

EDIT: I had good stability with the latest one on SMC's US website. I didn't like the European firmware as much.
[text was edited by author 2003-02-03 01:09:15]

kocheroni
join:2002-05-12

kocheroni

Member

thankyou, yes i agree they are POS. I am definately not going to buy another SMC product again, because when you call up (you know your calling india right away), you ask them a question, and it's like yuy have to repeat it 4 times, very slowly for them to understand. Kinda sad for a company to outsource it's customer service like that so that people can't even communicate what the problem was. I told them forget about it and i'll just figure it out myself. I had done a firmware upgrade before it completely stopped working. So, i put in my linksys wireless router for right now, and then I'll put in the other one in a few minutes and try to get it going again (I like the 100 WAN/LAN ports).

russr
join:2000-07-25
Hillsborough, NJ

russr to kocheroni

Member

to kocheroni
Again what firmware did you upgrade to?

kocheroni
join:2002-05-12

kocheroni

Member

1.2, however the problem more lied w/in the fact that part of the time it was 192.168.2.1 i=dumb.

Honestly, i'm not sure what the problem was, however it could simply be something between the modem and router cause sometimes when you plug in a piece of hardware it has problems syncing. Everything has worked out and it's been up for half the day so far, and hopefully it'll be up for a long time like it was before.

russr
join:2000-07-25
Hillsborough, NJ

russr to kocheroni

Member

to kocheroni
As I said, the US firmware 1.20a is fairly stable.

kocheroni
join:2002-05-12

kocheroni

Member

hmm, happened again last night, but i had the old firmware, i'm not quite sure what i've been doing, i'll upgrade to the new stuff again today, it hink i had done something wrong.

pleekmo
Triptoe Through The Tulips
Premium Member
join:2001-09-14
Manchester, CT

pleekmo to kocheroni

Premium Member

to kocheroni

Re: A Possible Solution? (An Idea, At Least)

I did indeed revert back to my original setup (Internet > Speedstream > SMC > computers, rather than the naked Speedstream) and just about every half hour I'd lose connectivity. Then I had an idea...

Originally when I installed XP on this machine (leaving Win98SE on the other three), the XP machine could not "see" the other machines on my LAN. So I installed NetBEUI on the thing.

Well, I'd read somewhere that XP uses TCP/IP for all file transfers, LAN and WAN. So it would appear that NetBEUI was superfluous. So I uninstalled that protocol, feeling that perhaps it was causing some sort of conflict.

It seems to run fine now. I did have a spontaneous reboot about four hours later, but I think that might have been due to overheating. I use the area around my computer to emplace CD jewel cases, which end up covering the machine's side vents. Currently the machine has run fine for the past 25 hours.

One of the other things I did try was an XP TCP/IP reset, thinking that perhaps the issue was TCP/IP stack corruption. So if you are running other OSes, you may wish to check your networking protocols and uninstall the ones you don't need. And if that doesn't fix the "hangup" issue, perhaps uninstalling and reinstalling the remaining protocols may.

Of course, 25 hours is not a long test by any means, so take my words here with a grain of salt (or several, for that matter). I think I've had the Barracade stay connected for as long as three days, but generally it had hung up on me after less than a day. I'll try to keep you posted on how long it stays stable.

But I thought I'd post my current experiences in the hope that it may trigger some brainstorm among others and also perhaps in the interest of showing that we must look at all possibilities -- even ones that do not appear to be logical or sensible.

kocheroni
join:2002-05-12

kocheroni

Member

Re: My SMC7004VBR is having random "hangups"

Ok, here's what's happening...

This was never an issue until I started using emule, so I'm not sure if it has somethign to do with that or not. I have tried it on the new 1.20a firmware + the firmware that came with the router. I have port 4662 tcp and 4672 udp open for emule. Now, what tends to happen is the longer it runs, the slower this computer seems to get.

Last night I noticed ic ouldn't access buy.com on this computer (the one running emule w/ win xp), however on any other computer in the house I could. I woke up and it was still working fine, but when i came home 4 hours later, it wasn't working any more and no computer could access the internet. So with a simple restart, everything went back to the way it was, however it seems that every 24 hours or so, maybe al ittle longer, something causes the router to freeze. I can't access the WAN, and it doesn't even detect the LAN. Do you think this could be because of some type of packet traffic collisions or something w/ the emule program?
kocheroni

kocheroni

Member

well, as far as the barricade itself, i had it up and running for over 3 months I believe. I didn't have to reset it ever, and never had any problems, it's just been recent since i started using emule. I might not let it run tonight and see what happens, or not use it for the next couple days. If it happens to be emule, i'll check in the p2p forum waht their suggestion is.

pleekmo
Triptoe Through The Tulips
Premium Member
join:2001-09-14
Manchester, CT

pleekmo to kocheroni

Premium Member

to kocheroni
said by kocheroni:
This was never an issue until I started using emule, so I'm not sure if it has somethign to do with that or not.
Here's a couple little items from my Furthur bugfix report:

- Fixed bug that would eventually cause Furthur to use all available CPU
time.

- Fixed a large number of memory and resource leaks in various places. The biggest was a problem that was causing TCP sockets and 45K buffers to never be freed.


I would guess that possibly your e-mule TCP sockets might not be getting freed. Perhaps you ought to file a bug report with them.

P2P software apparently tends to use a large number of TCP sockets (take a look at your NAPT table) and perhaps ends up overwhelming the memory of routers. Perhaps router manufacturers ought to begin to install more memory into the things.
pleekmo

pleekmo to kocheroni

Premium Member

to kocheroni
Over 50 hours and counting. No LAN hangups yet.

However, I have run into a slight issue with the other computer. GetRight seems to be hanging up; I don't know if it's because it doesn't like the new Netscape 7 installation or because it doesn't like Proxomitron. Going to attempt re-install the software.

I suppose it's remotely possible that it's acting funny because I removed NetBEUI from the computer it's attempting to send data to.
kmaisel
Premium Member
join:2003-02-06
Colorado Springs, CO

kmaisel to kocheroni

Premium Member

to kocheroni
I too had the same hangup problems - it had to do with the router not being able to keep up with the DHCP changes from the ISP and passing it to the clients. Once I upgraded the firmware I have had no problems - the firmware documentation also mentioned that it fixed some DHCP problems.

pleekmo
Triptoe Through The Tulips
Premium Member
join:2001-09-14
Manchester, CT

pleekmo to kocheroni

Premium Member

to kocheroni

Re: My SMC7004VBR Is Still Truckin'

Over 75 hours and not a hiccup. I think I've found my own particular solution.

It would appear that some SMC 7004VBR difficulties are external in nature and not as intrinsic as one would believe.

kocheroni
join:2002-05-12

kocheroni

Member

Re: My SMC7004VBR is having random "hangups"

hi, sorry I didn't respond to this in a while. So this is the log from my router, it's obviously an emule problem and we are trying to diagnose it.

02/06/2003 23:20:42 **SYN Flood (per Min) Stop** ---->> --- (from WAN)
02/06/2003 23:20:42 **SYN Flood (per Min)** 207.5.201.17, 2429->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:42 **SYN Flood** 207.5.201.17, 2429->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:42 **SYN Flood (per Min)** 217.144.201.154, 61354->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:42 **SYN Flood** 217.144.201.154, 61354->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:42 **SYN Flood (per Min)** 212.208.241.225, 4629->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:42 **SYN Flood** 212.208.241.225, 4629->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 80.48.242.8, 1671->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 80.48.242.8, 1671->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 212.17.118.40, 3496->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 212.17.118.40, 3496->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 24.150.87.181, 4024->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 24.150.87.181, 4024->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 12.208.8.42, 11923->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 12.208.8.42, 11923->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 217.84.144.193, 2140->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 217.84.144.193, 2140->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 81.218.82.91, 4849->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 81.218.82.91, 4849->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 80.222.3.179, 2429->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 80.222.3.179, 2429->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 212.244.84.189, 4541->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 212.244.84.189, 4541->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 217.233.112.137, 4036->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 217.233.112.137, 4036->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 213.168.123.22, 2874->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 213.168.123.22, 2874->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 80.28.26.107, 4416->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 80.28.26.107, 4416->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 218.76.28.160, 2178->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 218.76.28.160, 2178->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 80.161.140.59, 2405->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 80.161.140.59, 2405->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 62.212.100.191, 60135->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 62.212.100.191, 60135->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 80.186.28.254, 1875->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 80.186.28.254, 1875->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 195.215.188.50, 4243->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 195.215.188.50, 4243->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 172.177.176.34, 3342->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 172.177.176.34, 3342->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 65.97.15.151, 3941->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 65.97.15.151, 3941->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 80.28.4.20, 1100->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 80.28.4.20, 1100->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 212.185.224.234, 62831->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 212.185.224.234, 62831->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 61.179.112.103, 4792->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 61.179.112.103, 4792->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood (per Min)** 213.60.128.10, 3620->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:41 **SYN Flood** 213.60.128.10, 3620->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 80.135.174.54, 2213->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 80.135.174.54, 2213->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 217.35.14.174, 2135->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 217.35.14.174, 2135->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 81.49.36.198, 2612->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 81.49.36.198, 2612->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 62.233.226.254, 61845->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 62.233.226.254, 61845->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 193.253.229.18, 1160->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 193.253.229.18, 1160->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 62.16.199.37, 4163->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 62.16.199.37, 4163->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 213.25.122.230, 3472->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 213.25.122.230, 3472->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 62.179.14.10, 3380->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 62.179.14.10, 3380->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 217.133.222.177, 3398->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 217.133.222.177, 3398->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 81.48.132.146, 4131->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 81.48.132.146, 4131->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 68.98.148.149, 2916->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 68.98.148.149, 2916->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 80.36.118.224, 3520->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 80.36.118.224, 3520->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 62.254.54.17, 2836->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 62.254.54.17, 2836->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 193.140.143.161, 2192->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 193.140.143.161, 2192->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 81.7.127.81, 3824->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 81.7.127.81, 3824->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 194.27.153.2, 21184->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 194.27.153.2, 21184->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 213.143.79.146, 2944->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 213.143.79.146, 2944->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 139.30.43.236, 2678->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 139.30.43.236, 2678->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 12.247.177.63, 1340->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 12.247.177.63, 1340->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 80.224.182.164, 1460->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 80.224.182.164, 1460->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 194.224.226.175, 20418->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 194.224.226.175, 20418->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 213.250.68.57, 27786->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 213.250.68.57, 27786->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood (per Min)** 81.218.82.91, 4849->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:40 **SYN Flood** 81.218.82.91, 4849->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 80.131.45.130, 2157->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 80.131.45.130, 2157->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 80.199.6.101, 1197->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 80.199.6.101, 1197->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 61.216.76.25, 4225->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 61.216.76.25, 4225->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 80.238.45.150, 4556->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 80.238.45.150, 4556->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 80.203.16.138, 24456->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 80.203.16.138, 24456->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 217.84.144.193, 2140->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 217.84.144.193, 2140->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 217.238.123.247, 3603->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 217.238.123.247, 3603->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 172.197.70.179, 4369->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 172.197.70.179, 4369->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 213.93.179.196, 1137->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 213.93.179.196, 1137->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 62.61.133.59, 2042->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 62.61.133.59, 2042->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 80.141.72.90, 3018->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 80.141.72.90, 3018->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 81.56.102.102, 1984->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 81.56.102.102, 1984->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 217.232.28.72, 45998->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 217.232.28.72, 45998->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 81.51.124.242, 2694->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 81.51.124.242, 2694->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 80.28.26.107, 4416->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 80.28.26.107, 4416->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 217.172.246.176, 3020->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 217.172.246.176, 3020->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 80.132.100.179, 16355->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 80.132.100.179, 16355->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 212.62.89.189, 62995->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 212.62.89.189, 62995->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 67.80.98.216, 3572->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 67.80.98.216, 3572->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 217.96.143.221, 4571->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 217.96.143.221, 4571->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 212.194.152.205, 4618->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 212.194.152.205, 4618->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 80.110.160.249, 2976->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 80.110.160.249, 2976->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 80.4.199.95, 4570->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 80.4.199.95, 4570->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood (per Min)** 153.19.108.37, 59787->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:39 **SYN Flood** 153.19.108.37, 59787->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:38 **SYN Flood (per Min)** 213.67.4.48, 3126->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:38 **SYN Flood** 213.67.4.48, 3126->> 192.168.1.101, 4662 (from WAN)
02/06/2003 23:20:38 **SYN Flood (per Min)** 24.42.41.55, 3158->> 192.168.1.101, 4662 (from WAN)

obviously I'm 192.168.1.101 and 4662 is the emule port. The only thing I can figure out is that there are too many requests. I might need to forward ports or something. It's been fien over night and I'm sure it'll remain working since I'm not running emule right now.

Mem
join:2002-01-03
Nashville, TN

Mem

Member

Your problem may be with the firewall settings - is it enabled while you are getting the SYN Flood messages?
[text was edited by author 2003-02-07 07:44:54]

pleekmo
Triptoe Through The Tulips
Premium Member
join:2001-09-14
Manchester, CT

pleekmo

Premium Member

said by Mem:
Your problem may be with the firewall settings - is it enabled while you are getting the SYN Flood messages?
D---, you know, you've just pointed out to me that I've neglected to mention that I currently have my router firewall turned off. It's still going strong after nearly 83 hours.

Mem
join:2002-01-03
Nashville, TN
·Google Fiber
·AT&T FTTP

Mem

Member

I've been concerned about the small amount of memory in the SMC routers. About 1/8 or less than the quantity I have in my business class ones. With so many port openings required for P2P, I suspect that may be a problem.

The firewall looks at TCP/UDP sessions to see if a DDoS attack is occuring and tries to make decisions as to what to do. If the firewall is enabled, one setting that needs to be changed from default is the Maximum incomplete TCP/UDP sessions number from the same host. If browsing, email, etc. it should be changed from the default of 10 to 30. With P2P programs, it may need to be set even higher, say to 50 or so (I think it depends on the application). The SYN flood messages in the router log will show up if this setting needs to be higher (of course they could be a real probe so don't set it higher just because these happen once in a while).

There may be other settings that need some changes based on your applications. I don't use P2P (sounds like I'm in the stoneage, huh?) so I haven't had the chance to test that type of configuration.

pleekmo
Triptoe Through The Tulips
Premium Member
join:2001-09-14
Manchester, CT

pleekmo

Premium Member

Mem, thanks for the information. It may come in handy soon.

I have had the router's firewall turned off for some time now since reading in this forum about the instability having it on results in. However, the next time I need to reboot my main machine or when I drop my connection (whenever that may be...) I'll perhaps test out the firewall just to see what happens.

I do use P2P, though not the usual ones: Furthur and BitTorrent. I download lots of Grateful Dead shows in shorten format (perhaps a hundred a month), which is why those two in particular are being used. (Shorten is a lossless audio compression format; unlike mp3, in which 90% of the audio data is thrown away.)

kocheroni
join:2002-05-12

kocheroni

Member

I appreciate that, I believe this to be the problem also and am going to try to go w/o the firewall on and see how it works out.

pleekmo
Triptoe Through The Tulips
Premium Member
join:2001-09-14
Manchester, CT

pleekmo to kocheroni

Premium Member

to kocheroni
Still truckin' along after nearly 100 hours (over 4.5 days). Again, this is with the router's firewall turned off. Of course, I have a software firewall installed on my computers.