On Tue, Aug 9, 2022 at 8:57 AM Roy Marples wrote:
>
> On 08/08/2022 23:27, George Michaelson wrote:
> > Yes. and I was trying to say, the rc.d system should alllow this to
> > say "It wont work, you had rtsold_enabled=YES set" because these have
> > to be eithe
Yes. and I was trying to say, the rc.d system should alllow this to
say "It wont work, you had rtsold_enabled=YES set" because these have
to be either/or in my understanding of things.
You can't both do SLAAC and DHCPv6. Its either/or.
On Tue, Aug 9, 2022 at 8:22 AM Roy Marples wrote:
>
> On 08/
On Sun, 7 Aug 2022, 3:32 pm Ben Woods, wrote:
> Hi freebsd-net,
>
> I would like to propose dhcpcd is imported into FreeBSD base.
>
I'd be in favour. If it makes stateful IPv6 easier for people who don't
live SLAAC it's helping.
This would be one of those one-or-the-other-not-both things you m
In my opinion, these changes are definitely worth accepting. Removing
barriers to deployment of 240/4 is a good thing.
The changes are really simple, easy to understand and gated by sysctl
which is sensible. I really hope we can move from 'default off' to
'default on' in a reasonably short period
Is there a reason (avoid bikeshedding) the field width can't be
increased to allow the bgeXhexIsVeryLong0 names to work?
I'm not saying "you can alias around this" is bad, but I sense we're
walking into a world which is where Linux is, with every physical
device called eth0/1/2 and then "which" de
n 13, 2022 at 6:15 PM Patrick M. Hausen wrote:
>
> Hi all,
>
> > Am 13.01.2022 um 06:41 schrieb George Michaelson :
> >
> > I just found a couple of odd quirks in bridge
> >
> > 1) you can't bridge an MTU 9000 interface to taps. If you dial it back
>
I just found a couple of odd quirks in bridge
1) you can't bridge an MTU 9000 interface to taps. If you dial it back
to 1500 it works fine. I might have missed this being a limit in the
man
2) when you delete a bridge, and re-create it, some of the addm
"history" can come live. faulty debug sugge
The following reply was made to PR kern/154134; it has been noted by GNATS.
From: George Michaelson
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/154134: [ip6] stuck kernel state in LISTEN on ipv6 daemon
which has been killed
Date: Mon, 24 Jan 2011 12:44:07 +1000
On 24/01/2011, at 8:03
On Sat, 23 Jun 2007 00:39:46 +0100
"Bruce M. Simpson" <[EMAIL PROTECTED]> wrote:
> The fact that it does work at all is to do with how protocol domain
> attach works with struct ifnet. I am thinking that in future a lot of
> this should change, in order to avoid a number of issues we currently
on a 6-STABLE host, I added:
ipv6_enable="YES"
ipv6_network_interfaces="bge1"
to rc.conf, and ran /etc/rc.d/network_ipv6
this did not bring IPv6 live. rtsol reported problems with get_llflag()
calls. However across reboot, the system came up with IPv6 fine.
Can somebody explain w
10 matches
Mail list logo
