(05-06-2024, 10:06 AM)Tim Curtis Wrote:

(05-06-2024, 12:44 AM)TheOldPresbyope Wrote: @nosferatu_cat 

Quote:Wifi connection.  I set the static address through the networking setup screen as I always have.

Ok, so I tried it that way too---no Ethernet and only WiFi. I got the same result I got with a wired connection. Four open ports detected by nmap and I have access to the player (a different one physically but also m900pre5) via webUI and ssh.

Not a clue what's happening to your setup.

As an aside, I believe reserving IP addresses in the router is better practice than setting static IPs in the player's interfaces.

ETA

After ignoring this player for an hour or so I tried to connect to the webUI again and couldn't. The player's interface was still detected by ping but nmap now found all ports were closed. 

I spent some 10 minutes trying to understand what was happening when suddenly I found the ports open again and full access restored.

There's nothing in the journal log to suggest what's happening. This is a head-scratcher for sure but I'll keep looking for clues.

Regards,
Kent

Interesti

Maybe something to do with the .nmconnection files?

(05-07-2024, 01:44 PM)fdealexa Wrote: Sorry Kent,
I was preparing my post (I am not an English mother tongue) while you sent yours.
Sorry again and best regards,
Francesco

(05-07-2024, 12:35 PM)TheOldPresbyope Wrote:

(05-06-2024, 10:06 AM)Tim Curtis Wrote:

(05-06-2024, 12:44 AM)TheOldPresbyope Wrote: @nosferatu_cat 

Quote:Wifi connection.  I set the static address through the networking setup screen as I always have.

Ok, so I tried it that way too---no Ethernet and only WiFi. I got the same result I got with a wired connection. Four open ports detected by nmap and I have access to the player (a different one physically but also m900pre5) via webUI and ssh.

Not a clue what's happening to your setup.

As an aside, I believe reserving IP addresses in the router is better practice than setting static IPs in the player's interfaces.

ETA

After ignoring this player for an hour or so I tried to connect to the webUI again and couldn't. The player's interface was still detected by ping but nmap now found all ports were closed. 

I spent some 10 minutes trying to understand what was happening when suddenly I found the ports open again and full access restored.

There's nothing in the journal log to suggest what's happening. This is a head-scratcher for sure but I'll keep looking for clues.

Regards,
Kent

Interesti

Maybe something to do with the .nmconnection files?

My test was invalid. I didn't notice I forgot to set the netmask for the static WiFi connection so the value remained the default 255.255.255.255.

Moved the uSD card to a Pi400 so I could work from the command line even if networking were borked. ifconfig reports

Code:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 10.0.0.251  netmask 255.255.255.255  broadcast 0.0.0.0

Both the netmask and the broadcast address are incorrect for my network.

I set the WiFi netmask to 255.255.255.0 and rebooted. Now ifconfig reports

Code:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 10.0.0.251  netmask 255.255.255.0  broadcast 10.0.0.255

So fas so good. The player is again accessible from my network via the webUI. 

I have to leave town in a few hours. I'll leave this player running and check again when I get back at the end of the week.

Regards,
Kent


PS - just to be clear, the static address I chose, 10.0.0.251, lies outside the range of IP addresses dynamically allocated by the DHCP server on my router. It is not, however, an assigned IP address, e.g., an address assigned by the DHCP server to a specific MAC address.

(05-07-2024, 05:06 PM)nosferatu_cat Wrote:

(05-07-2024, 12:35 PM)TheOldPresbyope Wrote:

(05-06-2024, 10:06 AM)Tim Curtis Wrote:

(05-06-2024, 12:44 AM)TheOldPresbyope Wrote: @nosferatu_cat 

Quote:Wifi connection.  I set the static address through the networking setup screen as I always have.

Ok, so I tried it that way too---no Ethernet and only WiFi. I got the same result I got with a wired connection. Four open ports detected by nmap and I have access to the player (a different one physically but also m900pre5) via webUI and ssh.

Not a clue what's happening to your setup.

As an aside, I believe reserving IP addresses in the router is better practice than setting static IPs in the player's interfaces.

ETA

After ignoring this player for an hour or so I tried to connect to the webUI again and couldn't. The player's interface was still detected by ping but nmap now found all ports were closed. 

I spent some 10 minutes trying to understand what was happening when suddenly I found the ports open again and full access restored.

There's nothing in the journal log to suggest what's happening. This is a head-scratcher for sure but I'll keep looking for clues.

Regards,
Kent

Interesti

Maybe something to do with the .nmconnection files?

My test was invalid. I didn't notice I forgot to set the netmask for the static WiFi connection so the value remained the default 255.255.255.255.

Moved the uSD card to a Pi400 so I could work from the command line even if networking were borked. ifconfig reports

Code:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 10.0.0.251  netmask 255.255.255.255  broadcast 0.0.0.0

