anyone know what 'ping: sendto: Can't assign requested" means

[DTD]

On Tue, 20 Dec 2016, Adam Vande More wrote:

> On Tue, Dec 6, 2016 at 12:33 PM, DTD <doug at safeport.com> wrote:
>       For truth in advertising this is pinging from a jail. The problem is limited to pinging
>       outside of the jailed environment. I took a shot a the ping source to see if there was an
>       illuminating comment around the message but got lost in tacking this through libc source.
>
>       I can show this is not a routing issue and the jails can ping. Our LAN has a
>       dozen or so devices all in the network 192.168.2.0/24. To demonstrate the
>       problem I used two hosts in the LAN and some external systems. The jail
>       environment is chaos (host) and two jails, gaia and gsscc. First, from either
>       jail all the above is ping-able:
>
>       From gaia:
>
>       gaia:~> ping -c 2 chaos
>       PING chaos.boltsys.com (192.168.2.117): 56 data bytes
>       64 bytes from 192.168.2.117: icmp_seq=0 ttl=64 time=0.020 ms
>       64 bytes from 192.168.2.117: icmp_seq=1 ttl=64 time=0.047 ms
>
>       --- chaos.boltsys.com ping statistics ---
>       2 packets transmitted, 2 packets received, 0.0% packet loss
>       round-trip min/avg/max/stddev = 0.020/0.034/0.047/0.013 ms
>       gaia:~> ping -c 2 gsscc
>       PING gsscc.boltsys.com (192.168.2.111): 56 data bytes
>       64 bytes from 192.168.2.111: icmp_seq=0 ttl=64 time=0.022 ms
>       64 bytes from 192.168.2.111: icmp_seq=1 ttl=64 time=0.023 ms
>
>       artemis is a host on the 192.168.2.0/24:
>
>       gaia:~> ping -c 2 artemis
>       PING artemis.boltsys.com (192.168.2.102): 56 data bytes
>       ping: sendto: Can't assign requested address
>       ping: sendto: Can't assign requested address
> 
Neat, thanks Adam.

gaia:~> ping -S 192.168.2.110 artemis
PING artemis.boltsys.com (192.168.2.102) from 192.168.2.110: 56 data bytes
64 bytes from 192.168.2.102: icmp_seq=0 ttl=64 time=0.974 ms
64 bytes from 192.168.2.102: icmp_seq=1 ttl=64 time=1.082 ms
64 bytes from 192.168.2.102: icmp_seq=2 ttl=64 time=0.742 ms
64 bytes from 192.168.2.102: icmp_seq=3 ttl=64 time=1.256 ms
^C
As 192.168.2.110 is the jail IP address:

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
         ether c8:9c:dc:eb:ab:fb
         inet 192.168.2.110 netmask 0xffffffff broadcast 192.168.2.110
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active

I guess it's a jail thingy in kernel. Seems like a bug to me but I could not 
even find where the error was coming from. Thank you again. I would (and did 
not) get -S from 'man ping' as solving the problem

Doug

_____
Douglas Denault
http://www.safeport.com
doug at safeport.com
Voice: 301-217-9220
   Fax: 301-217-9277