3 ms·
It appears someone else ran into this and worked around it by adding routes to the gateway device to route to the new destination on behalf of the client. [1][2
by LinuxBender 4y ago
It appears someone else ran into this and worked around it by adding routes to the gateway device to route to the new destination on behalf of the client. [1][2] Not sure if that would work in your setup.
[1] - https://discourse.pi-hole.net/t/push-static-route-to-android-client/47055 https://discourse.pi-hole.net/t/push-static-route-to-android...
[2] - https://dhcp-users.isc.narkive.com/Z6gxzMDm/static-routes-option-not-working-on-android-based-embedded-platform https://dhcp-users.isc.narkive.com/Z6gxzMDm/static-routes-op...
- linker3000 4y agoThanks for doing some digging. Unfortunately the default gateway/router (A Nokia GPON terminator) does not support adding static LAN routes - it's more of a 'fit and forget' home-grade product and isn't too sophisticated (the available documentation's pretty rubbish too!). The problem will go away in about a month when the Nokia is replaced with a GPON bridge and a Draytek router, then the current 67Mbit VDSL service will be decommissioned just leaving the gigabit FTTP WAN connection.
- LinuxBender 4y agoThat's unfortunate. Perhaps one albeit clucky work-around would be to have your Wifi connected to a Linux router, that then routes to your Nokia? By Linux router I just mean a cheap Linux box with ip forwarding enabled and set the routes there? Beyond that I am out of ideas.
- linker3000 4y agoYeah, I started go mentally down the rabbit hole - for example I have an access point running OpenWrt, a few Linux servers and I could find a Raspberry Pi or five, but just decided the gain for the reconfiguration pain was not worth the effort.