On Thu, 15 Nov 2001, Chrisy Luke wrote:
> > > only packets already leaving the system can be hijacked and forwarded
> > > to a 2nd machine. Incoming packets can only be forwarded to local
> > > addresses/port combinations.
>
> My fault. I was being lazy when I wrote it. :)
Ah it WAS you I comm
Excuse me feollowing up to myself, but...
Chrisy Luke wrote (on Nov 15):
> It looks good. The ipfw syntax doesn't quite make sense to me.
> Also, are you requiring that they all be on the same ipfw rule number?
Ignore this. Just occured to me you're sharing load based on a netmask.
A small stat
Julian Elischer wrote (on Nov 15):
> Oops forgot the patch.. here it is...
I almost replied to the first - too quick off the mark!
> Julian Elischer wrote:
> > Ipfw 'fwd' at present has teh following restriction:
> >
> > only packets already leaving the system can be hijacked and forwarded
>
Oops forgot the patch.. here it is...
Julian Elischer wrote:
>
> The following patch is expected to
> allow the forwarding of INCOMING packets to an arbitrary next hop
> controlled by the ipfw fwd command..
>
> Ipfw 'fwd' at present has teh following restriction:
>
> only packets already le
The following patch is expected to
allow the forwarding of INCOMING packets to an arbitrary next hop
controlled by the ipfw fwd command..
Ipfw 'fwd' at present has teh following restriction:
only packets already leaving the system can be hijacked and forwarded
to a 2nd machine. Incoming packet
hi,
how can I setup tunneling firewall using ipsec or something alike?
(need to use some ports which are prohibited).
Do I have to have some computer behind firewall (unfirewalled) and
some programs running on it also?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net
Trond Davidsen writes:
> > If you can get mpd into a state where "kill -9" doesn't kill it,
> > then that seems like a kernel bug to me, and so we should probably
> > hone in on that first.. maybe we can come up with a simple test
> > case, e.g. using the event library debug output, write a progr
We are running the SecureID clients on freeBSD 4.4
I don't think they have the server running on FreeBSD
but we are just using a sun for that.
The radiusd code has the option to link with their libraries
so we did that.. that gives us a freebsd SecureID based radiusd.
(it's the ascend radiusd)
t
> >
> > This one is pretty critical. If you can't support SecurID passwords
> > (60sec lifetime) then there are lots of sites that won't be
> able to work
> > with the system at all. We've already seen this problem
> with the Cisco
> > LEAP stuff.
>
> Does anyone else have secureID fobs runn
>
> Hmm.. well, we should try to pick this apart one problem at a time.
>
> If you can get mpd into a state where "kill -9" doesn't kill it,
> then that seems like a kernel bug to me, and so we should probably
> hone in on that first.. maybe we can come up with a simple test
> case, e.g. using
10 matches
Mail list logo
