Venus GX does not accept static IP gateway

Question

question

brmurray asked Jan 11, '21

Venus GX does not accept static IP gateway

Hello,

My Venus GX seemingly cannot accept a gateway when using a static (manual) IP address. I can enter the gateway, but it reverts to 0.0.0.0 when I click Return.

No problem entering Gateway...

...but it's not saved correctly.

I can the Venux GX at the Static IP via LAN directly and indirectly (through a switch). I can also access other remote nodes via a VPN service, but not the Venux GX. Thus while it could be a VPN problem, my first suspicion is the Venux GX gateway.

I'm relatively new with IP networking, so please let me know if I'm missing another possible solution.

Thanks,

Bryan

Venus GX - VGX TCP IP Networking

1610402926959.png (51.1 KiB)

1610403013184.png (66.8 KiB)

1610404968081.png (29.2 KiB)

1

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Javier Comellys commented · Sep 24, 2021 at 03:22 PM

Hi, my problem is in the following case:

Venus GX - Switch - Router (The Cloud) - Laptop,

The ping test between Laptop to Venus GX is OK, but in the software (VictronConnect) I can´t see the information. The department of ITC told me that they have open all the port. I checked the Port: 80 and it is open. Please I apreciate your support to see the inverter with VictronConnect software

Thanks Javier

0 ·

Modifications Space

Node Red Space

Answer 1 · 2021-01-12T09:32:23Z

markus answered · Jan 12, 2021 at 09:32 AM

In order to reach the VenusGX through your VPN tunnel, you must enter a gateway on your VenusGX (your VPN router)

What IP are you trying to enter as the gateway? 192.168.2.000? A gateway cannot have zeros in the last part of the IP address.

BR

2

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

brmurray commented · Jan 15, 2021 at 09:07 PM

Hi Markus,

Understood; I won't post the gateway here, but the last group is not 000.

The problem is that when I enter the gateway (e.g. 192.168.2.yyy) and press enter, the VenuxGX does not accept the gateway and reverts to 000.000.000.000. This happens when connecting via VRM, LAN, and direct WiFi. Is this perhaps a bug?

Thanks,

Bryan

0 ·

markus ♦♦ brmurray commented · Jan 16, 2021 at 08:30 AM

I just tried that out by myself, it was no problem setting a Gateway.

Another tipp that can work: Use DHCP and set a fixed lease for your VenusGX. (Venus GX is always getting the same IP then)

This can (most propably) be done on your router (if it does DHCP).

BR

0 ·

Answer 2 · 2021-01-15T22:32:36Z

seb71 answered · Jan 15, 2021 at 10:32 PM

If you configure it normally (but with manually configured networking settings), does it work?

By normally I mean to use for gateway the LAN IP of your Internet router. And then see if VRM works.

1

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

brmurray commented · Jan 20, 2021 at 01:41 AM

I haven't tried that, but the problem seems to be that the VenusGX won't accept any IP address; it just reverts to 0. Interesting, I can enter static IP, just not the gateway.

0 ·

manual-ip-gateway-fail.mp4 (2.6 MiB)

Answer 3 · 2021-01-20T02:43:55Z

Ingo answered · Jan 20, 2021 at 02:43 AM

I think the problem is when you have both LAN and Wireless interfaces active. The default-gateway can only be set on one interface. If you currently connect to WiFi then you will have to disable it and connect to the LAN interface and then set it.

*Note that you need to be on the same subnet to do that as there is no default-gateway for the LAN interface and you might lose connectivity once the WiFi is disabled.

1

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

brmurray commented · Jan 20, 2021 at 06:57 PM

Thanks Ingo!

0 ·

Answer 4 · 2021-04-02T10:04:54Z

Hello,

I do have the very same issue as described above by brmurray in his different posts.

CURRENT INSTALLATION

CERBO GX with the following connections:

HDMI and USB1: Cerbo GX Touch 50 display
Ethernet: Garmin GPSMAP 8412
VE.Direct1 to 3: SmartSolar MMPTs and BMV712
VE.Bus1: Multiplus
VE.Bus2: not used
VA.Can1 to 4: not used
USB2 to 3: not used

Venus firmware upgraded to 2.63

Connected to VRM through home router

Installed in July 2020

WIFI CONNECTION ISSUE

I want to install a ALFA WIFI CAMP PRO2 router with amplified WiFi antenna on board so that I can connect easily to a marina hotspot to get access to internet for emails and so, and to have the Cerbo connect to VRM. This used to work fine at home (marina home with boat just outside) when connecting CERBO to my FREEBOX home router, directly or through 2 existing Wifi extenders (NETGEAR and ZYXEL).

I installed the ALFA router, connected to my FREEBOX home router and tested Internet connection with 2 devices. Then, I tried to connect the CERBO to the ALFA and this is when things turn sour. I did many many tests and could not define a clear pattern of when it works and when it does not. To make a long story short, it does fail most of the time but not always when connecting to ALFA and it does succeed most of the time but not always when connecting to FREEBOX, NETGEAR or ZYXEL:

