April-23rd-2019, 07:24 AM
I have investigated a little bit your DNS problem.
If you have successfully setup a cifx0 interface then calling the command
will give you a similar output like the following
There are two networks up and running and the default route is via the docker0 bridge 172.17.0.1.
If I now remove the network cable of eth0 and call
then I get no response ... cause all unroutable network traffic goes through eth0 due to the default route setting ... but eth0 connection it is no more.
If I now call
to set the routing to the exisiting cifx0 then ping to google.com works fine as expected.
So I cannot confirm with the latest container that resolving DNS does not work.
If you have successfully setup a cifx0 interface then calling the command
Code:
ip route show
will give you a similar output like the following
Code:
default via 172.17.0.1 dev eth0
10.11.0.0/16 dev cifx0 proto kernel scope link src 10.11.5.25
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2
There are two networks up and running and the default route is via the docker0 bridge 172.17.0.1.
If I now remove the network cable of eth0 and call
Code:
ping google.com
then I get no response ... cause all unroutable network traffic goes through eth0 due to the default route setting ... but eth0 connection it is no more.
If I now call
Code:
ip route delete default
ip route add default via 10.11.5.25 dev cifx0
to set the routing to the exisiting cifx0 then ping to google.com works fine as expected.
So I cannot confirm with the latest container that resolving DNS does not work.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)