[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Crash related to VLANs in Oct 18th -current
On 23/10/2017 11:28, Tom Ivar Helbekkmo wrote:
> Has something changed that makes dhcpcd now insist on listening to all
> interfaces (including the 802.1q trunk)?
I will try and improve the logic so it's only the relevant interfaces.
The change was made to allow IP address sharing on many interfaces via
DHCP without actually removing the IP address from the non active
This might have been over-zealous on my part.
> Can I make it not do that?
Currently not, no.
Hopefully I can change it so that no toggle for it is needed.
> Oh, and I notice that IPv6 generates a local address on wm0, as on
> everything else. That just looks weird on an 802.1q trunk. Is there a
> way to make it not do that?
I don't know anything about 802.1q trunks.
How can I tell that it is one, and why shouldn't it have a local address?
> # cat /etc/ifconfig.wm0
> media 100baseTX mediaopt full-duplex
> ip4csum tcp4csum udp4csum
> # ifconfig wm0
> wm0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> address: 00:13:72:f7:00:06
> media: Ethernet 100baseTX full-duplex
> status: active
> inet6 fe80::213:72ff:fef7:6%wm0/64 flags 0x0 scopeid 0x1
> Which VLAN is that IPv6 address on, anyway? :)
It's the address belonging to wm0 interface.
See my earlier query.
Even if dhcpcd is not used, if IPv6 is enabled in the kernel and
auto-link local is set for the interface (which it is by default and it
looks like you've not disabled it in ifconfig.wm0) then you would get
this address anyway.
Main Index |
Thread Index |