Static IP or OctoPi in work network

Get Help Networking
1

What is the problem?

Setting up Static IP

What did you already try to solve it?

Found IP from DHCP, Setup SSH and can make connection consistently, Set hostname and can SSH into that. I have gone through several how to's on doing this but there are multiple options and I get stuck. The vids and forum topics I've seen don't seem to match what I'm seeing as options in Raspi-Config.

I'd really like someone to point me to a resource that shows how it's done in a current version of OctoPi. I just keep hitting points where my setup doesn't match the how to sections of the tutorials.

Have you tried running in safe mode?

No

Did running in safe mode solve the problem?

Still haven't tried it as I don't think it's applicable here.

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog... no bundle, no support, unless the reason you couldn't retrieve the bundle is your network issues

octoprint-systeminfo-20241008200214.zip (16.1 KB)

WRITE HERE

Additional information about your setup

Hardware you are trying to connect to, hardware you are trying to connect from, router, access point, used operating systems, ... as much data as possible

Trying to set up a static IP so we can use Octopi and Obico in our work setting. Working with our IT department who have set up a static IP for us tied to the Mac address of the Raspberry Pi. I just need to configure the Pi to use the static Ip that was given to us but can't seem to get to the right info in the Pi to set it up.

2

Hello @tracyofleming !

When you are in SSH, run a

ifconfig

You will get something like this:

pi@octopi:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.40  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::44be:4ae:3aea:a85b  prefixlen 64  scopeid 0x20<link>
        inet6 fd19:be15:4f40:4fb6:3362:b8bd:b097:2039  prefixlen 64  scopeid 0x0<global>
        ether b8:27:eb:37:76:20  txqueuelen 1000  (Ethernet)
        RX packets 2781199  bytes 902932673 (861.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 194521  bytes 51631418 (49.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 112385  bytes 26563262 (25.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 112385  bytes 26563262 (25.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:62:23:75  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@octopi:~ $

Behind inet, you get your IP

When the static IP is already assigned to the Pi, there is nothing more to do on the Pi.

3

I believe that you are running a Bullseye (11) version of the OS. You can check with
cat /etc/os-release. I also assume you have the ability to connect a keyboard and monitor or you are setting a static IP address on only one interface (either eth0 or wlan0) and can SSH into the RPi on the other interface.

Use this guide to setup a static IP on Bullseye (11).

Bookworm (12) will use a different tool, google for "raspberry pi bookworm static ip".

4

Do you really need to setup the static IP on the Pi when rhe router is already static on the MAC-address?

5

@Ewald_Ikemann is 100% correct here. If your IT team has configured the pi to have a static IP, you do not need to do anything. What they have done is tell the DHCP server to give your Pi the same ip every time it asks for one. So the Static IP assignment is handled through the network DHCP server.

If anything you need to make sure that your Pi is configured to use DHCP. And if it is, the result will be that every time your pi connects to the network, it will ask the DHCP server if it can have an address. And the DHCP server will give it the same one every time. That is what makes it static in this instance.

1 Like