On Fri, 2005-03-25 at 21:56, Jeroen Geusebroek wrote:
> On Fri, 25 Mar 2005 14:02:11 -0500, Braden McGrath
> Sure that sounds logical; but how does the 2.254 (m0n0) peer know that it should
> route 192.168.1.0 traffic through the tunnel? AFAIK there is no way to configure
> that (at least using the GUI).
By adding a static route - secound menu-item in the gui.
Thats where you tell where traffic go, if it's not on the local
interfaces, and not going via the default gateway (via WAN).
I'm doing sometthing simular except it's not via VPN. I have a
LTSP-server running, and the workstation-network goes thru the server.
> Interface Network Gateway Description
> LAN 192.168.250.0/24 10.10.0.190 LTSP arbejds-stationer
> LAN 18.104.22.168/32 10.10.0.254 Trafik til webserver mv sendes via LAN istedet for Sonofon
Furthermore trafic to my second public IP (via PPPoE) is routed directly to my server, instead of
filling up my WAN-link. That's also possible using static routes.
Henning Wangerin <mailinglists dash after dash 041101 underscore reply dash not dash possible at hpc dot dk>