ipv4 192.168.1.52 "invalid input" #29

Closed
opened 2020-12-19 03:13:30 +08:00 by jbqubit · 8 comments

With latest firmware that builds.

Connection to 192.168.1.26 23 port [tcp/telnet] succeeded!
ipv4 192.168.1.52
{ "error": "invalid input" }
With latest firmware that builds. ```$ nc -vv 192.168.1.26 23 Connection to 192.168.1.26 23 port [tcp/telnet] succeeded! ipv4 192.168.1.52 { "error": "invalid input" } ```

Yes. Now with sufficient configuration storage in flash, you get to specify the subnet mask length, and the default gateway!

As reflected in README.md:
ipv4 <X.X.X.X/L> [Y.Y.Y.Y]

This is now immediately written to flash. The config/save commands deal only with channel parameters.

Yes. Now with sufficient configuration storage in flash, you get to specify the subnet mask length, and the default gateway! As reflected in README.md: `ipv4 <X.X.X.X/L> [Y.Y.Y.Y]` This is now immediately written to flash. The `config`/`save` commands deal only with channel parameters.
astro closed this issue 2020-12-19 04:24:17 +08:00

ipv4 <X.X.X.X/L> [Y.Y.Y.Y] Configure IPv4 address, netmask length, and optional default gateway

I doubt 99% of users are going to care about setting netmask length or custom gateway. How about
ipv4 <X.X.X.X> [Y.Y.Y.Y Z.Z.Z.Z] where X is IP, Y is netmask and Z is gateway. That way simple things remain simple.

```ipv4 <X.X.X.X/L> [Y.Y.Y.Y] Configure IPv4 address, netmask length, and optional default gateway``` I doubt 99% of users are going to care about setting netmask length or custom gateway. How about ```ipv4 <X.X.X.X> [Y.Y.Y.Y Z.Z.Z.Z]``` where X is IP, Y is netmask and Z is gateway. That way simple things remain simple.

Where is the default gateway used anyway? Though we might need it if we add MQTT.

Where is the default gateway used anyway? Though we might need it if we add MQTT.

Also, <X.X.X.X/L> syntax isn't used elsewhere in Sinara/ARTIQ as far as I've seen.

Also, ```<X.X.X.X/L>``` syntax isn't used elsewhere in Sinara/ARTIQ as far as I've seen.

<X.X.X.X/L> (CIDR) is the modern standard way of expressing a network interface address. This new shape of IPv4 configuration is supposed to be much more intuitive because it looks like on every other device.

`<X.X.X.X/L>` (*CIDR*) is the modern standard way of expressing a network interface address. This new shape of IPv4 configuration is supposed to be much more intuitive because it looks like on every other device.

https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing doesn't mention /L so I guess it's not that prevalent. I think what you mean is /24 for conventional subnet with mask 255.255.255.0.

https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing doesn't mention /L so I guess it's not that prevalent. I think what you mean is /24 for conventional subnet with mask 255.255.255.0.

where L is in the range 0..=32

where L is in the range 0..=32

If you insist on using the /modern standard/ please update the documentation so the 99% solution is obvious. Something like the following would be helpful.

Set IPv4 address and netmask, following the [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation, and optional default gateway. A common CIDR is X.X.X.X/24 which corresponds to the 255.255.255.0 subnet mask.

If you insist on using the /modern standard/ please update the documentation so the 99% solution is obvious. Something like the following would be helpful. ```Set IPv4 address and netmask, following the [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation, and optional default gateway. A common CIDR is X.X.X.X/24 which corresponds to the 255.255.255.0 subnet mask.```
Sign in to join this conversation.
No Label
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/thermostat#29
There is no content yet.