|
|
2010-08-25
, 20:19
|
|
Posts: 2 |
Thanked: 1 time |
Joined on Aug 2010
|
#41
|
| The Following User Says Thank You to japes For This Useful Post: | ||
|
|
2010-08-25
, 20:29
|
|
Posts: 968 |
Thanked: 974 times |
Joined on Nov 2008
@ Ohio
|
#42
|
I'd be interested to hear how everyone else's connection reliability fairs when using v4+v6.
|
|
2010-08-25
, 20:40
|
|
Posts: 57 |
Thanked: 39 times |
Joined on Aug 2010
|
#43
|
I will try to check this out tonight (won't get on wifi at home).
I did install your ipv6 only connection. Works fine, can access the web, etc. However, it appears that it gives me problems with my sip connection (Gizmo5) and TOR (theonering - google voice access). Both end up with network errors.
Is there anything I should add to /etc/resolv.conf
I added nameserver 2607:FB09:BEEF:A::1 above nameserver 127.0.0.1
commented it out later. Either way ipv6 only give network error for SIP and TOR, ipv4+ipv6 they work fine.
Thanks
| The Following User Says Thank You to ddrown For This Useful Post: | ||
|
|
2010-08-25
, 20:51
|
|
Posts: 42 |
Thanked: 30 times |
Joined on Aug 2010
|
#44
|
You shouldn't need to modify /etc/resolv.conf. The plugin gets the DNS servers from the connection setup and puts them in /var/run/resolv.conf.gprs (which is where dnsmasq looks for them).
I expect the problem with SIP and TOR to be the same as with MSN, having an IPv4 address embedded in the data. This means that DNS64 doesn't have a chance to rewrite the IPv4 address into a IPv6 one. So it probably won't be fixed without an update to that application.
If the SIP server is IPv4, there is some ALG wrangling that needs to happen since in the IPv6-only scenario the NAT64 must protocol translate the SIP and related RTP packets from IPv6 on your handset to IPv4 on the server. This protocol translation generally works well for web and email, but applications with seperate control and media channels like SIP and RTSP tend to be challenge.
| The Following User Says Thank You to tmojoe For This Useful Post: | ||
|
|
2010-08-25
, 21:46
|
|
Posts: 968 |
Thanked: 974 times |
Joined on Nov 2008
@ Ohio
|
#45
|
|
|
2010-08-25
, 21:56
|
|
Posts: 87 |
Thanked: 16 times |
Joined on Aug 2010
@ Southern California
|
#46
|
|
|
2010-08-25
, 22:18
|
|
|
Posts: 118 |
Thanked: 38 times |
Joined on Apr 2010
@ California
|
#47
|
|
|
2010-08-25
, 22:23
|
|
Posts: 968 |
Thanked: 974 times |
Joined on Nov 2008
@ Ohio
|
#48
|
Form has been sent.... For those who have this, did you have to actually wait a week to get confirmation??
| The Following User Says Thank You to lemmyslender For This Useful Post: | ||
|
|
2010-08-25
, 22:34
|
|
|
Posts: 118 |
Thanked: 38 times |
Joined on Apr 2010
@ California
|
#49
|
|
|
2010-08-25
, 23:00
|
|
Posts: 5,795 |
Thanked: 3,151 times |
Joined on Feb 2007
@ Agoura Hills Calif
|
#50
|
I have a package to make v6 setup a little easier at:
http://code.google.com/p/n900ipv6/wiki/README
This will give you a v6-only connection option (and leaves your v4-only connection alone). I've been using it for a week now, and the only thing I've run into is MSN is broken (known problem with the MSN protocol).
Please let me know if you have any questions.
![]() |
| Tags |
| ipv6s, tmobile |
| Thread Tools | |
|