On Fri, 02 Aug 2024 23:05:33 +0100 Karl Denninger wrote ---
> This is what is typically in /etc/rc.conf:
I don't see anything wrong there.
> And in /usr/local/etc/dhcpcd.conf I have changed "duid" to
> "clientid" which appears to get a repeatable IPv4 IF the host
On Thu, 01 Aug 2024 16:24:54 +0100 Chris Ross wrote ---
>
> [Long message, apologies. Thoughts mostly after the log output.]
>
> > On Jul 24, 2024, at 04:12, Roy Marples r...@marples.name> wrote:
> > dhcpcd can indeed setup the internal networks within th
Roy Marples
On Wed, 31 Jul 2024 03:38:46 +0100 Karl Denninger wrote ---
> Starting dhcpcd.
> dhcpcd-10.0.8 starting
> igb0: link state changed to UP
> igb1: link state changed to UP
> no interfaces have a carrier
> Additio
On Tue, 30 Jul 2024 15:06:17 +0100 Karl Denninger wrote ---
> Ok so I have a "new problem" attempting to use dhcp6c for BOTH
> IPv4 and IPv6.
> This is the salient part of the configuration file (the rest is
> basically defaults):
> # Generate SLAAC address
On Sat, 27 Jul 2024 04:21:08 +0100 moto kawasaki wrote ---
>
> Hi Chris, all
>
> I am struggling the same problem too, and here is my working
> configuration for dhcp6c in my test environment.
> Hope this can be help.
>
>
> vtnet0 is uplink, where I expect to receive RA from I
On Wed, 24 Jul 2024 05:04:12 +0100 Chris Ross wrote ---
>
>
> > On Jul 23, 2024, at 13:23, Roy Marples r...@marples.name> wrote:
> > On Tue, 23 Jul 2024 18:11:18 +0100 cross+free...@distal.com wrote
> >
> >
> >> tl;dr; anyone
On Wed, 24 Jul 2024 02:48:15 +0100 Karl Denninger wrote ---
> I'd like to replicate this that is currently being sent up via
> dhcp6c, which is not quite-clear to me from the docs on how to do that.
> #
> # This configuration will attempt to get /56 or a /60 fr
Hi
On Tue, 23 Jul 2024 18:11:18 +0100 cross+free...@distal.com wrote
> tl;dr; anyone have a good IPv6 network setup based on an IA_PD from
> their provider? Any details or advice to share?
>
> The current router is x86_64 FreeBSD 11.x, but I’m building the FreeBSD
> 14.1 system to repl
Hi Mark
On Tue, 16 Jul 2024 21:04:27 +0100 Mark Johnston wrote ---
> Hello,
>
> When IPv6 SLAAC is configured for an interface, the kernel will update
> its default router list upon receipt of a router advertisement. In so
> doing it may install a default route; in the kernel this
Hi Ed
On Thu, 06 Jun 2024 02:48:36 +0100 Ed Maste wrote ---
> On Sun, 7 Aug 2022 at 01:32, Ben Woods woods...@freebsd.org> wrote:
> In the previous threads some objections were raised about dhcpcd's
> lack of sandboxing (Capsicum / privilege separation), which has since
> been address
On Mon, 08 Apr 2024 04:16:47 +0100 Anton Yudin wrote ---
> I'm running a FreeBSD 14 with two interfaces that use DHCP. I would like
> to make one of the interfaces to never set the default route. Right now the
> first interface to be fully up sets the default route.
>
> I tri
28.10.2023 23:21,
Roy Marples wrote:
> What you would do is open a route socket, then call getifaddrs and then
> listen on the route socket for new interfaces.
>
> Then you can maintain a list of current vlans and take action accordingly.
I'd like to be able to make a couple of system
Hi Dries
On 26/07/2020 09:30, driesm.michi...@gmail.com wrote:
Following the discussion a while ago regarding the import of a DHCPv6 client.
The current state of dhcpcd is such that capsicum and privelege separation is
fully implemented.
How do we move forward with this? I’d really like to
date some rtsock internals and will
take a look at this one.
Thank you for your suggestion!
There is a phabricator differential written by Roy Marples that does
this:
https://reviews.freebsd.org/D5469
Wow! Thank you for the pointing me to this review. Will look&test in a day or
two.
Hi Ben
On 30/11/2019 02:52, Ben Woods wrote:
I have just added the new port net/dhcpcd-devel which uses the latest commit
(273915d), and enables privilege separation.
If you would care to update port net/dhcpcd to dhcpcd-9.0.0 which I've just
released this discussion can move forwards again :
Hey Ben
On 30/11/2019 02:52, Ben Woods wrote:
I have just added the new port net/dhcpcd-devel which uses the latest
commit (273915d), and enables privilege separation.
So far it seems to be working ok for me!
Good!
I've had a fair bit of feedback from the initial commit and the latest
(whic
On 28/11/2019 22:50, Ben Woods wrote:
It is not yet enabled by default until he gets more feedback from others
that it is working ok. I intend to update the FreeBSD port to enable
this feature (perhaps with a “-devel” port) to allow it to be tested
more easily on FreeBSD.
Please add it as a n
On 13/10/2019 20:32, Hiroki Sato wrote:
Ben Woods wrote
in :
wo> On Fri, 11 Oct 2019 at 08:32, Ben Woods wrote:
wo> As promised, I have completed my initial work to import dhcpcd into FreeBSD
wo> base, and it is ready for review, testing and comment at the link below.
wo> https://reviews.fr
On 12/10/2019 03:04, Hiroki Sato wrote:
I emphasize again here that people who want to use dhcpcd are still
able to install net/dhcpcd and override a combination of utilities
such as rtsold. Ditto for ISC's IPv6-capable dhclient. My opinion
about the import is that if we adopt dhcpcd in
On 11/10/2019 20:40, Hiroki Sato wrote:
I do not have a strong objection on dhcpcd (I am using it on some of
my FreeBSD boxes actually) but let me explain the reason why I chose
wide-dhcp as the candidate. That is because it is a small,
functional DHCPv6-only implementation. I am planni
On 07/10/2019 20:20, Julian Elischer wrote:
> On 10/7/19 12:05 PM, Roy Marples wrote:
>> On 07/10/2019 19:45, Julian Elischer wrote:
>>> I'm not HRS, but as it uses netlink, how does NetBSD use it? (i.e.
>>> how do we simulate that?)
>>
>> d
On 07/10/2019 19:45, Julian Elischer wrote:
I'm not HRS, but as it uses netlink, how does NetBSD use it? (i.e. how
do we simulate that?)
dhcpcd has a driver per OS:
BSD == route(4)
Linux == netlink(3)
Solaris == route(4) along with an unholy mashup of streamio(7)
I try and keep OS specific de
22 matches
Mail list logo
