Am Dienstag, 13. Februar 2007 00:49 schrieb Thorsten Glaser: > Hi, > > I've - finally - got my Asus WL-500g to run with trunk and do > network on LAN and WAN interfaces, now I have the following problem: > > BSD router w/ inet connection > [fxp0] > > > switch--------[WAN]asus > > | [LAN] > > [ne1] | > laptop[ne0]----------+ > > The interfaces are configured as follows: > > Normal in-house LAN: > fxp0 = 192.168.0.82/24 > ne1 = 192.168.0.224/24 (DHCP) > WAN = 192.168.0.221/24 (DHCP) > > Crossover between laptop and asus: > ne0 = 192.168.1.2/24 (static) > LAN = 192.168.1.1/24 (static) > > The BSD router also runs rtadvd on fxp0 for IPv6. > > Now, after coming up, I have the following state: > > 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 > link/ether 00:11:d8:18:b9:08 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.1/24 scope global eth0 > inet6 fe80::211:d8ff:fe18:b908/64 scope link > 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 > link/ether 00:11:d8:18:b9:08 brd ff:ff:ff:ff:ff:ff > inet 192.168.0.221/24 scope global eth1 > > As we can see, eth0 (LAN) has a link-local address, eth1 doesn't. > > Now, the problem is: > > [EMAIL PROTECTED]:/var/www/htdocs/tmp $ ping6 ff02::1%ne0 > PING6(56=40+8+8 bytes) fe80::280:c8ff:febc:9a16%ne0 --> ff02::1%ne0 > 16 bytes from fe80::280:c8ff:febc:9a16%ne0, icmp_seq=0 hlim=64 time=0.499 > ms 16 bytes from fe80::280:c8ff:febc:9a16%ne0, icmp_seq=1 hlim=64 time=0.36 > ms 16 bytes from fe80::280:c8ff:febc:9a16%ne0, icmp_seq=2 hlim=64 > time=0.359 ms […] > > This may be expected if LAN doesn't have a link-local > address, but… > > [EMAIL PROTECTED]:/var/www/htdocs/tmp $ ping6 ff02::1%ne1 > PING6(56=40+8+8 bytes) fe80::250:baff:fe82:b6b4%ne1 --> ff02::1%ne1 > 16 bytes from fe80::250:baff:fe82:b6b4%ne1, icmp_seq=0 hlim=64 time=0.526 > ms 16 bytes from fe80::202:b3ff:feb7:54e8%ne1, icmp_seq=0 hlim=64 > time=4.393 ms(DUP!) 16 bytes from fe80::250:baff:fe82:b6b4%ne1, icmp_seq=1 > hlim=64 time=0.46 ms 16 bytes from fe80::202:b3ff:feb7:54e8%ne1, icmp_seq=1 > hlim=64 time=4.191 ms(DUP!) 16 bytes from fe80::250:baff:fe82:b6b4%ne1, > icmp_seq=2 hlim=64 time=0.401 ms 16 bytes from > fe80::202:b3ff:feb7:54e8%ne1, icmp_seq=2 hlim=64 time=4.164 ms(DUP!) […] > > … it not answering on the WAN iface with its link-local > address is not expected; as per IPv6 spec I have to > receive replies from fe80::211:d8ff:fe18:b908%ne1 on > my laptop. (ping6ing ff02::1%fxp0 from the router does > not yield a different result, FWIW.) > > [EMAIL PROTECTED]:~ $ grep -v -e '^$' -e '^#' /etc/network/interfaces > auto lo > iface lo inet loopback > auto eth0 > iface eth0 inet static > address 192.168.1.1 > netmask 255.255.255.0 > > auto eth1 > iface eth1 inet dhcp > > Maybe this helps. Could anyone enlighten me if there's > something in /proc which I must enable so that it does > join the ff02::1 multicast group, or what?
mine works as expected: # ping6 ff02::1 PING ff02::1 (ff02::1): 56 data bytes 64 bytes from fe80::217:31ff:fed6:9031%eth2: icmp_seq=0 ttl=64 time=1.030 ms --- ff02::1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 1.030/1.030/1.030/0.000 ms so it replys to ff02::1 (meaning all "nodes"). my ipv6 router (linux debian box) doesn't reply to this, but it replys to ff02::2 (all routers): # ping6 ff02::2 PING ff02::2 (ff02::2): 56 data bytes 64 bytes from fe80::20a:5eff:fe1e:c321%eth2: icmp_seq=0 ttl=64 time=164.890 ms --- ff02::2 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 164.890/164.890/164.890/0.000 ms but your network setup look strange. on my asus wl500gP my lan interface is called eth0.0 (switch ports 1-5) and my wan is called eth0.1 (switch ports 0 & 5). I am not sure what the layout on a wl500g is, but are sure eth0 and eth1 is ok? on asus wl500gP the eth1 also exists but isn't useable at all. do you have ipv6_forward enabled? if so, I guess it just answers to ff02::2, because then it's a router :) hope this helps :) --Ralph > bye, > //mirabile _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
