On 19.11.2007, at 06:03, alexus wrote:
how i can acomplish this with ipf? i have ipf on that box
Write this in ipf.rules:
pass out quick on fxp0 to fxp1:$fxp1_gw from $fxp1_ip to any keep
state
don't forget to replace $fxp1_*.
This solution can be also accomplished with IPFW, options
how i can acomplish this with ipf? i have ipf on that box
On Nov 16, 2007 4:45 PM, Todor Dragnev <[EMAIL PROTECTED]> wrote:
> Hi,
>
> you must use advanced routing, this is very easy on linux with
> iproute2 but freebsd is far away for now(maybe forever) and you must
> use pf or ipf for this situa
alexus wrote:
i dont see any difference as at the end i still get this
216.112.241.24/29 216.112.241.25 UGS 00 fxp1
in my netstat -rn, and no its still doesn't work...
On Nov 16, 2007 12:07 PM, Steve Bertrand <[EMAIL PROTECTED]> wrote:
alexus wrote:
my privat
Hi,
you must use advanced routing, this is very easy on linux with
iproute2 but freebsd is far away for now(maybe forever) and you must
use pf or ipf for this situation.
So, enable pf in rc.conf
pf_enable="YES"
Add this line to the end of pf.conf:
pass out quick route-to (fxp1 $fxp1_gw
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 <[EMAIL PROTECTED]> wrote:
> alexus wrote:
> > i dont
alexus wrote:
> i dont see any difference as at the end i still get this
>
> 216.112.241.24/29 216.112.241.25 UGS 00 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 REMOT
i'm pretty sure you can do it on freebsd, especially if its possible
on Linux, routing works same way as on Linux
On Nov 16, 2007 4:51 PM, Bram Van Steenlandt <[EMAIL PROTECTED]> wrote:
>
> alexus wrote:
> > i dont see any difference as at the end i still get this
> >
> > 216.112.241.24/29 216.11
i dont see any difference as at the end i still get this
216.112.241.24/29 216.112.241.25 UGS 00 fxp1
in my netstat -rn, and no its still doesn't work...
On Nov 16, 2007 12:07 PM, Steve Bertrand <[EMAIL PROTECTED]> wrote:
> alexus wrote:
> > my private IP that eventually
my private IP that eventually resolves to public IP through PIX is
different then coming from my other public IP that assigned on my fxp1
that comes from another ISP, the fxp1 IP already configured this way
so it pass everything to my box
what i've tried is adding route on my box
route add 216.11
alexus wrote:
> my private IP that eventually resolves to public IP through PIX is
> different then coming from my other public IP that assigned on my fxp1
> that comes from another ISP, the fxp1 IP already configured this way
> so it pass everything to my box
>
> what i've tried is adding route o
yes, i know that, and i want my defaultroute to stay 192.168.1.1, what
i also want is to be able to access it through 216.112.241.30 (fxp1)
On Nov 16, 2007 1:38 AM, Girish Venkatachalam
<[EMAIL PROTECTED]> wrote:
> On 00:18:42 Nov 16, alexus wrote:
> > Hello,
> >
> > I have two NICs on my box, one
Girish Venkatachalam wrote:
> On 00:18:42 Nov 16, alexus wrote:
>> Hello,
>>
>> I have two NICs on my box, one (primary) connected to switch and have
>> private IP. that IP also have a static route on Cisco PIX for
>> accessing this box from outside. the other interface has public IP
>> that is con
On 00:18:42 Nov 16, alexus wrote:
> Hello,
>
> I have two NICs on my box, one (primary) connected to switch and have
> private IP. that IP also have a static route on Cisco PIX for
> accessing this box from outside. the other interface has public IP
> that is connected to another switch, i configu
Hello,
I have two NICs on my box, one (primary) connected to switch and have
private IP. that IP also have a static route on Cisco PIX for
accessing this box from outside. the other interface has public IP
that is connected to another switch, i configure both IPs through
/etc/rc.conf, but I can no
14 matches
Mail list logo
