> On 9/30/24 19:36, Jamie Landeg-Jones wrote:
> > Kyle Evans wrote:
> >
> >> It might be that the better long-term approach is to teach updatedb.sh
> >> how to drop privileges and push that out of the periodic script to avoid
> >> surprises like this from the different execution environments. Th
> On Sun, Sep 29, 2024 at 02:13:01PM +, Gary Jennejohn wrote:
>
> >I personally have been using a customized kernel configuration file for
> >25 years or more and I have no intention of changing it.
> >
> >Just because INET6 shows up in all the boilerplate config files doesn't
> >change the fa
> Shawn Webb writes:
>
> > While probably less efficient than just running the tools outright, I
> > usually just set up a tmpfs that I chroot into and install those kinds
> > of packages.
>
> Yeah, I do something similar, with the footnote that I more often than
> not have no internet connection
> On Thu, Jul 11, 2024 at 5:49?PM Rodney W. Grimes <
> freebsd-...@gndrsh.dnsmgr.net> wrote:
>
> > > My bhyve VMs have been all fine until now.
> > > I can't ping them and can't SSH into them. However, I can connect to them
> > > wi
> My bhyve VMs have been all fine until now.
> I can't ping them and can't SSH into them. However, I can connect to them
> with VNCViewer from a remote host (my PC from my house) :-(
>
> I haven't done any changes on the host at all.
> dnsmasq is running, but seems like the VMs aren't getting the
> On 7/6/24 02:17, Rodney W. Grimes wrote:
> > Host A *still* has/had a port open, and that port can lingere
> > for several reasons, and that can cause issues.
> >
> > Ok, good, check both A and B.
>
> I had checked this too: neither A nor B had the port stil
> On 7/5/24 16:32, Rodney W. Grimes wrote:
>
> >> However, I just changed UDP port and it seems to work!
>
> The "solution" didn't last: after a little more than 3 hours, this
> tunnel stopped working again :(
>
> Strangely restartin
> On 7/5/24 11:31, Ronald Klop wrote:
>
> > Of course this can be a firewall or routing issue somewhere in between
> > the hosts blocking traffic from B to A.
>
> Hmm...
> The two hosts can communicate with any other protocol.
> Also the VPN can handshake, so packets are exchanged correctly.
> I
> On Sun, Jun 30, 2024 at 8:23?AM Rodney W. Grimes
> wrote:
> >
> > > On Fri, Jun 28, 2024 at 6:26?PM Rick Macklem
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I've installed FreeBSD current in a bhvye
> This could be the project that you are interested in :
>
> https://github.com/quickemu-project/quickemu
Or perhaps just make netboot.xyz run ontop of PXE in bhyve???
https://netboot.xyz
(This is actually rather simple to do, use the PXE built into
bhyve ED2K to load a full featured iPXE (alrea
> On Fri, Jun 28, 2024 at 6:26?PM Rick Macklem wrote:
> >
> > Hi,
> >
> > I've installed FreeBSD current in a bhvye instance. Everything
> > went ok, with UFS as a root partition.
> > Then I created a zpool in another partition...
> > - Now, every time I boot it I have to
> > OK set currdev=disk
> On Fri, Jun 14, 2024 at 06:42:09AM GMT, Rodney W. Grimes wrote:
> > > "Poul-Henning Kamp" writes:
> > >
> > > > Defaulting to a /8 netmask for 192.168.x.y does not make *any* sense
> > > > ever.
> > >
> > > Well, no
> On Fri, 14 Jun 2024 at 11:13, Rodney W. Grimes
> wrote:
> >
> > That section is about how the router responds to an ICMP redirect
> > set to IT, not one that is going THROUGH it.
>
> Sorry I wasn't explicit, in all cases I'm talking about ICMP REDIRECTs
> On Fri, 14 Jun 2024 at 09:52, Rodney W. Grimes
> wrote:
> > >
> > > I would argue that having IP forwarding enabled (i.e.
> > > net.inet.ip.forwarding for IPv4) is what establishes FreeBSD as a
> > > router, and ICMP REDIRECT messages are al
> > > > Discarding ICMP redirects on a internet host is non-conformant with
> > > > STD-3 via rfc-1122. Processing of ICMP rediects is a MUST for hosts.
> > >
> > > In that case our default of "auto" is non-conformant if you have a
> > > routing daemon.
> >
> > NO, because then your not subject to
> On Wed, 12 Jun 2024 at 18:05, Chris wrote:
> >
> > As Rodeney already effectively explains; dropping packets makes routing,
> > and discovery exceedingly difficult. Which is NOT what the average user
> > wants,
>
> This is on end hosts only, not routers (which already drop ICMP REDIRECT).
Prob
> "Poul-Henning Kamp" writes:
>
> > Defaulting to a /8 netmask for 192.168.x.y does not make *any* sense ever.
>
> Well, not in the last 30 years or so, anyway.
No, never ever did /8 make since on 192.*.*.*, that has always been
class C address space.
--
Rod Grimes
[ Charset UTF-8 unsupported, converting... ]
> On Thu, 13 Jun 2024 at 09:39, Rodney W. Grimes
> wrote:
> >
> > Discarding ICMP redirects on a internet host is non-conformant with
> > STD-3 via rfc-1122. Processing of ICMP rediects is a MUST for hosts.
>
> In that
> I propose that we start dropping inbound ICMP REDIRECTs by default, by
> setting the net.inet.icmp.drop_redirect sysctl to 1 by default (and
> changing the associated rc.conf machinery). I've opened a Phabricator
> review at https://reviews.freebsd.org/D45102.
>
> ICMP REDIRECTs served a useful
> On 2024-06-12 15:05, Chris wrote:
> > On 2024-06-12 14:47, Rodney W. Grimes wrote:
> >>> I propose that we start dropping inbound ICMP REDIRECTs by default, by
> >>> setting the net.inet.icmp.drop_redirect sysctl to 1 by default (and
> >>> changing t
> I propose that we start dropping inbound ICMP REDIRECTs by default, by
> setting the net.inet.icmp.drop_redirect sysctl to 1 by default (and
> changing the associated rc.conf machinery). I've opened a Phabricator
> review at https://reviews.freebsd.org/D45102.
I propse that we NOT do this. If y
>
> Michael Gmelin writes:
>
> > You can do an interface route hack
>
> I think you misunderstand the situation.
>
> We are talking about people who have /etc/rc.conf files which relied
> on how default netmasks have worked for nearly three decades,
>
> Now that we have changed that de
> Scott writes:
> > Anyway, fun's over. Perhaps this is a greater lesson that the Foundation
> > provide the rules under which code is added or removed from base and then
> > we'd all be the wiser.
>
> The FreeBSD Foundation does not set project policy, the FreeBSD Core
> Team does.
Sadly tha
> > of course, gethostid(3) is now deprecated in favour of sysctl(3), and the
> > hostid(8) command is gone, and there's now more than one flavour of
> > Internet-capable UNIX in the world, and there's more than one Internet
> > address family now. so what i did in 1990 is a guide only inasmuch as
> Short version:
>
> Using FreeBSD as a BGP router has network issues caused by suboptimal
> default IPv4 source address selection when connected to Internet
> Exchanges (which are required to use IPs that aren't routable on the
> Internet). I was hoping to find more elegant workarounds or encour
> I get the following error "arpresolve: can't allocate llinfo for 1.1.245.192
> on vlan320" I can't explain. (IP edited). I only setup 1.1.245.192/31 between
> this vlan which parent is a VF from a MLX5EN(4) card .
>
> I am using a generated mac address and distribute IPs over OSPF with bird.
> Hello, I have a problem with the installation of OPNSense 24.1. I am unable
> to activate the Ethernet port BCM57416 NetXtreme-E Dual-Media 10G RDMA
> Ethernet Controller.
>
> He doesn't recognize them, does anyone have a solution?
>
> The same problem with Realtek Semi conductor co. RTL8125
[ Charset UTF-8 unsupported, converting... ]
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276463
>
> Rebecca Cran changed:
>
>What|Removed |Added
>
> CC|
> Am 26.01.24 um 17:09 schrieb Rodney W. Grimes:
> >> Am 25.01.24 um 16:38 schrieb Ed Maste:
> >>> On Wed, 24 Jan 2024 at 12:30, Warner Losh wrote:
> >>> sbin/growfs/tests/legacy_test.pl
> >>> tools/regression/msdosfs/msdosfstest-2.sh
> >>
> On Fri, Jan 26, 2024 at 9:17?AM Rodney W. Grimes <
> freebsd-...@gndrsh.dnsmgr.net> wrote:
>
> > [ Charset UTF-8 unsupported, converting... ]
> > > On Thu, Jan 25, 2024, 10:49?AM Rodney W. Grimes <
> > > freebsd-...@gndrsh.dnsmgr.net> wrote:
>
>
>
> > On 26. Jan 2024, at 18:02, Rodney W. Grimes
> > wrote:
> >
> > -- Start of PGP signed section.
> >> Am 2024-01-25 18:49, schrieb Rodney W. Grimes:
> >>>> On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote:
> >>>>
[ Charset UTF-8 unsupported, converting... ]
> On Thu, Jan 25, 2024, 10:49?AM Rodney W. Grimes <
> freebsd-...@gndrsh.dnsmgr.net> wrote:
>
> > > On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote:
> > >
> > > > On Thu, 25 Jan 2024 at 11:00, Rodney W. Grime
> Am 25.01.24 um 16:38 schrieb Ed Maste:
> > On Wed, 24 Jan 2024 at 12:30, Warner Losh wrote:
> >>
> >> Those are the only users in the tree, but not for long :)
> >
> > I have some reviews open to remove some old fdisk / diskabel /
> > bsdlabel invocations from the tree.
> >
> > With those appl
-- Start of PGP signed section.
> Am 2024-01-25 18:49, schrieb Rodney W. Grimes:
> >> On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote:
> >>
> >> > On Thu, 25 Jan 2024 at 11:00, Rodney W. Grimes
> >> > wrote:
> >> > >
> >> > &
> On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote:
>
> > On Thu, 25 Jan 2024 at 11:00, Rodney W. Grimes
> > wrote:
> > >
> > > > These will need to be addressed before actually removing any of these
> > > > binaries, of course.
> > >
> On Wed, 24 Jan 2024 at 12:30, Warner Losh wrote:
> >
> > Those are the only users in the tree, but not for long :)
>
> I have some reviews open to remove some old fdisk / diskabel /
> bsdlabel invocations from the tree.
>
> With those applied, for fdisk I see the following references
> (exclud
> I would agree personally, to moving to ports (eg ports/sysutils) with
> a DEPRECATED in the DESCR or something, or better yet a Make
> invokation event to say "superceded, here is how to proceed against
> advice") or something.
They are totally useless as ports when your booted from install
medi
> On Wed, Jan 24, 2024 at 8:45?AM Ed Maste wrote:
>
> > MBR (PC BIOS) partition tables were historically maintained with
> > fdisk(8), but gpart(8) has long been the preferred method for working
> > with partition tables of all types. fdisk has been declared as
> > obsolete in the man page since
> Am 2024-01-10 22:49, schrieb Mark Millard:
>
> > I never use atime, always noatime, for UFS. That said, I'd never
> > propose
> > changing the long standing defaults for commands and calls. I'd avoid:
>
> [good points I fully agree on]
>
> There's one possibility which nobody talked about yet
> Olivier Certner wrote on
> Date: Wed, 10 Jan 2024 10:01:48 UTC :
>
> > What I'm saying is that, based on others' input so far, my own (long, even
> > if not as long as yours) experience and some late reflection, is that
> > "noatime" should be the default (everywhere, all mounts and all FSes)
> On 2023-12-23 10:17, Ceri Davies wrote:
> > I really don?t like the idea of adding flags that make the program ignore a
> > config file. I also think this is premature until ZFS installs are default
> > on all architectures.
> >
> > However, if you must (and I see you have) change this, pleas
> On 2023-12-23 06:52, Konstantin Belousov wrote:
> > On Fri, Dec 22, 2023 at 11:18:23PM -0800, Xin Li wrote:
> >> Hi,
> >>
> >> Inspired by D42961, I propose that we move forward with disabling the
> >> compression by default in newsyslog, as implemented in
> >> https://reviews.freebsd.org/D43169
> On Mon, 23 Oct 2023 at 11:06, Rodney W. Grimes
> wrote:
> >
> > This is a regression of forms... I have been using ventoy to boot FreeBSD
> > since 12 or so and this is the first I have heard of a failure to boot
> > FreeBSD with Ventoy, so my ask is, what change
> On Mon, 16 Oct 2023 at 13:46, Gy?rgy P?sztor
> wrote:
> >
> >> I am interested in looking for a way to make Ventoy support more
> >> reliable, but that will not happen for 14.0.
> >
> > Is it depending on Ventoy?
>
> Yes, Ventoy needs to be updated for newer FreeBSD releases. For more info,
>
> I love that there are oh, 700+ people on these mailing lists, but we
> have zero visibility due to google not indexing them, where hackernews
> does. This is going to be an issue dominating the web (again, sadly)
> for a few weeks at least, and it would really help to be doing it
> there, rather
> I love that there are oh, 700+ people on these mailing lists, but we
> have zero visibility due to google not indexing them, where hackernews
> does. This is going to be an issue dominating the web (again, sadly)
> for a few weeks at least, and it would really help to be doing it
> there, rather
> I love that there are oh, 700+ people on these mailing lists, but we
> have zero visibility due to google not indexing them, where hackernews
> does. This is going to be an issue dominating the web (again, sadly)
> for a few weeks at least, and it would really help to be doing it
> there, rather
> On Sat, Jul 1, 2023 at 12:23?AM Rodney W. Grimes
> wrote:
> >
> > > This paper does a really good job of measuring the impacts of tcp
> > > cross traffic, including BBRv2, against the videoconferencing
> > > subsystems in signal, telegram, and whatsapp.
&
> This paper does a really good job of measuring the impacts of tcp
> cross traffic, including BBRv2, against the videoconferencing
> subsystems in signal, telegram, and whatsapp.
Did I miss something? The paper only shows a dumb bell topology with
instream traffic, I did not see any cross flow t
> On Sat, Jul 1, 2023 at 12:23?AM Rodney W. Grimes
> wrote:
> >
> > > This paper does a really good job of measuring the impacts of tcp
> > > cross traffic, including BBRv2, against the videoconferencing
> > > subsystems in signal, telegram, and whatsapp.
&
> This paper does a really good job of measuring the impacts of tcp
> cross traffic, including BBRv2, against the videoconferencing
> subsystems in signal, telegram, and whatsapp.
Did I miss something? The paper only shows a dumb bell topology with
instream traffic, I did not see any cross flow t
> On Mon, Jun 26, 2023 at 7:50?AM Vitaliy Gusev wrote:
> >
> > Hi Aryeh,
> >
> > Have you wired a guest memory with bhyve's -S option?
> >
> > -S Wire guest memory
> >
> >
> > Anyway, OS does not have another choice than kill a process to free some
> > memory
> > when RAM+swap is fully u
> The branch main has been updated by grahamperrin:
>
> URL:
> https://cgit.FreeBSD.org/src/commit/?id=6469f9c595c609dd552ec198a16c471c87df7c57
>
> commit 6469f9c595c609dd552ec198a16c471c87df7c57
> Author: Graham Perrin
> AuthorDate: 2023-06-10 08:41:35 +
> Commit: Graham Perrin
>
> The branch main has been updated by grahamperrin:
>
> URL:
> https://cgit.FreeBSD.org/src/commit/?id=6469f9c595c609dd552ec198a16c471c87df7c57
>
> commit 6469f9c595c609dd552ec198a16c471c87df7c57
> Author: Graham Perrin
> AuthorDate: 2023-06-10 08:41:35 +
> Commit: Graham Perrin
>
> >
> >
> > > On Jun 4, 2023, at 12:07 PM, Rodney W. Grimes
> > > wrote:
> > >
> > >> Hey ipfw folks ? Im skipping questions@ and asking this directly here,
> > >>
> > >> FreeBSD 12.4 (amd64)
> > >>
&
>
>
> > On Jun 4, 2023, at 12:07 PM, Rodney W. Grimes
> > wrote:
> >
> >> Hey ipfw folks ? Im skipping questions@ and asking this directly here,
> >>
> >> FreeBSD 12.4 (amd64)
> >>
> >> Assume a partial firewall rulese
> Hey ipfw folks ? Im skipping questions@ and asking this directly here,
>
> FreeBSD 12.4 (amd64)
>
> Assume a partial firewall ruleset like this:
>
> 00300 0 0 allow ip from any to any via lo0
> 00400 0 0 allow ip from any to any via lo1
> 00500 0 0 deny ip from any to 127.0.0.0/8 in
>
> It turns out all seven hosts in my cluster report
> a null password for root in /usr/src/etc/master.passwd:
> root::0:0::0:0:Charlie &:/root:/bin/sh
>
> Is that intentional?
No, but I suspect your build/update procedures are infact telling
the system to do this. Someone else pointed out etcupd
> On 26 May 2023, at 12:35, bob prohaska wrote:
>
> > While going through normal security email from a Pi2
> > running -current I was disturbed to find:
> >
> > Checking for passwordless accounts:
> > root::0:0::0:0:Charlie &:/root:/bin/sh
> >
> > The machine had locked up on a -j4 buildworld sinc
> On 12 May 2023, at 19:43, Rodney W. Grimes wrote:
>
> >> Rod and I discussed this, and I?m top-posting a summary of a proposal that
> >> we both support. I?ll leave the last message from the list below for
> >> reference. Our consensus is that the main proble
> On 12 May 2023, at 19:43, Rodney W. Grimes wrote:
>
> >> Rod and I discussed this, and I?m top-posting a summary of a proposal that
> >> we both support. I?ll leave the last message from the list below for
> >> reference. Our consensus is that the main proble
explicitly for pw to create the
> directory, and manually create a /home symlink if desired. If they have
> a small root file system, they will want to put home directories elsewhere.
>
> A followup change would be to change various man pages that refer to
> /usr/home.
>
&g
explicitly for pw to create the
> directory, and manually create a /home symlink if desired. If they have
> a small root file system, they will want to put home directories elsewhere.
>
> A followup change would be to change various man pages that refer to
> /usr/home.
>
&g
> On Thu, 11 May 2023 23:08:30 +0200
> Yuri wrote:
>
> > Warner Losh wrote:
> > >
> > >
> > > On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes
> > > mailto:freebsd-...@gndrsh.dnsmgr.net>>
> > > wrote:
> > >
> > &g
> On Thu, May 11, 2023, 2:16 PM Yuri wrote:
>
> > Warner Losh wrote:
> > > The branch main has been updated by imp:
> > >
> > > URL:
> > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0
> > >
> > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0
> > > Author: W
> On 11 May 2023, at 9:58, Rodney W. Grimes wrote:
>
> >> On Wed, 10 May 2023 16:48:12 -0500
> >> Mike Karels wrote:
> >>
> >>> On 10 May 2023, at 10:13, Cy Schubert wrote:
> >>>
> >>>> In message , Mitchell
>
> On 11 May 2023, at 9:58, Rodney W. Grimes wrote:
>
> >> On Wed, 10 May 2023 16:48:12 -0500
> >> Mike Karels wrote:
> >>
> >>> On 10 May 2023, at 10:13, Cy Schubert wrote:
> >>>
> >>>> In message , Mitchell
>
> On Wed, 10 May 2023 16:48:12 -0500
> Mike Karels wrote:
>
> > On 10 May 2023, at 10:13, Cy Schubert wrote:
> >
> > > In message , Mitchell
> > > Horne w
> > > rites:
> > >> On 5/10/23 11:19, Rodney W. Grimes wrote:
> > >
> On Wed, 10 May 2023 16:48:12 -0500
> Mike Karels wrote:
>
> > On 10 May 2023, at 10:13, Cy Schubert wrote:
> >
> > > In message , Mitchell
> > > Horne w
> > > rites:
> > >> On 5/10/23 11:19, Rodney W. Grimes wrote:
> > >
> The branch main has been updated by mhorne:
>
> URL:
> https://cgit.FreeBSD.org/src/commit/?id=36db6b04962a01ff7b21592def02d4c570dac939
>
> commit 36db6b04962a01ff7b21592def02d4c570dac939
> Author: Mitchell Horne
> AuthorDate: 2023-05-10 12:53:56 +
> Commit: Mitchell Horne
> Comm
> The branch main has been updated by mhorne:
>
> URL:
> https://cgit.FreeBSD.org/src/commit/?id=36db6b04962a01ff7b21592def02d4c570dac939
>
> commit 36db6b04962a01ff7b21592def02d4c570dac939
> Author: Mitchell Horne
> AuthorDate: 2023-05-10 12:53:56 +
> Commit: Mitchell Horne
> Comm
Second attempt, first one failed due to not being a member
of the list :-(.
> Adding freebsd-transp...@freebsd.org to get that specific groups
> eyes on this issue.
>
> Rod
>
> > As per newreno_ack_received() in sys/netinet/cc/cc_newreno.c,
> > FreeBSD TCP sender strictly follows RFC 5681 with R
Second attempt, first one failed due to not being a member
of the list :-(.
> Adding freebsd-transp...@freebsd.org to get that specific groups
> eyes on this issue.
>
> Rod
>
> > As per newreno_ack_received() in sys/netinet/cc/cc_newreno.c,
> > FreeBSD TCP sender strictly follows RFC 5681 with R
Adding freebsd-transp...@freebsd.org to get that specific groups
eyes on this issue.
Rod
> As per newreno_ack_received() in sys/netinet/cc/cc_newreno.c,
> FreeBSD TCP sender strictly follows RFC 5681 with RFC 3465 extension
> That is, during slow-start, when receiving an ACK of 'bytes_acked'
>
>
> On Wed, 26 Apr 2023, Rodney W. Grimes via Starlink wrote:
>
> > Now that water cooled steel plate, if you treat it like a sacrificial
> > anode in a water heater, ie you expect it to be erroded over time it
> > could get interesting.
>
> They are designing towar
> I found it interesting that the pad was constructed of Fondag. This is pure
> calcium aluminate cement. The cement and aggregate are both made of the
> same clinker, there's just a difference in size of the particles. The
> aggregate doesn't simply have a physical bond to the cement, there is a
>
> On Wed, Apr 26, 2023 at 1:41?PM Rodney W. Grimes
> wrote:
> >
> > > As always I enjoy the flood of information we get on this list!
> > >
> > > still, so far, my research on a nitrogen deluge system (instead of
> > > water) has come up emp
> As always I enjoy the flood of information we get on this list!
>
> still, so far, my research on a nitrogen deluge system (instead of
> water) has come up empty for me, except as a fire suppressant. So it?s
> either crazy or brilliant. Or both! I really liked the idea of
> something cooler that
> The article about the ASCEND project says:
> "Very low ambient temperatures in space will dramatically reduce the need
> for cooling equipment that consumes enormous amounts of energy. A
> significant part of a data center?s energy use is for cooling equipment,
> accounting for more than 50% in s
> On Sun, 16 Apr 2023, David Fern?ndez via Starlink wrote:
>
> > The idea would be that the satellite inspects IP packets and when it
> > detects a DNS query, instead of forwarding the packet to ground
> > station, it just answers back to the sender of the query.
>
> This would be a bad way to im
> On Fri, Apr 14, 2023 at 12:36?PM David Lang wrote:
> >
> > On Fri, 14 Apr 2023, Rodney W. Grimes via Starlink wrote:
> >
> > >> I keep wondering when or if Nasa will find a way to move their DNS
> > >> root server "up there" . DNS
> "The Kepler Network will streamline on-orbit communications with a
> network infrastructure designed to act as Internet exchange points
> (IXP) for space-to-space data relay. The Internet-ready constellation
> will deliver data to and from spacecraft in real time, enabling
> high-speed data relay
> On Fri, Apr 7, 2023 at 12:08?PM Warner Losh wrote:
> >
> >
> >
> > On Fri, Apr 7, 2023 at 6:20?AM Poul-Henning Kamp
> > wrote:
> >>
> >>
> >> Alan Somers writes:
> >> > On Fri, Apr 7, 2023 at 2:22=E2=80=AFAM Poul-Henning Kamp
> >> > wrote:
> >>
> >> > > I would expect them to be lim
> > On 3. Mar 2023, at 14:52, Rodney W. Grimes
> > wrote:
> >
> >>> On 2. Mar 2023, at 18:20, Rodney W. Grimes
> >>> wrote:
> >>>
> >>>>> On 2. Mar 2023, at 02:24, Rodney W. Grimes
> >>>>> wrote:
&
[ Charset UTF-8 unsupported, converting... ]
> "Rodney W. Grimes" writes:
> > I've read a few of the linux how to's on running unbound chrooted and
> > it leads me to belive that /etc/unbound/unbound.conf is the correct
> > value of the path to the
[ Charset UTF-8 unsupported, converting... ]
> "Rodney W. Grimes" writes:
> > I've read a few of the linux how to's on running unbound chrooted and
> > it leads me to belive that /etc/unbound/unbound.conf is the correct
> > value of the path to the
> > On 2. Mar 2023, at 18:20, Rodney W. Grimes
> > wrote:
> >
> >>> On 2. Mar 2023, at 02:24, Rodney W. Grimes
> >>> wrote:
> >>>
> >>>> Hi group,
> >>>>
> >>>> Maybe someone
> > On 2. Mar 2023, at 02:24, Rodney W. Grimes
> > wrote:
> >
> >> Hi group,
> >>
> >> Maybe someone can help me with this question - as I am usually only
> >> looking at L4 and the top side of L3 ;)
> >>
> >>
> Hi group,
>
> Maybe someone can help me with this question - as I am usually only
> looking at L4 and the top side of L3 ;)
>
> In order to validate a peculiar switches behavior, I want to adjust some
> fields in gracious arps sent out by an interface, after a new IP is
> assigned or changed
> The branch main has been updated by des:
>
> URL:
> https://cgit.FreeBSD.org/src/commit/?id=cb96a0ef0040fa7968245ab203ab70a7ed2d275d
>
> commit cb96a0ef0040fa7968245ab203ab70a7ed2d275d
> Author: Dag-Erling Sm?rgrav
> AuthorDate: 2023-02-03 15:37:24 +
> Commit: Dag-Erling Sm?rgrav
> The branch main has been updated by des:
>
> URL:
> https://cgit.FreeBSD.org/src/commit/?id=cb96a0ef0040fa7968245ab203ab70a7ed2d275d
>
> commit cb96a0ef0040fa7968245ab203ab70a7ed2d275d
> Author: Dag-Erling Sm?rgrav
> AuthorDate: 2023-02-03 15:37:24 +
> Commit: Dag-Erling Sm?rgrav
>
> Emmanuel Vadot writes:
> > On Thu, 02 Feb 2023 20:58:58 +
> > "Poul-Henning Kamp" wrote:
> >
> > >
> > > parv/FreeBSD writes:
> > >
> > > > > Does backlight(8) works for you?
> > > >
> > > > Thanks for the clue. It does! It does ...
> > > >
> > > > - I get the same numbe
> In message <202301181645.30igj4ra010...@gndrsh.dnsmgr.net>, "Rodney W.
> Grimes"
> writes:
> > > > In message <202301181551.30ifpbru010...@gndrsh.dnsmgr.net>, "Rodney W.
> > > > Grimes"
> In message <202301181645.30igj4ra010...@gndrsh.dnsmgr.net>, "Rodney W.
> Grimes"
> writes:
> > > > In message <202301181551.30ifpbru010...@gndrsh.dnsmgr.net>, "Rodney W.
> > > > Grimes"
> > In message <202301181551.30ifpbru010...@gndrsh.dnsmgr.net>, "Rodney W.
> > Grimes"
> > writes:
> > > [ Charset UTF-8 unsupported, converting... ]
> > > >
> > > >
> > > > > On 18 Jan 2023, at 16:34, Rodn
> > In message <202301181551.30ifpbru010...@gndrsh.dnsmgr.net>, "Rodney W.
> > Grimes"
> > writes:
> > > [ Charset UTF-8 unsupported, converting... ]
> > > >
> > > >
> > > > > On 18 Jan 2023, at 16:34, Rodn
> In message <202301181551.30ifpbru010...@gndrsh.dnsmgr.net>, "Rodney W.
> Grimes"
> writes:
> > [ Charset UTF-8 unsupported, converting... ]
> > >
> > >
> > > > On 18 Jan 2023, at 16:34, Rodney W. Grimes
> > > > wr
>
> In message <202301181551.30ifpbru010...@gndrsh.dnsmgr.net>, "Rodney W.
> Grimes"
> writes:
> > [ Charset UTF-8 unsupported, converting... ]
> > >
> > >
> > > > On 18 Jan 2023, at 16:34, Rodney W. Grimes
> > > > wr
>
[ Charset UTF-8 unsupported, converting... ]
>
>
> > On 18 Jan 2023, at 16:34, Rodney W. Grimes
> > wrote:
> >
> > No, otis fixed it thus:
> > -#define CONFIGFILE "/usr/local/etc/unbound/unbound.conf"
> > +#define CONFIGFILE "/var/unb
[ Charset UTF-8 unsupported, converting... ]
>
>
> > On 18 Jan 2023, at 16:34, Rodney W. Grimes
> > wrote:
> >
> > No, otis fixed it thus:
> > -#define CONFIGFILE "/usr/local/etc/unbound/unbound.conf"
> > +#define CONFIGFILE "/var/unb
1 - 100 of 1023 matches
Mail list logo
