Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just encountered an odd network stack glitch and wondered if anyone has seen this before, or knows what could cause it. When I connect to services on localhost (127.0.0.1) if there is a process listening, it works OK as expected. If there is no process listening, I should get a NAK and see a connection refused message. With this glitch, that was not happening. And this was with 127.0.0.1 to 127.0.0.1. Nothing was listening, but the SYN attempts were all that were happening. If there was something listening that worked OK. Connections to other hosts worked as expected. A reboot fixed it. Sure seemed odd to me.
Next time instead of talking about issues please try to support your findings with a more "formal" report including kernel version, technical details like packet dumps et cetera.
Next time instead of talking about issues please try to support your findings with a more "formal" report including kernel version, technical details like packet dumps et cetera.
//NTLB
Talking about an issue is specifically what I wanted to do, before filing any formal report. In this case, there isn't much to report, except that it is kernel "2.6.35-24-generic" in Ubuntu 10.10 amd64. Some kinds of problems, like this one, are not something so easily dealt with, because of their extreme intermittent behavior. Talking about it first might lead to some insight in how to go about coming up with technical details.
I'm also curious how it is your reply to my post precedes it by two days.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.