--On Saturday, November 09, 2002 01:47:23 AM +0100 Hans Rakers
<hans@xxxxxxxx> wrote:
> Thanks for your reply. Some clarification: not the whole /48 is
> active yet. We were assigned a /48 but only a /64 is active atm.
> The gateway ip is up and running on the ISP's Juniper m20. I've
> checked this using the traceroute6 tool on www.ipng.nl
>
> Still unreachable by my test hosts though. I was told by my ISP
> that the only things necessary was a 'ifconfig eth0 add
> 2001:xxx:1290:something/64' and 'route -A inet add default gw
> 2001:xxx:1290::1 dev eth0' as pointed out in my first posting.
Hmm, try
route -A inet add 2000::/3 gw 2001:xxx:1290::1 dev eth0
instead of using "default" (which is sure not working on current
vanilla Linux kernels)
> I've
> also tried a vanilla 2.4.19 kernel this afternoon to no avail.
>
> Could it be the switch (3Com 3300XM) not handling or forwarding
> multicasts properly, since there is no reply to the neighbor
> solicitation?
Normally a non multicast capable switch should use broadcast instead.
A good thing (in case of that this switch is not able to mirror a
full duplex port) is to take a "very cheap sure not switching" hub
from networker's "first-aid supplies", place them inbetween the link
switch<->ISP, start sniffing on the 3rd port of that hub and see
what's really happen here.
Peter
---
Dr. Peter Bieringer
mailto: pb at bieringer dot de
http://www.bieringer.de/pb/
Key 0x958F422D : B501 24F4 9418 23E2 C0F3 F833 7B57 AA7B 958F 422DAttachment:
pgpxKCtO7FaKn.pgp
Description: PGP signature