[Click] Hex addresses in lineariplookup messages

[Eddie Kohler]

Hi Bart,

Yeah, that's a little weird.  I updated the code to use unparse(), and to 
print at most 5 messages.  It doesn't push the packet out because, if you want 
to push the packet out, that's very easy to implement: add a default route.

Eddie


Bart Braem wrote:
> 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
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click