On Friday 23 March 2007 11:04, Dan Cook wrote:
> my idea is to use a bridge for the regular access and a route for the new
> application access. Sat a bridge from eth0 to eth1 but routing to newlink
> from eth0 to eth2. I would like to use the linux box as the firewall for
> the newlink side of things.
More complex then probably needed:
/------------firewall 192.168.0.1/24 (3/4 T)
client-->(switching) hub
\------------firewall 192.168.0.2/24 (NewLink)
client(s) static routes:
ip route add default via 192.168.0.1
ip route add <newlinkdstaddr> via 192.168.0.2
You could also use a different network (192.168.1.1/24) for Newlink
and add a second address to the client(s) eth's , if that makes more
sense.
Dave
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
