On 2021/08/23 22:21, Klemens Nanni wrote:
> On Mon, Aug 23, 2021 at 07:03:45PM +0200, Solene Rapenne wrote:
> > pf.conf says this in QUEUEING
> > https://man.openbsd.org/pf.conf#QUEUEING
> >
> > > If the referenced queue does not exist on the outgoing interface,
> > > the default queue for that
On 2021/08/23 19:03, Solene Rapenne wrote:
> pf.conf says this in QUEUEING
> https://man.openbsd.org/pf.conf#QUEUEING
>
> > If the referenced queue does not exist on the outgoing interface,
> > the default queue for that interface is used.
>
> however, with this simple config
>
> queue std on
In rev 1.61, references to resolv.conf.tail were removed, so it appears that
this page is now meant to solely document resolv.conf, a single file. So that
makes this sentence make not-so-much sense:
The configuration options (which may be placed in either file) are:
Diff below removes
On Mon, Aug 23, 2021 at 07:03:45PM +0200, Solene Rapenne wrote:
> pf.conf says this in QUEUEING
> https://man.openbsd.org/pf.conf#QUEUEING
>
> > If the referenced queue does not exist on the outgoing interface,
> > the default queue for that interface is used.
This text is outdated, pfctl gained
pf.conf says this in QUEUEING
https://man.openbsd.org/pf.conf#QUEUEING
> If the referenced queue does not exist on the outgoing interface,
> the default queue for that interface is used.
however, with this simple config
queue std on re0 bandwidth 100M
queue lan parent std bandwidth 100M
queue
On Mon, Aug 23, 2021 at 08:18:13PM +0200, Alessandro De Laurenzis wrote:
> Greetings,
>
> I was reluctant to submit this patch, since I'm not a native English
> speaker and this could be a wordplay joke, but if not, and it is really
> citing the Latin phrase popularly attributed to Julius
So I was playing with a usb network adapter and noticed that dhcpleased
and slaacd would hold on to them when I unplugged them.
They would be listed as "unknown" because we can't find the if_name for
the if_index anymore.
Turns out we are not getting a RTM_IFINFO when an interface disappears
but
On Mon, Aug 23, 2021, Alessandro De Laurenzis wrote:
> and this could be a wordplay joke,
AFAICT it is.
--
Address is valid for this mailing list only, please do not reply
to it direcly, but to the list.
Greetings,
I was reluctant to submit this patch, since I'm not a native English
speaker and this could be a wordplay joke, but if not, and it is really
citing the Latin phrase popularly attributed to Julius Caesar (see e.g.
[1], but there are plenty on the net, of course), the wrong order
On 2021-08-22 18:36 -04, Scott Bennett wrote:
> Like the rad(8) and unwind(8) manuals do, add references to
> dhcpleased.conf(5) in the appropriate places.
Committed, thanks!
>
> Cheers,
> Scott
>
> diff 4ccbc464479218d5b5f4125325c4d9358f653323 /usr/src
> blob -
> Date: Mon, 23 Aug 2021 17:53:06 +0200
> From: Patrick Wildt
>
> Hi,
>
> so on the new Parallels version, when using the 'Other' OS setting,
> virtio(4) won't attach. Apparently it's not Virtio 1.0, because even
> Fedora 34 falls back to the 'legacy' driver.
>
> While our code expects (and
Hi,
so on the new Parallels version, when using the 'Other' OS setting,
virtio(4) won't attach. Apparently it's not Virtio 1.0, because even
Fedora 34 falls back to the 'legacy' driver.
While our code expects (and requires) an I/O BAR, it seems to be that
the PCI device only provides two memory
On Mon, Aug 23, 2021 at 08:57:59AM -0500, joshua stein wrote:
> On Sun, 22 Aug 2021 at 22:37:51 -0600, Thomas Frohwein wrote:
[...]
> > I thought I had the same problem on my new Asus Expertbook B9400CEA.
> > During boot, while reordering libraries and later it would print:
> >
> > dwiic2: timed
On Sun, 22 Aug 2021 at 22:37:51 -0600, Thomas Frohwein wrote:
> On Sun, Aug 22, 2021 at 09:50:15PM -0500, joshua stein wrote:
> > On a particular laptop with a touchpad behind ihidev, dwiic would
> > report a timeout every time it had to fetch touch data:
> >
> > dwiic0: timed out reading
14 matches
Mail list logo
