Hi to everybody

First of all, excuse me for my low english level, becouse I'm still learning it

I've got one little problem with my linux system, using slackware 10.2

When the system has arround 3 or 6 uptime days (the quantitie of days allways change), it becomes not able to start new internet connections. It also keeps the currently activated connections (such an irc server connection), but it isn't able to connect to a news servers. It happens with Torrents, overnet network servers, Direct Connect hubbs, ftp servers... and even with http connections with an internet browser. For example, when I type on a console the next command:
lynx url (I still can't post urls on this forum)

I only get this message from lynx : "Making HTTP connection to url"

Anyway, when I make a ping to an url, I get a response of it and never loss a packet, so, it isn't a problem from the DNS server.

Months ago, I had the same problem on the same computer with slacware9, using a different 2.4.xx kernel.

I also have tried different network card, allways getting the same problem. I tried to rebood the router when that problem appeared, but nothing happened. Notwithstanding, I don't think that is the routers fault, because when I have this problems, it is only with this computer, so I can connect to internet without problems from other computer from my network (using windows xp), and not needing to reboot my router.

There is something weird. There seems to be a network problem, but I was surprised when I discovered that the computer is still running samba withouth problems, so I can see the shared folders from other computer. Also, I can connect to the computer with sshd sessions from other computer on the same network using putty.

When I reboot the system, the problem dissappears.

Does anyone has an idea?

Thank you very much to everybody

makinavaja

Hello,

I was surprised to find exactly the same problem as I suffer from being described here! I'm running a Slackware 10.2 as a NAT router, with latest kernel 2.4.32. And the problem is precisely the same - strange enough to sound but it is true! After some days of operation the router refuses to make new Internet connections - but which is curious not from all the machines that are behind the NAT, just let's say from 2-3 machines. At this moment, I can ping from those problematic machines any address with no problem, also I can open and browse the FTP site on the router itself successfully. And of course from the rest of the machines the Internet is working perfectly.

Please, somebody shed some light how to diagnose this strange and hard problem !

thank you
Evgeni

Hi again
Lately this problem was becoming worse than usual, and it needed only around 2 or 3 days of uptime to restart the problem with the internet connections again.

I took a look on iptables (erasing all rules), and also I cheeked the file

/proc/sys/net/ipv4/netfilter/ip_conntrack_max

becouse I readed in some forums that using p2p programas like edonkey can give you problems, and it was a solution increase the number inside that file (up to 40952) ,but it was unsuccessfull for my computer

The last test I'm doing right now, is trying a new kernel, the 2.6.16.9. With it, it has improved a lot!, Since I changed the kernel, the problem has dissapeared (well, I'm not sure), and now the system has an uptime of 10 days. (before, I wasn't able to arrive up to 3 days becuase of the problem with the internet connection)

I will post updates about this change next week... because I'm not really sure if updating the kernel is the final solution.

Best regards and good luck! you will need it! ^^

Hello,

Makinavaja, thanks for the reply.
Please, can you answer some questions for me in order to be able to see whether your problem is exactly similar to mine:
1. What kernel were you using before uprading to 2.6.16.9 ?
2. When your problem occurs is there any PC that can still use the Internet, or the problem pertains to absolutely all the PCs ?
3. When the problem occurs can you let's say open www pages on the server itself ?

Thanks and regards,
Evgeni

1. What kernel were you using before uprading to 2.6.16.9 ?

I used the default kernel used by slackware10.2 during installation, that one name bare.i. Its version its... 2.4.31

2. When your problem occurs is there any PC that can still use the Internet, or the problem pertains to absolutely all the PCs ?
The other pc on my network is able to connect to internet when the problem appears, the problem is only present on the linux computer with slackware10.2. BUT, the problems are only related with new internet connections, because samba is still fully operative, also, the dns server works so I can ping to a website using its url, but, the system becomes unable to create a new connection. Another poing, the systems keeps alive the current created connections, (for example, a connection to a irc server), but when it must be restarted, it becomes loosed, it cannot be created again.


3. When the problem occurs can you let's say open www pages on the server itself ?
If you mean as server my linux computer, then the answer is no, it can't. The most simple example can be tested by a console command like: "lynx url" (I still can't post real urls on the forum...)
The screen freezes at "making http connection", and after a minute, it reports me an error because the lynx www browser wasn't able to connect the website.


Best regards, and good luck with the problem!!

Makinavaja

maybe slackware 10.2 is not stable

khalis...maybe that's true, or not
I've got some friends that never had that problem before using slackware 9 or slackware10...

The problem must be related to a combination of the default kernel used by the installation script, and some hardware issues...

Anyway... I've readed at some forums that some people is having quite similar problems using anothers distros, so... I still don't want change my linux distro for another one... I love slackware too much!


Cheers


Makinavaja

P.D.One electrical problem in my house crashed the instalation and my linux computer turned off today at morning ... my 11 days uptime dissapeared, I'm going to need more time to test if the problem has been solved at last, or not... sorry gepas