|
Mac OS X clients forget default route
![[de]](/s/countries/de.gif) Shadow Hawkins on Wednesday, 13 May 2009 00:01:29
Hi,
my setup looks as follows:
I have a Linksys WRT54GL running OpenWRT as IPv6 router, which runs aiccu and radvd to announce parts of my subnet 2a01:198:300::/48 to clients in the local wired and wireless networks. Clients are Mac OS X and Linux machines.
With the latter everything is fine, but the Mac OS X machines have a little issue: some time after they connected to the network and autoconfigured themselves, they "forget" the default route they got from the router, and on trying to connect to IPv6 hosts I get a "No route to host" error. Re-adding that route manually works, but they will forget it again.
(This isn't easy to check, but "some time" seems always to be approximately 2 hours.)
My current workaround is to add a static route for 2000::/3 on the OSX clients, which they won't forget (at least not till the next link down & link up), but that's obviously not how stateless autoconfiguration should work.
So, has anyone ever experienced this problem or has got an idea how I could solve it?
Best regards,
Jannis Andrija Schnitzer
Below: the router's radvd.conf - as you see, I tried to set lifetime for that route to infinity, but that doesn't help.
interface eth0.0
{
AdvSendAdvert on;
MaxRtrAdvInterval 600;
MinRtrAdvInterval 200;
prefix 2A01:198:300::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
};
route ::/0
{
AdvRouteLifetime infinity;
};
};
interface wlan0
{
AdvSendAdvert on;
MaxRtrAdvInterval 600;
MinRtrAdvInterval 200;
prefix 2A01:198:300:FADE::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
};
route ::/0
{
AdvRouteLifetime infinity;
};
};
Mac OS X clients forget default route
![[pt]](/s/countries/pt.gif) Shadow Hawkins on Thursday, 14 May 2009 15:12:46
I'm also having the same problem with Mac OS X, but my other end is an OpenBSD router.
Does it happen on both wired and wireless interface?
My problem seems to be with the wireless interface only.
Mac OS X clients forget default route
Shadow Hawkins on Friday, 15 May 2009 12:57:15
Usually I run the following commands to get things working.
Turn off and on wireless device,
ndp -n -cPR
route -n flush -inet6
rtsol <wireless_device> (en1)
It's not pretty but works.
Mac OS X clients forget default route
Shadow Hawkins on Sunday, 14 March 2010 00:27:25
And then your route is remembered infinitely long? That didn't work for me.
Mac OS X clients forget default route
![[fi]](/s/countries/fi.gif) Shadow Hawkins on Saturday, 27 June 2009 10:38:48
I've had the same issue on my AppleTV.
What I'm now trying is to manually install a more specific route into the tunnel than the default, i.e., to 2000::/3, which still matches all the currently routable IPv6 space:
route add -inet6 2000:: -prefixlen 3 -iface tun0
Mac OS X clients forget default route
Shadow Hawkins on Sunday, 02 August 2009 16:57:18
That's what I do as a workaround, too, see original post.
Mac OS X clients forget default route
![[br]](/s/countries/br.gif) Shadow Hawkins on Monday, 27 July 2009 16:17:45
Do not use the auto-configuration of Mac OS. Use manual configuration that will work out, but if you disconnect, perhaps a warning could appear in use IPv6, just give one:
ifconfig en0 down
ifconfig en0 up
That will connect and work.
Mac OS X clients forget default route
Shadow Hawkins on Sunday, 14 March 2010 00:26:49
Not at all.
Mac OS X clients forget default route
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 30 March 2010 16:31:07
I've have no trouble with OSX (10.5.x, 10.6.x) and IPv6. I'm not doing radvd on my WRT54G right now, but I have. My working radvd (on CentOS) works fine with as simple a radvd.conf as this:
interface eth1
{
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
prefix 2001:db8:1:0::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};
Below: the router's radvd.conf - as you see, I tried to set lifetime for that route to infinity, but that doesn't help.
interface eth0.0
{
AdvSendAdvert on;
...
prefix 2A01:198:300::/64
{
...};
...};
interface wlan0
{
AdvSendAdvert on;
...
prefix 2A01:198:300:FADE::/64
{
...};
...
};
The interfaces you are using for the router are different than my OpenWRT experiences. Also, is your wireless indeed broken into a separate segment from your Ethernet ports, as you have the router configed?
What's your OpenWRT /etc/config/network look like? Is eth0.0 part of the br_lan bridge interface or did you do something to break it out?
How about your /etc/config/wireless? What 'option network' is your wifi interface (wlan0/wl0/etc.) in?
At the OpenWRT command prompt, what do you get from a 'ifconfig'? What intefaces have the IPv4 addresses? Did you likewise manually assign those interfaces IPv6 addresses for your appropriate subnet ranges?
What do you see if, on your LAN devices, you enter a 'rdisc6 [interface]'? (On Linux, you might need to 'apt-get/yum install ndisc6'; on OSX with MacPorts, you might need 'ports install ndisc6'.)
|
Posting is only allowed when you are