Dhcpd running by default?

Tango

@mitu said in Dhcpd running by default?:
...

Post the output of the ifconfig command.

A bit more behind this. When I saw the dhcp shutting down (probably was dhcpcd - by the time I saw it, it was scrolling off the screen), when it shutdown, I restarted - that's when I saw the IP address that was out of range. (I think it started with 169 - which made no sense!) I shut down again and brought it up here, thinking if there was an IP address issue, that would explain why I couldn't ssh in to the system.

Now, up in my study, I can't connect to it from anything else at this point, so I have a screenshot of the ifconfig output - and now, even though it is connected to my LAN, there is only an IP6 address, no IP4 address.

mitu

@tango said in Dhcpd running by default?:

I restarted - that's when I saw the IP address that was out of range. (I think it started with 169 - which made no sense!)

The 169. range is an auto-configuration (zeroconf) LAN range, used by systems when there is no other IP configuration mechanism available (DHCP or static IP). See https://en.wikipedia.org/wiki/Zero-configuration_networking#Address_selection.

and now, even though it is connected to my LAN, there is only an IP6 address, no IP4 address.

Check if the cable has correct connectivity to your DHCP server. Try a static IP and see if it can reach other systems in the LAN.

Tango

@mitu said in Dhcpd running by default?:
...

Check if the cable has correct connectivity to your DHCP server. Try a static IP and see if it can reach other systems in the LAN.

Can't ping a thing right now. The dhcpcd service does seem to be running, though.

mitu

Then you might not have connectivity, it doesn't seem to be a software issue.

Tango

@mitu said in Dhcpd running by default?:

Then you might not have connectivity, it doesn't seem to be a software issue.

This wasn't news I wanted to hear, but it tells me what I needed to know. I looked at the RJ45. The yellow light is on, the green never goes on. I put in some SDCards with Ubuntu and RetroPie on them. (Ubuntu was a new setup and took over 2 hours to get to anything beyond setup - spent a LOT of time just waiting on it.) Neither the Ubuntu or RetroPie OS showed anything different for ifconfig.

I plugged the CAT5 cable into another computer on the same desk and it worked fine.

I guess that means that lightning strike from a few weeks ago not only blew out a network switch, but the Pi RJ45 as well.

Thanks for helping me troubleshoot it. I guess that Pi needs replacing. At least I can still store it and use it whenever I am using a Pi system that doesn't need to be on the network.

That's on a 3B. If I get a Pi 4, will the same RetroPi image work on that without a problem?

mitu

@tango said in Dhcpd running by default?:

That's on a 3B. If I get a Pi 4, will the same RetroPi image work on that without a problem?

No, you'd need a re-install or you can get an USB ethernet adapter to replace the broken ethernet port and keep the existing system.

Tango

@mitu said in Dhcpd running by default?:

@tango said in Dhcpd running by default?:

That's on a 3B. If I get a Pi 4, will the same RetroPi image work on that without a problem?

No, you'd need a re-install or you can get an USB ethernet adapter to replace the broken ethernet port and keep the existing system.

The full OS is on a USB drive. There's no SD card in it. Can I just plug the USB drive into a Pi of a matching model? In other words, go from this 3B+ to another 3B+?

mitu

@tango As long as the other system is configured for USB boot, then yes, it should work fine.

Tango

@mitu

I know this sounds like I'm being picky, but I just want to be sure I get this. Again, moving just the USB drive, which contains the full OS.

So if I go from 3B+ to 3B+, as long as the new one is configured for USB boot, I'm okay.

But if I go from 3B+ to 4, then it won't work? I take it the hardware on the 4 is significantly different to keep that working?

mitu

@tango said in Dhcpd running by default?:

So if I go from 3B+ to 3B+, as long as the new one is configured for USB boot, I'm okay.

Yes.

But if I go from 3B+ to 4, then it won't work? I take it the hardware on the 4 is significantly different to keep that working

Yes. Technically, it might work if you're upgrading all the packages on the Pi4 system after the switch, but there's so many of things that could go wrong (older OS, not compatible with the Pi4, emulator settings set for the older Pi models, etc.).
I'd start over with a fresh installation on a Pi4 and transfer the ROMs/BIOS and a few configurations (EmulationStation mainly).

Tango

@mitu Thank you!

I was thinking about the same if I upgraded - reinstall, then copy over all ROMs. If I copy over /home/pi/RetroPie (isn't that the directory? with it off, I can't check) and all the folders and files in that tree, will that get all my settings for Emulation Station and all the scores and so on?

(I know it won't of course, include things like /etc/samba/smb.conf or sshd_conf.)

mitu

@tango The ES settings are not in /home/pi/RetroPie, but in /opt/retropie/configs/all/emulationstation, so they will not be transferred over just by copying that folder.

Tango

@mitu said in Dhcpd running by default?:

@tango The ES settings are not in /home/pi/RetroPie, but in /opt/retropie/configs/all/emulationstation, so they will not be transferred over just by copying that folder.

So if I copy those two directory trees over, that should get all my ES and game settings, scores, and such?

mitu

@tango said in Dhcpd running by default?:

So if I copy those two directory trees over, that should get all my ES and game settings, scores, and such?

No, just the ES settings, hiscores, ROMS, BIOS files. What do you mean by game settings ? If you created .cfg files for games in the ROMs folder(s), then they'll be copied as part of ROM folders.

Tango

SOLUTION:

I brought this up in another thread, but that covers other issues, so for details that aren't here, you can check there.

I solved this on the dhcp server (dnsmasq). Oddly enough, even though I was specifying to use 172.16.7.17, somehow it was being read as 172.16.7.174. I have no idea why, but that was in my reserved range of IP addresses to not give out, so the dhcp server was having issues with that and not giving it to the Pi.

I changed and ended up using 172.16.7.11 instead of .17. After I changed to that, allowing time for propagation, it worked out.

It is puzzling, since the dhcpcd logs on the Pi say they're being offered 172.16.7.17, but the server says it's .174 instead of .17. I have not tried to change back - I don't want to deal with that again. (I'm wondering if something was glitchy when the dhcp server wrote the config file to the drive.)