|
2017-02-10
, 07:13
|
Community Council |
Posts: 685 |
Thanked: 1,234 times |
Joined on Sep 2010
@ Mbabane
|
#2
|
|
2017-02-10
, 16:01
|
Posts: 175 |
Thanked: 210 times |
Joined on Mar 2013
|
#3
|
gprs0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.127.47.xxx P-t-P:10.127.47.xxx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MTU:1400 Metric:1 RX packets:2371 errors:0 dropped:0 overruns:0 frame:0 TX packets:1700 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:2679790 (2.5 MiB) TX bytes:120760 (117.9 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:5935 errors:0 dropped:0 overruns:0 frame:0 TX packets:5935 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:381592 (372.6 KiB) TX bytes:381592 (372.6 KiB) phonet0 Link encap:UNSPEC HWaddr 15-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP POINTOPOINT RUNNING NOARP MTU:4000 Metric:1 RX packets:73866 errors:0 dropped:0 overruns:0 frame:0 TX packets:26775 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:29760428 (28.3 MiB) TX bytes:1859874 (1.7 MiB)
Server: 127.0.0.1 Address 1: 127.0.0.1 N900 Name: google.com Address 1: 216.58.214.238 bud02s24-in-f14.1e100.net Address 2: 2a00:1450:400d:807::200e bud02s22-in-x0e.1e100.net
|
2017-02-11
, 11:31
|
Posts: 175 |
Thanked: 210 times |
Joined on Mar 2013
|
#4
|
inet6 addr: fe80::5e57:c8ff:fe5d:df13/64 Scope:Link
Server: 127.0.0.1 Address 1: 127.0.0.1 N900 Name: google.com Address 1: 216.58.214.238 bud02s24-in-f14.1e100.net Address 2: 2a00:1450:4016:803::200e muc03s08-in-x0e.1e100.net
|
2017-02-13
, 19:14
|
Posts: 2,290 |
Thanked: 4,134 times |
Joined on Apr 2010
@ UK
|
#5
|
|
2017-02-13
, 21:16
|
Posts: 175 |
Thanked: 210 times |
Joined on Mar 2013
|
#6
|
v6 is enabled on most modern stuff now to aid transition to v6.
|
2017-02-13
, 21:36
|
Community Council |
Posts: 685 |
Thanked: 1,234 times |
Joined on Sep 2010
@ Mbabane
|
#7
|
|
2017-02-13
, 22:06
|
Posts: 2,290 |
Thanked: 4,134 times |
Joined on Apr 2010
@ UK
|
#8
|
|
2017-02-14
, 19:22
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#9
|
The Following 6 Users Say Thank You to pali For This Useful Post: | ||
|
2017-02-15
, 15:43
|
Posts: 175 |
Thanked: 210 times |
Joined on Mar 2013
|
#10
|
1) Stock kernel does not support IPv6, so by default there is no way to open/bind IPv6 socket
2) Basically all default Maemo 5 applications have disabled IPv6 support, so they do not try to open/bind IPv6 socket (even you have kernel with IPv6 support)
3) Disabling IPv6 support can be achieved by sysctl which you already wrote. When disable_ipv6=1 then *no* userspace application is able to open/bind IPv6 socket. Kernel acts same as if IPv6 support was disabled at compile time.
4) Asking DNS server for AAAA record has nothing and absolutely nothing with IPv6 support. You can ask for AAAA record of some hostname via IPv6 DNS socket and also via *IPv4* DNS socket. POSIX applications uses getaddrinfo() function (see man 3 getaddrinfo) which is supposed to do DNS lookups.
5) Router has nothing allowing IPv6 connections and AAAA queries. Those are two different things which has nothing in common. DNS is application protocol (layer 7) and IPv6 is network protocol (layer 3).
6) DNS resolving does not have to be slow "because of IPv6". You can ask (and system libraries probably do it) for ANY address for some host and you get both IPv4 and IPv6 address.
7) IPv6 Link-Local address cannot be used for making "internet" connection and IIRC connect() is not possible.
So... In IPv4-only network there should be absolutely no penalty with enabled IPv6 support in kernel or applications.
Problem can be in IPv4-only network which advertise IPv6 availabilty (which is non-working). But simple disabling IPv6 in kernel fixes it.
So if you are seeing some problems even after disabling IPv6 then it is probably not IPv6 related.
Tags |
disable, ipv6-support, maemo |
|
So, I seem to find some infos about how to enable ipv6 on the N900 but not on how to completely disable it.
I don't use ipv6 and sometimes the dns queries are slow because an ipv6 is first looked for before asking for an ipv4.
And also because I would rather use ipv4 only (I understand the usefulness of ipv6 but I never completely understood how it worked).
I've tried :
Any ideas?