Debian8 (Jessie) on Turris Omnia

[j0n4s82]

@technik007_cz

This is working for me, thanks @janskyj(U need “apt-get download dhcpcd5” on your turris terminal screen, then move downloaded *.deb package to your lxc container root folder, then log in lxc container and run apt-get remove isc-dhcp-client -y && dpkg -i dhcpcd5.deb in folder where you put deb file and reboot and it should work instantly. )

@janskyj @woosting @miska @technik007_cz I am getting this when trying to implement this suggestion:

root@turris:~# apt-get download dhcpcd5
-ash: apt-get: not found
root@turris:~#

I was guessing I have to install apt-get, but then:

root@turris:~# opkg install apt-get
Unknown package 'apt-get'.
Collected errors:
 * opkg_install_cmd: Cannot install package apt-get.

What am I missing here? Am I correct in doing this from my turris shell?!

Sorry for the confused me…

[miska]

@j0n4s82

What am I missing here? Am I correct in doing this from my turris shell?!

Sorry for the confused me…

No, you are supposed to do it inside the container. Use lxc-attach -n container to get inside your container.

[janskyj]

@j0n4s82

What am I missing here? Am I correct in doing this from my turris shell?!

Sorry for the confused me…

Hello j0n4s82,
technik007_cz described it in the way that he run apt-get from inside openwrt (I don’t know where he got apt package for openwrt) but you don’t have to want to do it like that. The way how I did it (I consider it easiest) is to configure it first time in debian by hand (ifconfig to set ip address and /etc/resolv.conf to dns name server). Than you can run apt-get update and use it in ordinary way…
Moreover, You mostly going to run some services in debian. They can be even accessible from outside (in DMZ like configuration). So you probably want to prevent possible random debian ip address change and configure it staticly in debian /etc/network/interfaces…

[Ondrej_Caletka]

You can also set up static MAC and/or IP address directly in the LXC configuration file. In that case, you don’t have to run any configuration inside the container at all:

lxc.network.hwaddr = 02:01:de:00:00:01
lxc.network.ipv4 = 192.168.1.2/24
lxc.network.ipv4.gateway = 192.168.1.1

[woosting]

@j0n4s82

In response to your PM (I prefer open communication so others can pick up on it / be helpedat the same time) in general I did the following:

@technik007_cz

U need “apt-get download dhcpcd5” on your turris terminal screen, then move downloaded *.deb package to your lxc container root folder, then log in lxc container and run apt-get remove isc-dhcp-client -y && dpkg -i dhcpcd5.deb in folder where you put deb file and reboot and it should work instantly.

However I used wget to get the dhcpcd5.deb package on the omnia; then moved it to the root folder of the container, then uninstalled isc-dhcp-client (using apt-get remove) from whithin each debian container and installed the dhcpcd5.deb (using dpkg -i).

Basically it boils down to:

• Download a stand-alaone Debian Lennie dhcpcd5 package (for armhf) directly from their site (via wget or the tooling of you choosing) onto your Omnia (using wget from a command prompt obtained through an ssh connection to your Omnia box).
• Move it to the file-sysem of your container (so it is accessible from within your container).
• Start the container and attach to it.
• Uninstall the failing isc-dhcp-client (apt-get remove), from within the container.
• Install the other (using dpkg and the .deb file you placed in the fs of the container), from within the container.
• apt-get update && apt-get upgrade

I have no time for copy/paste ready commands (and test them), but I think you should be able to manage from here, following this logic.

If there is a step that needs clarification / you are encountering troubles let us know. It’s not that hard though, I think you will manage (assuming you have basic CLI knowledge).

[Big_boss]

@woosting

(for armhf)

Can we download *.ipk files for “armhf” to install it on the Omnia it self?

[woosting]

I dont know about .ipk file, but to be clear; I downloaded the .deb onto the omnia; but installed it in my debian container.

[Big_boss]

Yeah i know :). But i was wondering because mvu…or what it is called (compiled package especially made for the arm processor of the Omnia) aren’t that many.

[j0n4s82]

@woosting

In response to your PM (I prefer open communication so others can pick up on it / be helpedat the same time) in general I did the following:

Good clarification @woosting. Thanks for putting it together. I am almost there.
EDIT @woosting @Big_boss And my container is working as it should with dhcpcd5 installed and the other workaround as described here removed!

[woosting]

@j0n4s82

EDIT @woosting @Big_boss And my container is working as it should with dhcpcd5 installed!

[lampra]

Hi, I expect that my problem is relevant to this topic.
I have configured omnia with DNSSEC, cz.nic’s DNS servers, DNS forwarding enabled, mwan3 (Lte failover) and a Jessie container. I use static ipv4 for the container.
When wan is working DNS resolution is fine in the container. When wan is not working (Lte failover) i can ping lets say google dns (8.8.8.8) but i have no dns resolution.
As a workaround I changed the resolv.conf file in the container from #nameserver 10.0.3.1
to nameserver 8.8.8.8
While this works, I am not sure if this is a proper solution. Any idea?