Hi
I am running Trinity, having installed it from the latest CD live, using Ubuntu 14.04. On monday I set my wired net with the tdenetworkmanager only.
Everything worked fine, the connection was set manually, the connected icon for wired showed up.
Then yesterday, I connected to a wirless net, using tdenetworkmanager, again everything fine.
Today I deactivated the wireless card and tried to connect again to the wired net. It did not work.
I found out that the resolv.conf file, which is a link from /run/resolv/resolv.conf --> /etc/resolv.conf was empty. So I manually set a new connection, but the resolv.conf file was not changed, I replaced the resolv.conf file by the correct file and then the connection worked, however the icon, still shows wired connection *not* connected. This is annoying.
Does anybody using the same distribution have this problem and knows a solution?
Thanks
Uwe Brauer
2016-11-02 12:25 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com:
Hi
I am running Trinity, having installed it from the latest CD live, using Ubuntu 14.04. On monday I set my wired net with the tdenetworkmanager only.
Everything worked fine, the connection was set manually, the connected icon for wired showed up.
Then yesterday, I connected to a wirless net, using tdenetworkmanager, again everything fine.
Today I deactivated the wireless card and tried to connect again to the wired net. It did not work.
I found out that the resolv.conf file, which is a link from /run/resolv/resolv.conf --> /etc/resolv.conf was empty. So I manually set a new connection, but the resolv.conf file was not changed, I replaced the resolv.conf file by the correct file and then the connection worked, however the icon, still shows wired connection *not* connected. This is annoying.
Does anybody using the same distribution have this problem and knows a solution?
Thanks
Uwe Brauer
Hello, I'm using Debian, so it could be different for you. But you have to comment your eth0 lines on your file /etc/network/interfaces. And you have to change the bolean of ifup line on the file /etc/Networkmanager/Networkmanager.conf Try to do it an reboot ? Bye ;)
2016-11-02 12:25 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com:
Hello, I'm using Debian, so it could be different for you. But you have to comment your eth0 lines on your file /etc/network/interfaces.
Hm thanks.
I renamed that file to interface-org, maybe this is not sufficient. Are you saying I should comment out *all* lines concerning eth0? Even auto eth0?
I have right now in the file interface-org
auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0
iface eth0 inet static address XXX.XX.XX.XX netmask 255.255.255.0 gateway XXX.XX.XX.XX
auto eth0
Where I put in this mail dummy values for the relevant entries.
And you have to change the bolean of ifup line on the file /etc/Networkmanager/Networkmanager.conf Try to do it an reboot ?
There is no [ifup] line only a [ifupdown] line
So should I change
[ifupdown] managed=false
To [ifupdown] managed=true
And just in case
[ifup] managed=true
2016-11-02 15:25 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com:
2016-11-02 12:25 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com: Hello, I'm using Debian, so it could be different for you. But you have to comment your eth0 lines on your file /etc/network/interfaces.
Hm thanks.
I renamed that file to interface-org, maybe this is not sufficient. Are you saying I should comment out *all* lines concerning eth0? Even auto eth0?
I have right now in the file interface-org
auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0
iface eth0 inet static address XXX.XX.XX.XX netmask 255.255.255.0 gateway XXX.XX.XX.XX
auto eth0
Where I put in this mail dummy values for the relevant entries.
And you have to change the bolean of ifup line on the file /etc/Networkmanager/Networkmanager.conf Try to do it an reboot ?
There is no [ifup] line only a [ifupdown] line
So should I change
[ifupdown] managed=false
To [ifupdown] managed=true
And just in case
[ifup] managed=true
I'll send you my files when i'll be back at home. I'm on my win7 job computer now =) But basically, you have to let NM , ond only NM manage your wired connection.
2016-11-02 15:25 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com:
2016-11-02 12:25 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com: Hello, I'm using Debian, so it could be different for you. But you have to comment your eth0 lines on your file /etc/network/interfaces.
Hm thanks.
I renamed that file to interface-org, maybe this is not sufficient. Are you saying I should comment out *all* lines concerning eth0? Even auto eth0?
I have right now in the file interface-org
auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0
iface eth0 inet static address XXX.XX.XX.XX netmask 255.255.255.0 gateway XXX.XX.XX.XX
auto eth0
Where I put in this mail dummy values for the relevant entries.
And you have to change the bolean of ifup line on the file /etc/Networkmanager/Networkmanager.conf Try to do it an reboot ?
There is no [ifup] line only a [ifupdown] line
So should I change
[ifupdown] managed=false
To [ifupdown] managed=true
And just in case
[ifup] managed=true
I'll send you my files when i'll be back at home. I'm on my win7 job computer now =) But basically, you have to let NM , ond only NM manage your wired connection.
Then, This is my two files :
nano /etc/network/interfaces =================================================== # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface auto lo iface lo inet loopback
# The primary network interface # allow-hotplug eth0 # iface eth0 inet dhcp ===================================================
Comment all lines about all of your interfaces you will use with NM.
nano /etc/NetworkManager/NetworkManager.conf =================================================== [main] plugins=ifupdown,keyfile
[ifupdown] managed=true ===================================================
And set ifupdown to true to all NM to managed all interfaces. Now your can create a new wired connection in NM with all the parameters you want.
Bye.
2016-11-02 18:28 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com:
On 02/11/16 17:11, Nicolas Dobigeon wrote:
2016-11-02 15:25 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com:
2016-11-02 12:25 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com: Hello, I'm using Debian, so it could be different for you. But you have to comment your eth0 lines on your file
/etc/network/interfaces.
Hm thanks.
I renamed that file to interface-org, maybe this is not sufficient. Are you saying I should comment out *all* lines concerning eth0? Even auto eth0?
I have right now in the file interface-org
auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0
iface eth0 inet static address XXX.XX.XX.XX netmask 255.255.255.0 gateway XXX.XX.XX.XX
auto eth0
Where I put in this mail dummy values for the relevant entries.
And you have to change the bolean of ifup line on the file /etc/Networkmanager/Networkmanager.conf Try to do it an reboot ?
There is no [ifup] line only a [ifupdown] line
So should I change
[ifupdown] managed=false
To [ifupdown] managed=true
And just in case
[ifup] managed=true
I'll send you my files when i'll be back at home. I'm on my win7 job computer now =) But basically, you have to let NM , ond only NM manage your wired connection.
Then, This is my two files :
thanks I have one question
nano /etc/network/interfaces
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
this line is strange, this directory is empty in my case, I will comment out that line?
# The loopback network interface auto lo iface lo inet loopback
# The primary network interface # allow-hotplug eth0
# iface eth0 inet dhcp
Comment all lines about all of your interfaces you will use with NM.
nano /etc/NetworkManager/NetworkManager.conf
[main] plugins=ifupdown,keyfile
[ifupdown] managed=true ===================================================
And set ifupdown to true to all NM to managed all interfaces. Now your can create a new wired connection in NM with all the parameters you want.
Bye.
You can comment this line, it should be OK, it exists for those who use multiple files to set many interfaces in different files.
2016-11-02 18:28 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com:
You can comment this line, it should be OK, it exists for those who use multiple files to set many interfaces in different files.
Ok, thanks very much, now it works as excepted! I switched several times between wireless and the wired net and the icon and the connection works now.
Last question: not to you necessarily but to the list:
When I set up the wired connection via tdenetworkmanager how can a specify more than 1 DNS server? a Comma separated list did not work, a simple space as separator neither. I checked the file /run/resolvconf/resolv.conf
But in my environment sometimes one of the DNS server fails. So it is prudent to specify more than only one.
Uwe Brauer wrote:
2016-11-02 18:28 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com:
You can comment this line, it should be OK, it exists for those who use multiple files to set many interfaces in different files.
Ok, thanks very much, now it works as excepted! I switched several times between wireless and the wired net and the icon and the connection works now.
Last question: not to you necessarily but to the list:
When I set up the wired connection via tdenetworkmanager how can a specify more than 1 DNS server? a Comma separated list did not work, a simple space as separator neither. I checked the file /run/resolvconf/resolv.conf
But in my environment sometimes one of the DNS server fails. So it is prudent to specify more than only one.
If you are obtaining IP via DHCP you can not set up additional information. If you setup the interface manually, try white space (If I recall correctly)
On Wednesday 02 November 2016 19:50:44 deloptes wrote:
Uwe Brauer wrote:
2016-11-02 18:28 GMT+01:00 Uwe Brauer oub.oub.oub@gmail.com:
You can comment this line, it should be OK, it exists for those who use multiple files to set many interfaces in different files.
Ok, thanks very much, now it works as excepted! I switched several times between wireless and the wired net and the icon and the connection works now.
Last question: not to you necessarily but to the list:
When I set up the wired connection via tdenetworkmanager how can a specify more than 1 DNS server? a Comma separated list did not work, a simple space as separator neither. I checked the file /run/resolvconf/resolv.conf
But in my environment sometimes one of the DNS server fails. So it is prudent to specify more than only one.
If you are obtaining IP via DHCP you can not set up additional information. If you setup the interface manually, try white space (If I recall correctly)
Uwe Brauer,
The resolvconf will have a problem ... it'll be system wide. You won't be able to have different DNS for different connection, for exemple at home and at work.
In your cas you should set in your connection setting in NM. But the TDE-NM is not the most complete, there is only one field to set DNS servers. Also, you can try to use the ncurses NM tool "nmtui" where you will be able to get two DNS field. I never had to use it in my case but it should be OK for you.
Bye.
On Wed, 2 Nov 2016, Uwe Brauer wrote:
When I set up the wired connection via tdenetworkmanager how can a specify more than 1 DNS server? a Comma separated list did not work, a simple space as separator neither. I checked the file /run/resolvconf/resolv.conf
But in my environment sometimes one of the DNS server fails. So it is prudent to specify more than only one.
In my resolv.conf I use multiple lines. viz:
nameserver 1.2.3.4 nameserver 4.5.6.7 nameserver 8.9.10.11 ... etc/usw.
Jonesy
-
deloptes -
Dobigeon Nicolas -
Jonesy -
Nicolas Dobigeon
-
Uwe Brauer -
Uwe Brauer