Hi Cameron
192.168.1.x (eth0) is the local LAN which has internet access via 10.0.0.220
and this works always has worked
Although there are other networks on x.x.2.x and x.x.3.x they are handled by
other systems
I have just implemented a new network at x.x.4.x. This is via a Radio wave
LAN bridge. This is being implemented via our Linux RH7.2 box using
IPTables. The .4.x network has been implemented as an aliased address on
eth0 with the .1.x network
The interface card is at 1.220 for the local LAN and 4.220 for the radio
LAN.
>From the radio network I can Ping 4.220 and get a reply. From the .1.x
network I can ping the .4.220 and the .4.253 and 4.254 radio link bridge
devices.
>From a PC at the other end of the radio bridge I can ping both radio
devices and the Linux interface @ 4.220.
>From a PC at the other end of the radio bridge I cannot ping or contact
either the 1.220 interface nor any PC on the .1.x network
Redhat 7.2 with IPTables eth0 has .1.220 and an aliases address .4.220
Radio Radio Linux Box
End1 End2 xxxxxxx
xxxx xxxx 4.220 x x
--- x x ----------- x x ------------------ x x-----eth1
x.x.x.x = Internet
x x x x eth0 x x
xxxx xxxx - x x
192.168.4.254 192.168.4.253 - xxxxxxx
-
eth0 also = 1.220 and other
PCs on .1.x
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
