The Following User Says Thank You to hawaii For This Useful Post: | ||
![]() |
2010-10-21
, 19:49
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#12
|
The Following User Says Thank You to egoshin For This Useful Post: | ||
![]() |
2010-10-21
, 21:51
|
|
Posts: 1,030 |
Thanked: 792 times |
Joined on Jun 2009
|
#13
|
![]() |
2010-10-21
, 22:16
|
|
Posts: 1,030 |
Thanked: 792 times |
Joined on Jun 2009
|
#14
|
The Following 2 Users Say Thank You to hawaii For This Useful Post: | ||
![]() |
2010-10-21
, 22:39
|
Posts: 458 |
Thanked: 783 times |
Joined on Jan 2010
@ France
|
#15
|
colin.stephane,
Does your backported version support network interfaces other than wlan0?
Thank you
The Following User Says Thank You to colin.stephane For This Useful Post: | ||
![]() |
2010-10-21
, 22:45
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#16
|
As a side note - if you're interested in dumping RAW data from ANY network interface, regardless of link type, see attached. This is stupid useful, it's an absolute necessity for me.
binary only, and it will attach to the first active interface or one supplied through `-i $INTERFACE`.
![]() |
2010-10-22
, 13:51
|
Posts: 393 |
Thanked: 67 times |
Joined on Feb 2010
|
#17
|
Hi,
Yes, it work with phonet0 for example but doesn't report any MAC or IP since this interface is not connected ...
I have also compiled the package for x86 to be able to use it on many interfaces on Firewall I have build at office, something like bonding + vlan with name like 'bond0.200:FWB2'
To be clear, I have made the x86 package before the armel one, because I needed the new version to be able to use it on my Firewall interfaces ...
A++
![]() |
2010-12-27
, 16:19
|
Posts: 3 |
Thanked: 0 times |
Joined on Dec 2010
|
#18
|
As a side note - if you're interested in dumping RAW data from ANY network interface, regardless of link type, see attached. This is stupid useful, it's an absolute necessity for me.
binary only, and it will attach to the first active interface or one supplied through `-i $INTERFACE`.
I'm not sure what gprs0 link spec is - the easiest way to fix this would be to bridge a tun/tap interface to it to get a layer 3-2 device to bind to with netdiscover.