when connecting Automatic to the ALFA, the Gateway IP address on the CERBO is not populated and shows "----", but it is properly populated most of the time when connecting to the FREEBOX, the NETGEAR or the ZYXEL
when connecting Manual to the ALFA or any other, the IP address entered as Gateway is most of the time replaced by "-----" after validation. Sometimes it did work after modifying or re-entering DNS IP address.

My engineer gut feeling tells me that we have some bugs here with some random behavior that I could not figure out.

To go one step further, I would not want to connect the CERBO to the ALFA with Ethernet cable because this would require that I also connect the GPSMAP to the router with Ethernet cable and Garmin does not want any Ethernet connection on the GPSMAP except for Garmin interfaces. Despite that, my installer did connect the CERBO and would assume any issue, but so far, so good…

Last and not very important, CERBO does not seem to store known network passwords as opposed to what the manual says page 15… It does make testing a bigger pain :-(

Any help would be most welcome.

Thanks

Answer 5 · 2021-09-23T15:22:38Z

Hi all

I have the same problem as mentioned before. Following-up on the hints provided above, I can confirm that the default gateway is only defined on the Wifi connection. However, regardless whether the default gateway is provided by the DHCP server (router) or configured manually, after a few seconds the default gateway is removed by connmand. I am attaching the logs below - the removal of the default route is shown in the last line of the log.

Any advice would be appreciated.

Many thanks!

Sep 20 12:18:29 beaglebone daemon.info avahi-daemon[14090]: Withdrawing address record for AAA.BBB.XX.21 on wifi0. 

Sep 20 12:18:29 beaglebone daemon.info avahi-daemon[14090]: Leaving mDNS multicast group on interface wifi0.IPv4 with address AAA.BBB.XX.21. 

Sep 20 12:18:29 beaglebone daemon.info avahi-daemon[14090]: Joining mDNS multicast group on interface wifi0.IPv4 with address AAA.BBB.XX.21. 

Sep 20 12:18:29 beaglebone daemon.info avahi-daemon[14090]: Registering new address record for AAA.BBB.XX.21 on wifi0.IPv4. 

Sep 20 12:18:29 beaglebone daemon.info connmand[584]: wifi0 {del} address AAA.BBB.XX.21/24 label wifi0 

Sep 20 12:18:29 beaglebone daemon.info connmand[584]: wifi0 {del} route AAA.BBB.XX.0 gw 0.0.0.0 scope 253  

Sep 20 12:18:29 beaglebone daemon.info connmand[584]: wifi0 {add} address AAA.BBB.XX.21/24 label wifi0 family 2 

Sep 20 12:18:29 beaglebone daemon.info connmand[584]: wifi0 {add} route AAA.BBB.XX.0 gw 0.0.0.0 scope 253  

Sep 20 12:18:29 beaglebone daemon.info connmand[584]: wifi0 {add} route AAA.BBB.XX.2 gw 0.0.0.0 scope 253  

Sep 20 12:18:29 beaglebone daemon.info connmand[584]: wifi0 {add} route 0.0.0.0 gw AAA.BBB.XX.2 scope 0  

Sep 20 12:18:30 beaglebone daemon.info connmand[584]: wifi0 {add} route 82.165.8.211 gw AAA.BBB.XX.2 scope 0  

Sep 20 12:18:30 beaglebone daemon.info connmand[584]: wifi0 {del} route 82.165.8.211 gw AAA.BBB.XX.2 scope 0  

Sep 20 12:18:31 beaglebone daemon.info avahi-daemon[14090]: Leaving mDNS multicast group on interface ap0.IPv4 with address 172.24.24.1. 

Sep 20 12:18:31 beaglebone daemon.info avahi-daemon[14090]: Leaving mDNS multicast group on interface wifi0.IPv4 with address AAA.BBB.XX.21. 

Sep 20 12:18:31 beaglebone daemon.info avahi-daemon[14090]: Leaving mDNS multicast group on interface eth0.IPv4 with address AAA.BBB.YY.21. 

Sep 20 12:18:32 beaglebone daemon.info avahi-daemon[14271]: Joining mDNS multicast group on interface ap0.IPv4 with address 172.24.24.1. 

Sep 20 12:18:32 beaglebone daemon.info avahi-daemon[14271]: Joining mDNS multicast group on interface wifi0.IPv4 with address AAA.BBB.XX.21. 

Sep 20 12:18:32 beaglebone daemon.info avahi-daemon[14271]: Joining mDNS multicast group on interface eth0.IPv4 with address AAA.BBB.YY.21. 

Sep 20 12:18:32 beaglebone daemon.info avahi-daemon[14271]: Registering new address record for 172.24.24.1 on ap0.IPv4. 

Sep 20 12:18:32 beaglebone daemon.info avahi-daemon[14271]: Registering new address record for AAA.BBB.XX.21 on wifi0.IPv4. 

Sep 20 12:18:32 beaglebone daemon.info avahi-daemon[14271]: Registering new address record for AAA.BBB.YY.21 on eth0.IPv4. 

Sep 20 12:20:34 beaglebone daemon.info connmand[584]: wifi0 {del} route 0.0.0.0 gw AAA.BBB.XX.2 scope 0

question