[Wolves] Network routing problem

Nigel R nigelren at yahoo.co.uk
Sat Dec 31 10:36:26 UTC 2011


Thanks for your ideas, I'll give that a go when I get chance.  The one thing that has sprung to mind which is that I probably didn't set the routes on both machines.  This probably meant that the traffic was getting too the target machine, but then didn't know how to send it back so it probably went out through the default gateway ( out to the www ).  This makes sense now and should sort my problem out, as that great thinker and philosopher once said - D'oh!

Anyway - have a good New Year everyone :)



>________________________________
> From: Dan Dart <dandart at googlemail.com>
>To: Wolverhampton Linux User Group <wolves at mailman.lug.org.uk> 
>Sent: Thursday, 29 December 2011, 19:01
>Subject: Re: [Wolves] Network routing problem
> 
>Would've thought it'd be as simple as:
>
>vm-a $ route add -net 192.168.100.100-192.168.100.199 gw 192.168.122.2
>vm-b $ route add -net 192.168.122.100-192.168.122.199 gw 192.168.122.1
>
>or similar.
>
>_______________________________________________
>Wolves LUG mailing list
>Homepage: http://www.wolveslug.org.uk/
>Mailing list: Wolves at mailman.lug.org.uk
>Mailing list home: https://mailman.lug.org.uk/mailman/listinfo/wolves
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/wolves/attachments/20111231/744bff49/attachment.htm>


More information about the Wolves mailing list