Hi, thank you for contacting JustAnswer.com. My name is Russell. I will do my best to provide the right answer to your question.
I have some simple advice: if those instructions aren't working for you, then they either misstate something or leave something vital out. Linux 'documentation' is often that crudely unreliable, unfortunately.
Before you reboot and try to connect to the new Arch Linux on the Pogo Plug 4, do you set the IP address on it to come up at a fixed IP address? do you set its Linux eth0 to be listening and active? if you don't, it won't come up at any IP address, or it will come up - as assigned by DHCP perhaps - at an IP Address that you cannot forsee and must discover by guesswork or examination and inference.
What have to tried to do, to examine and infer the IP identity of the Pogo Plug device on your network ? Reading the DHCP Assignments tables of your local router box (if the Pogo device is connected to it with an Ethernet cable, especially) would be the most likely way to go with that.
(And if the Pogo device had a 'console' connection, that would be the best thing to examine it by, since it would show scrolling bootup/startup messages including info about network status. That's an IF, since I doubt that it has.)
So, can you PING it at that address and get a response, after the restart?
But the original OS's IP address setting isn't significant with regard to a new OS install upon it.
Have you configured the new installs to a particular, static IP address, e.g. using ifconfig or similar command in the startup scripts of the new OS install ?
This seems best, ***** ***** is simply put, and has an Arch Linux example too:
The configuration file is a text file that can be edited with a standard Linux text editor even if the OS that supports and uses the file is not running at the time. (Editing it with a Windows editor would be rather inadvisable for certain reasons.)
If the command is
ln -s /dev/null /etc/systemd/network/10-dhcp.network
and if it says 'no such file', then you may need to create the file first as an empty file by
cat > /etc/systemd/network/10-dhcp.network
and then Ctrl-Z to terminate the cat operation. Note: this has to be /etc/systemd/network on the target system that is going to be used, not on the system you are running the install with. Context is important here.
Let me explain what I mean please:
- you are using one system to configure the Pogo Plug, correct?
- so you are booted up off that one system not the Pogo Plug, while configuring the Pogo Plug, correct?
- so the commands that alter files should alter the files on the Pogo Plug system, not on the system you are running to do the configuring of the Pogo Plug with. That's the context.
The 'target system' is the Pogo Plug.
The 'system you are running' is the one you are using to configure it.
I regret that I seem to be making no progress in advising you, and for that I apologize.
Since a different Expert here might have more success at helping you, I would like to give you that opportunity to improve, by Opting Out, which opens the case to other Experts without cutting off communication.