James Knott wrote:
On 09/08/2014 04:15 PM, Linda Walsh wrote:
FWIW, what you are doing was the advice when IPv6 was introduced, but it was changed. The advice now, is to prefer an end-to-end 4-4 connection over a 4-6-6-4 as the latter introduces considerable inefficiencies and slowdowns to the net as a whole. If you really have a native 6-6, that's preferred, but a 6-6 that is really a disguised 4-4 is wasting BW.
I don't sent IPv4 over IPv6. Sorry, I can see my nomenclature was unclear. What I meant by 4-6-6-4 was having native IPv4 connectivity at each end and are using a 6-in-4 or toredo tunnel to talk from an IPv6 app (like DNS) to an IPv6 app on the other end (a ipv6 DNs resolver).. With the important detail being that you don't have native ipv6 connecting your end to the other -- instead you rely on some encapsulation over ipv4.
That's the part they said to move away from. if you have native ipv4 connectivity on each end, then use ipv4 -- only if you have a native ipv6 on both ends (that isn't tunneled over ipv4) does it make sense to use ipv6. At least that was the gist of the recommendation. Some papers on the problem : IPv6 delay and loss performance evolution - http://www-nas.et.tudelft.nl/people/Piet/papers/IJCS_2008_ipv6_delft_ripe.pd... A security issue: Packet Fragmentation in IPv6 over IPv4 Tunnels https://www.cs.duke.edu/~xinl/apan-mtu.pdf And a well rated comparison of 6-in-4 tunneling protocols: RFC 7059 - A Comparison of *IPv6*-*over*-*IPv4 Tunnel* Mechanisms <http://www.google.com/url?q=http://tools.ietf.org/html/rfc7059&sa=U&ei=MWAOVOfKI6G1iwLAk4CACA&ved=0CBQQFjAA&sig2=JvoKb_jSfFW8Qr43fLpJYw&usg=AFQjCNFTs4pRxrP2YZoaorW0v7Yid_lA_w> http://tools.ietf.org/html/rfc7059 But the
I tunnel IPv6 and IPv4 goes per usual. Regardless, the problem was accessing a DNS server.
Maybe the higher one is considered authoritative so lower ones don't get checked? nscd gives more control, but is intended for local resolving...
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org