You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I looked at the support dump this operator posted on the forum and I see in /etc/config.mesh/_setup that "dmz_mode = 0" and that "dmz_dhcp_end = " (empty value). On my test node when I clear the DHCP End value on the Setup page, press Save Changes, then the "Bad Gateway" message appears. Some data validation could prevent empty values and force numeric values in those fields when in NAT Mode.
The text was updated successfully, but these errors were encountered:
So looking at /etc/config.mesh/_setup I see the following values:
dmz_dhcp_end =
dmz_dhcp_limit = -1
Clearly _end is blank which is bad, but _limit is -1 which is also bad. I'm not sure how this file got corrupted (I assume by the perl code at some point in the past, and it's much more blasé about empty strings being the value 0) but the user could edit this by hand to fix it.
I'll look at adding some code to prevent (or default) the blank DHCP End value.
Forum post reports "Bad Gateway" messages on the Setup page in certain cases when using NAT Mode. https://www.arednmesh.org/content/navigating-cgi-binsetup-gives-502-bad-gateway-status-code
I looked at the support dump this operator posted on the forum and I see in /etc/config.mesh/_setup that "dmz_mode = 0" and that "dmz_dhcp_end = " (empty value). On my test node when I clear the DHCP End value on the Setup page, press Save Changes, then the "Bad Gateway" message appears. Some data validation could prevent empty values and force numeric values in those fields when in NAT Mode.
The text was updated successfully, but these errors were encountered: