I have a TRENDnet TEW-714TRU single-Ethernet + 802.11N travel router I'm trying to add to an existing network. I've tried configuring it as a dumb AP, meaning that the wireless and Ethernet interfaces are bridged together and dnsmasq and odhcpd are stopped and disabled. The main internet-facing router on my network is a Buffalo WZR-HP-G300NH also running LEDE.
The travel router's network config looks like the following. I removed anything to do with WAN, because it has only one Ethernet port.
cat /etc/config/network config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config globals 'globals' option ula_prefix 'fd05:3734:4036::/48' config interface 'lan' option type 'bridge' option ifname 'eth0.1 eth0' option proto 'static' option ipaddr '192.168.1.10' option netmask '255.255.255.0' option gateway '192.168.1.1' option dns '192.168.1.1' config device 'lan_dev' option name 'eth0.1 eth0' option macaddr '00:14:d1:dd:ee:ff' config switch option name 'rt305x' option reset '1' option enable_vlan '1' config switch_vlan option device 'rt305x' option vlan '1' option ports '0 6'
The problem I'm seeing is that, when I connect the travel router to the LAN, everything works fine for a few seconds, but then eventually all traffic even between hosts on my LAN stops. As soon as I disconnect the travel router from the LAN, the network goes back to normal.
On the Buffalo router, when the travel router is on the LAN, I see many messages like this:
[2065205.279781] br-lan: received packet on eth0.1 with own address as source address [2065206.277421] br-lan: received packet on eth0.1 with own address as source address
Are these messages referring to IP addresses or to MAC addresses?
The travel router's br-lan IP is statically assigned to 192.168.1.10. The Buffalo router's br-lan IP address is 192.168.1.1. When I run arp on the Buffalo router, I don't see anything obvious, like duplicate MAC addresses.
Would could be going on? Any pointers on what I can do to investigate further?
Could it be that a host that was connected to a different AP on the network, then connected to the travel router's AP, confuses the switches on the network, leading to a switching loop or something?