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.
It is hard to say what the problem is, at least for me.
If you set the other computer with a static IP, can It see (ping, pump, etc) the router? I mean, is the conection working?. If it is then try to pump the IP manually... if it works check your ifup script.
Originally posted by LinguelSanchez I think if you have a 10.* IP-address the subnet mask will be 255.0.0.0
Not necessarily. The IP range for eth1 as it is set up is 10.0.0.0/24 (10.0.0.x, netmask 255.255.255.0) for a home network, although it could theoretically be 10.0.0.0/8 (10.x.x.x, netmask 255.0.0.0), but that is a little too big of a subnet for a private LAN.
Once you get the DHCP working, you'll need to configure iptables (the kernel-level firewall for Linux) for NAT, IP forwarding, and masquerading. I suggest this post: http://www.linuxquestions.org/questi...hreadid=121379
Last edited by computergeek84; 01-06-2004 at 11:44 AM.
well... when i set the non-router linux conputer with 'ifconfig eth0 10.0.0.2 netmask 255.255.255.0' and 'route add default gw 10.0.0.1', it still can't ping the router.
here's what 'route' shows on the non-router linux computer:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 * 255.255.255.0 U 0 0 0 eth0
default 10.0.0.1 0.0.0.0 UG 0 0 0 eth0
on the router, when i start up dhcpd manually by typing 'dhcpd eth1', these are the last few lines the it prints to the screen:
Listening on LPF/eth1/00:20:af:a2:5e:ce/10.0.0.0/24
Sending on LPF/eth1/00:20:af:a2:5e:ce/10.0.0.0/24
Sending on Socket/fallback/fallback-net
i was wondering if this would have anything to do with the trouble i'm having.
one last thing..... i noticed that when i look at the ethernet card that is connected to the internet (eth0) on the router, it has a light that is lit up ( green ).
for the non-router linux computer, however, the ethernet card isn't lit up. but when i take the cable from the router and plug it into the non-router, it's ethernet card light turns on. i was wondering if there's some sort of setting i have to setup so that the router brodcasts a certain signal to all the computers connected to the hub, or if that's just a light saying there's a data transfer going on.
Looks like there is a physical problem with either your hub or the cables connecting both computers to the hub. Does the hub show any green lights lit up when the computers are plugged into it? If one is out, it's probably a bad cable. If both are out, maybe you have a bad hub. Are the computers close enough together where you could test their connection with a single crossover cable?
well... i fixed the hub problem... there was a little button that was called MDI/MDIX... and it was set to MDI... i changed it to MDIX and it works fine now. don't have a clue what that did though. now the non-linux computer can get it's dhcp stuff just fine, it's getting to the internet that's a problem.
i just have to get eth1 working again..... when i try 'modprobe 3c509 "irq=13" ', the module loads correctly and everything, but 'ifup eth1' doesn't work.
"there was a little button that was called MDI/MDIX"
That was to change the port to crossover mode. When connecting Device to Device you need to use a crossover cable. Either you depress a button like the one you saw or you use a cable that crossess over pins 1,2 with pins 3,6 on the ethernet jack.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.