New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't configure static IP #746
Comments
Let's see if we can get to the bottom of this. First, are you trying configure WiFi or Ethernet? |
Thanks for the quick reply! Connected to ethernet - it is an rpi3 so it does have built-in wifi. EDIT: It appears if I run |
Hi, @abrenoch
and reboot the device. glad to help |
Closing out the issue. Will re-open if it doesn't solve the problem. |
thanks @antonmolodykh that did seem to work, which is strange because I copied my previous settings (from an old screenly install) from that file verbatim and was not able to get onto the network.. Must have missed something... Also I guess the 'edit dhcpcd.conf' message in that interfaces file was totally moot. I feel like the ability to set the settings with 'network.ini' was a bit of an easier solution, but I'm sure you have your reasons for changing it! Thanks you for the help guys! |
@vpetersson Thanks for your answer. I downloaded the latest Screenly OSE ver on 2018-03-01 and installed on my Raspberry Pi 3 Model B I was planning to deploy the Rpi with Screenly OSE in a location with only WiFi connection. The configuration using the captive portal worked a charm. On reboot it was easy to see the IP addres to access screenly assets from another PC. No issues here. Well here is the issue: My DHCP server also does not report the Rpi as connected, so I cannot verify the IP Address either I plugged in a keyboard and ctrl+alt+F1 to confirm the IP address. Shure the address was still the same and the pc was still running, but could not access the webpage like previous evening. My only option then would be to reboot to let it reconnect to the DHCP server. So I have two options: OR assign a static IP address and do not show the splash screen So I followed the instructions provided: #746 Mine: auto wlan0 So I was exited to find a detailed instruction for th eversion I am using. Reboot with sudu reboot ctr+alt+F1 to check the IP address: Yes it is "192.168.1.115" Back to square 0 console, comment out the wlan0 setting in the /etc/network/interfaces file: So for now my ONLY option to add, remove or change assets is to leave splash screen ON, reboot so I can see the IP address and to access screenly web interface. Any pointers? |
Hi @fritserasmus |
I think there is some confusion here, which is understandable. Let me take a step back to explain what I think is the root cause for at least the network config (@antonmolodykh's point above should hopefully solve the other one).
The former is the older method, that is still widely used. When you configure networking using the captive portal, this will configure the wireless network using Network Manager. This means that if you also try to configure the same network interface using the other method, you're likely going to end up having trouble. It is certainly possible to configure the wifi using
To my knowledge, you cannot mix and match between Network Manager by setting just a static IP in the interfaces file. If you instead want to use purely use Network Manager, I recommend looking into Hope that helps. |
hi i have not been able to open that file i dont see it in any folder. how you manage to open it ? i tried to connect thru ssh and it says connection refused. @antonmolodykh @vpetersson |
@gady87 Yes, that's because OpenSSH is disabled by default in Rasbian (and subsequently Screenly OSE). You need to enable it first using |
In case anyone searching how to set up the static ip for the ethernet (eth0) connection: You have to use Tested with the current release screenly ose 10.1 (based on Raspbian 9.11) Basically, you just enable ssh - connect and run this commands with your settings:
Now your ssh session should be broken (Like this: And your screenly-ose should have a static ip on eth0 from now on. |
does this also work with the wifi ?
… On 8/07/2021, at 3:59 AM, Gabriel Wanzek ***@***.***> wrote:
In case anyone searching how to set up the static ip for the ethernet (eth0) connection: You have to use nmcli like described here <https://www.screenly.io/blog/2018/01/19/screenly-ose-0.13-is-available/#:~:text=For%20custom%20Ethernet%20configuration%20and%20advanced%20configurations%2C%20you%20can%20either%20use%20nmcli%20by%20hand%20on%20the%20device%2C%20or%20configure%20networking%20through%20/etc/network/interfaces.>
Tested with the current release screenly ose 10.1 (based on Raspbian 9.11)
Basically, you just enable ssh - connect and run this commands with your settings:
$ nmcli dev status
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected Wired connection 1
wlan0 wifi disconnected --
lo loopback unmanaged --
$ sudo nmcli con mod 'Wired connection 1' ipv4.addresses 10.0.3.10/8
$ sudo nmcli con mod 'Wired connection 1' ipv4.gateway 10.0.0.1
$ sudo nmcli con mod 'Wired connection 1' ipv4.dns 10.0.0.1
$ sudo nmcli con mod 'Wired connection 1' ipv4.method manual
$ sudo nmcli con 'Wired connection 1' up
Now your ssh session should be broken (Like this: packet_write_wait: Connection to 10.200.0.99 port 22: Broken pipe)
And your screenly-ose should have a static ip on eth0 from now on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#746 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHOW57STXMGHQZALOVJWCFTTWVSF7ANCNFSM4ERCS35A>.
|
@gady87 I think it should, but better make a fresh installation on a test-device in case things break. |
Thanks
… On 9/07/2021, at 3:45 AM, Gabriel Wanzek ***@***.***> wrote:
@gady87 <https://github.com/gady87> I think it should, but better make a fresh installation on a test-device in case things break.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#746 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHOW57UYNXJJJQ4J3WBOEUDTW2ZLLANCNFSM4ERCS35A>.
|
I'm not sure what has changed, but trying to configure the network settings in the most recent update is, I'm sorry to say, an absolute mess.
I look at an article barely 3 months old (https://support.screenly.io/hc/en-us/articles/213678343-How-do-I-configure-a-Screenly-node-to-use-a-static-IP-) that says to use the config tool. When following the link to the tool one of the first things it says is "This tool can no longer be used with Screenly OSE", and provides a link to this page (https://www.screenly.io/blog/2018/01/19/screenly-ose-0.13-is-available/) which says to edit
/etc/network/interfaces
. Okay, so I open that file and one of the first things that file says is "For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'". So I hop into that file and make the needed changes, reboot, and no change to my IP... So I go back a step and try modifying/etc/network/interfaces
like the old way, reboot, and network connectivity does not work at all. Okay, so I go back to the page I first linked to to follow the manual process - which tells me to do exactly what the second page I linked to says no longer works (making a network.ini file in boot).Frankly, I can't figure out how to set a static IP since the 'paradise city' update... and all the instructions I have found lead me in circles.
Can we please get some clear instructions on how to manually modify the network settings? Nothing seems to be working for me now.
Thanks!
The text was updated successfully, but these errors were encountered: