[EMAIL PROTECTED] wrote:
As far as I can see, print_vendor_attr() in print-radius.c doesn't
account for the fact that the length field includes itself (1 byte)
and type (1 byte), thus attempting to print 2 bytes too much when
printing the ASCII text form of the Value field.
Yes.
However, while
Sebastien Raveau wrote:
I could always make a separate capture just to be able to forward all traffic
while my first capture is filtered, but I am not comfortable with that
solution. This is why I am writing this feature proposal to this list:
* possibility of registering a separate callback fu
Hello,
After having used libpcap with great pleasure for years (thanks to all the
people working on it), I think I just found a limitation to it...
I am writing a sniffer with support for both ARP poisoning and BPF filtering.
The problem is: if I want to impersonate a router for example, ARP p
As far as I can see, print_vendor_attr() in print-radius.c doesn't
account for the fact that the length field includes itself (1 byte)
and type (1 byte), thus attempting to print 2 bytes too much when
printing the ASCII text form of the Value field. Example:
Vendor Specific Attribute (26), len
