I’m going to use this for (among other things) a test server for SFTP connections. Through YAST2, I configured a static address for the Ethernet port.
If I hook my Pi up to a monitor with a keyboard and mouse, it works exactly as it should.
If I plug it in down in my basement, where there is no HDMI, keyboard, nor mouse, it reverts to DHCP and refuses SSH connections.
I bring it back upstairs, it works fine.
It’s all on the same network, but when it’s downstairs it goes through a switch (not sure how that would matter). How is it possible that this is happening? Any insight would be greatly appreciated.
If you search through the Forums (Might be in the Install or Application Forums) you’ll find threads that describe a RPi “feature” that the MAC address changes constantly in different situations, so you can’t rely on any set network configuration from one boot to the next because network configurations are associated with network device MAC addresses.
I don’t remember that a solution was ever described in any of these openSUSE forum threads.
A quick Google turns up how you can set the MAC address for raspbian, but I don’t see a reference for how to do this with u-boot which is what all non-raspbian images use. I see Google hits that it’s supposed to be possible but there was a possible related bug in March 2017.
Maybe your Google skills are better than mine… or is in U-boot documentation somewhere…
BTW - If you set up the network services to be based on named resolution instead of IP address and never turn off your RPi, you can generally avoid most of the problems associated with changing MAC addresses and IP addresses… You’ll just have to remember that if your RPi changes IP addresses, then it might take some time for the other machines in your network to re-discover where your RPi is. Re-discovery will depend on stuff like if you’re running a Workgroup or Domain network services and security.
If you search through the Forums (Might be in the Install or Application
Forums) you’ll find threads that describe a RPi “feature” that the MAC
address changes constantly in different situations, so you can’t rely on
any set network configuration from one boot to the next because network
configurations are associated with network device MAC addresses.
I don’t remember that a solution was ever described in any of these
openSUSE forum threads.
A quick Google turns up how you can set the MAC address for raspbian,
but I don’t see a reference for how to do this with u-boot which is what
all non-raspbian images use. I see Google hits that it’s supposed to be
possible but there was a possible related bug in March 2017.
Maybe your Google skills are better than mine… or is in U-boot
documentation somewhere…
TSU
Hi
I have four RPI3’s here, they are connected to a five port switch, the
other port connects to a wireless repeater. A standalone setup the
switch and repeater all run on 5V so have a 60W six port 5V power block
feeding those and the RPI’s.
All four have static IP addresses, Two run SLES, one openSUSE Leap
42.3 JeOS and the last one Tumbleweed JeOS. All systems retain the same
MAC address over cold/warm power cycles.
Of those one (A SLES system) sometimes doesn’t come up on the network
from a cold start, AFAIK it’s the delay in the switch/repeater so make
sure I power those first (stale arp cache?). The system is up as
verified over a serial connection, restarting the network brings it up.
@OP do you have a USB TTL cable to connect to the RPI? Are the activity
LED’s active on the RPI, what if you pull the ethernet cable or perhaps
power cycle the switch?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.87-18.29-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
