Re: Promiscuous ports under Linux

2017-05-04 Thread Peter Pearson
On Thu, 4 May 2017 18:04:02 + (UTC), Grant Edwards wrote: > On 2017-05-04, Peter Pearson wrote: > >> I'm curious to survey all my LAN traffic in various ways, and it seems >> likely that I will see phenomena that I don't understand, and focussing >> in on those phenomena is likely to require

Re: Promiscuous ports under Linux

2017-05-04 Thread Grant Edwards
On 2017-05-04, Peter Pearson wrote: > I'm curious to survey all my LAN traffic in various ways, and it seems > likely that I will see phenomena that I don't understand, and focussing > in on those phenomena is likely to require more flexible filtering > than Wireshark can provide. I expect to le

Re: Promiscuous ports under Linux

2017-05-04 Thread Peter Pearson
On Thu, 04 May 2017 10:26:45 GMT, alister wrote: > On Wed, 03 May 2017 23:57:49 +, Peter Pearson wrote: > >> Cobbling together a minimalist ethernet-sniffing program, I was hoping >> to use this simple mechanism for setting the socket to "promiscuous >> mode" (to see all traffic going past, in

Re: Promiscuous ports under Linux

2017-05-04 Thread alister
On Thu, 04 May 2017 14:11:04 +0300, Marko Rauhamaa wrote: > alister : > >> On Wed, 03 May 2017 23:57:49 +, Peter Pearson wrote: >> >>> Cobbling together a minimalist ethernet-sniffing program, I was hoping >>> to use this simple mechanism for setting the socket to "promiscuous >>> mode" (to s

Re: Promiscuous ports under Linux

2017-05-04 Thread Marko Rauhamaa
alister : > On Wed, 03 May 2017 23:57:49 +, Peter Pearson wrote: > >> Cobbling together a minimalist ethernet-sniffing program, I was >> hoping to use this simple mechanism for setting the socket to >> "promiscuous mode" (to see all traffic going past, instead of just >> traffic addressed to m

Re: Promiscuous ports under Linux

2017-05-04 Thread alister
On Wed, 03 May 2017 23:57:49 +, Peter Pearson wrote: > Cobbling together a minimalist ethernet-sniffing program, I was hoping > to use this simple mechanism for setting the socket to "promiscuous > mode" (to see all traffic going past, instead of just traffic addressed > to my machine): > >

Re: Promiscuous ports under Linux

2017-05-03 Thread Marko Rauhamaa
Peter Pearson : > Cobbling together a minimalist ethernet-sniffing program, I was hoping > to use this simple mechanism for setting the socket to "promiscuous > mode" (to see all traffic going past, instead of just traffic > addressed to my machine): > > s.ioctl(socket.SIO_RCVALL, socket.RCVAL

Re: Promiscuous ports under Linux

2017-05-03 Thread Peter Pearson
On Wed, 3 May 2017 18:09:08 -0700, Rob Gaddi wrote: > On 05/03/2017 04:57 PM, Peter Pearson wrote: >> Cobbling together a minimalist ethernet-sniffing program, I was hoping >> to use this simple mechanism for setting the socket to "promiscuous >> mode" (to see all traffic going past, instead of jus

Re: Promiscuous ports under Linux

2017-05-03 Thread Rob Gaddi
On 05/03/2017 04:57 PM, Peter Pearson wrote: Cobbling together a minimalist ethernet-sniffing program, I was hoping to use this simple mechanism for setting the socket to "promiscuous mode" (to see all traffic going past, instead of just traffic addressed to my machine): s.ioctl(socket.SIO_R

Promiscuous ports under Linux

2017-05-03 Thread Peter Pearson
Cobbling together a minimalist ethernet-sniffing program, I was hoping to use this simple mechanism for setting the socket to "promiscuous mode" (to see all traffic going past, instead of just traffic addressed to my machine): s.ioctl(socket.SIO_RCVALL, socket.RCVALL_ON) Unfortunately, it see