Bugzilla – Bug 10871
bad IP address shown in remote login page, can't login
Last modified: 2009-09-08 09:29:03 UTC
steps: - set up player to connect via ethernet - disconnect ethernet - set up player to connect via wireless - turn on remote login - notice that the ip address listed is incorrect (i.e. an autoip address) - also notice that you can't login - reboot - notice that remote login is turned off - turn it on - correct IP address is displayed, - still can't log in /etc/inetd.conf is zero length.
adding Richard for comment- Richard, the zero length inetd.conf file makes me think we need to either a) issue some sync commands from SetupSSH as a workaround, as we do in Networking, or b) prioritize a fix for the underlying filesystem write problem thoughts?
testing twice against these steps with a factory reset r4012, I am not able to reproduce this. I never see a zeroconf address on eth0, which may be the reason I don't see it reproduced. this is ifconfig after dropping ethernet and picking up a wifi network. All looks well, including Fab4 remote login UI address # ifconfig eth0 Link encap:Ethernet HWaddr 00:04:20:22:00:1D UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:336 errors:0 dropped:0 overruns:0 frame:0 TX packets:265 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:69731 (68.0 KiB) TX bytes:37606 (36.7 KiB) Base address:0x8000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:130 (130.0 B) TX bytes:130 (130.0 B) wlan0 Link encap:Ethernet HWaddr 00:04:20:22:00:1D inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:35 errors:0 dropped:0 overruns:0 frame:0 TX packets:42 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7353 (7.1 KiB) TX bytes:6413 (6.2 KiB) #
Should we ever display a zeroconf address in the help for remote login? If not, we could just put in a check to not use a 169.254.* address... back to you Dean
Testing with 4020, it's better, I get the correct IP address displayed, but following the steps below, after the reboot, the Enable SSH setting doesn't stick or actually allow login. Can you reproduce?
BTW: An autoip address is a valid address and is probably useful when connecting ethernet-to-ethernet without a dhcp server. It's not routable to the outside world, but the Internet is overrated, as far as I'm concerned. As a separate bug, we'll need some indication when the squeezebox has lost its network connection. Will open...
Yes, I think what Dean is seeing is due to the filesystem needing sync bug. I'll try to look at that soon.
*** Bug 10951 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 10743 ***