[Klug-general] routing on smoothwall
Peter Childs
peterachilds at gmail.com
Wed Nov 21 21:29:12 UTC 2012
Right the gw needs to be on the local network hence
If your lan is 192.168.1.*
Your default gateway might be 192.168.1.254
If you have a second gateway on 192.168.1.253 you only want to use for
accessing 10.20.244.2 you can route the packets with
Route add -net 10.20.244.2 netmask 255.255.255.255 gw 192.168.1.253
In otherwords you want the smoothwall box on this side not the otherwise.
The smoothwall box on the others side may need to know where to forward
incoming messages to. ...
Or as least I think that's what you want. ...
Peter
Peter
On 21 Nov 2012 20:06, "Alan Buchel" <alan at communitytechnology.org.uk> wrote:
> I have 2 servers on separate sites replicating overnight via the
> networks main internet uplinks.
> There are no longer enough hours in the night for the rep to complete
> though, but also doing it in the day takes so much bandwidth that the
> users' internet becomes unusable.
>
> Have therefore installed a new broadband line on each site to be used
> for replication only. The uplinks are firewalled by smoothwall boxen,
> and my problem is getting the servers to talk to eachother via this
> uplink as opposed to the default gateway.
>
> Have tried setting static routes on the servers so they go out through
> smoothwall when they want to communicate. Then on the smoothies:
>
> route add -net 10.20.224.2 netmask 255.255.255.255 gw 81.2.xxx.xxx eth0
>
> where:
> 10.20.224.2 = the server on the other site
> 81.2.xxx.xxx = the smoothwall on the other site
>
> but of course I get:
>
> SIOCADDRT: No such process.
>
> I am misunderstanding something about routing and probably networking
> theory, does anyone have any advice or pointers?
>
> Alan
>
> _______________________________________________
> Kent mailing list
> Kent at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/kent
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/kent/attachments/20121121/09f4fade/attachment.html>
More information about the Kent
mailing list