Changing Flukso gateway ip

by B-Man on

my network has to go offline for a week, so have been trialing a 4g wingle connected to a spare router.

i have it all hooked up but when i connect the flukso it wont connect

On the "192.168.10.33/#/status" page the "Gateway IP address" displays the old gateway address any ideas on how to change this? as i get an error in the "Flukso.net ping test"
even after a reboot

its listing "Gateway IP address" 192.168.10.1
but needs to be 192.168.1.1

i can't find an option to change it on the web gui

i found this on another post on here

  1. This is what I have for my wan connection in /overlay/etc/config/network
  2.  
  3. config interface 'wan'
  4.         option proto 'static'
  5.         option ipaddr '10.0.0.120'
  6.         option netmask '255.255.255.0'
  7.         option ifname 'eth0'
  8.         option dns '8.8.8.8'
  9.         option gateway '10.0.0.1'
  10. Make sure you know what you are doing because you can loose the connection to your device!
  11. More info: http://wiki.openwrt.org/doc/uci/network

but mine shows this

  1. config interface 'loopback'
  2.         option ifname 'lo'
  3.         option proto 'static'
  4.         option ipaddr '127.0.0.1'
  5.         option netmask '255.0.0.0'
  6.  
  7. config interface 'wan'
  8.         option proto 'dhcp'
  9.         option ifname 'eth0'
  10.  
  11. config interface 'lan'
  12.         option type 'bridge'
  13.         option proto 'static'
  14.         option ipaddr '192.168.255.1'
  15.         option netmask '255.255.255.0'
  16.         option ifname 'wlan0'

can i just add "option gateway '192.168.1.1'" to the wan config?

‹ Gas sensor stopped working SERIAL NUMBER NOT RECOGINIZED ›
degerrit's picture
degerrit |

I ran my flukso on 3G for a year, and did something like you want to do.
But I had a kinda special setup, where my old telco-provided-and-unmanageable router was still behaving as DHCP server, but not connected to the internet (I used it only as a wireless access point).
So in my case, I configured proto to 'static' on the flukso wireless interface, in order to use a laptop with a 3G connection as "real" router and dns server. The laptop was attached to the old router.

In your case, assuming you are in full control of your router, I don't see why your router couldn't be a dhcp server and provide all the needed settings (ip, dns, gateway, subnet mask) to your flukso.
This would by far be easier and less risky than going full static.

An issue I see is that your gateway needs to be in the same subnet as your flukso - 192.168.1.1 is NOT in the same network as 192.168.10.33, at least not if the subnet mask is the common /24 (255.255.255.0).
Adding a gateway probably won't do much when proto is still dhcp, I think.

- Do you have 2 routers, both acting as dhcp server, hence the 2 different IP ranges?
- Or is your router NAT'ing the network your flukso is attached to? This would explain the different gateway (both can be valid, each in its own network, in that case).
- What does 'route -n' show ?
- Which interface (lan or wireless) would your flukso use to connect to your router?