1

In the last 2 weeks, my Lighthouse IP address changes every couple of days when connected to a router. That would be caused by the Lighthouse shutting down and coming back with a new IP address.

Can I set the Lighthouse’s IP address at a fixed number? Ken

2

SNIP

Sorry, I gave instructions for the new unreleased version. :smile:

You need to edit the file /mnt/persist/config.xml. It’s an XML file and it should look something like this:

<?xml version="1.0"?>
<config>
  <version>1</version>
  <network>
    <mode>connected</mode>
    <conf>static</conf>
    <address>192.168.1.12</address>
    <netmask>255.255.255.0</netmask>
    <gateway>192.168.1.1</gateway>
    <dns>192.168.1.1</dns>
  </network>
</config>

Save the file and restart the box.

Just in case you don’t know what these are (or if someone else bumps into this thread that doesn’t)… The dns and gateway are your router’s IP. The address field is your desired address. And netmaks is usually 255.255.255.0 (unless you know that it’s not, in which case you don’t need my explanation about what it should be).

1 Like
3

hello, I tried to change
there /mnt/persist/config.xml
ip is always assigned by dhcp.
has anything changed with version
Librarian v3.1 / 3.1 Lighthouse?

4

Yes, the new version uses /etc/network/interfaces, which is documented here:

https://wiki.debian.org/NetworkConfiguration
5

hello, it is supported IPv6?

6

As far as I know, yes.

7

I wrote this configuration, but is no longer working on the network LAN / wireless Lighthouse.
how do I reset?

auto eth0
iface eth0 inet static
address 10.49.1.10
netmask 255.255.255.0
broadcast 10.49.1.255
network 10.49.0.0
gateway 10.49.1.1

8

Take out the SD card and delete the persist.img on it.

9

sd card where I find?

10

Oh, sorry, it’s a lighthouse… hm, that’ll be a bit tricky.

Since you configured it to use static IP, you could try connecting it directly to a computer, and assign the computer an address such as 10.49.1.11. Hopefully that will allow you to SSH back into it. Then you remove /mnt/persist/etc/network/interfaces file and reboot.

11

10.49.1.11 in the network does not respond, do not understand what happened.
wifi is visible but you can not connect.

12

You have to set your computer to that IP address and try to connect to the address you set your Lighthouse to which is 10.49.1.10.

13

I did a scan ip 10.49.1.1 - 10.49.1.255
located just my computer 10.49.1.100.

14

Hm… well, it’s busted for now. I’ll figure out how to get you out of there, but I’ll need some time because we’re working on the Lantern release atm.

15

I await your help.
thank you

16

solved:
Download the boot.img file from the download link above.
Download the stable image from archive.outernet.is7.
Copy the both the .img file and .pkg file to an SD card, and rename the .pkg file to outernet-rx.pkg.
Power down Lightouse
Insert the SD card
Power up Lighthouse
When LEDs stop blinking, remove SD card
Power-cycle Lighthouse

17

currently this is the answer

Loading user interface…

If interface does not appear to load for more than 10 minutes, you should restart the receiver.

18

to avoid further errors
ipstatic for configuration?

sudo vi / etc / network / interfaces

auto lo eth0 wlan0

iface lo inet loopback

iface eth0 inet manual
   post-up /sbin/dhcpcfg $IFACE up
   pre-down /sbin/dhcpcfg $IFACE down

iface wlan0 inet static
   address 192.168.0.1
   netmask 255.255.255.0
   dns-nameservers 192.168.0.1
19

I fixed your post a little because the configuration was completely mangled.

So to make eth0 static, you just need to make it look like this:

iface eth0 inet static
   address <IP addr of the receiver>
   gateway <Your router IP>
   netmask 255.255.255.0
   dns-nameservers <Same as gateway>

That should work. Don’t mess with the auto line at the top because that will most definitely cause the wifi interface to become unusable.

20

It has passed an hour but interface appears