Why EV Charger accept 192.168.64.205, but not accept: 192.168.65.101:
I know from many Home-User-Devices that they have problems with larger subnets. Sometimes they consider a 255.255.255.0 net to be the default, and if the Gateway does not match the Net of the IP entered, it throws an error, assuming invalid configuration.
What happens if you set an (invalid) Gateway / DNS of 192.168.65.1? Does it allow to save configuration then?
After it, this was accepted:
Let me understand well…
Do you want the information from one subnet (…65.x) to route through the gateway from another subnet (…64.y)?
The same, computers from one subnet (…65.x) to look for DNS info on a DNS (server) from another subnet (…64.y)?
If yes, maybe it’s a rule somewhere that don’t allow cross-networking…
Look at mask: this is not 255.255.255.0
My subnet is bigger
240 = 11110000
from 64.x to 79.x this one subnet.
Sorry, missed that… 
then it seems like a bug - maybe sensitive towards the sequence of events:
- The validation of ip vs gateway is faulty with regards to the subnet.
- Changing the IP after the gatway causes the validation to be executed and assume an error.
- Changing the Gateway after the IP does not trigger validation, and the setting is working, if the prior combination was flagged “ok”.
(or something like this)
Hi, Piotr. Can you please describe how you applied Gateway address 192.168.64.1(like on the screenshot)? I can’t repeat it on my EVCS. All the time have error 102.
if u use the mask 255,255,0,0 should work, no?
It seems there is some issue with manual IP settings validation. It will be fixed in an upcoming release.
1 Like
I commissioned yesterday my evcs.
On the victron connect app android there was something phishy going on. I tried set manual ip and I struggled 2, maybe 3 times. Went to the windows computer and everything was accepted at first try.