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