Re: Binding a packet socket to interface down

[Evgeniy Polyakov <johnpol@2ka.mipt.ru>]

On Thu, Jun 22, 2006 at 06:32:29PM +0300, Robert Iakobashvili (coroberti@gmail.com) wrote:
> Hi,
> 
> When packet socket (PF_SOCKET) is attempted in syscall bind () to the
> network interface, which is down (no IF_UPP flag), packet_do_bind ()
> sets error to the socket, but bind () does not fail.
> 
> When datagram, stream or raw socket fail to bind to some local
> ip-port/ip, bind () fails.
> 
> Is this behavior of bind () for packet socket done deliberately, or
> better to correct it so that bind will fail and return errno, e.g. ENODEV?
> Thanks.

man page says that packet socket does not handle any errors.
And actually packet socket binds to the device, but you can not read
data. When device will be turned on, packet socket should start
to function (packet_notifier() -> NETDEV_UP)..


-- 
	Evgeniy Polyakov