alexus at gmail.com
Fri Nov 16 13:36:52 PST 2007
but then i'm going say route _ALL_ traffic for that, and i need to be
able to get in through both interfaces, as if one ISP is down, i can
access in through another... thats the whole point of this thing
On Nov 16, 2007 4:04 PM, Steve Bertrand <iaccounts at ibctech.ca> wrote:
> alexus wrote:
> > i dont see any difference as at the end i still get this
> > 184.108.40.206/29 220.127.116.11 UGS 0 0 fxp1
> > in my netstat -rn, and no its still doesn't work...
> This is not the point.
> You need a route via the gateway that 216 is connected to for the REMOTE
> IP/network. Say for instance your 'home' connection is:
> 18.104.22.168, then you need a route like this:
> route add 22.214.171.124/32 $isp_gateway
> What you have:
> 126.96.36.199/29 188.8.131.52 UGS 0 0 fxp1
> ...says '184.108.40.206/29 should be routed to 220.127.116.11. That is
> ALL it will route via that path.
More information about the freebsd-questions