The following handful-line patch (left the original assignments
commented out) causes rtadvd to conform to the man page *except* you
have to actually specify the interface to change pltime and vltime;
doing so in "default" is not picked up.
I initiated a bug report; is there a reason it should
BTW the reason this behavior is definitely bad news is the following:
Note that if the delegated address changes the host in question does get
it marked "deprecated" essentially immediately but it remains in the
address table for a very long time which is both pointless and, if the
delegated a
Nope -- no change:
07:44:23.810602 IP6 (hlim 255, next-header ICMPv6 (58) payload length:
56) fe80::2e0:b4ff:fe68:f895 > ff02::1: [icmp6 sum ok] ICMP6, router
advertisement, length 56
hop limit 64, Flags [none], pref medium, router lifetime 1800s,
reachable time 0ms, retrans timer 0ms
Hi Karl,
What if you use a = instead of the #? For example :vltime=86400:
I set rdnss and dnssl using = and that works.
John
On Thu, 24 Jul 2025 at 01:38, Karl Denninger wrote:
> On 7/23/2025 16:47, Bjoern A. Zeeb wrote:
>
> On Wed, 23 Jul 2025, Karl Denninger wrote:
>
> Hi,
>
> (sorry I del
On 7/23/2025 16:47, Bjoern A. Zeeb wrote:
On Wed, 23 Jul 2025, Karl Denninger wrote:
Hi,
(sorry I deleted the message as the tex/only part was barely parsable).
Can you, for testing, try adding an
addr="xxx:xxx:xxx:::":\
to one of your entries and see if the behaviour changes?
/bz
r
On Wed, 23 Jul 2025, Karl Denninger wrote:
Hi,
(sorry I deleted the message as the tex/only part was barely parsable).
Can you, for testing, try adding an
addr="xxx:xxx:xxx:::":\
to one of your entries and see if the behaviour changes?
/bz
--
Bjoern A. Zeeb
Roy Marples writes:
Hi Roy
> As Eugene said, you can use dhcpcd in ports with the slaac directive like so
>
> interface bge0
>slaac token ::dead:beef
>
> Then you get ::dead:beef appended to each autoconf address from the RA.
> You could use ::1 for your token which should meet your needs as
Am Fri, 21 Feb 2025 10:44:12 +
Bob Bishop schrieb:
> Hi,
>
> > On 21 Feb 2025, at 06:52, A FreeBSD User wrote:
> >
> > Hello,
> >
> > Linux (especially OpenWRT we use) knows about a concept named "IPv6
> > tokenized interface
> > identifier". The concept is self explanatory, a interface/
On 2/21/2025 18:15, Roy Marples wrote:
Well, it sounds good!
But I would rather you don't screw the pooch if the network fails and it's a
pain to recover :/
Saying that, you could setup a static address on the box so you can get to it
over the LAN even if dhcpcd fails.
If it's the WAN interfa
On Fri, 21 Feb 2025 22:59:15 + Karl Denninger
wrote ---
> On 2/21/2025 14:18, Roy Marples wrote:
> Aha! On Fri, 21 Feb 2025 18:34:25 + Roy Marples
> wrote --- > On Fri, 21 Feb 2025 17:49:28 +
> Karl Denninger wrote --- > >
On 2/21/2025 14:18, Roy Marples wrote:
Aha!
On Fri, 21 Feb 2025 18:34:25 + Roy Marples wrote
---
> On Fri, 21 Feb 2025 17:49:28 + Karl
Denninger wrote ---
> > The issue that I had with it not configuring properly on a
cold boot, as far as I know, has no
Aha!
On Fri, 21 Feb 2025 18:34:25 + Roy Marples wrote
---
> On Fri, 21 Feb 2025 17:49:28 + Karl Denninger
> wrote ---
> > The issue that I had with it not configuring properly on a
> cold boot, as far as I know, has not been addressed -- unless there a
On Fri, 21 Feb 2025 17:49:28 + Karl Denninger
wrote ---
> The issue that I had with it not configuring properly on a cold
> boot, as far as I know, has not been addressed -- unless there are updates
> since you and I conversed on that point.
I was never able to repli
On 2/21/2025 12:47, Roy Marples wrote:
On Fri, 21 Feb 2025 06:52:33 + A FreeBSD
User wrote ---
> Linux has this feature since a while and I can not believe that FreeBSD
lacks such a feature.
Work on merging dhcpcd into FreeBSD has sadly stalled for reasons unknown.
https://revie
On Fri, 21 Feb 2025 06:52:33 + A FreeBSD User
wrote ---
> Linux has this feature since a while and I can not believe that FreeBSD
> lacks such a feature.
Work on merging dhcpcd into FreeBSD has sadly stalled for reasons unknown.
https://reviews.freebsd.org/D22012
Maybe some Free
Hi
On Fri, 21 Feb 2025 13:31:53 + Eugene Pereviazko
wrote ---
> 21.02.25 08:52, A FreeBSD User пише:
> > Hello,
> >
> > Linux (especially OpenWRT we use) knows about a concept named "IPv6
> > tokenized interface
> > identifier". The concept is self explanatory, a interface/rou
21.02.25 08:52, A FreeBSD User пише:
Hello,
Linux (especially OpenWRT we use) knows about a concept named "IPv6 tokenized
interface
identifier". The concept is self explanatory, a interface/router obtains a
propagated prefix
and the concept allows the explicit definition of the host portion.
On 1 March 2011 02:28, User Red35 wrote:
>
> I am getting started with IPv6 and I am trying to get rtadvd working on
> the carp interface but it is not working so far.
>
>
> ### I have carp failover between two firewalls. The default gateway for
> ### hosts internal to the firewall is 172.31.9
Jinmei-san,
Thank you for the response.
What I wonder is how one would define the "typical, default" case.
Although RFC 2461/2462 does not say much about it, I am having a hard
time seeing in which case it would be beneficial to advertise deprecated
prefixes as preferred by default.
On the other
> On Mon, 05 Feb 2007 16:56:49 -0800,
> "Eugene M. Kim" <[EMAIL PROTECTED]> said:
> Note that the two automatically configured addresses on em0 are still
> preferred, while the prefix 2001:470:1f01:3222::/64 is deprecated on the
> router.
> I believe rtadvd(8) should advertise deprecated
> On Fri, 18 May 2001 03:01:13 -0400,
> [EMAIL PROTECTED] said:
> I need the following information on the rtadvd daemon implementation.
> If no configuration file is created & we have given -s option with rtadvd from
>where will it construct the rtadvd information ( struct rainfo).
I
21 matches
Mail list logo
