Goatbert
New Around Here
Hello,
I've got my AC66U running in AP Mode with the latest stable release of Merlin's excellent firmware. However, I'm running into an issue - for some reason my wireless clients aren't able to connect, even though if I restore my old config and plug the router back into WAN connection they start working again. My best guess is it might not be passing DHCP packets to the clients? They don't show up in the DHCP logs (BIND running on a centos 6.4 box).
Pretty tired but I'll do some additional testing tomorrow. I've tried with the WAN port plugged into the network and with one of the LAN ports the result is identical. This is what is in the log, I suspect it has something to do with the problem but I'm so tired I can't think:
Apr 17 04:03:39 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:39 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:39 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:39 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:43 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:48 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:50 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:50 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:53 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:58 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:03 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:08 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:16 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:16 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:17 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:22 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:27 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:32 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:37 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:42 kernel: vlan1: received packet with own address as source address
Apr 17 04:05:59 kernel: vlan1: received packet with own address as source address
Apr 17 04:05:59 kernel: vlan1: received packet with own address as source address
Apr 17 04:05:59 kernel: vlan1: received packet with own address as source address
Apr 17 04:05:59 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:26 notify_rc : set_wltxpower;restart_wireless
Apr 17 04:06:28 kernel: device eth1 left promiscuous mode
Apr 17 04:06:28 kernel: br0: port 2(eth1) entering disabled state
Apr 17 04:06:28 kernel: device eth2 left promiscuous mode
Apr 17 04:06:28 kernel: br0: port 3(eth2) entering disabled state
Apr 17 04:06:28 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.39.31 (r341183)
Apr 17 04:06:28 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.30.39.31 (r341183)
Apr 17 04:06:29 kernel: device eth1 entered promiscuous mode
Apr 17 04:06:29 kernel: br0: port 2(eth1) entering learning state
Apr 17 04:06:29 kernel: br0: topology change detected, propagating
Apr 17 04:06:29 kernel: br0: port 2(eth1) entering forwarding state
Apr 17 04:06:29 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Apr 17 04:06:30 kernel: device eth2 entered promiscuous mode
Apr 17 04:06:30 kernel: br0: port 3(eth2) entering learning state
Apr 17 04:06:30 kernel: br0: topology change detected, propagating
Apr 17 04:06:30 kernel: br0: port 3(eth2) entering forwarding state
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:43 kernel: printk: 244 messages suppressed.
Apr 17 04:06:43 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:49 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:54 kernel: printk: 5 messages suppressed.
Apr 17 04:06:54 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:01 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:14 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:19 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:19 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:21 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:32 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:44 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:47 notify_rc : restart_rstats;restart_conntrack;restart_leds;restart_cstats
Apr 17 04:07:56 kernel: vlan1: received packet with own address as source address
Apr 17 04:08:21 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:19 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:19 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:16:15 kernel: printk: 2 messages suppressed.
Apr 17 04:16:15 kernel: vlan1: received packet with own address as source address
Apr 17 04:16:15 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:22:32 kernel: printk: 2 messages suppressed.
Apr 17 04:22:32 kernel: vlan1: received packet with own address as source address
Apr 17 04:22:32 kernel: vlan1: received packet with own address as source address
Thanks!
I've got my AC66U running in AP Mode with the latest stable release of Merlin's excellent firmware. However, I'm running into an issue - for some reason my wireless clients aren't able to connect, even though if I restore my old config and plug the router back into WAN connection they start working again. My best guess is it might not be passing DHCP packets to the clients? They don't show up in the DHCP logs (BIND running on a centos 6.4 box).
Pretty tired but I'll do some additional testing tomorrow. I've tried with the WAN port plugged into the network and with one of the LAN ports the result is identical. This is what is in the log, I suspect it has something to do with the problem but I'm so tired I can't think:
Apr 17 04:03:39 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:39 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:39 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:39 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:43 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:48 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:50 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:50 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:53 kernel: vlan1: received packet with own address as source address
Apr 17 04:03:58 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:03 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:08 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:16 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:16 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:17 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:22 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:27 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:32 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:37 kernel: vlan1: received packet with own address as source address
Apr 17 04:04:42 kernel: vlan1: received packet with own address as source address
Apr 17 04:05:59 kernel: vlan1: received packet with own address as source address
Apr 17 04:05:59 kernel: vlan1: received packet with own address as source address
Apr 17 04:05:59 kernel: vlan1: received packet with own address as source address
Apr 17 04:05:59 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:26 notify_rc : set_wltxpower;restart_wireless
Apr 17 04:06:28 kernel: device eth1 left promiscuous mode
Apr 17 04:06:28 kernel: br0: port 2(eth1) entering disabled state
Apr 17 04:06:28 kernel: device eth2 left promiscuous mode
Apr 17 04:06:28 kernel: br0: port 3(eth2) entering disabled state
Apr 17 04:06:28 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.39.31 (r341183)
Apr 17 04:06:28 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.30.39.31 (r341183)
Apr 17 04:06:29 kernel: device eth1 entered promiscuous mode
Apr 17 04:06:29 kernel: br0: port 2(eth1) entering learning state
Apr 17 04:06:29 kernel: br0: topology change detected, propagating
Apr 17 04:06:29 kernel: br0: port 2(eth1) entering forwarding state
Apr 17 04:06:29 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Apr 17 04:06:30 kernel: device eth2 entered promiscuous mode
Apr 17 04:06:30 kernel: br0: port 3(eth2) entering learning state
Apr 17 04:06:30 kernel: br0: topology change detected, propagating
Apr 17 04:06:30 kernel: br0: port 3(eth2) entering forwarding state
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:36 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:43 kernel: printk: 244 messages suppressed.
Apr 17 04:06:43 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:49 kernel: vlan1: received packet with own address as source address
Apr 17 04:06:54 kernel: printk: 5 messages suppressed.
Apr 17 04:06:54 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:01 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:14 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:19 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:19 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:21 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:32 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:44 kernel: vlan1: received packet with own address as source address
Apr 17 04:07:47 notify_rc : restart_rstats;restart_conntrack;restart_leds;restart_cstats
Apr 17 04:07:56 kernel: vlan1: received packet with own address as source address
Apr 17 04:08:21 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:19 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:19 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:11:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:16:15 kernel: printk: 2 messages suppressed.
Apr 17 04:16:15 kernel: vlan1: received packet with own address as source address
Apr 17 04:16:15 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:21:35 kernel: vlan1: received packet with own address as source address
Apr 17 04:22:32 kernel: printk: 2 messages suppressed.
Apr 17 04:22:32 kernel: vlan1: received packet with own address as source address
Apr 17 04:22:32 kernel: vlan1: received packet with own address as source address
Thanks!
