|| At our office we are running a Novell 4.11 network (IPX). We connect to
|| the Internet through an IPX/IP gateway. It forwards packets to our router,
|| which then go to the ISP.
|| I have set up a computer with RedHat Linux 5.1 on it. Kernel 2.0.35. I am
|| trying to connect to the Internet using our router, but I am not getting it
|| to work. This is what I do:
|| insmod eepro io=0x300 irq=10 . . . to connect the Intel Ethernet 10 card.
|| This seems fine.
|| ifconfig eth0 192.168.1.1 netmask 255.255.255.0
192.168.x.0 are reserved networks, and won't be reachable from
outside without additional measures (NAT/IP Masquerading). Are you
sure 192.168.1.0 is your local network address (and 192.168.1.1 your
|| Then when I do ifconfig, it shows both lo and eth0, and eth0 is UP and
|| receiving packets. Good so far. I think I chose a proper IP address for
|| my machine to make it in the allowable range for Intranets.
|| route add -net 192.168.1.0
|| This should point to my computer. Linux accepts this and the routing table
|| looks like this:
[Reformatted. Please use a fixed width font and don't word wrap.]
|| Destination Gateway Genmask Flags Metric Ref Use Iface
|| 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
|| 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
A good routing table, provided that 192.168.1.0 is correct.
|| Then I need to connect to our router, which is 220.127.116.11. This is
|| where I run into trouble.
|| route add 18.104.22.168 results in SIOCADDRT: network is unreachable
You're adding a route to 22.214.171.124 and expect the system to divine
where those packets have to go. It does its best trying 126.96.36.199
(probably), but that fails. This is not going to work.
|| So I route del and try again, this time trying
|| route add -net default gw 188.8.131.52 eth0
The router has more than one address; one for each interface. The "outer"
interface of your router is probably 184.108.40.206. You need the
address of the "inner" interface, which is probably on the internal
192.168.1.0 network. You might guess 192.168.1.1 or 192.168.1.254.
If 220.127.116.11 is actually the inner address, then you local network
is probably 18.104.22.168/255.255.255.128 (see below for netmask) instead
of 192.168.1.0/255.255.255.0. Also, your machine's address will be on
|| Then when I try to look at the routing table, it lists the first two lines
|| and freezes. I have to ctrl-c out.
The route command is trying to find out hostnames associated with the
addresses. However, your routing table is incorrect and route has to
wait for the lookups to timeout. Wait long enough, and route will give
up and print numbers anyway.
It used to work before because your routing table didn't give a route to
the name server at all instead of a wrong one. Therefore, route could
give up quickly.
Use the -n option to route to skip the lookups and print numbers.
|| Through various combinations, the best I have ever done is to ping the
|| ISP's WAN port, but nothing beyond that returns any packets to me.
Duh! And which combination was that?!
|| BTW, our IPX/IP gateway connects to the router using a mask of
This doesn't matter too much right now. You could specify the netmask
with ifconfig and route.
|| As you can see, I know just enough to be dangerous,
I agree completely. :-)
|| but not enough to
|| accomplish what I want. I have been through the network HOWTO and the
|| newsgroups, but I still can't figure it out. What am I missing here?
Either figure out your own address and that of the network you're on,
or figure out the internal address of the router, which is most probably
on the local network.
<http://www.xs4all.nl/~zweije/> | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] | -- Paul Tomblin on a.s.r.