* Fixing an output problem of the ip address and netmask on Debian Stretch when using the Status page

Instead of the IP Address, the word inet is being displayed in the status page
This also resultet, that the status page is stating that CumuluxMX is NOT Running

___cumulusmx____.jpg

This is now fixed and compatible with Debian Jessie and Debian Stretch

(Attention: People who already using a cumulusmxsh.conf and updating from an earlier Version do NOT need to add new parameters or replace their existing cumulusmxsh.conf with the file in this update.
When running the script the first time, new Parameters will be added automatically to cumulusmxsh.conf)

New version is available in the first Post

You do not have the required permissions to view the files attached to this post.

Hello Richard
yes, I remember this...but unfortunately at that time I had not the chance to install the new debian...so I could not find a solution.
The main problem was, that the output of the "ifconfig eth0" in older debian verisons was different from the output in the new stretch version.
So my command to get the IP and netmask did not work anymore....but I found a new command which was unknown for me, to get just the ip address without any grep's and cut's which works on Debian Jessie and Stretch. (hostname -I did it)

Sionce I have not tested it yet, I can not say anything.
But, the problem between Debian Jessie and Stretch was not a problem with the bash script, only the output of one command was different (ifconfig)
And as long they do not change commands, I am sure, everything will work also with the next OS update

* Fixing an output problem of the ip address and netmask on Debian Stretch when using the Status page

Instead of the IP Address, the word inet is being displayed in the status page
This also resultet, that the status page is stating that CumuluxMX is NOT Running

___cumulusmx____.jpg

This is now fixed and compatible with Debian Jessie and Debian Stretch

(Attention: People who already using a cumulusmxsh.conf and updating from an earlier Version do NOT need to add new parameters or replace their existing cumulusmxsh.conf with the file in this update.
When running the script the first time, new Parameters will be added automatically to cumulusmxsh.conf)

New version is available in the first Post

Hi Slash! Thanks for the script, it works like a charm and it very well written! I finally can control my station remotely via a SSH connection!

One thing I noticed is that IPADDRESS=$(hostname -I) was not populating my IP correctly. It was getting all the IPs of the machine (ipv4 [space] ipv6 [space] other ipv6s). This didn't affect the functionalities of the script but gave some error messages.
I fixed it just replacing the "$(hostname -I)" for my machine local fixed IP.
Just wanted to let you know in case this is something needs to be fixed/updated.

It looks like every Linxux operating system is displaying it's ip address different then others.
My Debian for example:hostname --help
-i, --ip-address addresses for the host name
-I, --all-ip-addresses all addresses for the host

when using -i I am getitng 127.0.0.1
when using -I I am getting my IPv4
This is working for me, and I also have an IPv6 address on my Raspberry, but hostname -I is only displaying my IPv4 address.
Lubuntu seem to displaying all IP addresses
I am curious to know if this is working for you?ip -f inet addr show eth0 | grep -Po 'inet \K[\d.]+'

CumulusMX is not listening on TCP Port: 8998 (http://192.168.178.124 2a02:8071:2bba:7f00:2518:70aa:1c3a:67ee :8998)
Maybe CumulusMX has not finnished to start yet or running on a different TCP Port then 8998.
Please wait additional 30 seconds and try again, If it still fail, restart CumulusMX to clearly start on TCP Port 8998 <(sudo) ./cumulusmx.sh -r>

However, everything is working fine. Data are uploaded and there are no issues. I also rebooted the Pi a couple of times.
Does anyone know these things? Obviously, this is just depending on the fact that the Pi is now connect to another router.

To answer my last post a bit. I just noticed that my new router is connceted via IPv6 and IPv4 is only set through DS-Lite. This seems to be the reason that the error is thrown up. But everything works fine...

jnstllng wrote:To answer my last post a bit. I just noticed that my new router is connceted via IPv6 and IPv4 is only set through DS-Lite. This seems to be the reason that the error is thrown up. But everything works fine...

I will Look at this this Weekend, if it is possible to surpress IPv6 Output.
I also have a cable Connection with unitymedia but gladly an IPv4 Connection
Jan