ipnat problems on RELENG_5 (ipnat fails to load its tables)

Since I am having ipnat problems on FreeBSD 5.4, and none on 5.3, I was hoping to help out the matter of tracking down the bug. I was wanting a little help with backing out some CVS changes made in the last three months to the kernel. I see now that ipnat has undergone a major update between

Re: xxconfig for if_bridge

Hi, > On Fri, 3 Jun 2005 14:01:40 +1200 > Andrew Thompson <[EMAIL PROTECTED]> said: thompsa> The if_bridge code that will soon be committed can be configured using thompsa> either brconfig or ifconfig. thompsa> http://people.freebsd.org/~thompsa/ thompsa> Only one tool will be committed

RE: (KAME-snap 9091) RADIX_MPATH support

> > The KAME RADIS_MPATH is supported only on NetBSD. > I should have read IMPLEMENTATION more carefully. > > FreeBSD maay be compiable with the option, but it will not > work properly. > I will try fixing the FreeBSD boot problem and then submit the changes for review if there

Re: xxconfig for if_bridge

On Fri, Jun 03, 2005 at 02:01:40PM +1200, Andrew Thompson wrote: > Hi, > > > The if_bridge code that will soon be committed can be configured using > either brconfig or ifconfig. > > http://people.freebsd.org/~thompsa/ > > Only one tool will be committed and I would like to get opinions on > wh

xxconfig for if_bridge

Hi, The if_bridge code that will soon be committed can be configured using either brconfig or ifconfig. http://people.freebsd.org/~thompsa/ Only one tool will be committed and I would like to get opinions on which one ppl prefer brconfig - new util to /sbin + same as NetBSD/OpenBSD - would

Re: (KAME-snap 9091) RADIX_MPATH support

Hi, From: "Li, Qing" <[EMAIL PROTECTED]> Date: Thu, 2 Jun 2005 12:46:33 -0700 > Is RADIX_MPATH still supported in KAME ? > > Enabling RADIX_MPATH on FreeBSD 5.4 panic on bootup and the > system just reset. I cannot get into the debugger. The KAME RADIS_MPATH is supported only on Net

Re: issue with route

If memory serves me right, Andre Oppermann wrote: > Oh, BTW. Don't be afraid when you get brucified. Bruce' style > comments are a very valuable learning resource. Everyone of us got > brucified more than once. ;-) (I'm talking about Bruce Evans, bde@)

RE: issue with route

> > Please check if my variant does the right thing in all cases. > If you can confirm, then you can go ahead and write up a > descriptive commit message. > Okay, I will verify your version. > > Then please send me your final patch including proposed > commit message for final revi

Re: ndiscvt make failure

On Thu, 2 Jun 2005, lysergius2001 wrote: > Can anyone help? > I am trying to install Belkin fd57000 pci wireless card in a box running > FBSD 5.3. I got as far as compiling ndiscvt but the compile breaks with a > very long list of errors. I have checked and double checked each step of the > pr

RADIX_MPATH support

Hi, Is RADIX_MPATH still supported in KAME ? Enabling RADIX_MPATH on FreeBSD 5.4 panic on bootup and the system just reset. I cannot get into the debugger. After investigating the same code on a FreeBSD 5.4 based variant system, I found the deletion code appears to be a

Re: issue with route

> On Thu, 02 Jun 2005 13:33:32 +0200, > Andre Oppermann <[EMAIL PROTECTED]> said: >> I verified this behavior on both FreeBSD 5.4 Release and 6.0-CURRENT. > Looks very strange indeed. >> I think this behavior is probably not intended and should be treated >> as a bug. I did a quick patc

Re: issue with route

"Li, Qing" wrote: > > > > > Please post unified diffs, they are far easier to read for humans. > > > > Sorry, here is the patch again. > > -- Qing > > Index: route.c > === > RCS file: /home/ncvs/src/sys/net/route.c,v >

RE: issue with route

> > EINVAL might be a more appropriate error code. > - heavygear# route add 10.1.1.1 -inet6 fe80::1%fxp0 route: writing to routing socket: Invalid argument add host 10.1.1.1: gateway fe80::1%fxp0: Invalid argument - You're right. Thanks, -- Qing _

RE: issue with route

> > Please post unified diffs, they are far easier to read for humans. > Sorry, here is the patch again. -- Qing Index: route.c === RCS file: /home/ncvs/src/sys/net/route.c,v retrieving revision 1.108 diff -u -r1.108

ndiscvt make failure

Can anyone help? I am trying to install Belkin fd57000 pci wireless card in a box running FBSD 5.3. I got as far as compiling ndiscvt but the compile breaks with a very long list of errors. I have checked and double checked each step of the process as set out in the manual and various sources

Re: issue with route

Hi, > On Thu, 02 Jun 2005 13:33:32 +0200 > Andre Oppermann <[EMAIL PROTECTED]> said: > I think this behavior is probably not intended and should be treated > as a bug. I did a quick patch in sys/net/route.c > (it's just as easy in sbin/route.c). andre> Unless this causes or suppose

Re: issue with route

"Li, Qing" wrote: > > > When I issued the following command by accident today: > >route add default -inet6 fe80:20d:56ff:fe8d:d4b0%fxp0 > > The netstat shows the following: > > Internet: > DestinationGatewayFlagsRefs Use Netif > Expire > default

Re: issue with route

On Thu, 2 Jun 2005, Li, Qing wrote: > route add 10.1.1.1 -inet6 fe80::1%fxp0 Out of curiosity, how are packets actually routed when using this? ~Neo-Vortex ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freeb

issue with route

When I issued the following command by accident today: route add default -inet6 fe80:20d:56ff:fe8d:d4b0%fxp0 The netstat shows the following: Internet: DestinationGatewayFlagsRefs Use Netif Expire defaultfe80:20d:56ff:fe8d:d4b0%fxp0