Peter Rabbitson wrote:
James Yonan wrote:
Peter Rabbitson wrote:
James Yonan wrote:
Peter Rabbitson wrote:
Eventually the best way to deal with this is to test for
ip_addr_dotted_quad_safe and is_special_addr, and then attempt a dns
lookup on the string supplied for route. If anything come
Peter Rabbitson wrote:
James Yonan wrote:
Peter Rabbitson wrote:
James Yonan wrote:
Peter Rabbitson wrote:
Eventually the best way to deal with this is to test for
ip_addr_dotted_quad_safe and is_special_addr, and then attempt a dns
lookup on the string supplied for route. If anything come
James Yonan wrote:
>
>
> Peter Rabbitson wrote:
>> James Yonan wrote:
>>> Peter Rabbitson wrote:
>>
Eventually the best way to deal with this is to test for
ip_addr_dotted_quad_safe and is_special_addr, and then attempt a dns
lookup on the string supplied for route. If anything com
James Yonan wrote:
>
>
> Peter Rabbitson wrote:
>> James Yonan wrote:
>>> Peter Rabbitson wrote:
>>
Eventually the best way to deal with this is to test for
ip_addr_dotted_quad_safe and is_special_addr, and then attempt a dns
lookup on the string supplied for route. If anything com
Peter Rabbitson wrote:
James Yonan wrote:
Peter Rabbitson wrote:
Eventually the best way to deal with this is to test for
ip_addr_dotted_quad_safe and is_special_addr, and then attempt a dns
lookup on the string supplied for route. If anything comes back - use
the result as the routed IPs.
James Yonan wrote:
> Peter Rabbitson wrote:
>>
>> Eventually the best way to deal with this is to test for
>> ip_addr_dotted_quad_safe and is_special_addr, and then attempt a dns
>> lookup on the string supplied for route. If anything comes back - use
>> the result as the routed IPs. Otherwise war
Peter Rabbitson wrote:
Hello,
I would like to duplicate a concern about the proposed fix, voiced over
at the debian BTS
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493488#29, before the
final version ships.
=
This fix breaks the follo
