Q: Cannot access Ethernet network
I have recently updated my network router and am having trouble getting things to work. My Internet access is wireless (no land line). For over 6 years I have successfully used a Netgear MBR624GU 3G Broadband wireless Router which allowed me to access the Internet as well as supporting an Ethernet physical network (with other computers, printers and a Sonos music system with iTunes library on a NAS). The Netgear router was also on the Ethernet network (all with 192.168.2.0/24 IP addresses). There was also Wi-Fi access for iPad, etc.
Moving now on to LTE my new contract brought me a Huawei Mobile WiFi E5577C router. This has no Ethernet port. I have managed to access the Internet via it. However, I now can't access the Ethernet network - ping reports 'Request timeout' and printers and Sonos system aren't accessible. That seems strange to me, for I thought direct access to this physical network should be easy. I have tried things like disabling the Wi-Fi but that didn't make Ethernet access work. I have set the Ethernet network with highest priority in the Service Order, Wi-Fi second. Currently I have both Ethernet and Wi-Fi configured manually (assigning Wi-Fi 192.168.3.0 and Ethernet 192.168.2.0 IP addresses, Wi-Fi with 192.168.3.2 as Router - I have also tried using DHCP but with no more success). I have also tried both with and without the Netgear router additionally attached to the Ethernet net but that didn't seem to make any difference.
I did think that I maybe need a different router with an Ethernet port (like the Netgear) but, since I will have to pay for that myself, I would rather know whether that is the only solution before spending the cash.
I assume I have understood something wrongly in this setup. If anyone can give me any tips or suggest what else I could try, I will be very grateful. If I should post any more detailed data, please let me know.
iMac (27-inch, Late 2013), OS X El Capitan (10.11.3), OWC Thunderbolt 2 Dock
Posted on Mar 22, 2016 4:07 AM
You're going to have to set up some sort of IP routing or bridging from the wired to the wireless network, or you'll have to set up the local boxes with multiple network connections with separate subnets. You might need static routes for devices with multiple network paths, but you will minimally need to have your wired and wireless networks in separate subnets. This so that your network traffic can be set via Wi-Fi to the ISP, or via wired to other local devices.
Or get a modem that has wired and wireless. Or one that has wired, if you're inclined to set up and manage your own network.
If there's the budget and inclination to manage your own network... My usual preference involves isolated devices for each of the major functions, and with the ISP device at the edge and configured minimally. That is, an ISP modem device with a wired connection and a "bridging" mode for the ISP connection. Then a locally-controlled gateway router firewall box, and a separate Wi-Fi device and preferably one with an access point (AP) mode. Have your own gateway box provide firewall services, NAT and related. Keep the ISP device as simple as possible. This is more boxes up front, but when one box fails or when you swap ISPs, only the ISP modem might need to change. The other devices will not need to change. There are both positives and negatives to this approach, as — for instance — you also manage all of your network security and your configuration, "within" your own network "behind" the ISP modem. The ISP techs can only get as far as the modem, and will only assist you with that part of your network.
Network bridge: works like a hunk of wire in a wired network, for most considerations. Basically transparent to IP network traffic.
Network router: transfers IP traffic between two or more different IP subnets. Very much visible to IP network traffic.
Welcome to IP networking.
Posted on Mar 23, 2016 8:41 AM