2019-08-10, 06:05 PM
Every time I boot Raspbian / Openplotter it seems to "forget" the standard gateway.
I have to run the command sudo ip route add default via 192.168.1.1 every time I boot to get internet.
I have this setting in Openplotter 1.2.0 Alpha, on a Pi3B+
Network tab:
RPi3+: AP + client
Addresses:
Multiplexed NMEA 0183:
10.10.10.1:10110
192.168.1.103:10110
Signal K Server:
10.10.10.1:3000
192.168.1.103:3000
VNC remote desktop:
10.10.10.1:5900
192.168.1.103:5900
node-red:
10.10.10.1:1880
192.168.1.103:1880
MQTT local broker:
10.10.10.1:1883
192.168.1.103:1883
Status info:
wlan1 is AP
up network: wlan0 wlan1
dnsmasq (dhcp-server): running
hostapd (AP): running
dhcpcd: running
avahi-daemon: running
IP address
192.168.1.103 wlan0
10.10.10.1 wlan1
Hardware info:
Raspberry 3B+
Internal wifi is the AP
External USB dongle (Edimax) is working fine
I have tried:
- Re-installing hostapd, dhcpcd
- Editing the verious files in /etc/network/interfaces.d to static values, or dynamic
- Seeing if it is an external cause (repeater, router/modem, I even tried by using a mobile hotspot on smarphone)
- Problem realy only seems to exist when having an AP and client together.
- Testing if the system has enough power
Weird thing is, it worked fine for ages! Nothing seemed updated. Maybe has to do with dchp leases / timers.
Internet is OK when:
- Using client mode only, gateway is assigned automatically, and internet is OK
- Manually assigning a gateway with the command sudo ip route add default via 192.168.1.1
Hope there is someone with a solution like:
- Automatic gateway assigned
- Alternative solution, automatically run the command sudo ip route add default via 192.168.1.1 when booting? (don't know how to do this, but also not preferred)
I have to run the command sudo ip route add default via 192.168.1.1 every time I boot to get internet.
I have this setting in Openplotter 1.2.0 Alpha, on a Pi3B+
Network tab:
RPi3+: AP + client
Addresses:
Multiplexed NMEA 0183:
10.10.10.1:10110
192.168.1.103:10110
Signal K Server:
10.10.10.1:3000
192.168.1.103:3000
VNC remote desktop:
10.10.10.1:5900
192.168.1.103:5900
node-red:
10.10.10.1:1880
192.168.1.103:1880
MQTT local broker:
10.10.10.1:1883
192.168.1.103:1883
Status info:
wlan1 is AP
up network: wlan0 wlan1
dnsmasq (dhcp-server): running
hostapd (AP): running
dhcpcd: running
avahi-daemon: running
IP address
192.168.1.103 wlan0
10.10.10.1 wlan1
Hardware info:
Raspberry 3B+
Internal wifi is the AP
External USB dongle (Edimax) is working fine
I have tried:
- Re-installing hostapd, dhcpcd
- Editing the verious files in /etc/network/interfaces.d to static values, or dynamic
- Seeing if it is an external cause (repeater, router/modem, I even tried by using a mobile hotspot on smarphone)
- Problem realy only seems to exist when having an AP and client together.
- Testing if the system has enough power
Weird thing is, it worked fine for ages! Nothing seemed updated. Maybe has to do with dchp leases / timers.
Internet is OK when:
- Using client mode only, gateway is assigned automatically, and internet is OK
- Manually assigning a gateway with the command sudo ip route add default via 192.168.1.1
Hope there is someone with a solution like:
- Automatic gateway assigned
- Alternative solution, automatically run the command sudo ip route add default via 192.168.1.1 when booting? (don't know how to do this, but also not preferred)