Adding to bugs@ for the non misc@ readers, it seems this is still
a problem:
https://marc.info/?l=openbsd-misc&m=152710944022541&w=2
Summarised: vlan on em, vlan has no IP, unless vlan has a second
"ifconfig up" the parent interface does not get put in promisc.
On 2018/04/21 11:36, David Dahlb
Am Friday, den 20.04.2018, 15:26 + schrieb Dahlberg, David:
> let me first try to confirm this on
> the real machine. Sometimes the VBox networking does funny stuff.
I cannot find any differences in the behaviour between 6.3-release and
6.3-stable. But indeed VBox is weird. I cannot reproduce
Am Saturday, den 21.04.2018, 11:36 +0200 schrieb David Dahlberg:
> Maybe something on the hardware side of the Intel NIC?
If I utter such words, I owe you at least a dmesg(8) from the machine,
where this happens. But my Shuttle with re(4) also needs an additional
invitation ("ifconfig vlanNN up")
Am Freitag, den 20.04.2018, 14:44 +0200 schrieb Stefan Sperling:
> On Fri, Apr 20, 2018 at 09:59:34AM +, david.dahlberg@fkie.fraunhof
> er.de wrote:
> > When using vether(4) in a bridge(4), unicast packets directed to
> > the
> > vether are not received.
>
> Please compile a kernel from the l
On Fri, Apr 20, 2018 at 09:59:34AM +, david.dahlb...@fkie.fraunhofer.de
wrote:
> When using vether(4) in a bridge(4), unicast packets directed to the
> vether are not received. I do not even see them at all in tcpdump. Neither
> on the vether, the bridge, nor any of the physical devices. Othe
>Synopsis: Unicast packet loss on bridge(4) combinations
>Category: kernel amd64
>Environment:
System : OpenBSD 6.3
Details : OpenBSD 6.3 (GENERIC) #100: Sat Mar 24 14:17:45 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compi
