[opensuse] NetworkManager fails with dhcp time-out
openSUSE 13.2 I cannot and have never succeeded getting NetworkManager to work with my wireless machines. My latest attempt on an acer laptop seems to fail with dhcp timing out, logs are at: http://wahoo.no-ip.org/~pat/NetworkManager.log.txt google searches have provided some hits but nothing that I find helps. Please help me solve this. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed 03 Dec 2014 08:50:22 AM CST, Patrick Shanahan wrote:
openSUSE 13.2
I cannot and have never succeeded getting NetworkManager to work with my wireless machines. My latest attempt on an acer laptop seems to fail with dhcp timing out, logs are at: http://wahoo.no-ip.org/~pat/NetworkManager.log.txt
google searches have provided some hits but nothing that I find helps.
Please help me solve this.
tks, Hi I see that with wireless routers set to n speed only and 1x1 adapters.
-- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default up 19:55, 3 users, load average: 0.02, 0.06, 0.08 CPU Intel® B840@1.9GHz | GPU Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Malcolm <malcolmlewis@cableone.net> [12-03-14 09:58]:
On Wed 03 Dec 2014 08:50:22 AM CST, Patrick Shanahan wrote:
openSUSE 13.2
I cannot and have never succeeded getting NetworkManager to work with my wireless machines. My latest attempt on an acer laptop seems to fail with dhcp timing out, logs are at: http://wahoo.no-ip.org/~pat/NetworkManager.log.txt
google searches have provided some hits but nothing that I find helps.
Please help me solve this.
tks,
Hi I see that with wireless routers set to n speed only and 1x1 adapters.
I don't understand ?? What are you saying I should do? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed 03 Dec 2014 10:05:35 AM CST, Patrick Shanahan wrote:
* Malcolm <malcolmlewis@cableone.net> [12-03-14 09:58]:
On Wed 03 Dec 2014 08:50:22 AM CST, Patrick Shanahan wrote:
openSUSE 13.2
I cannot and have never succeeded getting NetworkManager to work with my wireless machines. My latest attempt on an acer laptop seems to fail with dhcp timing out, logs are at: http://wahoo.no-ip.org/~pat/NetworkManager.log.txt
google searches have provided some hits but nothing that I find helps.
Please help me solve this.
tks,
Hi I see that with wireless routers set to n speed only and 1x1 adapters.
I don't understand ?? What are you saying I should do?
tks, Hi Check your wireless router configuration. I see it here with a SBG6580 if I set to only use 'n' speed and the adapter is a 1x1 type;
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Hewlett-Packard Company AR9485/HB125 802.11bgn 1×1 Wi-Fi Adapter [103c:1838] If I can get the router to set the bandwidth at 40Mhz it's fine I get 150Mb/s, but it drops back to 20Mhz sometimes and see what your seeing, turn off the 'n' speed only wireless drops back to 72.2Mb/s and connects... -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default up 20:34, 3 users, load average: 0.04, 0.11, 0.16 CPU Intel® B840@1.9GHz | GPU Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Malcolm <malcolmlewis@cableone.net> [12-03-14 10:44]:
On Wed 03 Dec 2014 10:05:35 AM CST, Patrick Shanahan wrote:
* Malcolm <malcolmlewis@cableone.net> [12-03-14 09:58]:
On Wed 03 Dec 2014 08:50:22 AM CST, Patrick Shanahan wrote:
openSUSE 13.2
I cannot and have never succeeded getting NetworkManager to work with my wireless machines. My latest attempt on an acer laptop seems to fail with dhcp timing out, logs are at: http://wahoo.no-ip.org/~pat/NetworkManager.log.txt
google searches have provided some hits but nothing that I find helps.
Please help me solve this.
tks,
Hi I see that with wireless routers set to n speed only and 1x1 adapters.
I don't understand ?? What are you saying I should do?
tks, Hi Check your wireless router configuration. I see it here with a SBG6580 if I set to only use 'n' speed and the adapter is a 1x1 type;
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Hewlett-Packard Company AR9485/HB125 802.11bgn 1×1 Wi-Fi Adapter [103c:1838]
If I can get the router to set the bandwidth at 40Mhz it's fine I get 150Mb/s, but it drops back to 20Mhz sometimes and see what your seeing, turn off the 'n' speed only wireless drops back to 72.2Mb/s and connects...
Would that be relevant since the connection works fine using wicked? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed 03 Dec 2014 02:30:50 PM CST, Patrick Shanahan wrote:
* Malcolm <malcolmlewis@cableone.net> [12-03-14 10:44]:
On Wed 03 Dec 2014 10:05:35 AM CST, Patrick Shanahan wrote:
* Malcolm <malcolmlewis@cableone.net> [12-03-14 09:58]:
On Wed 03 Dec 2014 08:50:22 AM CST, Patrick Shanahan wrote:
openSUSE 13.2
I cannot and have never succeeded getting NetworkManager to work with my wireless machines. My latest attempt on an acer laptop seems to fail with dhcp timing out, logs are at: http://wahoo.no-ip.org/~pat/NetworkManager.log.txt
google searches have provided some hits but nothing that I find helps.
Please help me solve this.
tks,
Hi I see that with wireless routers set to n speed only and 1x1 adapters.
I don't understand ?? What are you saying I should do?
tks, Hi Check your wireless router configuration. I see it here with a SBG6580 if I set to only use 'n' speed and the adapter is a 1x1 type;
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Hewlett-Packard Company AR9485/HB125 802.11bgn 1×1 Wi-Fi Adapter [103c:1838]
If I can get the router to set the bandwidth at 40Mhz it's fine I get 150Mb/s, but it drops back to 20Mhz sometimes and see what your seeing, turn off the 'n' speed only wireless drops back to 72.2Mb/s and connects...
Would that be relevant since the connection works fine using wicked?
Hi Hmmm, well I only see it with 1x1 adapters running NM, the other devices are fine, including one using wicked. -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default up 1 day 1:06, 4 users, load average: 0.22, 0.16, 0.19 CPU Intel® B840@1.9GHz | GPU Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-03 14:50, Patrick Shanahan wrote:
openSUSE 13.2
I cannot and have never succeeded getting NetworkManager to work with my wireless machines. My latest attempt on an acer laptop seems to fail with dhcp timing out, logs are at: http://wahoo.no-ip.org/~pat/NetworkManager.log.txt
Does it work if you set a fixed IP? I see that your network associates, that is, you get a connection, apparently:
Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> (wlp3s0): supplicant interface state: 4-way handshake -> completed Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network '.....'. Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled. Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started... Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0] Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds) Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> dhclient started with pid 7269 ... Dec 02 23:25:18 acer.wahoo.no-ip.org dhclient[7269]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x5a64e896) Dec 02 23:25:18 acer.wahoo.no-ip.org NetworkManager[856]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x5a64e896) Dec 02 23:25:25 acer.wahoo.no-ip.org NetworkManager[856]: <warn> (wlp3s0): DHCPv4 request timed out. Dec 02 23:25:25 acer.wahoo.no-ip.org dhclient[7269]: Received signal 15, initiating shutdown.
There are two dhcp clients, maybe you have to try with "the other". I never remember which. Or simply try with a fixed IP, at least temporarily. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wed, Dec 03, 2014 at 10:03:03PM +0100, Carlos E. R. wrote:
On 2014-12-03 14:50, Patrick Shanahan wrote:
openSUSE 13.2
I cannot and have never succeeded getting NetworkManager to work with my wireless machines. My latest attempt on an acer laptop seems to fail with dhcp timing out, logs are at: http://wahoo.no-ip.org/~pat/NetworkManager.log.txt
Does it work if you set a fixed IP?
I see that your network associates, that is, you get a connection, apparently:
This has been a constant problem and it is systemd related, and I'm not being toungue in cheek. Something changed and on several laptops I have and in diferent environments, when networkmanger is on, it doesn't do cryptography correclty, of who hell knows what is wrong because there is no system log. If you stop Network manager with systemd and run it with wicd straight, it works.... and then even that seems to ultimately stop working. Meanwhile, in the same exact enviroment, Manjaro Openrc with wicd, it works nearly flawlessly everywhere.
Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> (wlp3s0): supplicant interface state: 4-way handshake -> completed Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network '.....'. Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled. Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started... Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0] Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds) Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> dhclient started with pid 7269 ... Dec 02 23:25:18 acer.wahoo.no-ip.org dhclient[7269]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x5a64e896) Dec 02 23:25:18 acer.wahoo.no-ip.org NetworkManager[856]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x5a64e896) Dec 02 23:25:25 acer.wahoo.no-ip.org NetworkManager[856]: <warn> (wlp3s0): DHCPv4 request timed out. Dec 02 23:25:25 acer.wahoo.no-ip.org dhclient[7269]: Received signal 15, initiating shutdown.
There are two dhcp clients, maybe you have to try with "the other". I never remember which. Or simply try with a fixed IP, at least temporarily.
-- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [12-03-14 16:04]:
On 2014-12-03 14:50, Patrick Shanahan wrote:
openSUSE 13.2
I cannot and have never succeeded getting NetworkManager to work with my wireless machines. My latest attempt on an acer laptop seems to fail with dhcp timing out, logs are at: http://wahoo.no-ip.org/~pat/NetworkManager.log.txt
Does it work if you set a fixed IP?
I used yast-network and set fixed ip and it worked in wicked. Did not change dhcp (4&6) used yast to change to NWMan enabled NWM widgett Says it is trying to connect says setting network address never connected rebooted still trying to connect, gets to "setting network address" and nothing more. finally (17:18) stopped NWM and used yast to change back to wicked. left static address (192.168.1.14) network is up but only local and cannot ping outside by name or numerical removed static addr and now have full netowrk access reassigned static addr and lost network outside router removed static addr and regained access outside router That part of problem may be in router ??? NetworkManager logs from time changed to NWM to changing back to wicked are: http://wahoo.no-ip.org/~pat/NetworkManager.log1.txt
I see that your network associates, that is, you get a connection, apparently:
Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> (wlp3s0): supplicant interface state: 4-way handshake -> completed Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network '.....'. Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled. Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started... Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0] Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds) Dec 02 23:24:39 acer.wahoo.no-ip.org NetworkManager[856]: <info> dhclient started with pid 7269 ... Dec 02 23:25:18 acer.wahoo.no-ip.org dhclient[7269]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x5a64e896) Dec 02 23:25:18 acer.wahoo.no-ip.org NetworkManager[856]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x5a64e896) Dec 02 23:25:25 acer.wahoo.no-ip.org NetworkManager[856]: <warn> (wlp3s0): DHCPv4 request timed out. Dec 02 23:25:25 acer.wahoo.no-ip.org dhclient[7269]: Received signal 15, initiating shutdown.
There are two dhcp clients, maybe you have to try with "the other". I never remember which. Or simply try with a fixed IP, at least temporarily.
changed to fixed ip and was able to connect using wicked the dhcp clients allow dhcp 4 dhcp 6 dhcp 4&6 I have dhcp 4&6 but dhcp4 is failing and afaik, dhcp6 is not used here... tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-03 23:45, Patrick Shanahan wrote:
* Carlos E. R. <> [12-03-14 16:04]:
Does it work if you set a fixed IP?
I used yast-network and set fixed ip and it worked in wicked. Did not change dhcp (4&6) used yast to change to NWMan enabled NWM widgett
No, no. Set a fixed IP in Network manager. Of course, you will also need to define the gateway and the name server manually.
There are two dhcp clients, maybe you have to try with "the other". I never remember which. Or simply try with a fixed IP, at least temporarily.
changed to fixed ip and was able to connect using wicked
the dhcp clients allow dhcp 4 dhcp 6 dhcp 4&6
I have dhcp 4&6 but dhcp4 is failing and afaik, dhcp6 is not used here...
No, I refer to dhcp-client vs dhcpcd. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/03/2014 05:47 PM, Carlos E. R. wrote:
No, I refer to dhcp-client vs dhcpcd.
Do you mean dhclient ? - -- After all is said and done, more is said than done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlR/xnAACgkQv7M3G5+2DLJBigCfYLtEFU475pf/7miDRPZqDva/ ou0AnRnhp0cK84balHcwOrygvHOMD+/u =vUAI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-04 03:26, John Andersen wrote:
On 12/03/2014 05:47 PM, Carlos E. R. wrote:
No, I refer to dhcp-client vs dhcpcd.
Do you mean dhclient ?
Maybe. I'm unsure. I just looked at the rpm names. I know that there are two different clients, and I know that some people need to use the "other", whichever that is, or the "other other". But I don't remember using that trick myself, so I don't remember the name of each one or the details of the trick. O:-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [12-03-14 21:50]:
On 2014-12-04 03:26, John Andersen wrote:
On 12/03/2014 05:47 PM, Carlos E. R. wrote:
No, I refer to dhcp-client vs dhcpcd.
Do you mean dhclient ?
Maybe. I'm unsure. I just looked at the rpm names.
I know that there are two different clients, and I know that some people need to use the "other", whichever that is, or the "other other". But I don't remember using that trick myself, so I don't remember the name of each one or the details of the trick.
#> zypper se -is dhc Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+-------------+---------+-----------------+--------+--------------------- i | dhcp | package | 4.2.6-9.5.1 | x86_64 | openSUSE-13.2-Update i | dhcp-client | package | 4.2.6-9.5.1 | x86_64 | openSUSE-13.2-Update i | dhcpcd | package | 3.2.3-47.80.6.1 | x86_64 | openSUSE-13.2-Oss -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [12-03-14 20:48]:
On 2014-12-03 23:45, Patrick Shanahan wrote:
* Carlos E. R. <> [12-03-14 16:04]:
Does it work if you set a fixed IP?
I used yast-network and set fixed ip and it worked in wicked. Did not change dhcp (4&6) used yast to change to NWMan enabled NWM widgett
No, no. Set a fixed IP in Network manager. Of course, you will also need to define the gateway and the name server manually.
yes 192.168.1.14 255.255.255.0 search nfs2.no-ip.org clmboh1-dns2.columbus.rr.com wahoo.no-ip.org nameserver 129.250.35.250 nameserver 209.253.113.18 nameserver 205.171.3.65 but no luck :^( tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 3 december 2014 23:30:03 schreef Patrick Shanahan:
* Carlos E. R. <robin.listas@telefonica.net> [12-03-14 20:48]:
On 2014-12-03 23:45, Patrick Shanahan wrote:
* Carlos E. R. <> [12-03-14 16:04]:
Does it work if you set a fixed IP?
I used yast-network and set fixed ip and it worked in wicked. Did not change dhcp (4&6) used yast to change to NWMan enabled NWM widgett
No, no. Set a fixed IP in Network manager. Of course, you will also need to define the gateway and the name server manually.
yes 192.168.1.14 255.255.255.0 search nfs2.no-ip.org clmboh1-dns2.columbus.rr.com wahoo.no-ip.org nameserver 129.250.35.250 nameserver 209.253.113.18 nameserver 205.171.3.65
but no luck :^(
tks,
The IP address of the gateway is missing. Probably 192.168.1.1. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Freek de Kruijf <freek@opensuse.org> [12-04-14 04:21]:
Op woensdag 3 december 2014 23:30:03 schreef Patrick Shanahan:
* Carlos E. R. <robin.listas@telefonica.net> [12-03-14 20:48]:
On 2014-12-03 23:45, Patrick Shanahan wrote:
* Carlos E. R. <> [12-03-14 16:04]:
Does it work if you set a fixed IP?
I used yast-network and set fixed ip and it worked in wicked. Did not change dhcp (4&6) used yast to change to NWMan enabled NWM widgett
No, no. Set a fixed IP in Network manager. Of course, you will also need to define the gateway and the name server manually.
yes 192.168.1.14 255.255.255.0 search nfs2.no-ip.org clmboh1-dns2.columbus.rr.com wahoo.no-ip.org nameserver 129.250.35.250 nameserver 209.253.113.18 nameserver 205.171.3.65
but no luck :^(
tks,
The IP address of the gateway is missing. Probably 192.168.1.1.
my bad, you are correct, gateway is 192.168.1.1, router addr. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-04 14:57, Patrick Shanahan wrote:
No, no. Set a fixed IP in Network manager. Of course, you will also need to define the gateway and the name server manually.
yes 192.168.1.14 255.255.255.0 search nfs2.no-ip.org clmboh1-dns2.columbus.rr.com wahoo.no-ip.org nameserver 129.250.35.250 nameserver 209.253.113.18 nameserver 205.171.3.65
but no luck :^(
tks,
The IP address of the gateway is missing. Probably 192.168.1.1.
my bad, you are correct, gateway is 192.168.1.1, router addr.
And what exactly happened? We are talking of network manager with manual fixed config. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [12-04-14 09:59]:
On 2014-12-04 14:57, Patrick Shanahan wrote:
No, no. Set a fixed IP in Network manager. Of course, you will also need to define the gateway and the name server manually.
yes 192.168.1.14 255.255.255.0 search nfs2.no-ip.org clmboh1-dns2.columbus.rr.com wahoo.no-ip.org nameserver 129.250.35.250 nameserver 209.253.113.18 nameserver 205.171.3.65
but no luck :^(
tks,
The IP address of the gateway is missing. Probably 192.168.1.1.
my bad, you are correct, gateway is 192.168.1.1, router addr.
And what exactly happened?
We are talking of network manager with manual fixed config.
I set them in yast-netowrk and then changed to NetworkManager network control (in yast). Where do you manually fix the config for NM, my /etc/NetworkManager/NetworkManager.conf [main] plugins=ifcfg-suse,keyfile Hold the Presses! I have one laptop working. Enabled NM wiget, configured network from the widget wrench assigning fixed ip and router gateway, 192.168.1.1, and connected from the config menu. Closed the config menu and am now able to reconnect using the widgettttt. Trying the other laptop and will advise. tks much, guess the secret is gateway and fixed ip. What happens when I travel and use, say HolidayInn's network. Have to again use a fixed or same fixed ip and gateway ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [12-04-14 14:40]:
* Carlos E. R. <robin.listas@telefonica.net> [12-04-14 09:59]:
On 2014-12-04 14:57, Patrick Shanahan wrote:
No, no. Set a fixed IP in Network manager. Of course, you will also need to define the gateway and the name server manually.
yes 192.168.1.14 255.255.255.0 search nfs2.no-ip.org clmboh1-dns2.columbus.rr.com wahoo.no-ip.org nameserver 129.250.35.250 nameserver 209.253.113.18 nameserver 205.171.3.65
but no luck :^(
tks,
The IP address of the gateway is missing. Probably 192.168.1.1.
my bad, you are correct, gateway is 192.168.1.1, router addr.
And what exactly happened?
We are talking of network manager with manual fixed config.
I set them in yast-netowrk and then changed to NetworkManager network control (in yast).
Where do you manually fix the config for NM, my
/etc/NetworkManager/NetworkManager.conf [main] plugins=ifcfg-suse,keyfile
Hold the Presses!
I have one laptop working. Enabled NM wiget, configured network from the widget wrench assigning fixed ip and router gateway, 192.168.1.1, and connected from the config menu.
Closed the config menu and am now able to reconnect using the widgettttt.
Trying the other laptop and will advise.
tks much, guess the secret is gateway and fixed ip. What happens when I travel and use, say HolidayInn's network. Have to again use a fixed or same fixed ip and gateway ???
Ok, both laptops will now connect using NM but *only* at runlevel 5. If I log out of the GUI or decend to runlevel 3, I have no internet connection and do not seem to be able to achieve it using nmtui/nmtui-connect/nmtui-edit/.... tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 4 december 2014 15:25:00 schreef Patrick Shanahan:
Ok, both laptops will now connect using NM but *only* at runlevel 5. If I log out of the GUI or decend to runlevel 3, I have no internet connection and do not seem to be able to achieve it using nmtui/nmtui-connect/nmtui-edit/....
When you edit the connection (select the connection name and press Edit) you will see a number of tabs. In the one with the General settings you have to check that all users are allowed to use that connection. In that case the connection will be made during boot time and is available even without a user being logged in. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Thu, 4 Dec 2014 15:25:00 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Patrick Shanahan <paka@opensuse.org> [12-04-14 14:40]:
* Carlos E. R. <robin.listas@telefonica.net> [12-04-14 09:59]:
On 2014-12-04 14:57, Patrick Shanahan wrote:
> No, no. Set a fixed IP in Network manager. Of course, you will also need > to define the gateway and the name server manually.
yes 192.168.1.14 255.255.255.0 search nfs2.no-ip.org clmboh1-dns2.columbus.rr.com wahoo.no-ip.org nameserver 129.250.35.250 nameserver 209.253.113.18 nameserver 205.171.3.65
but no luck :^(
tks,
The IP address of the gateway is missing. Probably 192.168.1.1.
my bad, you are correct, gateway is 192.168.1.1, router addr.
And what exactly happened?
We are talking of network manager with manual fixed config.
I set them in yast-netowrk and then changed to NetworkManager network control (in yast).
Where do you manually fix the config for NM, my
/etc/NetworkManager/NetworkManager.conf [main] plugins=ifcfg-suse,keyfile
Hold the Presses!
I have one laptop working. Enabled NM wiget, configured network from the widget wrench assigning fixed ip and router gateway, 192.168.1.1, and connected from the config menu.
Closed the config menu and am now able to reconnect using the widgettttt.
Trying the other laptop and will advise.
tks much, guess the secret is gateway and fixed ip. What happens when I travel and use, say HolidayInn's network. Have to again use a fixed or same fixed ip and gateway ???
Ok, both laptops will now connect using NM but *only* at runlevel 5. If I log out of the GUI or decend to runlevel 3, I have no internet connection and do not seem to be able to achieve it using nmtui/nmtui-connect/nmtui-edit/....
NM needs AP secrets; these secrets can either be stored in NM configuration directly or provided by user agent running as part as user session. The widget you mention not only offers GUI to configure NM, but also provides user agent that supplies passwords on request. These agents traditionally were available for GUI sessions only and stored secrets in KDE KWallet or GNOME Keyring. When you designate connection as "available for all users" (or "system connection") secrets are stored centrally so NM can connect without waiting for a user. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 4 december 2014 14:38:54 schreef Patrick Shanahan:
Where do you manually fix the config for NM, my
/etc/NetworkManager/NetworkManager.conf [main] plugins=ifcfg-suse,keyfile
When you edit a connection in the NM widget, in the tab General settings, you can check "All users are allowed to make connections with this network", there will be a file in /etc/NetworkManager/system-connections/ with the name of the connection in which the details for this connection are present. So if you know what to enter there you can configure connections there. When you have them ready there, you can copy them to another system (newly generated system). -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/04/2014 11:38 AM, Patrick Shanahan wrote:
tks much, guess the secret is gateway and fixed ip. What happens when I travel and use, say HolidayInn's network. Have to again use a fixed or same fixed ip and gateway ???
Seriously, don't you think EVERYONE would be howling if that was the case? You seem to be on the Lynn-route (Sorry Lynn) of compounding problems due to an excess of hacking in partial fixes in the wrong place. Your DHCP client should work, and it should set the gateway, the broadcast, the name servers for you. These problems were all solved somewhere around 1984. GET THAT working and you will be able to stop all this silly hacking in of manual IPs. Why does your dhclient not work? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [12-04-14 15:48]:
On 12/04/2014 11:38 AM, Patrick Shanahan wrote:
tks much, guess the secret is gateway and fixed ip. What happens when I travel and use, say HolidayInn's network. Have to again use a fixed or same fixed ip and gateway ???
Seriously, don't you think EVERYONE would be howling if that was the case? You seem to be on the Lynn-route (Sorry Lynn) of compounding problems due to an excess of hacking in partial fixes in the wrong place.
Your DHCP client should work, and it should set the gateway, the broadcast, the name servers for you. These problems were all solved somewhere around 1984. GET THAT working and you will be able to stop all this silly hacking in of manual IPs.
Why does your dhclient not work?
The apparently it never has. I presently have three wireless connections locally from openSUSE boxes/laptops that all failed on initial setup/install to connect using NM, so being more familiar with if{up,down,in-th-middle}, I changed using yast{network}. What is and how to test, the problem with dhclient? I have not experienced this previous. tks, ps: I do not take the "Lynn-route" (also sorry) but follow the main route excepting the use of some non=standard repos for items I require. But don't we all do so? ps2: Having never been able to use NM and always being successful with ifup, I had no need before to worry about NM, and haven't. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/4/2014 1:01 PM, Patrick Shanahan wrote:
What is and how to test, the problem with dhclient? I have not experienced this previous.
There are a few situations that can cause problems for dhclient that have been encountered over the years. From Memory: Firewalls not allowing the dhcp protocol (port 53, again from memory). Problematic IPV6 implementation, in either the firewall or the workstation. Just turn off ipv6 to test. Some wifi routers would associate over one set of bands, then attempt to communicate on another set which would confound many older network cards (2.4ghs vs 5ghz). If your wifi has this bug, you have to flash new os to it or lock it to 2.4ghz), or you have to get new firmware for your network card. There may be more, but I haven't had a problem with NetworkManager or dhclient since 11.4 days. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [12-04-14 16:31]:
On 12/4/2014 1:01 PM, Patrick Shanahan wrote:
What is and how to test, the problem with dhclient? I have not experienced this previous.
There are a few situations that can cause problems for dhclient that have been encountered over the years. From Memory:
Firewalls not allowing the dhcp protocol (port 53, again from memory). Problematic IPV6 implementation, in either the firewall or the workstation. Just turn off ipv6 to test. Some wifi routers would associate over one set of bands, then attempt to communicate on another set which would confound many older network cards (2.4ghs vs 5ghz). If your wifi has this bug, you have to flash new os to it or lock it to 2.4ghz), or you have to get new firmware for your network card.
There may be more, but I haven't had a problem with NetworkManager or dhclient since 11.4 days.
Since I have no problem with wicked wouldn't you assume that dhcpclient *was* working properly? I can remember a time when it was necessary to disable ipv6, but the last time I dealt with disabling ipv6, it caused problem with ssh, iirc. Remember I know nothing about dhcpclient as I have not had occasion to have to learn.... tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-04 22:54, Patrick Shanahan wrote:
Since I have no problem with wicked wouldn't you assume that dhcpclient *was* working properly?
Are you sure that wicked is using dhcpclient? Maybe it is using one client that works, and NM is using another one that doesn't work. There are at least two clients. you should also check the firewall log just after a failed connection and see if something was blocked. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/04/2014 02:18 PM, Carlos E. R. wrote:
On 2014-12-04 22:54, Patrick Shanahan wrote:
Since I have no problem with wicked wouldn't you assume that dhcpclient *was* working properly?
Are you sure that wicked is using dhcpclient? Maybe it is using one client that works, and NM is using another one that doesn't work.
There are at least two clients.
you should also check the firewall log just after a failed connection and see if something was blocked.
Yes dhcpcd has been the historical client dhcp-client is the one that provides dhclient (without saying so What package provides dhclient ? What package requires dhclient? Either the RPM have undocumented dependencies, or Yast is falling down on the job of telling me what those are. See this:-------------------------------------- poulsbo:~ # zypper info --provides dhcp-client Loading repository data... Reading installed packages... Information for package dhcp-client: - ------------------------------------ Repository: Main Update Repository Name: dhcp-client Version: 4.2.6-9.9.1 Arch: x86_64 Vendor: openSUSE Installed: Yes Status: up-to-date Installed Size: 1.8 MiB Summary: ISC DHCP Client Description: This is an alternative DHCP client, the ISC DHCP client for Linux. Like "dhcpcd" (the client that is installed by default), it can be used to configure the network setup. IP address, hostname, routing, nameserver, netmask, and broadcast can be dynamically assigned while booting the machine. It is configurable via the configuration file /etc/dhclient.conf and you can define your own 'hooks' to be used by the /sbin/dhclient-script (which is called by the daemon). Provides: <---------------<<<< config(dhcp-client) == 4.2.6-9.9.1 dhcp-client == 4.2.6-9.9.1 dhcp-client(x86-64) == 4.2.6-9.9.1 - -------------------------------------------- It does not say it provides dhclient yet /sbin/dhclient is in its file list. Networkmanager definitely calls dhclient, you can see it in the process tree in System Monitor. Patrick: Do you even have the package dhcp-client installed? - -- After all is said and done, more is said than done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSA4rAACgkQv7M3G5+2DLJL9QCfWJi8VVl0fIphwckmx4zQo5Gr LkYAn1E9AwKiqJyeI2ZqQ6v0+r7KZE5z =qKmq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [12-04-14 17:42]: [...]
It does not say it provides dhclient yet /sbin/dhclient is in its file list. Networkmanager definitely calls dhclient, you can see it in the process tree in System Monitor.
Patrick: Do you even have the package dhcp-client installed?
#> rpm -qa *dhcp* dhcp-4.2.6-9.9.1.x86_64 dhcpcd-3.2.3-47.80.6.1.x86_64 dhcp-client-4.2.6-9.9.1.x86_64 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-04 20:38, Patrick Shanahan wrote:
* Carlos E. R. <> [12-04-14 09:59]:
I have one laptop working. Enabled NM wiget, configured network from the widget wrench assigning fixed ip and router gateway, 192.168.1.1, and connected from the config menu.
Yes, of course, that's where I meant. I thought you were using the widget or applet or whatever it is called, all the time, not configuration files. I don't have 13.2 on my laptop, so I can't try.
tks much, guess the secret is gateway and fixed ip. What happens when I travel and use, say HolidayInn's network. Have to again use a fixed or same fixed ip and gateway ???
Well, you can't. You need automatic setup on networks you have no control of. This was simply a test to verify that the connection actually works. Now the next step is finding out why automatics, ie, dhcp, doesn't work. I know that there are at least two dhcp client daemons, and sometimes one of them does not work. Find out from the logs (on automatic mode) or with "ps afxu | less" which client it is attempting to use, and remove the rpm if you do not find how to tell NM to use the other one. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [12-04-14 17:28]:
On 2014-12-04 20:38, Patrick Shanahan wrote:
* Carlos E. R. <> [12-04-14 09:59]:
I have one laptop working. Enabled NM wiget, configured network from the widget wrench assigning fixed ip and router gateway, 192.168.1.1, and connected from the config menu.
Yes, of course, that's where I meant. I thought you were using the widget or applet or whatever it is called, all the time, not configuration files.
I don't have 13.2 on my laptop, so I can't try.
tks much, guess the secret is gateway and fixed ip. What happens when I travel and use, say HolidayInn's network. Have to again use a fixed or same fixed ip and gateway ???
Well, you can't. You need automatic setup on networks you have no control of.
This was simply a test to verify that the connection actually works. Now the next step is finding out why automatics, ie, dhcp, doesn't work.
I know that there are at least two dhcp client daemons, and sometimes one of them does not work. Find out from the logs (on automatic mode) or with "ps afxu | less" which client it is attempting to use, and remove the rpm if you do not find how to tell NM to use the other one.
removed configured connection added new wireless connection connected journalctl -u NetworkManager |grep -i dhcp no output after time stamp when removed previous config removed net config added new wireless didn't assign static ip connection now work as would be expected. checked journalctl .... again and still no dhcp entries and playing with the second laptop I find that running /sbin/dhcpcd <dev> obtains a lease and allows connection. What do I need to do to make sure that dhcpcd runs when required. I would think that it would be a service initiated by the need for an address??? tks, think we are getting somewhere. Still do not understand why a fresh install does not connect, at least in my experience, to wireless internet :^) tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [12-04-14 18:33]: [...]
removed configured connection added new wireless connection connected
journalctl -u NetworkManager |grep -i dhcp
no output after time stamp when removed previous config
removed net config added new wireless didn't assign static ip
connection now work as would be expected.
checked journalctl .... again and still no dhcp entries
and playing with the second laptop I find that running /sbin/dhcpcd <dev> obtains a lease and allows connection.
What do I need to do to make sure that dhcpcd runs when required. I would think that it would be a service initiated by the need for an address???
tks, think we are getting somewhere.
Still do not understand why a fresh install does not connect, at least in my experience, to wireless internet :^)
ps: connection is restored after reboot -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [12-04-14 18:43]:
* Patrick Shanahan <paka@opensuse.org> [12-04-14 18:33]: [...]
removed configured connection added new wireless connection connected
journalctl -u NetworkManager |grep -i dhcp
no output after time stamp when removed previous config
removed net config added new wireless didn't assign static ip
connection now work as would be expected.
checked journalctl .... again and still no dhcp entries
and playing with the second laptop I find that running /sbin/dhcpcd <dev> obtains a lease and allows connection.
What do I need to do to make sure that dhcpcd runs when required. I would think that it would be a service initiated by the need for an address???
tks, think we are getting somewhere.
Still do not understand why a fresh install does not connect, at least in my experience, to wireless internet :^)
ps: connection is restored after reboot
fwiw, the second laptop connection is *not* restored after reboot, but comes up immediately after issuing: /sbin/dhcpcd <dev> but restarting the network drops the connection and it is not automagically restored nor will it connect w/o killing the pid of dhcpcd. fwiw, this machine is a dell inspiron w/intel WiFi Link 5100 AGN if that matters. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/04/2014 04:04 PM, Patrick Shanahan wrote:
* Patrick Shanahan <paka@opensuse.org> [12-04-14 18:43]:
* Patrick Shanahan <paka@opensuse.org> [12-04-14 18:33]: [...]
removed configured connection added new wireless connection connected
journalctl -u NetworkManager |grep -i dhcp
no output after time stamp when removed previous config
removed net config added new wireless didn't assign static ip
connection now work as would be expected.
checked journalctl .... again and still no dhcp entries
and playing with the second laptop I find that running /sbin/dhcpcd <dev> obtains a lease and allows connection.
What do I need to do to make sure that dhcpcd runs when required. I would think that it would be a service initiated by the need for an address???
tks, think we are getting somewhere.
Still do not understand why a fresh install does not connect, at least in my experience, to wireless internet :^)
ps: connection is restored after reboot
fwiw, the second laptop connection is *not* restored after reboot, but comes up immediately after issuing: /sbin/dhcpcd <dev>
but restarting the network drops the connection and it is not automagically restored nor will it connect w/o killing the pid of dhcpcd. fwiw, this machine is a dell inspiron w/intel WiFi Link 5100 AGN if that matters.
Maybe something in the configs? While fighting this issue did you tell yast not to use NetworkManager on this machine? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [12-04-14 19:15]:
On 12/04/2014 04:04 PM, Patrick Shanahan wrote: [...]
fwiw, the second laptop connection is *not* restored after reboot, but comes up immediately after issuing: /sbin/dhcpcd <dev>
but restarting the network drops the connection and it is not automagically restored nor will it connect w/o killing the pid of dhcpcd. fwiw, this machine is a dell inspiron w/intel WiFi Link 5100 AGN if that matters.
Maybe something in the configs?
I have not touched /etc/resolv.conf: # Generated by dhcpcd for interface wlp12s0 search wahoo.no-ip.org nameserver 8.8.8.8 nameserver 8.8.4.4 nameserver 65.24.0.164 but the file time-stamp indicates it was updated the last time I ran /sbin/dhcpcd.
While fighting this issue did you tell yast not to use NetworkManager on this machine?
Most certainly, don't want them fighting :^) and this stirred the pot some more: dell:~ # ps aux |grep -i network root 1294 0.0 0.2 333412 11940 ? Ssl 18:57 0:00 /usr/sbin/NetworkManager --no-daemon and: acer:~ # ps aufx |grep -i network root 853 0.0 0.1 489296 12484 ? Ssl 18:25 0:00 /usr/sbin/NetworkManager --no-daemon root 1260 0.0 0.1 12652 9632 ? S 18:25 0:00 \_/sbin/dhclient -d -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-wlp3s0.pid -lf /var/lib/NetworkManager/dhclient-672bd70d-adab-4db5-95f1-8fd9a7396e3f-wlp3s0.lease ////-cf /var/lib/NetworkManager/dhclient-wlp3s0.conf wlp3s0 dell is the fault machine, the acer appears solved. dell:~ # ps aux |grep dhcp root 1349 0.0 0.0 4272 124 ? Ss 18:59 0:00 /sbin/dhcpcd wlp12s0 And I do not see any provision for calling a different dhcp client tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/04/2014 04:33 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [12-04-14 19:15]:
On 12/04/2014 04:04 PM, Patrick Shanahan wrote: [...]
fwiw, the second laptop connection is *not* restored after reboot, but comes up immediately after issuing: /sbin/dhcpcd <dev>
but restarting the network drops the connection and it is not automagically restored nor will it connect w/o killing the pid of dhcpcd. fwiw, this machine is a dell inspiron w/intel WiFi Link 5100 AGN if that matters.
Maybe something in the configs?
I have not touched /etc/resolv.conf: # Generated by dhcpcd for interface wlp12s0 search wahoo.no-ip.org nameserver 8.8.8.8 nameserver 8.8.4.4 nameserver 65.24.0.164
but the file time-stamp indicates it was updated the last time I ran /sbin/dhcpcd.
While fighting this issue did you tell yast not to use NetworkManager on this machine?
Most certainly, don't want them fighting :^)
Well maybe match the settings on the Acer then? Let them duke it out ;-)
and this stirred the pot some more:
dell:~ # ps aux |grep -i network root 1294 0.0 0.2 333412 11940 ? Ssl 18:57 0:00 /usr/sbin/NetworkManager --no-daemon
and:
acer:~ # ps aufx |grep -i network root 853 0.0 0.1 489296 12484 ? Ssl 18:25 0:00 /usr/sbin/NetworkManager --no-daemon root 1260 0.0 0.1 12652 9632 ? S 18:25 0:00 \_/sbin/dhclient -d -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-wlp3s0.pid -lf /var/lib/NetworkManager/dhclient-672bd70d-adab-4db5-95f1-8fd9a7396e3f-wlp3s0.lease ////-cf /var/lib/NetworkManager/dhclient-wlp3s0.conf wlp3s0
dell is the fault machine, the acer appears solved.
dell:~ # ps aux |grep dhcp root 1349 0.0 0.0 4272 124 ? Ss 18:59 0:00 /sbin/dhcpcd wlp12s0
And I do not see any provision for calling a different dhcp client
tks,
I think mine looks more like your Acer....
poulsbo:~ # ps aux |grep -i network root 811 0.0 0.4 333696 14576 ? Ssl 15:44 0:01 /usr/sbin/NetworkManager --no-daemon root 4627 0.0 0.3 12652 9628 ? S 15:53 0:00 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid -lf /var/lib/NetworkManager/dhclient-bc6683a6-74e3-46cd-b20e-1debf70689bb-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 root 9225 0.0 0.0 9264 1600 pts/1 S+ 16:36 0:00 grep --color=auto -i network
-- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen <jsamyth@gmail.com> [12-04-14 19:39]:
On 12/04/2014 04:33 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [12-04-14 19:15]: [...]
While fighting this issue did you tell yast not to use NetworkManager on this machine?
Most certainly, don't want them fighting :^)
Well maybe match the settings on the Acer then? Let them duke it out ;-)
The setting the NetworkManager as far as I am able to change are the same on both machines, but the result is *not*. :^(
and this stirred the pot some more:
dell:~ # ps aux |grep -i network root 1294 0.0 0.2 333412 11940 ? Ssl 18:57 0:00 /usr/sbin/NetworkManager --no-daemon
[...]
I think mine looks more like your Acer....
Which seems to be working correctly :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [12-04-14 19:53]:
* John Andersen <jsamyth@gmail.com> [12-04-14 19:39]:
On 12/04/2014 04:33 PM, Patrick Shanahan wrote:
* John Andersen <jsamyth@gmail.com> [12-04-14 19:15]: [...]
While fighting this issue did you tell yast not to use NetworkManager on this machine?
Most certainly, don't want them fighting :^)
Well maybe match the settings on the Acer then? Let them duke it out ;-)
The setting the NetworkManager as far as I am able to change are the same on both machines, but the result is *not*. :^(
and this stirred the pot some more:
dell:~ # ps aux |grep -i network root 1294 0.0 0.2 333412 11940 ? Ssl 18:57 0:00 /usr/sbin/NetworkManager --no-daemon
[...]
I think mine looks more like your Acer....
Which seems to be working correctly :^)
But is not. Reboot requires "/sbin/dhcpcd <dev>" and re-initializing during a session requires killing pid of dhcpcd and "/sbin/dhcpcd <dev>". But at least I know how get NM to work. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-05 00:31, Patrick Shanahan wrote:
* Carlos E. R. <> [12-04-14 17:28]:
removed configured connection added new wireless connection connected
journalctl -u NetworkManager |grep -i dhcp
no output after time stamp when removed previous config
I don't know how to search messages in the log when it is systemd who is logging things. I would try to get the whole entire log in text, not that of network manager, into a text file, then grep it for dhcp entries. IMHO, that journalctl thing is good when you know under what unit it is going to appear, not when investigating an unknown issue. So get the entire log in text, which surely it can do, then grep it. probably "journalctl |grep -i dhcp". Maybe using "--since" to make it shorter. Try "--since=-1000", seems to be 1000 seconds before now.
and playing with the second laptop I find that running /sbin/dhcpcd <dev> obtains a lease and allows connection.
What do I need to do to make sure that dhcpcd runs when required. I would think that it would be a service initiated by the need for an address???
/sbin/dhcpcd is provided by dhcpcd. /sbin/dhclient is provided by dhcp-client. Thus, uninstall dhcp-client. Otherwise, grep all networkmanager configs to find out where the daemon is selected. I repeat, force the system to use the one that works, either by configuration of by removing THE OTHER. Whatever the "other" is. I have been saying this for days... >:-) And if you go on a trip, make sure you have both rpms in a directory, for re-installation if whichever one you select doesn't work at the place you are that moment. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/04/2014 05:16 PM, Carlos E. R. wrote:
/sbin/dhcpcd is provided by dhcpcd. /sbin/dhclient is provided by dhcp-client.
Thus, uninstall dhcp-client.
NO, NO, maybe uninstall the other one, but dhcp-client is the one that works with NetworkManager for Wifi. Anyway, on my machine they co-exist, both are installed. But only dhclient is actually used. Your command example was exactly right, just leave off the unit portion. On my machine: journalctl |grep -i dhcpcd YIELDS NOTHING Not a single message from dhcpcd. but journalctl |grep -i dhclient yields a great deal. And even in Patricks case, he got ONE of his machines working correctly and it shows dhclient being launched by NetworkManager (you will see this message in another subthred) but the failing machine shows messages that suggest dhcpcd is usurping control.
Otherwise, grep all networkmanager configs to find out where the daemon is selected.
Yup, that is what Patrick will be fighting next. I think it is some part of yast upon initial setup. (I don't know where to look either). I suspect that, because Patrick has always had trouble with networkmanager, he got in the habit of sending it to its room without dinner over many installs. (I know this feeling, I've banned all the desktop search nonsense just out of sheer spite for many releases and upgrades, only to be totally surprised to find Baloo works great on 12.3 and 13.2.) Wicked uses dhcpcd, and works, but dhcpcd does not seem to play nice with network manager. Maybe wicked itself does not play nice. - -- After all is said and done, more is said than done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSBDDgACgkQv7M3G5+2DLIvXgCfWjePjYSuExz2QFGq8ZoC/QxW XVkAmwa0nvAjndDzCwsPDwA2DTlyzud+ =OtMB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-05 02:36, John Andersen wrote:
On 12/04/2014 05:16 PM, Carlos E. R. wrote:
/sbin/dhcpcd is provided by dhcpcd. /sbin/dhclient is provided by dhcp-client.
Thus, uninstall dhcp-client.
NO, NO, maybe uninstall the other one, but dhcp-client is the one that works with NetworkManager for Wifi.
No, no. He said:
and playing with the second laptop I find that running /sbin/dhcpcd <dev> obtains a lease and allows connection.
So he has to keep "/sbin/dhcpcd", which gets an address when manually called, and remove "dhcp-client", which is not working, to force NM to call /sbin/dhcpcd instead. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/04/2014 05:51 PM, Carlos E. R. wrote: > On 2014-12-05 02:36, John Andersen wrote: >> On 12/04/2014 05:16 PM, Carlos E. R. wrote: >>> /sbin/dhcpcd is provided by dhcpcd. /sbin/dhclient is provided by dhcp-client. >> >>> Thus, uninstall dhcp-client. >> >> NO, NO, maybe uninstall the other one, but dhcp-client is the one that works with >> NetworkManager for Wifi. > > No, no. He said: > >> and playing with the second laptop I find that running /sbin/dhcpcd <dev> obtains a lease and >> allows connection. > > So he has to keep "/sbin/dhcpcd", which gets an address when manually called, and remove > "dhcp-client", which is not working, to force NM to call /sbin/dhcpcd instead. > Sorry prior copy to list was encrypted - my fault But you see, he doesn't have to do any of that on his acer, which works correctly, and uses dhclient (from dhcp-client package). Its his Dell that is currently misbehaving, and which the only way he can get it to work is by smacking dhcpcd upon reboot. The acer works fine without any such corporeal punishment. At least that is what I think I read in that thread. > nd this stirred the pot some more: > > dell:~ # ps aux |grep -i network root 1294 0.0 0.2 333412 11940 ? Ssl 18:57 > 0:00 /usr/sbin/NetworkManager - --no-daemon > > and: > > acer:~ # ps aufx |grep -i network root 853 0.0 0.1 489296 12484 ? Ssl 18:25 > 0:00 /usr/sbin/NetworkManager - --no-daemon > root 1260 0.0 0.1 12652 9632 ? S 18:25 0:00 \_/sbin/dhclient -d -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-wlp3s0.pid -lf /var/lib/NetworkManager/dhclient-672bd70d-adab-4db5-95f1-8fd9a7396e3f-wlp3s0.lease ////-cf /var/lib/NetworkManager/dhclient-wlp3s0.conf wlp3s0 > > dell is the fault machine, the acer appears solved. <----------<< - -- After all is said and done, more is said than done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSBE7wACgkQv7M3G5+2DLJTVwCfUj/KD8q6LD9jCm+393uUIxWg JXoAmwe/F9cYW608iO6/Cu+d2iKL5fJo =lQzg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Fri, 05 Dec 2014 02:51:50 +0100 "Carlos E. R." <robin.listas@telefonica.net> пишет:
On 2014-12-05 02:36, John Andersen wrote:
On 12/04/2014 05:16 PM, Carlos E. R. wrote:
/sbin/dhcpcd is provided by dhcpcd. /sbin/dhclient is provided by dhcp-client.
Thus, uninstall dhcp-client.
NO, NO, maybe uninstall the other one, but dhcp-client is the one that works with NetworkManager for Wifi.
No, no. He said:
and playing with the second laptop I find that running /sbin/dhcpcd <dev> obtains a lease and allows connection.
So he has to keep "/sbin/dhcpcd", which gets an address when manually called, and remove "dhcp-client", which is not working, to force NM to call /sbin/dhcpcd instead.
dhcp This key sets up what DHCP client NetworkManager will use. Presently dhclient and dhcpcd are supported. The client configured here should be available on your system too. If this key is missing, available DHCP clients are looked for in this order: dhclient, dhcpcd.
On 2014-12-05 07:52, Andrei Borzenkov wrote:
В Fri, 05 Dec 2014 02:51:50 +0100 "Carlos E. R." <> пишет:
So he has to keep "/sbin/dhcpcd", which gets an address when manually called, and remove "dhcp-client", which is not working, to force NM to call /sbin/dhcpcd instead.
dhcp This key sets up what DHCP client NetworkManager will use. Presently dhclient and dhcpcd are supported. The client configured here should be available on your system too. If this key is missing, available DHCP clients are looked for in this order: dhclient, dhcpcd.
On what file is that setting? I knew I had seen this years ago, but I can not find it now. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
В Fri, 05 Dec 2014 13:20:30 +0100 "Carlos E. R." <robin.listas@telefonica.net> пишет:
On 2014-12-05 07:52, Andrei Borzenkov wrote:
В Fri, 05 Dec 2014 02:51:50 +0100 "Carlos E. R." <> пишет:
So he has to keep "/sbin/dhcpcd", which gets an address when manually called, and remove "dhcp-client", which is not working, to force NM to call /sbin/dhcpcd instead.
dhcp This key sets up what DHCP client NetworkManager will use. Presently dhclient and dhcpcd are supported. The client configured here should be available on your system too. If this key is missing, available DHCP clients are looked for in this order: dhclient, dhcpcd.
On what file is that setting? I knew I had seen this years ago, but I can not find it now.
/etc/NetworkManager/NetworkManager.conf
On 2014-12-05 13:29, Andrei Borzenkov wrote:
В Fri, 05 Dec 2014 13:20:30 +0100 "Carlos E. R." <> пишет:
/etc/NetworkManager/NetworkManager.conf
Mmm. My desktop machine doesn't have that setting there, so I couldn't see it. Maybe my laptop has it. It is on "man NetworkManager.conf", of course, now that I know where to look ;-) Thanks. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Op vrijdag 5 december 2014 02:16:54 schreef Carlos E. R.:
I don't know how to search messages in the log when it is systemd who is logging things. I would try to get the whole entire log in text, not that of network manager, into a text file, then grep it for dhcp entries.
One can get back the old behavior with /var/log/messages and other log files, by installing the package rsyslog. It will remove one or more other packages. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-05 10:26, Freek de Kruijf wrote:
Op vrijdag 5 december 2014 02:16:54 schreef Carlos E. R.:
I don't know how to search messages in the log when it is systemd who is logging things. I would try to get the whole entire log in text, not that of network manager, into a text file, then grep it for dhcp entries.
One can get back the old behavior with /var/log/messages and other log files, by installing the package rsyslog. It will remove one or more other packages.
Yes, I know. But I'm trying to make do when helping others that have the systemd journal only ;-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 12/05/2014 01:26 AM, Freek de Kruijf wrote:
Op vrijdag 5 december 2014 02:16:54 schreef Carlos E. R.:
I don't know how to search messages in the log when it is systemd who is logging things. I would try to get the whole entire log in text, not that of network manager, into a text file, then grep it for dhcp entries.
One can get back the old behavior with /var/log/messages and other log files, by installing the package rsyslog. It will remove one or more other packages.
But unless you have specific need for this (such as processing the log via other applications, etc) using the capabilities of journalctl has some advantage and keeps your logs compressed as well. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Andrei Borzenkov -
Carlos E. R. -
Freek de Kruijf -
John Andersen -
Malcolm -
Patrick Shanahan -
Ruben Safir