[Click] Hex addresses in lineariplookup messages

[Bart Braem]

Hello,

We noticed that LinearIPLookup generates an error message with hex addresses 
in it when no route can be found, e.g.:
LinearIPLookup: no gw for 301a8c0
Why is there no translation to a string there? I know the conversion to string 
is easy so I guess there must be a reason for it.
Another remark: why does the element kill the packet itself? Why doesn't it 
push out the packet e.g. to generate ICMP error messages?

Bart
-- 
Bart Braem
PATS research group
Dept. of Mathematics and Computer Sciences
University of Antwerp
G2.36, Building G
Middelheimlaan 1
2020 Antwerpen, Belgium
Phone: +32 (0)3 265.35.19.
Fax: +32 (0)3 265.37.77.
Web: www.pats.ua.ac.be
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 309 bytes
Desc: not available
Url : https://amsterdam.lcs.mit.edu/pipermail/click/attachments/20060523/e8b9b374/attachment.pgp