On Wed, 2013-11-20 at 16:21 -0600, Kevin Martin wrote: > On 11/20/2013 03:21 PM, Louis Lagendijk wrote: > > Some time ago I asked a question about the broadcast address on Fedora > > 20. On my desktop (installed from one of Alpha TC's) the interface is > > brought up correctly, except that the broadcast address does not get set > > correctly: > > Ifconfig reports: > > > >> p5p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > >> inet 192.168.159.186 netmask 255.255.255.0 broadcast 0.0.0.0 > >> inet6 2001:981:688d:f2:1e6f:65ff:fed5:7742 prefixlen 128 > >> scopeid 0x0<global> > >> inet6 fe80::1e6f:65ff:fed5:7742 prefixlen 64 scopeid > >> 0x20<link> > >> ether 1c:6f:65:d5:77:42 txqueuelen 1000 (Ethernet) > >> RX packets 568712 bytes 540500284 (515.4 MiB) > >> RX errors 0 dropped 0 overruns 0 frame 0 > >> TX packets 359977 bytes 282238000 (269.1 MiB) > >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > The broadcast address is not set when I use DHCP, but is also missing > > when I use static address allocation. When I try a > > ifdown p5p1; ifup05p1 > > the broadcast address is setup correctly. > > > > Today I installed my laptop with Fedora 20 Beta. I see the same there: > > The broadcast address is not set. I originally suspected a faulty nic > > river. But on my laptop is occurs on both the wlan and ethernet > > interfaces. > > > > Does anybody else see the same thing? How can I debug this? With > > NetworkManager I am quite clueless on how to tackle this. > > > > Kind regards, Louis > > > > > Hmm, interesting. I, too, see this happening on a fully updated rawhide machine using NetworkManager: > > $ uname -a > Linux ktmtoshiba 3.13.0-0.rc0.git7.1.fc21.x86_64 #1 SMP Tue Nov 19 02:18:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > > $ ifconfig eth0 > eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 192.168.238.116 netmask 255.255.255.0 broadcast 0.0.0.0 > inet6 fe80::ca0a:a9ff:feb1:46c2 prefixlen 64 scopeid 0x20<link> > ether c8:0a:a9:b1:46:c2 txqueuelen 1000 (Ethernet) > RX packets 912190 bytes 1118290284 (1.0 GiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 257389 bytes 23661386 (22.5 MiB) > TX errors 0 dropped 0 overruns 0 carrier 1 collisions 0 > > It would appear to be in the interaction between dhclient and NetworkManager (which actually starts the nic and configures it, > dhclient or NetworkManager?) as my dhclient leases file also shows a broadcast address but, as you can see, none appears on my nic. > Seems like a bz should be raised for this. Ok, I will raise a BZ then Thanks for your feedback -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
