The subject is a console message from an IAP that I'm testing with. I tagged a vlan on the switch port connected to the IAP, and now I can't get to the IAP and airwave no longer sees it. It still gets an address from DHCP on the untagged/native vlan, but when I try to connect to it, the browser gets redirected to another IP address on the tagged VLAN. Anyone seen anything like this? I can't login via console, it doesn't accept any credentials, which makes me think maybe it's not the master in an IAP cluster. But there aren't supposed to be any other IAPs on the network. Below is the relevant conosle output.
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Dec 31 16:00:23 udhcpc[678]: send_discover: pkt num 1, secs 2
Dec 31 16:00:23 udhcpc[678]: Sending discover...
Dec 31 16:00:23 udhcpc[678]: send_selecting: pkt num 0, secs 0
Dec 31 16:00:23 udhcpc[678]: Sending select for 10.100.159.69...
Dec 31 16:00:23 udhcpc[678]: Lease of 10.100.159.69 obtained, lease time 28800
Dec 31 16:00:24 udhcpc[678]: DHCP OPT 43 deleted airwave config
10.100.159.69 255.255.254.0 10.100.158.1
Starting Webserver
[...]
asap_send_elected_master: sent successfully
wait for stm to initialize over
asap_send_elected_master: sent successfully
User: admin
Password:
User: admin
Password:
User: admin
Password:
User: