systemsettings and tdenetworkmanager switching between wired and wireless problem with DNS server
Hi - I used /opt/trinity/bin/systemsettings for setting the wired net
- and tdenetworkmanager for the wireless net.
Maybe this is not smart and I had no problems, when passing from wired --> wireless but problems when passing from wireless --> wired since the wireless deleted the DNS server entries in the resolv.conf
So usually I manually copied a backup of resolv.conf to /etc and run
sudo /etc/init.d/networking restart
But this does not work anymore in 14.04 as we discussed. So what is the smart way of configuring wired/wireless and what is the smart way of switching between wired/wireless????
Relying entirely on systemsettings or on tdenetworkmanager?
Uwe Brauer
Uwe Brauer wrote:
Relying entirely on systemsettings or on tdenetworkmanager?
yes my experience with NM is that is picky on others dealing with network settings, so I recommend using only NM. Do all your configurations there and clean up the rest. This is what I can recommend.
regards
"deloptes" == deloptes deloptes@gmail.com writes:
Uwe Brauer wrote:
Relying entirely on systemsettings or on tdenetworkmanager?
yes my experience with NM is that is picky on others dealing with network settings, so I recommend using only NM. Do all your configurations there and clean up the rest. This is what I can recommend.
Ok I tried that. I deactivated wired in systemsettings and tried to turn it on via tdenetworkmanager. Did not work out no connection. I attach a screenshot of my configuration data
Uwe
On Thursday 15 September 2016 11:01:10 Uwe Brauer wrote:
"deloptes" == deloptes deloptes@gmail.com writes:
Uwe Brauer wrote:
Relying entirely on systemsettings or on tdenetworkmanager?
yes my experience with NM is that is picky on others dealing with network settings, so I recommend using only NM. Do all your configurations there and clean up the rest. This is what I can recommend.
Ok I tried that. I deactivated wired in systemsettings and tried to turn it on via tdenetworkmanager. Did not work out no connection. I attach a screenshot of my configuration data
Uwe
Have you tried connecting your wired connection via DHCP? What happens?
To what PRECISELY are you trying to connect? My equivalent settings would be: IP address 192.168.0.2 Netmask 255.255.255.0 Gateway 192.168.0.1
I connect to the Internet via a modem-router, which connects to my ISP.
But I find it better to use DHCP in all individual machines (from Kindle, to the TV, to my desktop) and have the router dish out set IPs to named Mac Addresses (including wireless ones, so, FWIW, my Kindle always has the same IP).
Lisi
On Thursday 15 September 2016 11:01:10 Uwe Brauer wrote:
Have you tried connecting your wired connection via DHCP? What happens?
I cannot, my university does not support DHCP via wired, only via wireless.
To what PRECISELY are you trying to connect? My equivalent settings would be:
IP address 192.168.0.2 Netmask 255.255.255.0 Gateway 192.168.0.1
I have feeling that the setting of the DNS servers is not correct, but I don't know what to do.
Uwe
On Thursday 15 September 2016 15:04:01 Uwe Brauer wrote:
On Thursday 15 September 2016 11:01:10 Uwe Brauer wrote:
Have you tried connecting your wired connection via DHCP? What happens?
I cannot, my university does not support DHCP via wired, only via wireless.
To what PRECISELY are you trying to connect? My equivalent settings would be:
IP address 192.168.0.2 Netmask 255.255.255.0 Gateway 192.168.0.1
I have feeling that the setting of the DNS servers is not correct, but I don't know what to do.
Try 8.8.8.8 and 8.8.4.4 and see if it helps. Change it back if it doesn't!
We haven't really got enough information about the network.
Lisi
On Thursday 15 September 2016 15:04:01 Uwe Brauer wrote:
Try 8.8.8.8 and 8.8.4.4 and see if it helps. Change it back if it doesn't!
We haven't really got enough information about the network.
I am not sure what you mean.
Static Ip 147.96.12.44 Gateway 147.96.12.1 DNS Server 147.96.2.4 DNS Server 147.96.1.9
These are the data I inserted in Kubuntu's systemsettings and the wired connection works, I tried the same setting (as my screenshot indicated) but the wired connection does not work.
On Friday 16 September 2016 10:55:23 Uwe Brauer wrote:
On Thursday 15 September 2016 15:04:01 Uwe Brauer wrote:
Try 8.8.8.8 and 8.8.4.4 and see if it helps. Change it back if it doesn't!
We haven't really got enough information about the network.
I am not sure what you mean.
Static Ip 147.96.12.44 Gateway 147.96.12.1 DNS Server 147.96.2.4 DNS Server 147.96.1.9
These are the data I inserted in Kubuntu's systemsettings and the wired connection works, I tried the same setting (as my screenshot indicated) but the wired connection does not work.
That doesn't say what the network is.
If using only TDENetworkManager doesn't work, why not try using only Kubuntu?
Meanwhile, get up the wireless access that works then do: $ ip addr and post the result, to see if it will give either me or someone else a clue as to your network.
Lisi
Uwe is saying to use 8.8.8.8 and 8.8.4.4 as your DNS servers just to check. The system may not be able to reach the old ones regularly. The above ones are Google's and they do allow or at least don't stop people from using them.
On Fri, Sep 16, 2016 at 6:14 AM, Lisi Reisz lisi.reisz@gmail.com wrote:
On Friday 16 September 2016 10:55:23 Uwe Brauer wrote:
On Thursday 15 September 2016 15:04:01 Uwe Brauer wrote:
Try 8.8.8.8 and 8.8.4.4 and see if it helps. Change it back if it doesn't!
We haven't really got enough information about the network.
I am not sure what you mean.
Static Ip 147.96.12.44 Gateway 147.96.12.1 DNS Server 147.96.2.4 DNS Server 147.96.1.9
These are the data I inserted in Kubuntu's systemsettings and the wired connection works, I tried the same setting (as my screenshot indicated) but the wired connection does not work.
That doesn't say what the network is.
If using only TDENetworkManager doesn't work, why not try using only Kubuntu?
Meanwhile, get up the wireless access that works then do: $ ip addr and post the result, to see if it will give either me or someone else a clue as to your network.
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@ lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists. pearsoncomputing.net Read list messages on the web archive: http://trinity-users. pearsoncomputing.net/ Please remember not to top-post: http://trinity. pearsoncomputing.net/mailing_lists/#top-posting
On Friday 16 September 2016 11:23:24 Pisini, John wrote:
Uwe is saying to use 8.8.8.8 and 8.8.4.4 as your DNS servers just to check. The system may not be able to reach the old ones regularly. The above ones are Google's and they do allow or at least don't stop people from using them.
No, Uwe has the problem. I suggested Google's for exactly that reason, but Uwe did not report back.
Lisi
"Lisi" == Lisi Reisz lisi.reisz@gmail.com writes:
On Friday 16 September 2016 11:23:24 Pisini, John wrote:
Uwe is saying to use 8.8.8.8 and 8.8.4.4 as your DNS servers just to check. The system may not be able to reach the old ones regularly. The above ones are Google's and they do allow or at least don't stop people from using them.
No, Uwe has the problem. I suggested Google's for exactly that reason, but Uwe did not report back.
Ok I tried it out. I first disabled my wired net via systemsetting and then called tdenetworkmanager.
I attach the screenshot2 of the setting and the symbol of the icon, which indicates IMHO that it does not connect to the wired net. Please tell me whether the screenshots arrive.
Uwe Brauer wrote:
"Lisi" == Lisi Reisz lisi.reisz@gmail.com writes:
On Friday 16 September 2016 11:23:24 Pisini, John wrote:
Uwe is saying to use 8.8.8.8 and 8.8.4.4 as your DNS servers just to check. The system may not be able to reach the old ones regularly. The above ones are Google's and they do allow or at least don't stop people from using them.
No, Uwe has the problem. I suggested Google's for exactly that reason, but Uwe did not report back.
Ok I tried it out. I first disabled my wired net via systemsetting and then called tdenetworkmanager.
I attach the screenshot2 of the setting and the symbol of the icon, which indicates IMHO that it does not connect to the wired net. Please tell me whether the screenshots arrive.
I say use one or another. It could be also that NM from trinity is not in sync with ubuntus whatever, but in my opinion Uwe should not use system settings at all. For this, one needs to enter root password and NM is designed to do the work from user perspective.
regards
On Friday 16 September 2016 16:43:51 deloptes wrote:
Uwe Brauer wrote:
"Lisi" == Lisi Reisz
lisi.reisz@gmail.com writes:
On Friday 16 September 2016 11:23:24 Pisini, John wrote:
Uwe is saying to use 8.8.8.8 and 8.8.4.4 as your DNS servers just to check. The system may not be able to reach the old ones regularly. The above ones are Google's and they do allow or at least don't stop people from using them.
No, Uwe has the problem. I suggested Google's for exactly that reason, but Uwe did not report back.
Ok I tried it out. I first disabled my wired net via systemsetting and then called tdenetworkmanager.
I attach the screenshot2 of the setting and the symbol of the icon, which indicates IMHO that it does not connect to the wired net. Please tell me whether the screenshots arrive.
I say use one or another. It could be also that NM from trinity is not in sync with ubuntus whatever, but in my opinion Uwe should not use system settings at all. For this, one needs to enter root password and NM is designed to do the work from user perspective.
regards
I'm so glad someone that knows a GUI network manager from a well shoed racehorse has joined in this conversation!!
Lisi
On Friday 16 September 2016 15:53:03 Uwe Brauer wrote:
"Lisi" == Lisi Reisz lisi.reisz@gmail.com writes:
On Friday 16 September 2016 11:23:24 Pisini, John wrote:
Uwe is saying to use 8.8.8.8 and 8.8.4.4 as your DNS servers just to check. The system may not be able to reach the old ones regularly. The above ones are Google's and they do allow or at least don't stop people from using them.
No, Uwe has the problem. I suggested Google's for exactly that reason, but Uwe did not report back.
Ok I tried it out. I first disabled my wired net via systemsetting and then called tdenetworkmanager.
It sounds as though the two were being asked to give conflicting orders. I should remove it from one before testing the other. It may simply not have been working because system setting told it not to.
I attach the screenshot2 of the setting and the symbol of the icon, which indicates IMHO that it does not connect to the wired net. Please tell me whether the screenshots arrive.
The screenshots arrived, but I am afraid that I am not used to sorting networks out by looking at icons and I'm not really sure what I am looking at.
Did you run $ ip addr while the wireless was working?
If it is working, then do: $ ping 8.8.8.8
followed by
$ ping www.google.com
and send us the results. You may have to use ^C to stop the ping command, depending on how your system is set up.
DNS shouldn't affect connection, only finding sites.
I still have no picture of your network at all.
How (apart from the icon) do you know whether it is working or not?
Lisi
On Friday 16 September 2016 16:51:58 Lisi Reisz wrote:
On Friday 16 September 2016 15:53:03 Uwe Brauer wrote:
"Lisi" == Lisi Reisz lisi.reisz@gmail.com writes:
On Friday 16 September 2016 11:23:24 Pisini, John wrote:
Uwe is saying to use 8.8.8.8 and 8.8.4.4 as your DNS servers just to check. The system may not be able to reach the old ones regularly. The above ones are Google's and they do allow or at least don't stop people from using them.
No, Uwe has the problem. I suggested Google's for exactly that reason, but Uwe did not report back.
Ok I tried it out. I first disabled my wired net via systemsetting and then called tdenetworkmanager.
It sounds as though the two were being asked to give conflicting orders. I should remove it from one before testing the other. It may simply not have been working because system setting told it not to.
I attach the screenshot2 of the setting and the symbol of the icon, which indicates IMHO that it does not connect to the wired net. Please tell me whether the screenshots arrive.
The screenshots arrived, but I am afraid that I am not used to sorting networks out by looking at icons and I'm not really sure what I am looking at.
Did you run $ ip addr while the wireless was working?
If it is working, then do: $ ping 8.8.8.8
followed by
$ ping www.google.com
and send us the results. You may have to use ^C to stop the ping command, depending on how your system is set up.
DNS shouldn't affect connection, only finding sites.
I still have no picture of your network at all.
How (apart from the icon) do you know whether it is working or not?
Uwe - sorry, I should have asked. Do you know how to use a terminal? (Otherwise said, do you know how to work at the CLI?)
Lisi
-
deloptes -
Lisi Reisz -
Pisini, John -
Uwe Brauer -
Uwe Brauer