- Dec 22, 2011
- 5
- 0
- 18,510
I apologize in advance for any incorrect terminology. I have a Network set up in my home using an ASUS RT-N66U Dual-Band Wireless-N900 Gigabit Router (Operation Mode:Wireless router Firmware Version:3.0.0.4.376_3754)and a Motorola SURFboard SB6141 Cable Modem.
We have a couple wired connections into the router from PC's, one of which is a server running constantly. We also have several wifi connections (android phones, PC and Mac Laptop, etc.). We also have a Samsung smart TV which has a built in network card. We had been using it to connect to the network for a while, but the network card was extremely flaky. We were regularly experiencing connection problems. To resolve this, I purchased a TP-LINK TL-WR841N Wireless N300 Home Router, 300Mpbs, to use as a wireless bridge. Essentially it is now acting as my network card for the TV. That's all I need it for.
It works relatively well for the TV. Unfortunately there is something else going on now. It appears, when other devices are closer to the "bridge" router, they try to connect to that, and when they are closer to the main router they connect to that. It seems they are constantly struggling between the two and the connections are dropping. I notice this when streaming music from my phone. It will (not always) start stuttering. The stuttering always seems to go away when I unplug the "bridge" router.
the main router log is full of messages like this:
Apr 10 10:05:18 kernel: eth1: received packet with own address as source address
Apr 10 10:05:35 kernel: eth1: received packet with own address as source address
Apr 10 10:07:26 kernel: eth1: received packet with own address as source address
Apr 10 10:08:24 kernel: eth1: received packet with own address as source address
Apr 10 10:21:07 ntp: start NTP update
Apr 10 12:34:44 kernel: eth1: received packet with own address as source address
Apr 10 18:56:12 kernel: eth1: received packet with own address as source address
Apr 10 19:23:13 kernel: eth1: received packet with own address as source address
Apr 10 21:05:10 kernel: eth1: received packet with own address as source address
I don't know exactly what's going on, but that is my hunch. Any thoughts on how to resolve this? Thanks!
We have a couple wired connections into the router from PC's, one of which is a server running constantly. We also have several wifi connections (android phones, PC and Mac Laptop, etc.). We also have a Samsung smart TV which has a built in network card. We had been using it to connect to the network for a while, but the network card was extremely flaky. We were regularly experiencing connection problems. To resolve this, I purchased a TP-LINK TL-WR841N Wireless N300 Home Router, 300Mpbs, to use as a wireless bridge. Essentially it is now acting as my network card for the TV. That's all I need it for.
It works relatively well for the TV. Unfortunately there is something else going on now. It appears, when other devices are closer to the "bridge" router, they try to connect to that, and when they are closer to the main router they connect to that. It seems they are constantly struggling between the two and the connections are dropping. I notice this when streaming music from my phone. It will (not always) start stuttering. The stuttering always seems to go away when I unplug the "bridge" router.
the main router log is full of messages like this:
Apr 10 10:05:18 kernel: eth1: received packet with own address as source address
Apr 10 10:05:35 kernel: eth1: received packet with own address as source address
Apr 10 10:07:26 kernel: eth1: received packet with own address as source address
Apr 10 10:08:24 kernel: eth1: received packet with own address as source address
Apr 10 10:21:07 ntp: start NTP update
Apr 10 12:34:44 kernel: eth1: received packet with own address as source address
Apr 10 18:56:12 kernel: eth1: received packet with own address as source address
Apr 10 19:23:13 kernel: eth1: received packet with own address as source address
Apr 10 21:05:10 kernel: eth1: received packet with own address as source address
I don't know exactly what's going on, but that is my hunch. Any thoughts on how to resolve this? Thanks!
Facebook
Twitter
Instagram