I have an installation of Jessie lxqt running and am having difficulty getting it to use a static ip address.
in /etc/network/interfaces I have
auto eth0
iface eth0 inet static
address 192.168.1.113
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 184.16.33.54 184.16.4.22
my router has a reserved address for this mac address
and it worked on the angstrom and ubuntu images.
I am clearly doing something wrong.
Thanks in advance.
remove connman...
It takes over eth0..
Regards,
Hello Robert,
Is this connman also killing Jessie Console configuration (ETH-WifI)? Since a Month or Two I´m having problems with WiFi configuration and also with Eth under /etc/network/interfaces.
It is installed by default for some reason now?
Thanks!
Yeah, it's installed by default too now on the console images.
Feel free to remove it asap..
The 2 minute delays on bootup when eth0 wasn't plugged in forced me to
install connman by default..
Regards,
Now I understand why I could not configure WiFi…!!!
I solved ETH0 issue commenting it.
Do you think is that a bug (to be solved) on jessie?
Thnks for your answer!
By the way the 2 minute delay on boot is also solved replacing this: auto eth0 By this: allow-hotplug eth0
Best regards!
Unless eth0 is plugged in at boot..
Then it doesn't always get an ip address.
Regards,
@Robert
Any idea what is causing this ? I’ve yet to experience this myself, but I always use ethernet + static IP. Did I mention that I dislike connman with a passion ?
In Jessie, I've been playing around with, [ifplugd] this afternoon..
It seems to be doing what i want..
allow-hotplug eth0
iface eth0 inet dhcp
Regards,
Thanks for your answer again Robert.
Is this issue Kernel relevant? I mean, could be caused because Debian Jessie is supposed to be 3.16 by default and BBB-eMMC-flasher-debian-jessie-console-armhf-2015-04-09-2gb.img has 3.14 on it for BBB?
BRegards.
Nope, the 'issue' goes back to the "Lenny" days, networking was changed as such:
The login (screen/prompt) only shows up after a valid network
connection is created on (auto eth0), or it'll wait 2 minutes...
For bb.org, i've been using these tools to bring up eth0 over
(/etc/network/interfaces)
wheezy: wicd
jessie: connman
More Background, we don't see this 2minute time out in ubuntu, as i
patch it out:
https://github.com/RobertCNelson/omap-image-builder/blob/master/scripts/chroot.sh#L403
However, in debian, the 2 minute delay is complied in the code.
Regards,
yeah... Connman still works better then ifplugd:
After booting (without eth0 plugged in), then plug in i still get:
Apr 14 21:54:59 arm dhclient[195]: No DHCPOFFERS received.
Apr 14 21:54:59 arm dhclient[195]: No working leases in persistent
database - sleeping.
Apr 14 21:54:59 arm ifup[190]: No DHCPOFFERS received.
Apr 14 21:54:59 arm ifup[190]: No working leases in persistent
database - sleeping.
with:
allow-hotplug eth0
iface eth0 inet dhcp
and:
/etc/default/ifplugd
INTERFACES="eth0"
(or)
HOTPLUG_INTERFACES="eth0"
eth0 plugged in at power on: boots fast, eth0 works
eth0 un-plugged in at power on: boots fast, (eth0 doesn't auto connect
when connected..)
Yuck..
Regards,
Thanks for your tries!
When you say:
“”"
For bb.org, i’ve been using these tools to bring up eth0 over
(/etc/network/interfaces)
wheezy: wicd
jessie: connman
“”"
This is not strictly true right? because on jessie with connman the information on this path “/etc/network/interfaces” is nor really taked into consideration. Configuration is on other path (that I didn´t found it!!!)
Regarding this: “However, in debian, the 2 minute delay is complied in the code.”
Could be possible that the 2 minute delay is only affecting to ‘hdmi’? I´m not seeing as it through SSH.
Is bb.org considering Ubuntu or just Debian?
Best regards!
Thanks for your tries!
When you say:
"""
For bb.org, i've been using these tools to bring up eth0 over
(/etc/network/interfaces)
wheezy: wicd
jessie: connman
"""
This is not strictly true right? because on jessie with connman the
information on this path "/etc/network/interfaces" is nor really taked into
consideration. Configuration is on other path (that I didn´t found it!!!)Regarding this: "However, in debian, the 2 minute delay is complied in the
code."
Could be possible that the 2 minute delay is only affecting to 'hdmi'? I´m
not seeing as it through SSH.
no... Remove wicd/connman/etc..
Setup: /etc/network/interfaces
As:
auto eth0
iface eth0 inet dhcp
unplug ethernet and reboot..
You'll see exactly what i mean..
Is bb.org considering Ubuntu or just Debian?
ubuntu images are available. But after ubuntu moved to a 9 month
"support" cycle for non-lts's, using the non-lts's in a real embedded
application is just stupid..
Regards,
Crystal clear. Thanks mate!
Hello,
I´m testing connmanctl (debian-jessie-console-armhf-2015-04-09) and seems that I need to wrote complete path to it in order to interact with it “/usr/sbin/connmanctl”
I think it should be included on system or at least i´ve seen on forums is being used just with ‘connmanctl’. Any ideas how to do this?
Regards.
either "root" users or:
sudo connmanctl
Regards,
Hello, I have upgraded my Debian distribution to latest one:
https://rcn-ee.com/rootfs/bb.org/testing/2015-04-19/console/BBB-eMMC-flasher-debian-jessie-console-armhf-2015-04-19-2gb.img.xz
I am facing issues with WiFi. This is what I did:
sudo apt-get install wireless-tools wpasupplicant
sudo wpa_passphrase my_ssid my_password
sudo nano /etc/network/interfaces
auto wlan0
iface wlan0 inet dhcp
wpa-ssid my_ssid
wpa-psk my_generated_psk_password
sudo ifup wlan0
This is what I got:
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
Failed to bring up wlan0.
Any ideas (before this release everything worked like a charm)?
Thanks!
Does it help when you remove connman?
sudo apt-get remove connman
Regards,
Hell man you are fast, thanks!
Connman is not installed by default on that Release you made! So nop… Connman is not a trouble at this time… something else is interfering I think.
Thanks!