[opensuse] network manager only connects after 2nd or 3rd attempt
Hello, on my laptop with OS 13.2, after booting the network manager shows that it is connected to my wifi, but there is no connection to the internet, i can't even get to the router (192.168...) Then I click on disconnect and then on connect again and it usually works. Sometimes I need a third or a fourth attempt. It looks to me that if "connecting" takes a longer time, then the connection does not work, although shown as connected, and when it goes fast, it works... It does not depend on the distance to the antenna. What could be the reason for this? Where can I search and for what should I look? thanks for hints Daniel -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Daniel Bauer
Hello,
on my laptop with OS 13.2, after booting the network manager shows that it is connected to my wifi, but there is no connection to the internet, i can't even get to the router (192.168...)
Then I click on disconnect and then on connect again and it usually works. Sometimes I need a third or a fourth attempt. It looks to me that if "connecting" takes a longer time, then the connection does not work, although shown as connected, and when it goes fast, it works...
It does not depend on the distance to the antenna.
What could be the reason for this? Where can I search and for what should I look?
I have the same problem on all my machines and the only solution I find is wicked, app not adjective :) -- (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 31/05/15 11:11, Daniel Bauer wrote:
i can't even get to the router (192.168...)
What could be the reason for this?
Your signature gives two locations in different countries. In one of them, to get connected at all is remarkable, let alone at the second or fourth attempt. If at the other, then you're gonna have to send logs, versions and other stuff... HTH B -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 31.05.2015 um 12:31 schrieb buhorojo:
On 31/05/15 11:11, Daniel Bauer wrote:
i can't even get to the router (192.168...)
What could be the reason for this?
Your signature gives two locations in different countries. In one of them, to get connected at all is remarkable, let alone at the second or fourth attempt. If at the other, then you're gonna have to send logs, versions and other stuff... HTH B
:-) Spain, Telefonica, their "free" movistar router. it used to work before (actually don't know since which update, 3 weeks?). What versions, logs etc. do you want to see? -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-05-31 12:37, Daniel Bauer wrote:
:-) Spain, Telefonica, their "free" movistar router. it used to work before (actually don't know since which update, 3 weeks?).
I have a new Telefonica fiber connection. I have no problems with the laptop and their wifi, connects always first time, instantly. Takes longer in Windows. However, my tablet and phone have problems when I move to the other floor. The signal seems to be weak. If this becomes too problematic, I'm considering adding my own access point. I don't know if I have the latest update, because I used the portal to configure the router myself, instead of via their web page. I needed access to some settings, and I'm unsure if this disables their remote management or not. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2015-05-31 16:32, Carlos E. R. wrote:
On 2015-05-31 12:37, Daniel Bauer wrote:
:-) Spain, Telefonica, their "free" movistar router. it used to work before (actually don't know since which update, 3 weeks?).
I have a new Telefonica fiber connection. I have no problems with the laptop and their wifi, connects always first time, instantly.
I just remembered that I don't use dhcp on the laptop. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Op zondag 31 mei 2015 11:11:55 schreef Daniel Bauer:
Hello,
on my laptop with OS 13.2, after booting the network manager shows that it is connected to my wifi, but there is no connection to the internet, i can't even get to the router (192.168...)
This looks like a DHCP problem. Apparently connecting to your AP is OK, but after that you need to get an IP-address, a netmask, a default gateway, and a DNS, which takes time. After the first attempt you can interrogate these values using "ip a", "ip r" and "tail -3 /etc/resolv.conf" Depending on weather you use NetworkManager or wicked you can look at the logs by "journalctl -b -u NetworkManager" or "journalctl -b -u wicked" Do you have the same problem when configuring these settings static? -- 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
Sorry for late answer, too much sun to stay all day on the screen :-) Am 31.05.2015 um 14:04 schrieb Freek de Kruijf:
Op zondag 31 mei 2015 11:11:55 schreef Daniel Bauer:
Hello,
on my laptop with OS 13.2, after booting the network manager shows that it is connected to my wifi, but there is no connection to the internet, i can't even get to the router (192.168...)
This looks like a DHCP problem. Apparently connecting to your AP is OK, but after that you need to get an IP-address, a netmask, a default gateway, and a DNS, which takes time.
After the first attempt you can interrogate these values using "ip a", "ip r" and "tail -3 /etc/resolv.conf"
Depending on weather you use NetworkManager or wicked you can look at the logs by "journalctl -b -u NetworkManager" or "journalctl -b -u wicked"
I copy the log below, I see a warning, but I don't know what i wants to tell me :-)
Do you have the same problem when configuring these settings static?
stupid question: if I connect PC and laptop with static IP's, can others then still use dhcp? In fact I only connect with dhcp because I often have guests who use my wlan via dhcp. But if I can use static IP's and they still can use dhcp that would be great (I wouldn't have to search for actual IP's everytime I want to connect the two computers). So here's the output of journalctl -b -u NetworkManager:
-- Logs begin at Mon 2015-06-01 15:16:39 CEST, end at Mon 2015-06-01 15:23:17 CEST. -- Jun 01 15:18:35 meitli NetworkManager[1507]: <info> NetworkManager (version 0.9.10.0) is starting... Jun 01 15:18:35 meitli NetworkManager[1507]: <info> Read config: /etc/NetworkManager/NetworkManager.conf Jun 01 15:18:35 meitli NetworkManager[1507]: <info> WEXT support is enabled Jun 01 15:18:35 meitli NetworkManager[1507]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn Jun 01 15:18:35 meitli NetworkManager[1507]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc Jun 01 15:18:35 meitli NetworkManager[1507]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp Jun 01 15:18:35 meitli NetworkManager[1507]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list. Jun 01 15:18:35 meitli NetworkManager[1507]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Jun 01 15:18:35 meitli NetworkManager[1507]: <info> new connection /etc/NetworkManager/system-connections/XADOR Jun 01 15:18:35 meitli NetworkManager[1507]: <info> new connection /etc/NetworkManager/system-connections/flying cats Jun 01 15:18:36 meitli NetworkManager[1507]: <info> monitoring kernel firmware directory '/lib/firmware'. Jun 01 15:18:36 meitli NetworkManager[1507]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill0) (driver wl) Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WiFi hardware radio set enabled Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WWAN hardware radio set disabled Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wwan.so Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-adsl.so Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wifi.so Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WiFi enabled by radio killswitch; enabled by state file Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WWAN enabled by radio killswitch; disabled by state file Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WiMAX enabled by radio killswitch; enabled by state file Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Networking is enabled by state file Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> Setting system hostname to 'meitli.atelier.foto' (from system configuration) Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (lo): link connected Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (lo): carrier is ON Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1) Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0 Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): using nl80211 for WiFi device control Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'wl' ifindex: 2) Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/1 Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): preparing device Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): carrier is OFF Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): new Ethernet device (driver: 'tg3' ifindex: 3) Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/2 Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): preparing device Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): created default wired connection 'Wired connection 1' Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> use BlueZ version 5 Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> ModemManager available in the bus Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0) supports 1 scan SSIDs Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: starting -> ready Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: ready -> disconnected Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0) supports 1 scan SSIDs Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Auto-activating connection 'flying cats'. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) starting connection 'flying cats' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> NetworkManager state is now CONNECTING Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0] Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0/wireless): connection 'flying cats' has security, and secrets exist. No new secrets needed. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: added 'ssid' value 'flying cats' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: added 'scan_ssid' value '1' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: added 'psk' value '<omitted>' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: set interface ap_scan to 1 Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: inactive -> associating Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: associating -> 4-way handshake Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: 4-way handshake -> completed Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'flying ca Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0] Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds) Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> dhclient started with pid 1857 Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <warn> Unable to detect kernel support for extended IFA_FLAGS. Assume no kernel support. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete. Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Internet Systems Consortium DHCP Client 4.2.6 Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Copyright 2004-2014 Internet Systems Consortium. Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: All rights reserved. Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: For info, please visit https://www.isc.org/software/dhcp/ Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Internet Systems Consortium DHCP Client 4.2.6 Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Copyright 2004-2014 Internet Systems Consortium. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: All rights reserved. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: For info, please visit https://www.isc.org/software/dhcp/ Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Listening on LPF/wlp3s0/b8:8d:12:39:1b:ba Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Sending on LPF/wlp3s0/b8:8d:12:39:1b:ba Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Sending on Socket/fallback Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x4c3444d7) Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Listening on LPF/wlp3s0/b8:8d:12:39:1b:ba Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Sending on LPF/wlp3s0/b8:8d:12:39:1b:ba Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Sending on Socket/fallback Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x4c3444d7) Jun 01 15:18:43 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 5 (xid=0x4c3444d7) Jun 01 15:18:43 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 5 (xid=0x4c3444d7) Jun 01 15:18:48 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6 (xid=0x4c3444d7) Jun 01 15:18:48 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6 (xid=0x4c3444d7) Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router... Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Beginning DHCPv6 transaction (timeout in 45 seconds) Jun 01 15:18:54 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x4c3444d7) Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x4c3444d7) Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: <info> dhclient started with pid 2062 Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Internet Systems Consortium DHCP Client 4.2.6 Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Copyright 2004-2014 Internet Systems Consortium. Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: All rights reserved. Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: For info, please visit https://www.isc.org/software/dhcp/ Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Listening on Socket/wlp3s0 Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Sending on Socket/wlp3s0 Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: Internet Systems Consortium DHCP Client 4.2.6 Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: Copyright 2004-2014 Internet Systems Consortium. Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: All rights reserved. Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: For info, please visit https://www.isc.org/software/dhcp/ Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: Listening on Socket/wlp3s0 Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: Sending on Socket/wlp3s0 Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: PRC: Requesting information (INIT). Jun 01 15:18:55 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 0 ms elapsed. Jun 01 15:18:55 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 1030ms. Jun 01 15:18:55 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 1030ms. Jun 01 15:18:56 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 1030 ms elapsed. Jun 01 15:18:56 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 2000ms. Jun 01 15:18:56 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 2000ms. Jun 01 15:18:58 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 3030 ms elapsed. Jun 01 15:18:58 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 3860ms. Jun 01 15:18:58 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 3860ms. Jun 01 15:19:00 meitli.atelier.foto dhclient[1857]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:00 meitli.atelier.foto dhclient[1857]: DHCPOFFER from 192.168.1.1 Jun 01 15:19:00 meitli.atelier.foto NetworkManager[1507]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:00 meitli.atelier.foto NetworkManager[1507]: DHCPOFFER from 192.168.1.1 Jun 01 15:19:01 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 6890 ms elapsed. Jun 01 15:19:01 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 7670ms. Jun 01 15:19:01 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 7670ms. Jun 01 15:19:04 meitli.atelier.foto dhclient[1857]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:04 meitli.atelier.foto NetworkManager[1507]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:09 meitli.atelier.foto dhclient[1857]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:09 meitli.atelier.foto NetworkManager[1507]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:09 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 14570 ms elapsed. Jun 01 15:19:09 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 16040ms. Jun 01 15:19:09 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 16040ms. Jun 01 15:19:21 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x579229ba) Jun 01 15:19:21 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x579229ba) Jun 01 15:19:24 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6 (xid=0x579229ba) Jun 01 15:19:24 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6 (xid=0x579229ba) Jun 01 15:19:25 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 30630 ms elapsed. Jun 01 15:19:25 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 33100ms. Jun 01 15:19:25 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 33100ms. Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <warn> (wlp3s0): DHCPv4 request timed out. Jun 01 15:19:26 meitli.atelier.foto dhclient[1857]: Received signal 15, initiating shutdown. Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: Received signal 15, initiating shutdown. Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): canceled DHCP transaction, DHCP client pid 1857 Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) started... Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) complete. Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <warn> (wlp3s0): DHCPv6 request timed out. Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): canceled DHCP transaction, DHCP client pid 2062 Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv6 Commit) scheduled... Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv6 Commit) started... Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv6 Commit) complete. Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0] Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> NetworkManager state is now CONNECTED_LOCAL Jun 01 15:19:41 meitli.atelier.foto NetworkManager[1507]: <info> NetworkManager state is now CONNECTED_GLOBAL Jun 01 15:19:41 meitli.atelier.foto NetworkManager[1507]: <info> Policy set 'flying cats' (wlp3s0) as default for IPv6 routing and DNS. Jun 01 15:19:41 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) successful, device activated. lines 112-165/165 (END)
-- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 1 juni 2015 15:41:14 schreef Daniel Bauer:
I copy the log below, I see a warning, but I don't know what i wants to tell me :-)
Will comment below.
Do you have the same problem when configuring these settings static?
stupid question:
Only questions not asked are stupid.
if I connect PC and laptop with static IP's, can others then still use dhcp?
Sure. Your DHCP server only gives out a certain number of IP-addresses. So for static addresses you need to choose one that is not given out by the DHCP server.
In fact I only connect with dhcp because I often have guests who use my wlan via dhcp. But if I can use static IP's and they still can use dhcp that would be great (I wouldn't have to search for actual IP's everytime I want to connect the two computers).
So you can give these two static addresses.
So here's the output of journalctl -b -u NetworkManager:
-- Logs begin at Mon 2015-06-01 15:16:39 CEST, end at Mon 2015-06-01 15:23:17 CEST. -- Jun 01 15:18:35 meitli NetworkManager[1507]: <info> NetworkManager (version 0.9.10.0) is starting... Jun 01 15:18:35 meitli NetworkManager[1507]: <info> Read config: /etc/NetworkManager/NetworkManager.conf Jun 01 15:18:35 meitli NetworkManager[1507]: <info> WEXT support is enabled Jun 01 15:18:35 meitli NetworkManager[1507]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn Jun 01 15:18:35 meitli NetworkManager[1507]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc Jun 01 15:18:35 meitli NetworkManager[1507]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp Jun 01 15:18:35 meitli NetworkManager[1507]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list. Jun 01 15:18:35 meitli NetworkManager[1507]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Jun 01 15:18:35 meitli NetworkManager[1507]: <info> new connection /etc/NetworkManager/system-connections/XADOR Jun 01 15:18:35 meitli NetworkManager[1507]: <info> new connection /etc/NetworkManager/system-connections/flying cats Jun 01 15:18:36 meitli NetworkManager[1507]: <info> monitoring kernel firmware directory '/lib/firmware'. Jun 01 15:18:36 meitli NetworkManager[1507]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill0) (driver wl) Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WiFi hardware radio set enabled Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WWAN hardware radio set disabled Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wwan.so Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-adsl.so Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wifi.so Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WiFi enabled by radio killswitch; enabled by state file Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WWAN enabled by radio killswitch; disabled by state file Jun 01 15:18:36 meitli NetworkManager[1507]: <info> WiMAX enabled by radio killswitch; enabled by state file Jun 01 15:18:36 meitli NetworkManager[1507]: <info> Networking is enabled by state file Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> Setting system hostname to 'meitli.atelier.foto' (from system configuration) Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (lo): link connected Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (lo): carrier is ON Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1) Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0 Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): using nl80211 for WiFi device control Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'wl' ifindex: 2) Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/1 Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): preparing device Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): carrier is OFF Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): new Ethernet device (driver: 'tg3' ifindex: 3) Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/2 Jun 01 15:18:36 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): preparing device Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (eth0): created default wired connection 'Wired connection 1' Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> use BlueZ version 5 Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> ModemManager available in the bus Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0) supports 1 scan SSIDs Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: starting -> ready Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: ready -> disconnected Jun 01 15:18:37 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0) supports 1 scan SSIDs Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Auto-activating connection 'flying cats'. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) starting connection 'flying cats' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> NetworkManager state is now CONNECTING Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0] Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0/wireless): connection 'flying cats' has security, and secrets exist. No new secrets needed. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: added 'ssid' value 'flying cats' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: added 'scan_ssid' value '1' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: added 'psk' value '<omitted>' Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Config: set interface ap_scan to 1 Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: inactive -> associating Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: associating -> 4-way handshake Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): supplicant interface state: 4-way handshake -> completed Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'flying ca Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started... Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0] Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds) Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> dhclient started with pid 1857 Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <warn> Unable to detect kernel support for extended IFA_FLAGS. Assume no kernel support. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete. Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Internet Systems Consortium DHCP Client 4.2.6 Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Copyright 2004-2014 Internet Systems Consortium. Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: All rights reserved. Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: For info, please visit https://www.isc.org/software/dhcp/ Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Internet Systems Consortium DHCP Client 4.2.6 Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Copyright 2004-2014 Internet Systems Consortium. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: All rights reserved. Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: For info, please visit https://www.isc.org/software/dhcp/ Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Listening on LPF/wlp3s0/b8:8d:12:39:1b:ba Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Sending on LPF/wlp3s0/b8:8d:12:39:1b:ba Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: Sending on Socket/fallback Jun 01 15:18:40 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x4c3444d7) Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Listening on LPF/wlp3s0/b8:8d:12:39:1b:ba Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Sending on LPF/wlp3s0/b8:8d:12:39:1b:ba Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: Sending on Socket/fallback Jun 01 15:18:40 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x4c3444d7) Jun 01 15:18:43 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 5 (xid=0x4c3444d7) Jun 01 15:18:43 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 5 (xid=0x4c3444d7) Jun 01 15:18:48 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6 (xid=0x4c3444d7) Jun 01 15:18:48 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6 (xid=0x4c3444d7) Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router... Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Beginning DHCPv6 transaction (timeout in 45 seconds)
This where one of the the problems starts. 45 seconds later at 15:19:39 or rather 40 you can see the problem.
Jun 01 15:18:54 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x4c3444d7) Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x4c3444d7) Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: <info> dhclient started with pid 2062 Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Internet Systems Consortium DHCP Client 4.2.6 Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Copyright 2004-2014 Internet Systems Consortium. Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: All rights reserved. Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: For info, please visit https://www.isc.org/software/dhcp/ Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Listening on Socket/wlp3s0 Jun 01 15:18:54 meitli.atelier.foto dhclient[2062]: Sending on Socket/wlp3s0 Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: Internet Systems Consortium DHCP Client 4.2.6 Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: Copyright 2004-2014 Internet Systems Consortium. Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: All rights reserved. Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: For info, please visit https://www.isc.org/software/dhcp/ Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: Listening on Socket/wlp3s0 Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: Sending on Socket/wlp3s0 Jun 01 15:18:54 meitli.atelier.foto NetworkManager[1507]: PRC: Requesting information (INIT). Jun 01 15:18:55 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 0 ms elapsed. Jun 01 15:18:55 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 1030ms. Jun 01 15:18:55 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 1030ms. Jun 01 15:18:56 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 1030 ms elapsed. Jun 01 15:18:56 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 2000ms. Jun 01 15:18:56 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 2000ms. Jun 01 15:18:58 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 3030 ms elapsed. Jun 01 15:18:58 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 3860ms. Jun 01 15:18:58 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 3860ms. Jun 01 15:19:00 meitli.atelier.foto dhclient[1857]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:00 meitli.atelier.foto dhclient[1857]: DHCPOFFER from 192.168.1.1 Jun 01 15:19:00 meitli.atelier.foto NetworkManager[1507]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:00 meitli.atelier.foto NetworkManager[1507]: DHCPOFFER from 192.168.1.1 Jun 01 15:19:01 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 6890 ms elapsed. Jun 01 15:19:01 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 7670ms. Jun 01 15:19:01 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 7670ms. Jun 01 15:19:04 meitli.atelier.foto dhclient[1857]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:04 meitli.atelier.foto NetworkManager[1507]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:09 meitli.atelier.foto dhclient[1857]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:09 meitli.atelier.foto NetworkManager[1507]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67 (xid=0x4c3444d7) Jun 01 15:19:09 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 14570 ms elapsed. Jun 01 15:19:09 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 16040ms. Jun 01 15:19:09 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 16040ms. Jun 01 15:19:21 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x579229ba) Jun 01 15:19:21 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x579229ba) Jun 01 15:19:24 meitli.atelier.foto dhclient[1857]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6 (xid=0x579229ba) Jun 01 15:19:24 meitli.atelier.foto NetworkManager[1507]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6 (xid=0x579229ba) Jun 01 15:19:25 meitli.atelier.foto NetworkManager[1507]: XMT: Forming Info-Request, 30630 ms elapsed. Jun 01 15:19:25 meitli.atelier.foto dhclient[2062]: XMT: Info-Request on wlp3s0, interval 33100ms. Jun 01 15:19:25 meitli.atelier.foto NetworkManager[1507]: XMT: Info-Request on wlp3s0, interval 33100ms. Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <warn> (wlp3s0): DHCPv4 request timed out.
DHCPv4 request timed out. So your DHCP server is not responding in time.
Jun 01 15:19:26 meitli.atelier.foto dhclient[1857]: Received signal 15, initiating shutdown. Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: Received signal 15, initiating shutdown. Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): canceled DHCP transaction, DHCP client pid 1857 Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) started... Jun 01 15:19:26 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) complete. Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <warn> (wlp3s0): DHCPv6 request timed out.
Here is the timeout for DHCPv6.
Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): canceled DHCP transaction, DHCP client pid 2062 Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv6 Commit) scheduled... Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv6 Commit) started... Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv6 Commit) complete. Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0] Jun 01 15:19:40 meitli.atelier.foto NetworkManager[1507]: <info> NetworkManager state is now CONNECTED_LOCAL Jun 01 15:19:41 meitli.atelier.foto NetworkManager[1507]: <info> NetworkManager state is now CONNECTED_GLOBAL Jun 01 15:19:41 meitli.atelier.foto NetworkManager[1507]: <info> Policy set 'flying cats' (wlp3s0) as default for IPv6 routing and DNS. Jun 01 15:19:41 meitli.atelier.foto NetworkManager[1507]: <info> Activation (wlp3s0) successful, device activated. lines 112-165/165 (END)
Maybe the firewall blocks the responses. So reboot your system and see that you did not get an IP address. Please send the output of the command "tail -30 /var/log/firewall". -- 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
Am 01.06.2015 um 16:22 schrieb Freek de Kruijf: ...
Maybe the firewall blocks the responses.
Can this be? If it is the firewall shouldn’t it then block in general? Both times I rebooted today, at beginning I did not have an internet connection, but disconnecting and connecting again (in networkmanager) it worked immediately...
So reboot your system and see that you did not get an IP address. Please send the output of the command "tail -30 /var/log/firewall".
here's the output: meitli:~ # tail -30 /var/log/firewall 2015-06-01T15:18:42.759680+02:00 meitli kernel: [ 127.880943] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=414 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=374 2015-06-01T15:18:43.009730+02:00 meitli kernel: [ 128.131285] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=414 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=374 2015-06-01T15:18:43.210705+02:00 meitli kernel: [ 128.331637] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=384 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=344 2015-06-01T15:19:02.959699+02:00 meitli kernel: [ 148.098445] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:19:32.974701+02:00 meitli kernel: [ 178.139254] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:20:04.979643+02:00 meitli kernel: [ 210.171969] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:21:08.985672+02:00 meitli kernel: [ 274.233832] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:23:17.000704+02:00 meitli kernel: [ 402.359175] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:27:33.019713+02:00 meitli kernel: [ 658.600272] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:32:46.283677+02:00 meitli kernel: [ 972.136363] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:32:46.376645+02:00 meitli kernel: [ 972.229940] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=414 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=374 2015-06-01T15:32:46.404672+02:00 meitli kernel: [ 972.257396] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=246 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=206 2015-06-01T15:32:46.627647+02:00 meitli kernel: [ 972.480294] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=414 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=374 2015-06-01T15:32:46.877673+02:00 meitli kernel: [ 972.731238] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=414 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=374 2015-06-01T15:33:17.923990+02:00 meitli kernel: [ 1003.178063] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:33:49.924038+02:00 meitli kernel: [ 1035.206308] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:34:53.926023+02:00 meitli kernel: [ 1099.263392] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:37:01.949049+02:00 meitli kernel: [ 1227.397398] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:41:18.029045+02:00 meitli kernel: [ 1483.699906] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T15:49:50.130037+02:00 meitli kernel: [ 1996.244775] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T17:10:56.161193+02:00 meitli kernel: [ 46.210681] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=246 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=206 2015-06-01T17:10:56.161229+02:00 meitli kernel: [ 46.211104] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=414 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=374 2015-06-01T17:10:56.412203+02:00 meitli kernel: [ 46.461387] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=414 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=374 2015-06-01T17:10:56.663172+02:00 meitli kernel: [ 46.712698] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=414 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=374 2015-06-01T17:10:56.864216+02:00 meitli kernel: [ 46.913840] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=384 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=344 2015-06-01T17:11:26.479183+02:00 meitli kernel: [ 76.554860] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T17:11:41.488169+02:00 meitli kernel: [ 91.576534] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T17:11:57.490136+02:00 meitli kernel: [ 107.592649] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T17:12:29.497173+02:00 meitli kernel: [ 139.627279] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 2015-06-01T17:13:33.499841+02:00 meitli kernel: [ 203.685506] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 1 juni 2015 17:32:35 schreef Daniel Bauer:
Am 01.06.2015 um 16:22 schrieb Freek de Kruijf: ...
Maybe the firewall blocks the responses.
Can this be? If it is the firewall shouldn’t it then block in general? Both times I rebooted today, at beginning I did not have an internet connection, but disconnecting and connecting again (in networkmanager) it worked immediately...
So reboot your system and see that you did not get an IP address. Please send the output of the command "tail -30 /var/log/firewall".
here's the output:
meitli:~ # tail -30 /var/log/firewall 2015-06-01T17:13:33.499841+02:00 meitli kernel: [ 203.685506] SFW2-INext-DROP-DEFLT IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:ba8d:12ff:fe39:1bba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
So, it is not the firewall. Only IPv6 packets with SPT=5353 DPT=5353 get blocked, which is harmless. See http://en.wikipedia.org/wiki/Multicast_DNS for an explanation on the protocol.
From your previous message the conclusion is that either your DHCP requests do not reach the DHCP server or the responses do not reach your system.
You can analyze the first reason by having a system connected to the Ethernet next to your router and collecting broadcast packages, a DHCP request is a broadcast, and see if they arrive in that system. On that analyzing system you can use wireshark to collect packages. Analyzing the second reason is quite complicated, too complicated to explain. You need something like an intermediate Ethernet bridge that passes on the packages, but also copies these packages for analysis. -- 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 06/01/2015 07:22 AM, Freek de Kruijf wrote:
Op maandag 1 juni 2015 15:41:14 schreef Daniel Bauer:
I copy the log below, I see a warning, but I don't know what i wants to tell me :-)
Will comment below.
Do you have the same problem when configuring these settings static?
stupid question:
Only questions not asked are stupid.
if I connect PC and laptop with static IP's, can others then still use dhcp?
Sure. Your DHCP server only gives out a certain number of IP-addresses. So for static addresses you need to choose one that is not given out by the DHCP server.
In fact I only connect with dhcp because I often have guests who use my wlan via dhcp. But if I can use static IP's and they still can use dhcp that would be great (I wouldn't have to search for actual IP's everytime I want to connect the two computers).
So you can give these two static addresses.
Couple of minor corrections: 1) yes you can use a mix of static and dynamic IPs, but you may occasionally experience trouble after a static machine has been turned off for a long period. The static IP may be leased by the dhcp server, and when you turn the static machine back on there will be a collision, and the other machine will be forced to obtain a new lease. This is seldom done cleanly. 1a) Any properly functioning DHCP server (including in the cheapest of wifi routers) will ping an ip before it tries to lease it. This is how it detects and avoids usurped static ips. Obviously if the usurped static is powered off or disconnected it will get no reply and it will lease the IP. 2) The very best way is to make a reservation in your DHCP server for the mac address of the machines you want to always get the same IP (printers etc are good candidates). That way EVERYTHING can use dhcp. 2a) Even the cheapest routers allow dhcp reservations these days, as does any dhcp server running under opensuse. I always run this way - for many years and have never encountered anything that did not work. Further I've never encountered any device so primitive that it could not handle dhcp and therefore required a static IP. Its always a choice, reserved usually for those cases where there exists insufficient knowledge of how to get a dhcp server working. -- 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
Op maandag 1 juni 2015 14:10:36 schreef John Andersen:
Couple of minor corrections:
1) yes you can use a mix of static and dynamic IPs, but you may occasionally experience trouble after a static machine has been turned off for a long period. The static IP may be leased by the dhcp server, and when you turn the static machine back on there will be a collision, and the other machine will be forced to obtain a new lease. This is seldom done cleanly.
Not when you use an address outside the range given to the DHCP server as I mentioned in my message.
1a) Any properly functioning DHCP server (including in the cheapest of wifi routers) will ping an ip before it tries to lease it. This is how it detects and avoids usurped static ips. Obviously if the usurped static is powered off or disconnected it will get no reply and it will lease the IP.
2) The very best way is to make a reservation in your DHCP server for the mac address of the machines you want to always get the same IP (printers etc are good candidates). That way EVERYTHING can use dhcp.
2a) Even the cheapest routers allow dhcp reservations these days, as does any dhcp server running under opensuse. I always run this way - for many years and have never encountered anything that did not work.
Further I've never encountered any device so primitive that it could not handle dhcp and therefore required a static IP. Its always a choice, reserved usually for those cases where there exists insufficient knowledge of how to get a dhcp server working.
But in this case the DHCP server apparently does not work properly. -- 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 06/01/2015 02:38 PM, Freek de Kruijf wrote:
Op maandag 1 juni 2015 14:10:36 schreef John Andersen:
Couple of minor corrections:
1) yes you can use a mix of static and dynamic IPs, but you may occasionally experience trouble after a static machine has been turned off for a long period. The static IP may be leased by the dhcp server, and when you turn the static machine back on there will be a collision, and the other machine will be forced to obtain a new lease. This is seldom done cleanly.
Not when you use an address outside the range given to the DHCP server as I mentioned in my message.
1a) Any properly functioning DHCP server (including in the cheapest of wifi routers) will ping an ip before it tries to lease it. This is how it detects and avoids usurped static ips. Obviously if the usurped static is powered off or disconnected it will get no reply and it will lease the IP.
2) The very best way is to make a reservation in your DHCP server for the mac address of the machines you want to always get the same IP (printers etc are good candidates). That way EVERYTHING can use dhcp.
2a) Even the cheapest routers allow dhcp reservations these days, as does any dhcp server running under opensuse. I always run this way - for many years and have never encountered anything that did not work.
Further I've never encountered any device so primitive that it could not handle dhcp and therefore required a static IP. Its always a choice, reserved usually for those cases where there exists insufficient knowledge of how to get a dhcp server working.
But in this case the DHCP server apparently does not work properly.
Anyone having the wherewithal to set static addresses outside the range of the DHCP server would also have the ability to make sure the server is working. So, I guess I'll have to double down on my original assertion that in this day and age, there isn't a single valid excuse for using static IPs mixed with DHCP leased IPs. -- 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
On 06/01/2015 07:42 PM, John Andersen wrote:
So, I guess I'll have to double down on my original assertion that in this day and age, there isn't a single valid excuse for using static IPs mixed with DHCP leased IPs.
So, the DHCP server should have a DHCP address? ;-) Actually, in corporate networks, it's common to have permanent things like servers, routers etc. use static addresses and clients use DHCP. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/01/2015 05:38 PM, Freek de Kruijf wrote:
Not when you use an address outside the range given to the DHCP server as I mentioned in my message.
+1 I have NEVER had a problem with this. My static addresses are below .100 and my dynamic addresses are above .101. The two never get confused; there is never contention. And hey ... If I'm going to bind a MAC address to an IP address why not make it part of the static group anyway? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/01/2015 08:33 PM, Anton Aylward wrote:
If I'm going to bind a MAC address to an IP address why not make it part of the static group anyway?
Think portable devices that may be used on other networks. I have a notebook computer, tablet and smart phone. All have a MAC linked IP address configured on the DHCP server. This means they have a fixed address when at home and whatever address elsewhere. On the other hand, things that don't move, such as my desktop computer, firewall/router computer and WiFi access point have static addresses. I also have some A/V gear that have MAC linked addresses on the DHCP server. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-06-01 23:10, John Andersen wrote:
Couple of minor corrections:
1) yes you can use a mix of static and dynamic IPs, but you may occasionally experience trouble after a static machine has been turned off for a long period. The static IP may be leased by the dhcp server, and when you turn the static machine back on there will be a collision, and the other machine will be forced to obtain a new lease. This is seldom done cleanly.
No. Even a cheap home routers have a range of IPs that are given out by the dhcp server, and the rest that is not, so that you can use those as fixed IPs. There can not be those collisions you mention if you just find out what the proper range for fixed IPs is. And it is usually trivial to change the range in the control web page of the router. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlVs9ucACgkQja8UbcUWM1wvjAEAjYnSDQFmME9txJLT+s0vJIV3 1eFRRZO2YE0WlXCjybEBAIfu9c3/r5meh7vSB3lwR4IVnJo0VJHSkJp+fHvPF5Rv =dc8m -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On June 1, 2015 5:20:55 PM PDT, "Carlos E. R."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-06-01 23:10, John Andersen wrote:
Couple of minor corrections:
1) yes you can use a mix of static and dynamic IPs, but you may occasionally experience trouble after a static machine has been turned off for a long period. The static IP may be leased by the dhcp server, and when you turn the static machine back on there will be a collision, and the other machine will be forced to obtain a new lease. This is seldom done cleanly.
No.
Even a cheap home routers have a range of IPs that are given out by the dhcp server, and the rest that is not, so that you can use those as fixed IPs. There can not be those collisions you mention if you just find out what the proper range for fixed IPs is. And it is usually trivial to change the range in the control web page of the router.
- -- Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlVs9ucACgkQja8UbcUWM1wvjAEAjYnSDQFmME9txJLT+s0vJIV3 1eFRRZO2YE0WlXCjybEBAIfu9c3/r5meh7vSB3lwR4IVnJo0VJHSkJp+fHvPF5Rv =dc8m -----END PGP SIGNATURE-----
And even more trivial to set up address reservation. Usually 2 clicks -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-06-02 03:41, John Andersen wrote:
On June 1, 2015 5:20:55 PM PDT, "Carlos E. R." <> wrote:
And even more trivial to set up address reservation. Usually 2 clicks
Not on my current router. It took me about 12 minutes to find the location: a button at the bottom of the Advanced/LAN setup. Then you have to type both the MAC and the associated IP. It is designed for obscurity. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlVtEK0ACgkQja8UbcUWM1yKNAEAhTEGvabEEVFkxz1YlMJv6OOx ptgvcJfwvJyhXQIfx4QA/i79Md8evokv2Cj4LrCg8VAWoZM4yR3OkT61Cw9FUSam =RmqA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Anton Aylward -
buhorojo -
Carlos E. R. -
Daniel Bauer -
Freek de Kruijf -
James Knott -
John Andersen -
Patrick Shanahan