On a slightly side note, I'd much prefer to see FreeBSD with IPSEC
pseudo-interfaces a la OpenBSD/linux.
I'd much prefer to work with say, enc0, or ipsec1, than mess around with
guf half-tunnels makes complex routing much easier
Just a thought - perhaps a netgraph ipsec node is the
On Thursday 04 April 2002 09:53, Crist J. Clark wrote:
On Thu, Apr 04, 2002 at 09:12:40AM +0200, Sebastien Petit wrote:
[snip]
with the RFC2338, FreeBSD must respond to ARP query on 10.0.1.1 and
172.16.2.1 with 00:00:5E:01:01 MAC address and not with the real MAC
addresses of physical
According to arp(4), the pseudo-device ether is used to map between
10Mb/s Ethernet addresses and IP addresses. PR docs/35604 was opened
questioning whether this is true, or if it also supports 100Mb/s, and
possibly also gigabit Ethernet. I've searched Google and the mailing
list
Hello:
I'm following all the steps of the Handbook to make a
remote kernel debugging using GDB.
My problem is that when I write target remote /dev/cuaa0,
I can not see the source files because I received the
following message:
Cannot find the bounds of currect function
I run gdb with
in Apr, Sam Leffler probably wrote :
|1. Has anyone else seriously looked at doing this?
|2. Has anyone compared the OpenBSD and KAME implementations and understand
|their relative strengths? (e.g. is there some reason to work with KAME other
|than it's already in the system)
I realize you're
I continue with the same problem :(
Hello:
I'm following all the steps of the Handbook to make a
remote kernel debugging using GDB.
My problem is that when I write target remote /dev/cuaa0,
I can not see the source files because I received the
following message:
On Wed, 3 Apr 2002, Lars Eggert wrote:
We have a vtun setup (tethered.net) that does just that (relay the real
Internet to the inside of a NAT box) to support DARPA PI meetings. We're
currently documenting the thing and will put up a website with
descriptions and the config scripts. Ping me
As Brian Somers wrote:
The code now avoids adding a host route if the interface address is
0.0.0.0, and always treats a failure to add a host route as fatal
(previously, it masked EEXIST for some reason - I guessed because it
was trying to handle address re-assignment, but that works ok
Kris Kirby wrote:
What is required to make this work though is that you can get a few
static IPs inside the 216.6.6.129/25 net (in your example) to relay.
I'm a little confused by this.
It's simple, really. At ISI, for example, we have the 128.9/16 subnet.
We use a class C inside that block,
On Wed, 3 Apr 2002 11:15:45 -0800
Luigi Rizzo [EMAIL PROTECTED] wrote:
On Wed, Apr 03, 2002 at 08:59:23PM +0200, Christophe Prévotaux wrote:
Hi
I have reached the 655 firewalling rules limit (with discrete values)
in ipfw and I was wondering why ipfw will not let the user select
the
The code now avoids adding a host route if the interface address is
0.0.0.0, and always treats a failure to add a host route as fatal
(previously, it masked EEXIST for some reason - I guessed because it
was trying to handle address re-assignment, but that works ok with
this patch).
Juan Francisco Rodriguez Hervella writes:
I run gdb with xemacs with -k kernel, in the
directory /sys/compile/MY-KERNEL
You mean gdb -k kernel.debug right?
-Archie
__
Archie Cobbs * Packet Design *
I'm experience a really weird condition with the bridging code.
It looks like there is some race condition that causes an interface
to look like it's in promiscuous mode when it really isn't.
My setup has two Intel Gigabit cards with the Intel em driver.
(The gx driver causes auto-negotiation to
As Brian Somers wrote:
The code now avoids adding a host route if the interface address is
0.0.0.0, and always treats a failure to add a host route as fatal
(previously, it masked EEXIST for some reason - I guessed because it
was trying to handle address re-assignment, but that
The code now avoids adding a host route if the interface address is
0.0.0.0, and always treats a failure to add a host route as fatal
(previously, it masked EEXIST for some reason - I guessed because it
was trying to handle address re-assignment, but that works ok with
this patch).
On Thu, 4 Apr 2002, glaerumk wrote:
if I run natd to share a isdn connection, is there a way I can get
counterstrike and other online-games to work through the freebsd box
running natd?
Yes... and this question belongs on the freebsd-questions mailing
list not freebsd-net.
The code now avoids adding a host route if the interface address is
0.0.0.0, and always treats a failure to add a host route as fatal
(previously, it masked EEXIST for some reason - I guessed because it
was trying to handle address re-assignment, but that works ok with
this
On Thu, Apr 04, 2002 at 10:25:56PM +0200, Christophe Prevotaux wrote:
Luigi Rizzo [EMAIL PROTECTED] wrote:
On Wed, Apr 03, 2002 at 08:59:23PM +0200, Christophe Prévotaux wrote:
...
I have reached the 655 firewalling rules limit (with discrete values)
...
you know you can assign
The code now avoids adding a host route if the interface address is
0.0.0.0, and always treats a failure to add a host route as fatal
(previously, it masked EEXIST for some reason - I guessed because it
was trying to handle address re-assignment, but that works ok with
Little bit confused here.
Hope the formatting in the email isn't screwed up -
these things usually are. sorry
rl0 is the ethernet interface on the machine -and
I'm setting up IPv6 over IPv4 (6to4), using the stf0 interface. The box is
connected by PPP to the internet over tun0.
But I'm
On Fri, 5 Apr 2002 16:09:17 +1000,
Merlin [EMAIL PROTECTED] said:
rl0 is the ethernet interface on the machine -and I'm setting up IPv6 over IPv4
(6to4), using the stf0 interface. The box is connected by PPP to the internet over
tun0.
But I'm haveing trouble actually working out which is
On Fri, 5 Apr 2002 16:44:20 +1000,
Merlin [EMAIL PROTECTED] said:
(ps - can't get to your email address?)
(This was perhaps due to the mime-encoded full name in the from field.
You can ignore this problem because I'm on the list. Please just
reply to the list.)
My host name is
22 matches
Mail list logo
