On Tue, Nov 17, 2020 at 8:15 AM Mihai Popescu wrote:
> Lee Nelson wrote:
>
> > If I have multiple USB Ethernet adapters of identical make and model,
> > how does OpenBSD distinguish them over time.
>
> Is this happening to APU with same hardware interfaces, too?
>
No, 'wired in' interfaces are
Lee Nelson wrote:
> If I have multiple USB Ethernet adapters of identical make and model,
> how does OpenBSD distinguish them over time.
Is this happening to APU with same hardware interfaces, too?
On 2020-10-22, Lee Nelson wrote:
> And Theo's hint was spot on. I'm experimenting with arm64 on an RPI 4.
> Stability is not one of my expectations.
I would actually expect pi4 and the onboard bse(4) to be fairly stable.
Stability with USB is likely to be less good. (The onboard nic is also
dec
2020-10-22 07:35, Stuart Longland wrote:
PCIe devices _can_ be connected to a
Raspberry Pi 4, but it's a rather hap-hazard process that's not
recommended unless you _really_ like re-working high-speed data links
on
printed circuit boards.
Closest you get on a 'Pi is maybe some of the SPI Ether
On 22/10/20 1:08 pm, Lee Nelson wrote:
> The same sort of thing happened to me with me PCI cards, but it was
> another edge case. I had two identical 2-port NIC's representing
> em0-em3. The card with em0 and em1 died and brought the syste down with
> a kernel panic. Upon rebooting the card that
The same sort of thing happened to me with me PCI cards, but it was
another edge case. I had two identical 2-port NIC's representing em0-em3.
The card with em0 and em1 died and brought the syste down with a kernel
panic. Upon rebooting the card that had been em2 and em3 was now em0 and
em1
I thought we were free to worship our totalitarian leader, butt an all, on and
off list. This is, after all, not a linux list. :)
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, 21 October 2020 22:08, Stuart Longland
wrote:
> On 21/10/20 10:53 pm, pipus wro
On 21/10/20 10:53 pm, pipus wrote:
> but Theo your butt is magical :(
Perhaps you can worship it off list then. ;-)
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
but Theo your butt is magical :(
You do it no justice.
I have a microwave that is a bit glitchy .
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, 21 October 2020 07:42, Theo de Raadt wrote:
> Stuart Longland stua...@longlandclan.id.au wrote:
>
> > On 21/1
Stuart Longland wrote:
> On 21/10/20 9:55 am, Lee Nelson wrote:
> >> Alternatively use a single nic with vlans, and break out to separate
> >> ports on a managed switch.
> >>
> > Yes, that could work too, but this is one side of a pfsync/carp
> > redundant firewall setup, so I want to keep it as
On 21/10/20 9:55 am, Lee Nelson wrote:
>> Alternatively use a single nic with vlans, and break out to separate
>> ports on a managed switch.
>>
> Yes, that could work too, but this is one side of a pfsync/carp
> redundant firewall setup, so I want to keep it as simple as possible.
Silly question,
On Tue, 20 Oct 2020, Stuart Henderson wrote:
On 2020-10-20, Lee Nelson wrote:
The only real solution here, aside from using better hardware, seems to be
to use adapters with different drivers. That is the approach I'm trying
next.
Alternatively use a single nic with vlans, and break out
On 2020-10-20, Lee Nelson wrote:
> The only real solution here, aside from using better hardware, seems to be
> to use adapters with different drivers. That is the approach I'm trying
> next.
Alternatively use a single nic with vlans, and break out to separate
ports on a managed switch.
On Tue, 20 Oct 2020, Aaron Mason wrote:
On Tue, Oct 20, 2020 at 12:29 PM Lee Nelson wrote:
On Mon, 19 Oct 2020, Allan Streib wrote:
Lee Nelson writes:
I had considered some late-running script that would query the MAC's of
each NIC and then configure them accordingly or rewrite the
On Tue, Oct 20, 2020 at 12:29 PM Lee Nelson wrote:
>
>
>
> On Mon, 19 Oct 2020, Allan Streib wrote:
>
> > Lee Nelson writes:
> >
> >> I had considered some late-running script that would query the MAC's of
> >> each NIC and then configure them accordingly or rewrite the hostname.*
> >> files and
On Mon, 19 Oct 2020, Allan Streib wrote:
Lee Nelson writes:
I had considered some late-running script that would query the MAC's of
each NIC and then configure them accordingly or rewrite the hostname.*
files and call netstart on them, but that just seems sloppy and
unreliable.
What abou
Lee Nelson writes:
> I had considered some late-running script that would query the MAC's of
> each NIC and then configure them accordingly or rewrite the hostname.*
> files and call netstart on them, but that just seems sloppy and
> unreliable.
What about DHCP? It supports MAC-specific confi
On Mon, 19 Oct 2020, Theo de Raadt wrote:
Lee Nelson wrote:
If I have multiple USB Ethernet adapters of identical make and model,
how does OpenBSD distinguish them over time.
In the order their drivers reach "interface attach" code. There are
multiple reasons the drivers could reach thi
Lee Nelson wrote:
> If I have multiple USB Ethernet adapters of identical make and model,
> how does OpenBSD distinguish them over time.
In the order their drivers reach "interface attach" code. There are
multiple reasons the drivers could reach this out of order.
> In other words if
> there's
If I have multiple USB Ethernet adapters of identical make and model, how
does OpenBSD distinguish them over time. In other words if there's a
reboot or the adapters get unplugged and moved around and plugged back in,
is there a way to make sure that the adapters associated with axen0 and
a
20 matches
Mail list logo
