<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 20 November 2013 22:29, Louis Lagendijk <span dir="ltr"><<a href="mailto:louis@fazant.net" target="_blank">louis@fazant.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5">On Wed, 2013-11-20 at 16:21 -0600, Kevin Martin wrote:<br>
> On 11/20/2013 03:21 PM, Louis Lagendijk wrote:<br>
> > Some time ago I asked a question about the broadcast address on Fedora<br>
> > 20. On my desktop (installed from one of Alpha TC's) the interface is<br>
> > brought up correctly, except that the broadcast address does not get set<br>
> > correctly:<br>
> > Ifconfig reports:<br>
> ><br>
> >> p5p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br>
> >> inet 192.168.159.186 netmask 255.255.255.0 broadcast 0.0.0.0<br>
> >> inet6 2001:981:688d:f2:1e6f:65ff:fed5:7742 prefixlen 128<br>
> >> scopeid 0x0<global><br>
> >> inet6 fe80::1e6f:65ff:fed5:7742 prefixlen 64 scopeid<br>
> >> 0x20<link><br>
> >> ether 1c:6f:65:d5:77:42 txqueuelen 1000 (Ethernet)<br>
> >> RX packets 568712 bytes 540500284 (515.4 MiB)<br>
> >> RX errors 0 dropped 0 overruns 0 frame 0<br>
> >> TX packets 359977 bytes 282238000 (269.1 MiB)<br>
> >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br>
> ><br>
> > The broadcast address is not set when I use DHCP, but is also missing<br>
> > when I use static address allocation. When I try a<br>
> > ifdown p5p1; ifup05p1<br>
> > the broadcast address is setup correctly.<br>
> ></div></div></blockquote><div><br></div><div>Interestingly enough using the iproute tools mirrors the net-tools here to some extent... although net-tools reports 0.0.0.0 whereas iproute shows no broadcast address:</div>
<div><br></div><div> 2: p4p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000</div><div> link/ether d4:be:d9:7e:f3:ce brd ff:ff:ff:ff:ff:ff</div><div> inet <a href="http://10.81.10.110/24">10.81.10.110/24</a> scope global dynamic p4p1</div>
<div> valid_lft 18508sec preferred_lft 18508sec</div><div> inet6 fe80::d6be:d9ff:fe7e:f3ce/64 scope link </div><div> valid_lft forever preferred_lft forever</div><div><br></div><div>No brd bit is included in this compared to another interface that does have it:</div>
<div><br></div><div><div>12: virbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default </div><div> link/ether 52:54:00:72:fa:28 brd ff:ff:ff:ff:ff:ff</div><div> inet <a href="http://192.168.244.1/24">192.168.244.1/24</a> brd 192.168.244.255 scope global virbr1</div>
<div> valid_lft forever preferred_lft forever</div></div><div><br></div><div>However I'm curious as to the consequences of this given that broadcast address is just a function of network address against network mask anyway ...</div>
<div><br></div><div><br></div></div></div></div>