Masanobu SAITOH <[email protected]> writes: > On 2016/03/07 21:12, Tobias Nygren wrote: >> [...] >> I'm not sure if this is relevant to the discussion, but I have a wm(4) >> device (8086:1502) on -current that does not work after boot. It comes >> to life only after running "tcpdump -n -i wm0" once.
That's interesting -- I'll try that on my Dell 2650, and see what happens. It didn't do anything for the Dell E6400 laptop, though. > It must be a bug! Could you tell me how you set up network interface > include vlan? (e.g. part of /etc/rc.conf, /etc/ifconfig.xxx, and the > output of "ifconfig -a) For my part, I simply do this (vlan0 being my primary internal LAN, and vlan1 being the glue net facing my ISP): /etc/ifconfig.wm0: up media 100baseTX mediaopt full-duplex !sleep 30 /etc/ifconfig.vlan0: create vlan 10 vlanif wm0 inet 193.71.27.8 prefixlen 27 inet 193.71.27.5 prefixlen 27 alias inet 193.71.27.1 prefixlen 27 alias /etc/ifconfig.vlan1: create vlan 11 vlanif wm0 inet 81.0.129.41 prefixlen 30 !route -q add default 81.0.129.42 /etc/ifconfig.vlan2: create vlan 12 vlanif wm0 inet 172.27.201.1 prefixlen 24 /etc/ifconfig.vlan3: create vlan 13 vlanif wm0 inet 172.27.202.1 prefixlen 24 -tih -- Elections cannot be allowed to change anything. --Dr. Wolfgang Schäuble
