06-29-2012 03:14 PM
06-30-2012 05:38 AM
After some long search in the web, it seems my router doesn't support well IPV6 request.
So first question : is IPV6 activated on the NAS?
Second question : how can I desactivate in the NAS it without broking eveything?
06-30-2012 08:04 AM - edited 06-30-2012 08:04 AM
That's not what I meant. From the ARP output, above, it appears that your MAC is connected via both wired and WiFi simultaneously. Every hardware address appears on both en0 and en1 adapters. That can create all kinds of issues. But I don't know nearly enough about Mac to say for certain that's what I'm seeing...
The WiFi on my Fios box is turned off. I use my Airport Extreme for my wireless network.
07-10-2012 05:57 AM
Patrick, the NAS does have an ipv6 Link-Local address on the eth0 interface.
Almost *ALL* Linux, Windows and Mac boxes do. There should be no reason this should cause any issues on your network.
eth0 Link encap:Ethernet HWaddr 00:90:a9:f6:05:f8
inet addr:10.0.0.15 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::290:a9ff:fef6:5f8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:80617729 errors:0 dropped:0 overruns:0 frame:0
TX packets:39624835 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:3477467889 (3.2 GiB) TX bytes:1795424702 (1.6 GiB)
Windows IP Configuration
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : .....
Link-local IPv6 Address . . . . . : fe80::11df:8c34:ef9f:a403%11
Completely disabling V6 is actually rather complicated, because it requires interaction with the Kernel.
07-11-2012 12:24 AM
All router should support it, but my router is quite old (I may have a new one next year)
The linux kernel inside is version 2.4, and seems to have some bad support of IP V6
Also I read some post in the internet, that said my box has some bugs with IPV6.
07-15-2012 08:30 AM
I installed MBLD yesterday. My configuration is:
router : Orange Livebox2 (produced by sagem for France Telecom, Spain release))
two computers wired to the internal router switch: windows vista and ubuntu linux.
MBLD: connected also to the internal router switch.
several devices connected wirelessly: ipad, iphone, macbook air, windows xp laptop, popcornhour A-110, apple TV
After several minutes I observed the same problem ONLY with the wireless -connected devices: they couldn't connect to the internet. (wired computers experienced no issue). After troubleshooting the results are:
1*/ The problem comes from DNS. the router DHCP server assigns the router as DNS proxy-server. If you try to obtain an IP address via nslookup there is no answer from the router. BUT you can ping any public internet address so the packet transmission seems to work fine.
WORKAROUND: configure public DNS servers instead of using the router as a proxy in every device (ask your ISP which to configure or check the configuration of your router). This solves the inconveniences but doesn't solve the cause of the problem. --> this can help most of you until a better solution is found.
2*/ There is also another problem. This seems to be affecting the internal processes of the router. Access to the router configuration is very slow as if the CPU were busy.
3*/ As Patrick comments in a previous message in this thread, I agree with the relationship of this issue with the m-DNS issue in avahi. But can't access the OS in MBLD to try the workarounds posted in avahi.org (could someone give me a piece of an advice on this?)
4*/ After 24 hours working the router configuration access speed seems normal again but when I try to use the router as DNS proxy, the first answer is always a timeout (2seconds)., but the second try works well. With MLBD disconnected everything works fine again.
-I hate when behaviour changes without apparent cause. Makes troubleshooting a **bleep** !!!!--
I am NO expert, so, if someone can confirm my observations or try to connect the MBLD OS to check the m-DNS configuration it would be perfect.