On 11/2/2007 11:35 PM, Corey Hickey wrote:
I meant to do both, which I think is necessary in order to make the
OPs proposed scheme work without modification. I'll defer if I'm
wrong, though--I haven't tested it, and, as you said in your other
email, it's a very weird scenario.
As long as
Joshua Kwan wrote:
Hi LARTC,
I have two networks that I manage, A and B. They both have their own
primary gateways for hosts on the network, let's call them AR and BR.
There is another box, A1, which lives on network A but also has a wire
connecting it to a switch on network B. My goal is
On 10/31/07 19:50, Joshua Kwan wrote:
What am I doing wrong? Is this a job for iptables? I feel like I can
do this with just routing table magic.
As Corey said, make sure that IP Forwarding is enabled on A1.
You are setting your self up for a very weird scenario. Probably what
would be the
On 11/02/07 15:24, Corey Hickey wrote:
1. Check /proc/sys/net/ipv4/ip_forward on box A1 to see if it's
configured to route at all.
2. The hosts on network A will receive packets from miscellaneous IP
addresses in B's subnet, and not have any idea what to do with them.
You'll need to either
Grant Taylor wrote:
On 11/02/07 15:24, Corey Hickey wrote:
1. Check /proc/sys/net/ipv4/ip_forward on box A1 to see if it's
configured to route at all.
2. The hosts on network A will receive packets from miscellaneous IP
addresses in B's subnet, and not have any idea what to do with them.
Hi LARTC,
I have two networks that I manage, A and B. They both have their own
primary gateways for hosts on the network, let's call them AR and BR.
There is another box, A1, which lives on network A but also has a wire
connecting it to a switch on network B. My goal is to let hosts on B
access
