Hello All.

I have two PC's running (from what I can tell) redhat V5.0 (Hurricane).
Both of these machines have a WaveLan ISA slot card and a Ethernet Nic.

I want to be able to route straite through them. Example I have a Win2K box connected to the internet on one side, connected to it is one of the WaveLan router PC's, then through the air to the other WaveLan router PC connected to another PC running Win NT 4.0.
At the moment from the Win2K machine I can ping the first router and the second router via the air but I can not ping the Win NT machine. Nor can the NT machine ping the router it is directly connected to.
So basicly I have no real experince with Linux at all but I want to know more and I would like to start at trying to figure out where all the IP and routing info is so I can edit it to try and get this thing to work.

Thanks in advance for your help.

So you just need to route between two interfaces right? So the lan is something like
internet <--> Win2K <--> Linux <==air==> Linux <--> NT right?

So you need to route between the second linux box and NT yeah? What subnets do you have? Basically you enable routing between two interfaces by issuing when you have setup both interfaces, then just set the linux box as your default gateway.

Does this answer your question, I'm a little confused about that setup! Namely why do you need the linux boxes? Can't you put the wavelan cards in the Windows boxes?

cheers

Jamie..

Hello Jamie.

Yes that is the setup of the lan, I have included the IP address of the machines.
internet <--> Win2K (192.168.4.2)<--> Linux (192.168.4.1 <==air==> Linux (192.168.1.1) <--> NT (192.168.1.2).

Basically the machines have been setup by someone before and I'm trying to figure out the routing and IP configuration so I can change it to suit my requirements (as I really have no Idea about Linux yet!). The thing I don't understand is the NT machine can not ping the router it is directly connected to? But yet I can ping that router from the Win2K machine via the first router!

So do you think all I need to do is turn on IP forwarding?
Doesen't Linux act on the routing configuration untill you enable IP forwarding (please excuse my ignorance on this subject).

I'm using the two seperate Linux machines because they are mounted in the roof of two diffrent houses too enable them to be as close to the directional antenna to reduce coax cable loss.

Thanks for your time.

Linux will take notice of all the routing before IP forwarding is enabled to make decisions on where to send its own packets, but it won't forward any packets between interfaces. Hence if its set as your default gateway and IP forwarding isn't enabled none of the packets will get through. (although after a recent thread with Raz it looks like the first packet still gets through somehow! A little 'accidental feature' I feel)

As for the pinging, thats a bit weird; as to get to the machine on the 'other' side of your air then you'll have to have a route and be able to send data to the linux machine that you've got a copper connection to. You sure that the person who set them up hasn't put an ipchains (firewall) rule to drop ICMP echo requests? Do a ipchains -L and look for any rules that might be set in there, if you get output you can't figure out then post it to the forum. I'm assuming your on a 2.2.x kernel, if you're inface on 2.4.x then its iptables not ipchains, but I'm unsure of the command to list all your rules in iptables.

HTH

Jamie...

Hello Jamie.

Thanks for the info.

Even after doing the (echo "1" > /proc/sys/net/ipv4/ip_forward) I still get this:
[root@localhost sysconfig]# cat network
NETWORKING=yes
FORWARD_IPV4=false
HOSTNAME=localhost.localdomain

My machine also does not seem to reconise the comand IPCHAINS or IPTABLES, I also did a find for this files with no success.

Here is the config for both machines:

Router 1:
[joe@melba-gw /sbin]$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:750 errors:0 dropped:0 overruns:0
TX packets:0 errors:77960 dropped:750 overruns:0

eth0 Link encap:Ethernet HWaddr 08:00:2B:3B:74:FD
inet addr:192.168.4.1 Bcast:192.168.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16454 errors:0 dropped:0 overruns:0
TX packets:0 errors:0 dropped:12872 overruns:41
Interrupt:5 Base address:0x300

eth1 Link encap:Ethernet HWaddr 08:00:0E:20:5A:CF
inet addr:192.168.4.1 Bcast:192.168.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:52971 errors:0 dropped:0 overruns:0
TX packets:0 errors:4031262 dropped:53501 overruns:0
Interrupt:10 Base address:0x390


[joe@melba-gw /sbin]$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1


Router 2:
[root@localhost /sbin]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0
TX packets:0 errors:1932 dropped:19 overruns:0

eth0 Link encap:Ethernet HWaddr 08:00:09:A3:CBA
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2001 errors:4350 dropped:0 overruns:0
TX packets:0 errors:2520 dropped:60 overruns:0
Interrupt:3 Base address:0x300

eth1 Link encap:Ethernet HWaddr 08:00:0E:20:92:1B
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48181 errors:0 dropped:0 overruns:0
TX packets:0 errors:7362856 dropped:49433 overruns:0
Interrupt:10 Base address:0x390


[root@localhost /sbin]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 192.168.4.1 255.255.255.255 UGH 0 0 0 eth1
192.168.4.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
192.168.4.2 192.168.4.1 255.255.255.255 UGH 0 0 0 eth1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.4.1 0.0.0.0 UG 1 0 0 eth1

Unfortunatly no IPCHAINS info as it does not seem to work.

Any help would be great. Let me know if you need anymore info.

Thanks.

It looks to me like 'network' is just a file that is used at boot time to decide how to setup your networking. Activating IP Forwarding won't effect the file contents! To check your forwarding you want to do (AFAIK) cat /proc/sys/net/ipv4/ip_forward and see wether is says 1 or 0.

If you don't have ipchains or iptables around then you don't need to worry about the filewalling, unless there is a third part product installed. Actually - what kernel are you using? If its 2.0.x then try ipfwadm (I think that was the old command... its been a while).

So you still get no traffic being routed?

Jamie...

Hello Jamie.

There is a "1" when I do (cat /proc/sys/net/ipv4/ip_forward).

There does not seem to be a comand (ipfwadm) on my machine and I'm running Kernel 2.2.1.

I'm slowly getting places, I have now managed to be able to ping the second router from the NT machine.

There seems to be files some where that over write all the changes I'm makeing to the ifconfig and route. Do you know where these files maybe and how to modify them?

Thanks.

In slackware you would change this in your /etc/rc.d/rc.* files, but I'm not sure about older (or newer for that matter!) Redhat file locations. You said you did a 'cat network' at some place and it showed you the contents of a file - thats one place that mentioned the IP forwarding. Have a look for /etc/rc.* and see what turns up. Either that or start another thread with the title of 'network config in RH 5' or something like that, then on of the RH camp members will give you an answer.

Glad to hear that your getting there!

Cheers

Jamie...