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've finally got my network card to work in RH 7.2 (Intel EtherExpress) and it seems to be working fine (ie. initialised at boot time, listed in ifconfig, modules.conf, ioports, interrupts).
On this RH7.2 box, I can ping myself(eth0=192.168.0.2) no probs.
On my win2k box (the only other machine in my home network), I can also ping myself (192.168.0.1) but they can't seem to ping each other (host unreachable).
The lights on my hub show that the connections from these machines are up so I suspect it's a rounting problem but not sure how to correct it using Network Configuration in GNOME.
Any help will be welcome (or tell me what other infor to post if that helps)
Kernel IP routing table
Destination--Gatewy--Genmask---------Flgs--Met--Ref--Use--Iface
192.168.0.0--bob------255.255.255.0--UG------0----0---0----eth0
192.168.0.0--*---------255.255.255.0--U--------0----0---0----eth0
127.0.0.0-----*---------255.0.0.0---------U--------0---0----0----lo
default--------bob------0.0.0.0------------UG------0----0---0----eth0
(added dashes to keep the formatting)
Note: Bob is my win2k box, Molly is my Linux72 box.
2)Hub is stock standard hub (not router/switch etc)
3)I have a modem attached to my win2k box and can surf the net but my linux box can't.
4) No firewalling switched on at all
5)Linux hosts:
# Do not remove the following line, or various programs
# that require network functionality will fail.
192.168.0.2 molly molly
192.168.0.1 bob bob
127.0.0.1 localhost.localdomain localhost
Didn't work. I now think it's my win 2k box.(Local Area Network says no pakets sent/received and the hub light for this connect doesn't flash when issue a ping command.
Originally posted by Baver route add 192.168.0.1 gw 192.168.0.2
192.168.0.1 being the destination network
No. 192.168.0.1 is not the destination network, it is the address of another node on the 192.168.0.0. network (in this case, the Windows box).
Quote:
Originally posted by Baver and 192.168.0.2 being the NIC it's on on your linuxbox
Well yes, that is the Linux box's NIC's address on the LAN, but it is not the gateway address to the outside world; the gw addr would be the address of the Win box's NIC (192.169.0.1). As spato said though, it sounds like more work had to be done on the Win box's side to pass requests from the LAN (via the NIC in the Win box) to the modem, and then on to the outside world.
Spato:
I don't know if you can reference host names (as opposed to IPs) in your routing table, but my guess is not. Even if it is do-able, I'd stick with pure IP references in the routing table.
Here's the output of route from one of the Linux boxes on my LAN:
Code:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.0.0 * 255.255.255.0 U 0 0
0 eth0
127.0.0.0 * 255.0.0.0 U 0 0
0 lo
default 192.168.0.1 0.0.0.0 UG 0 0
0 eth0
[root@penguinbox~]#
-The 192.168.0.0 network entry can be generated by:
route add -net 192.168.0.0
(although this is doesn't usually need to be explicitly specified, as it seems to be derived from your other entries)
-The "default 192.168.0.1" entry is the address of my router, which you can specify by:
route add default gw <LAN-side IP of router>. Since your Linux box seems to be getting it's Net access though the Win box and it s modem, I would think that the gw entry in the Linux box's routing table should point to the IP of the NIC in the Win box.
I think your win2k box is locking down those ports, but I don't know how to check that for win2k. basically, MS has decided that you shouldn't be pingable.... I know that XP gives my friends weird troubles in that regard. perhaps win2k is similar.
try running an http server on your linux box, and see if your win2k box can bring it up. or, start a telnet server, and try to telnet into your linux box.
ahh, it seems i have things backwards. anyways, this is how i have things on my server, with ip masquerading on ppp0.
ok... hmm. I have a net set up with 3 win boxes using 10.0.0.5, 10.0.0.6, and 10.0.0.7, and three nics in my linuxbox using 10.0.0.1, 10.0.0.2, and 10.0.0.3 and until i execute
Growler
U forgot that I can't ping from win box to linux box either.Also, I didn't have this prob on another LAN (with win2k box (same ver) and RH72 box) so I'm fairly sure its my Win2k NIC.
DMR
Thanks.I'll replace NIC in win2k box first tho and then c what happens.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.