>To which I can only say that in IPv4 world and VPN, NAT is almost
>mandatory. For me, using NAT allows me to set up VPN specific
>routing for my special project within a corporate network without
>bothering the network administrator with using FreeBSD instead of
>their Cisco stuff for routing.
Hi,
My kernel
periodically crashes on me, is there a way to capture the kernel output before
the kernel reboots itself ? I suspect it might be something to do with my
changes in the kernel. But I don't know what might be causing it.
I'm looking for
something like what dmesg outputs, bu
Hello Friends:
I want to know about implementation and support of ECN in TCP/IP
stack of FreeBSD, is it a standard? Specifically to FreeBSD 3.2 I looked
at netinet but could not find any thing related to it. Do I need to get
some patch for ECN.
I looked at RFC 2481 and it says that ECN
Hi !
I am new here, so I was just wondering if there was any talk on
implementing AX.25 or X.25 protocol to FreeBSD?
AX.25 is protocol for Packet Radio (Internet through HAM devices). X.25
should be *little* similar to AX.25, but not that much. Having AX.25 done
already would be great, but if
>I am tempted to "outsource" the IPsec functionality away from the
>kernel using a demon on a divert socket, just like NATD. This would
>be more modular and keeps the kernel from panicing because of bugs
>in IPsec -- I did have embarrassing kernel crashes, just when I bragged
>about FreeBSD runnin
On 0, Aleksander Rozman - Andy <[EMAIL PROTECTED]> wrote:
> I am new here, so I was just wondering if there was any talk on
> implementing AX.25 or X.25 protocol to FreeBSD?
> AX.25 is protocol for Packet Radio (Internet through HAM devices). X.25
> should be *little* similar to AX.25, but not
