Re: How can I send packets to 255.255.255.255 from the command line?

2016-08-19 Thread Andrey V. Elsukov 
On 18.08.16 22:29, Ryan Stone wrote:
> I want to test a change to broadcast packet handling and I want to confirm
> that 255.255.255.255 is still handled correctly. Are there any command-line
> tools in FreeBSD that can send to the broadcast address?  ping
> 255.255.255.255 does not work correctly, unfortunately.

There is one in src/tools/regression/netinet/ipbroadcast
You can build it with command
# make WARNS=0

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature

Re: How can I send packets to 255.255.255.255 from the command line?

2016-08-19 Thread Valeri Galtsev 

On Fri, August 19, 2016 9:46 am, Andrey V. Elsukov wrote:
> On 18.08.16 22:29, Ryan Stone wrote:
>> I want to test a change to broadcast packet handling and I want to
>> confirm
>> that 255.255.255.255 is still handled correctly. Are there any
>> command-line
>> tools in FreeBSD that can send to the broadcast address?  ping
>> 255.255.255.255 does not work correctly, unfortunately.
>
> There is one in src/tools/regression/netinet/ipbroadcast
> You can build it with command
> # make WARNS=0
>

Am I the only one who is kind of kicked out of the chair when seeing
someone attempting to broadcast the who ipv4 internet: 255.255.255.255 ?!
Someone explain me this is OK and is not a "big bang" level of noise ;-(

Valeri

> --
> WBR, Andrey V. Elsukov
>
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: How can I send packets to 255.255.255.255 from the command line?

2016-08-19 Thread Charles Smith 
It is still limited to the "local network," about as harmless as a DHCP 
broadcast.

- Charles



Sent from my iPhone
> On Aug 19, 2016, at 11:15 AM, Valeri Galtsev  
> wrote:
> 
> 
>> On Fri, August 19, 2016 9:46 am, Andrey V. Elsukov wrote:
>>> On 18.08.16 22:29, Ryan Stone wrote:
>>> I want to test a change to broadcast packet handling and I want to
>>> confirm
>>> that 255.255.255.255 is still handled correctly. Are there any
>>> command-line
>>> tools in FreeBSD that can send to the broadcast address?  ping
>>> 255.255.255.255 does not work correctly, unfortunately.
>> 
>> There is one in src/tools/regression/netinet/ipbroadcast
>> You can build it with command
>> # make WARNS=0
>> 
> 
> Am I the only one who is kind of kicked out of the chair when seeing
> someone attempting to broadcast the who ipv4 internet: 255.255.255.255 ?!
> Someone explain me this is OK and is not a "big bang" level of noise ;-(
> 
> Valeri
> 
>> --
>> WBR, Andrey V. Elsukov
>> 
>> 
> 
> 
> 
> Valeri Galtsev
> Sr System Administrator
> Department of Astronomy and Astrophysics
> Kavli Institute for Cosmological Physics
> University of Chicago
> Phone: 773-702-4247
> 
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

iwn(4) association issues in 11-Stable (and maybe RC)

2016-08-19 Thread Kevin Oberman 
Lately I have had serious issues with my system successfully associating.
These were not present with 10.3.

> uname -a
FreeBSD rogue 11.0-BETA4 FreeBSD 11.0-BETA4 #1 r303806: Sat Aug  6 18:50:50
PDT 2016 root@rogue:/usr/obj/usr/src/sys/GENERIC.4BSD  amd64

iwn0@pci0:3:0:0:class=0x028000 card=0x13118086 chip=0x00858086 rev=0x34
hdr=0x00
cap 01[c8] = powerspec 3  supports D0 D3  current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint max data 128(128) FLR RO NS
 link x1(x1) speed 2.5(2.5) ASPM L1(L0s/L1)
ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected
ecap 0003[140] = Serial 1 a088b4c6ad28

Once associated, it works fine, but a dropped association is often not
re-established and the network fails to come up at boot time. Kernel is
GENERIC except the 4BSD scheduler.

I've been using a mobile hotspot this week during travels and it has become
a real pain. With  lot of patience and many "netif restart wlan0"
operations, it will come up, but it can be painful. Here is what I see in
messages:
Aug 19 00:13:52 rogue kernel: wlan0: Ethernet address: a0:88:b4:c6:ad:28
Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN
Aug 19 00:13:52 rogue kernel: iwn0: scan timeout
Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN
Aug 19 00:13:52 rogue kernel: iwn0: scan timeout
Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN
Aug 19 00:13:52 rogue kernel: iwn0: scan timeout
Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN
Aug 19 00:13:52 rogue kernel: iwn0: scan timeout
Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN
Aug 19 00:13:52 rogue kernel: iwn0: scan timeout
Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN
Aug 19 00:13:52 rogue kernel: iwn0: scan timeout
Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN
Aug 19 00:13:52 rogue kernel: iwn0: scan timeout
Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP
Aug 19 00:13:52 rogue kernel: ipfw2 (+ipv6) initialized, divert loadable,
nat loadable, default to deny, logging disabled
Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN
Aug 19 00:13:52 rogue kernel: iwn0: scan timeout
Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:14:17 rogue dhclient[362]: send_packet: Network is down
Aug 19 00:14:37 rogue dhclient[362]: send_packet: Network is down
Aug 19 00:14:39 rogue wpa_supplicant[350]: wlan0: CTRL-EVENT-TERMINATING
Aug 19 00:14:39 rogue dhclient[362]: connection closed
Aug 19 00:14:39 rogue dhclient[362]: exiting.
Aug 19 00:14:39 rogue rtsold[873]:  interface
wlan0 removed
Aug 19 00:14:39 rogue kernel: wlan0: Ethernet address: a0:88:b4:c6:ad:28
Aug 19 00:14:39 rogue wpa_supplicant[1621]: Successfully initialized
wpa_supplicant
Aug 19 00:14:39 rogue wpa_supplicant[1633]: Successfully initialized
wpa_supplicant
Aug 19 00:14:39 rogue root: /etc/rc.d/wpa_supplicant: WARNING: failed to
start wpa_supplicant
Aug 19 00:14:39 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Aug 19 00:14:39 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103,
val=0, arg_len=128]: Operation now in progress
Aug 19 00:14:39 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED
ret=-1 retry=1
Aug 19 00:14:40 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103,
val=0, arg_len=128]: Operation now in progress
Aug 19 00:14:40 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED
ret=-1 retry=1
Aug 19 00:14:41 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103,
val=0, arg_len=128]: Operation now in progress
Aug 19 00:14:41 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED
ret=-1 retry=1
Aug 19 00:14:42 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103,
val=0, arg_len=128]: Operation now in progress
Aug 19 00:14:42 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED
ret=-1 retry=1
Aug