well, the easier method would be to have MachineB on a seperate subnet, then do the following :
*) Add a route on your proxy for the MachineB subnet, to point to MachineA
*) On Machine B, set the default gateway to be MachineA
*) Turn on ip forwarding in your networking config on MachineA. I think under fedora it should
be as easy as 'echo 1 > /proc/sys/net/ipv4/ip_forward' in a startup script, or setting an
ip_forward=yes flag in your networking options (not sure where to do this in fedora tho).
*) Add an iptables forwarding rule if you need to (ie: if your FORWARD policy is set to a default
deny)
*) Finally, make sure the proxy can NAT or proxy for the MachineB subnet. If it can't, then
you might have to NAT MachineA onto MachineB, but this could get messy, slow etc. and not
really advised.
Otherwise, depending on what sort of connectivity you want to provide MachineB, you could setup a HTTP/HTTPS/FTP Squid proxy on MachineA, or a general Socks proxy. This would bypass crazy routing stuff entirely.
Having the two machines on the same subnet would involve proxying the MAC's of MachineB and the router for arp requests etc, which you might not be up for doing.
I take it the proxy doesn't have multiple ethernet ports... ?
Last edited by angrybeaver; 12-08-2005 at 11:27 PM.
|