Both the netmask and the broadcast address are incorrect for my network.

I set the WiFi netmask to 255.255.255.0 and rebooted. Now ifconfig reports

Code:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 10.0.0.251  netmask 255.255.255.0  broadcast 10.0.0.255

So fas so good. The player is again accessible from my network via the webUI. 

I have to leave town in a few hours. I'll leave this player running and check again when I get back at the end of the week.

Regards,
Kent


PS - just to be clear, the static address I chose, 10.0.0.251, lies outside the range of IP addresses dynamically allocated by the DHCP server on my router. It is not, however, an assigned IP address, e.g., an address assigned by the DHCP server to a specific MAC address.

Interesting.  I'll try 255 x 4 instead of x3.  Thanks.

(05-07-2024, 06:17 PM)nosferatu_cat Wrote:

(05-07-2024, 05:06 PM)nosferatu_cat Wrote:

(05-07-2024, 12:35 PM)TheOldPresbyope Wrote:

(05-06-2024, 10:06 AM)Tim Curtis Wrote:

(05-06-2024, 12:44 AM)TheOldPresbyope Wrote: @nosferatu_cat 



Ok, so I tried it that way too---no Ethernet and only WiFi. I got the same result I got with a wired connection. Four open ports detected by nmap and I have access to the player (a different one physically but also m900pre5) via webUI and ssh.

Not a clue what's happening to your setup.

As an aside, I believe reserving IP addresses in the router is better practice than setting static IPs in the player's interfaces.

ETA

After ignoring this player for an hour or so I tried to connect to the webUI again and couldn't. The player's interface was still detected by ping but nmap now found all ports were closed. 

I spent some 10 minutes trying to understand what was happening when suddenly I found the ports open again and full access restored.

There's nothing in the journal log to suggest what's happening. This is a head-scratcher for sure but I'll keep looking for clues.

Regards,
Kent

Interesti

Maybe something to do with the .nmconnection files?

My test was invalid. I didn't notice I forgot to set the netmask for the static WiFi connection so the value remained the default 255.255.255.255.

Moved the uSD card to a Pi400 so I could work from the command line even if networking were borked. ifconfig reports

Code:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 10.0.0.251  netmask 255.255.255.255  broadcast 0.0.0.0

Both the netmask and the broadcast address are incorrect for my network.

I set the WiFi netmask to 255.255.255.0 and rebooted. Now ifconfig reports

Code:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 10.0.0.251  netmask 255.255.255.0  broadcast 10.0.0.255

So fas so good. The player is again accessible from my network via the webUI. 

I have to leave town in a few hours. I'll leave this player running and check again when I get back at the end of the week.

Regards,
Kent


PS - just to be clear, the static address I chose, 10.0.0.251, lies outside the range of IP addresses dynamically allocated by the DHCP server on my router. It is not, however, an assigned IP address, e.g., an address assigned by the DHCP server to a specific MAC address.

Interesting.  I'll try 255 x 4 instead of x3.  Thanks.

Oops, misread.  I tried it and got no open ports.

(05-07-2024, 06:31 PM)nosferatu_cat Wrote:

(05-07-2024, 06:17 PM)nosferatu_cat Wrote:

(05-07-2024, 05:06 PM)nosferatu_cat Wrote:

(05-07-2024, 12:35 PM)TheOldPresbyope Wrote:

(05-06-2024, 10:06 AM)Tim Curtis Wrote: Interesti

Maybe something to do with the .nmconnection files?

My test was invalid. I didn't notice I forgot to set the netmask for the static WiFi connection so the value remained the default 255.255.255.255.

Moved the uSD card to a Pi400 so I could work from the command line even if networking were borked. ifconfig reports

Code:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 10.0.0.251  netmask 255.255.255.255  broadcast 0.0.0.0

Both the netmask and the broadcast address are incorrect for my network.

I set the WiFi netmask to 255.255.255.0 and rebooted. Now ifconfig reports

Code:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
       inet 10.0.0.251  netmask 255.255.255.0  broadcast 10.0.0.255

So fas so good. The player is again accessible from my network via the webUI. 

I have to leave town in a few hours. I'll leave this player running and check again when I get back at the end of the week.

Regards,
Kent


PS - just to be clear, the static address I chose, 10.0.0.251, lies outside the range of IP addresses dynamically allocated by the DHCP server on my router. It is not, however, an assigned IP address, e.g., an address assigned by the DHCP server to a specific MAC address.

Interesting.  I'll try 255 x 4 instead of x3.  Thanks.

Oops, misread.  I tried it and got no open ports.

OK, my aging brain may have missed the pick list of netmasks.  I normally enter 255.255.255.0 but may have just accepted the default.  On a fresh install I chose my option from the pick list and everything worked.  When I worked in IT we called an outcome like this the result of magic or sun spots.  I'll shut up now.