Date: Mon, 09 May 2022 15:18:04 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 263846] ng_bridge: can't ge an IP using DHCP when creating a vlan on an interface in the bridge Message-ID: <bug-263846-7501-NH2PCvkuj9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263846-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-263846-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263846 Lutz Donnerhacke <donner@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |donner@FreeBSD.org Assignee|net@FreeBSD.org |donner@FreeBSD.org Status|New |Open --- Comment #2 from Lutz Donnerhacke <donner@FreeBSD.org> --- ng_bridge is ethertype transparent, that means that vlan tagging is ignored. OTOH this may cause problems, if the same MAC address is used on different interfaces with different VLAN tags. I currently do not understand your setup. May I ask you to provide a bit mo= re about the netgraph topology? Something like the following: ``` # ngctl show bridge0: Name: bridge0 Type: bridge ID: 00000003 Num hooks: 2 Local hook Peer name Peer type Peer ID Peer hook=20= =20=20=20=20=20 ---------- --------- --------- ------- ---------=20= =20=20=20=20=20 link1 ngeth1 eiface 00000006 ether=20=20= =20=20=20=20=20=20=20=20 link0 ngeth0 eiface 00000005 ether=20=20= =20=20=20=20=20=20=20=20 # ifconfig ngeth0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1= 500 options=3D28<VLAN_MTU,JUMBO_MTU> ether 58:9c:fc:10:80:4d media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> ngeth1: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1= 500 options=3D28<VLAN_MTU,JUMBO_MTU> ether 58:9c:fc:10:ff:86 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> ngeth0.100: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 m= tu 1500 ether 58:9c:fc:10:80:4d inet 192.168.1.2 netmask 0xfffffff8 broadcast 192.168.1.7 groups: vlan vlan: 100 vlanproto: 802.1q vlanpcp: 0 parent interface: ngeth0 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> ngeth1.100: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 m= tu 1500 ether 58:9c:fc:10:ff:86 inet 192.168.2.3 netmask 0xfffffff8 broadcast 192.168.2.7 groups: vlan vlan: 100 vlanproto: 802.1q vlanpcp: 0 parent interface: ngeth1 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> ``` May I ask you to provide the bridge statistics? ``` # ngctl msg bridge0: getstats 0 Rec'd response "getstats" (4) from "[3]:": Args: { recvOctets=3D230 recvPackets=3D5 recvBroadcast=3D5 xmitOctets=3D552 xmitPackets=3D12 xmitBroadcasts=3D12 } # ngctl msg bridge0: getstats 1 Rec'd response "getstats" (4) from "[3]:": Args: { recvOctets=3D552 recvPackets=3D12 recvBroadcast=3D12 xmitOctets=3D230 xmitPackets=3D5 xmitBroadcasts=3D5 } ``` As you can see, the interfaces are mirroring each other: What is received on one link was transmitted to the other one. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263846-7501-NH2PCvkuj9>