Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

IP Routing Issue

  • 21-05-2019 3:39pm
    #1
    lobbylad
    Registered Users Posts: 125 ✭✭


    Hi,

    This is frustrating me now for a few days!

    eir f2000 setup with LAN IP of 192.168.1.254/24

    There are a few PCs and phones all with 192.168.1.30 -> 35 (all can ping each other)

    On 192.168.1.37 is a Google Wifi point, which has its own LAN as 192.168.86.0 (there are some laptops connected to 192.168.86.x via wifi, and a printer thats wired to the Google device).

    Problem is that anyone wired to the f2000 cannot see any of the devices on the Google Wifi? (in particular the printer and a chromecast)

    PC on 192.168.1.41 cannot ping 192.168.1.37 (the google wifi WAN IP)

    I've tried a static route on the f2000 to point 192.168.86.x to 192.168.1.37. When I do this and then a tracert it still shows the 86 networks as going out the WAN link from the f2000.

    (I see on the f2000 that br0 is setup and includes every port on the modem/router - I presume this is normal?)

    Every device can see the internet.

    I can't understand why I can't ping the WAN side of the google wifi device (192.168.1.37) - that should be local to my PC......

    Arrghh!!!


Comments

  • #2
    lobbylad
    Registered Users Posts: 125 ✭✭lobbylad


    Update: Appears that Google specifically block pinging of the WAN IP address of the device - so not being able to ping it isn't indicative of an issue!


  • #3
    Cuddlesworth
    Registered Users, Registered Users 2 Posts: 13,995 ✭✭✭✭Cuddlesworth


    lobbylad wrote: »
    Update: Appears that Google specifically block pinging of the WAN IP address of the device - so not being able to ping it isn't indicative of an issue!

    You have a nested network by setting it up like that. You can get out of the 192.168.68.x network but you will be unable to get into it. Your Google device takes the traffic outbound, NAT's it into the 192.168.1.37 IP and sends it on. It will only allow traffic coming out of the network, any attempts into it will fail.

    Best option is to have the google device function as an access point only and drop the two networks entirely, its called bridge mode.

    If its a Google "mesh" network with multiple google wifi points, then you will need to connected everything into the Google devices and turn the Vodafone F2000 into a modem only device.


  • #4
    lobbylad
    Registered Users Posts: 125 ✭✭lobbylad


    Ahh, that makes sense - I hadn't considered that the Google device was Nat'ing the 192.168.86 onto 192.168.1.37 -> which is only a one way operation

    Thanks! That makes sense so - I'll play around with re-jigging it


Advertisement