Old Synopsis: FreeBSD 7.2-amd64 panic w/IPv6
New Synopsis: [ip6] [panic] FreeBSD 7.2-amd64 panic w/IPv6
Responsible-Changed-From-To: freebsd-amd64->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun Nov 1 08:33:55 UTC 2009
Responsible-Changed-Why:
reclassify.
http://www.fr
On 10/31/09, Coleman Kane wrote:
> Paul,
>
> Did you get to send this to sam@, etc ?
Negative, now let @net know about it too.
> On Fri, 2009-10-30 at 16:52 +0100, Paul B Mahol wrote:
>> Hi,
>>
>> There is no point to do scanning how it is currently done:
>>
>> Index: if_ndis.c
>> ==
Hello,
What's the latest "stable" patch available for the latest 7.x source?
thanks
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Sebastian Hyrwall wrote:
You could still use a /32 and then add a route for the other IP via
the ethernet interface. This is effectively the same with a /31.
Does not work,
I see, I've checked this on 9.0 and found it working, not on 7.2.
Nikos
__
Hi everyone,
On a set of gw boxes I have 5 carp interfaces. 4 are working fine,
but on one for some reason the advskew setting isn't "sticking" (and I
get carp2: incorrect hash). I'm running 7.2-STABLE from a few days
ago.
gw-a# ifconfig carp2 vhid 12 advskew 100 pass abc123 10.0.100.1
On Sun, 1 Nov 2009 12:00, nrml@ wrote:
Hello,
What's the latest "stable" patch available for the latest 7.x source?
thanks
Checkout http://svn.freebsd.org/base/stable/7 (Subversion Repository)
You can also browse back to the root of that tree to get to the ViewVC
client to browse t
Hello.
I've got a 6.3 box in which I needed to use debug.mpsafenet=0 in order
to avoid deadlocks with ipfw uid rules.
I'm thinking of upgrading this to 7.2 and I see the above variable has
gone away. Does this mean it is now safe to use such ipfw rules?
The last things I could find wrt this ma
