[issue28545] socket.bind to AF_PACKET should use passed interface name

2016-10-28 Thread Martin Turon
Martin Turon added the comment: If I bind to port 0, it works for both tx and rx. Sorry for the false alarm! sock.bind(("monitor0", 0)) -- status: open -> closed ___ Python tracker <http://bugs.pytho

[issue28545] socket.bind to AF_PACKET should use passed interface name

2016-10-27 Thread Martin Turon
Martin Turon added the comment: Just for clarity, the high level bug is that when binding to an interface using AF_PACKET, transmissions work, but receive does not: sock = socket.socket(socket.AF_PACKET, socket.SOCK_RAW, ETH_P_IEEE802154) sock.bind(("monitor0", ETH_P_

[issue28545] socket.bind to AF_PACKET should use passed interface name

2016-10-27 Thread Martin Turon
New submission from Martin Turon: When binding to AF_PACKET linux kernel sockets, the interface name is not passed in when given -- it is always "". This causes problems, for example, receiving packets to a "monitor0" interface doesn't work. diff -r a6548e230ed6 Mod