Bridging Arris Gateway to Linksys E4200 and DLNA connect
I recently upgraded my WOW service to Ultra TV with the Arris Gateway. I connected one port on the gateway to my Linksys E4200 router. I use the Linksys wireless rather than the Arris because it has a faster wireless connection and a longer range. Also I was using the Linksys E4200 before the Arris and therefore there was very little setup.
All devices on network devices connected seamlessly. However there is one glitch. The CONNECT function on the Ultra TV does not see my DLNA servers on my network. I figured out that the problem was that the Arris used a different subnet (192.168.100.1) then the Linksys (192.168.1.1), and the Linksys was assigning all the local IPs.
It was suggested to me that I could bridge the Linksys to the Arris gateway. Calls to Linksys and WOW on how to do this failed. Neither party wanted to deal with the other branded device. So how best to bridge the two devices so that Ultra TV sees the DLNA servers (and content) on my network?
I am not a network expert so I feel uneasy just reading posts on bridging. Any help would be appreciated.
|reply to ecoles |
I had a similar issue in my setup.
My media is on a server. I dripped a second nic in the server and connected it right to the gateway. I adjusted firewall settings so that only requests to the DNLA port from the gateway's IP can get in.
What can I say, for now I do not fully trust my networks security to their gateway.
|reply to ecoles |
Put your router on the same subnet as the gateway, turn dhcp off, and enable access point mode if the router has it.
I gave up the UltraTV DHCP and went to the seperate subnet. Most of my devices can not take a static ip, so I needed an omni present DHCP server that remembers macs and ips.
The nic idea is a thought. I think I have a machine that is ethernet wired to UltraTV but also has available wireless. Running UltraTv at 5G and the old subnet at 2G but on channel 13 (due to neighborhood). The only problem with 13 its that some wifi drivers and programs do not even know that such a channel exists. If server's wifi can see the subnet on 13, I think I have a solution.