On 10/24/12 9:02 PM, Juha Heinanen wrote:
Richard Fuchs writes:
Obviously the DNS requests shouldn't happen in the first place.
exactly, that has been my point all the time. the patch that i proposed
is like aspirin until the real bug has been fixed.
Is the query type A or when dns for
On 24.10.2012 20:41, Juha Heinanen wrote:
Richard Fuchs writes:
this is not the real fix, but helps until someone figures out why dns
query on something that is not a name but wrongly formatted ipv6 address
is done in the first place.
What do you mean with wrongly formatted?
the ipv6
Daniel-Constantin Mierla writes:
The better fix looking at the patch you proposed would be to use the
function that detects is valid ipv6, not just something starting with
'['.
this has nothing to with what is valid ipv6, but rather, how does a
valid domain name look like. domain name
i would like to add and when hostpart of r-uri is ipv4 address,
wireshark tells me that kamailio does NOT try to resolve it from dns,
but when hostpart is [ipv6 address] then (as i have shown earlier),
kamailio tries to resolve it.
if it would be possible to make treatment of ipv6 hostpart the
On Thursday 25 October 2012, Juha Heinanen wrote:
an ipv6 address can thus never be a valid domain name. an ipv4 address,
on the other hand, is syntactically valid domain name and perhaps
someone has populated their local name server with such names.
But the application (kamailio) should not
On 10/25/12 4:33 PM, Alex Hermann wrote:
On Thursday 25 October 2012, Juha Heinanen wrote:
an ipv6 address can thus never be a valid domain name. an ipv4 address,
on the other hand, is syntactically valid domain name and perhaps
someone has populated their local name server with such names.
On 10/25/2012 05:33 PM, Alex Hermann wrote:
On Thursday 25 October 2012, Juha Heinanen wrote:
an ipv6 address can thus never be a valid domain name. an ipv4 address,
on the other hand, is syntactically valid domain name and perhaps
someone has populated their local name server with such names.
On Thursday 25 October 2012, Daniel-Constantin Mierla wrote:
On 10/25/12 4:33 PM, Alex Hermann wrote:
On Thursday 25 October 2012, Juha Heinanen wrote:
an ipv6 address can thus never be a valid domain name. an ipv4 address,
on the other hand, is syntactically valid domain name and perhaps
On 10/24/12 14:28, Juha Heinanen wrote:
this is not the real fix, but helps until someone figures out why dns
query on something that is not a name but wrongly formatted ipv6 address
is done in the first place.
What do you mean with wrongly formatted?
cheers
signature.asc
Description:
Richard Fuchs writes:
this is not the real fix, but helps until someone figures out why dns
query on something that is not a name but wrongly formatted ipv6 address
is done in the first place.
What do you mean with wrongly formatted?
the ipv6 address that is passed to dns server is
On 10/24/12 14:41, Juha Heinanen wrote:
Richard Fuchs writes:
this is not the real fix, but helps until someone figures out why dns
query on something that is not a name but wrongly formatted ipv6 address
is done in the first place.
What do you mean with wrongly formatted?
the ipv6
Richard Fuchs writes:
IPv6 addresses are supposed to be bracketed when used within an URI.
Otherwise a parser wouldn't be able to tell if an optional port was
given or not. Compare http://2620:0:2d0:200::8/ vs
http://[2620:0:2d0:200::8]/ vs http://2620:0:2d0:200::8:80/ vs
On 10/24/12 14:51, Juha Heinanen wrote:
Richard Fuchs writes:
IPv6 addresses are supposed to be bracketed when used within an URI.
Otherwise a parser wouldn't be able to tell if an optional port was
given or not. Compare http://2620:0:2d0:200::8/ vs
http://[2620:0:2d0:200::8]/ vs
Richard Fuchs writes:
Obviously the DNS requests shouldn't happen in the first place.
exactly, that has been my point all the time. the patch that i proposed
is like aspirin until the real bug has been fixed.
-- juha
___
SIP Express Router (SER)
14 matches
Mail list logo
