Linux - Networking This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
01-27-2013, 08:12 AM
|
#1
|
LQ Newbie
Registered: Jan 2013
Posts: 6
Rep: 
|
Unable to host servers.
Well, I get this issue with both my ethernet and wireless cards. Basically if I run “nc -l -p 1234” in one terminal and “nc localhost 1234” in another, anything I type in one will not show up in the other. The system calls that set everything up seem to complete successfully, but the data just doesn't reach the server for some reason. Any ideas?
EDIT: By the way, I can successfully send data to a server hosted somewhere else using nc. It just fails when I try to send data to my own server.
Last edited by dh_; 01-27-2013 at 08:15 AM.
Reason: fixed a grammatical error and added more info.
|
|
|
01-27-2013, 11:47 AM
|
#2
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
presumably it's related to iptables rules, show us "iptables -vnL"
|
|
|
01-27-2013, 09:12 PM
|
#3
|
LQ Newbie
Registered: Jan 2013
Posts: 6
Original Poster
Rep: 
|
Turns out I just needed to put the lo device up. Quite weird, I think, since not even my private network address would work.
|
|
|
01-28-2013, 02:23 AM
|
#4
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
lo should *always* be up, any ideas why it wasn't?
|
|
|
01-28-2013, 09:25 AM
|
#5
|
LQ Newbie
Registered: Jan 2013
Posts: 6
Original Poster
Rep: 
|
Well, I run the same distribution on two computers (Slackware 14.0) and it seems lo gets put up by the rc.inet1 script. I installed wicd, which is in the extras directory, on my laptop and because of that it loads rc.wicd instead of rc.inet1, which doesn't put lo up. I've fixed this by adding “ifconfig lo up” to rc.local.
|
|
|
All times are GMT -5. The time now is 02:00 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|