> Try "route delete -inet6 default gw ::1" to remove them.
Nope.
> man route :)
But:
"route flush -inet6" will wipe all of my IPv6 default gateways (even if the
command doesn't actually return, which of course led to very unpleasant worries
over here).
> As I mentioned, dump fxp0 as now you don't see which source/dest IPv4
> you are using and neither are you seeing any ICMP (v4) proto-41
> unreaches if the remote side actually doesn't like you.
I'm getting *nothing* at all on this interface, and nothing on xl0, my local LAN
interface, either. No ICMPv4 unreachables, nothing. Of course, I had to use this
command line:
sudo tcpdump -n -i fxp0 not port 22 and not port 25 and not port 80 and not port
53 and not port 443
to weed out all of the other traffic on this interface (it's a moderately busy
server), so I could be missing something...but I doubt it, since ICMP messages
typically aren't associated with any of those ports.
What was interesting on gif0, though, was:
12:00:04.686105 2001:5c0:8fff:fffe::28f5 > 2001:200:0:8002:203:47ff:fea5:3085:
icmp6: echo request
12:00:05.686089 2001:5c0:8fff:fffe::28f5 > 2001:200:0:8002:203:47ff:fea5:3085:
icmp6: echo request
12:00:06.006099 2001:5c0:8fff:fffe::28f5 > 2001:5c0:8fff:fffe::28f4: icmp6: echo
request
12:00:06.686098 2001:5c0:8fff:fffe::28f5 > 2001:200:0:8002:203:47ff:fea5:3085:
icmp6: echo request
I'm not sure why the machine suddenly decided to ping itself...but considering
that I can't ping 2001:5c0:8fff:fffe::28f4, I suppose that may be part of the
problem.
> How exactly did your routing table look like after you did exactly what?
Here, just for reference:
schnarff.com:~$ route -n show -inet6
Routing tables
Internet6:
Destination Gateway Flags
default 2001:5c0:8fff:fffe::28f4 UG
2000:: 2001:5c0:8fff:fffe::28f4 UG
2001:: 2001:5c0:8fff:fffe::28f4 UG
2001:5c0:8fff:fffe::28f4 2001:5c0:8fff:fffe::28f5 UH
2001:5c0:8fff:fffe::28f5 link#7 UH
2002:: ::1 UG
2002:7f00:: ::1 UG
2002:e000:: ::1 UG
2002:ff00:: ::1 UG
fe80:: ::1 UG
fe80::%xl0 link#1 U
fe80::210:4bff:fecc:1f2e%xl0 0:10:4b:cc:1f:2e UH
fe80::%fxp0 link#2 U
fe80::207:e9ff:fe82:984c%fxp0 0:7:e9:82:98:4c UH
fe80::%lo0 fe80::1%lo0 U
fe80::1%lo0 link#5 UH
fe80::%gif0 link#7 U
fe80::210:4bff:fecc:1f2e%gif0 link#7 UH
fec0:: ::1 UG
ff01:: ::1 U
ff02::%xl0 link#1 U
ff02::%fxp0 link#2 U
ff02::%lo0 ::1 U
ff02::%gif0 link#7 U
schnarff.com:~$ ifconfig -a
lo0: flags=8149<UP,LOOPBACK,RUNNING,PROMISC,MULTICAST> mtu 33224
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:10:4b:cc:1f:2e
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 192.168.2.69 netmask 0xffffff00 broadcast 192.168.2.255
inet6 fe80::210:4bff:fecc:1f2e%xl0 prefixlen 64 scopeid 0x1
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:07:e9:82:98:4c
media: Ethernet autoselect (10baseT)
status: active
inet6 fe80::207:e9ff:fe82:984c%fxp0 prefixlen 64 scopeid 0x2
inet 66.92.172.3 netmask 0xffffff00 broadcast 66.92.172.255
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33224
pfsync0: flags=0<> mtu 2020
enc0: flags=0<> mtu 1536
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
physical address inet 66.92.172.3 --> 206.123.31.116
inet6 fe80::210:4bff:fecc:1f2e%gif0 -> prefixlen 64 scopeid 0x7
inet6 2001:5c0:8fff:fffe::28f5 -> 2001:5c0:8fff:fffe::28f4 prefixlen 128
tentative
> TSP client should do it already for you.
> For the rest: google(openbsd rc.conf ipv6) eg
> http://schvin.net/writings/openbsd-ipv6.html
> http://www.fbunet.de/ipv6.shtml
I tried setting net.inet6.ip6.accept_rtadv=1 as per the first of these two and
then re-running tspc, with no luck. Something screwy is definitely going on
here. Perhaps it's that fxp0 (my external interface) only has a 127.0.0.0/8
style IPv6 address, and that gif0 has one of these addresses before its other
IPv6 address?
I think if nothing else, it'd be nice to have docs that explained WTF each of
the steps necessary to get up and running on IPv6 is supposed to actually be
doing, so that if something goes wrong, one can intelligently troubleshoot,
instead of just sit around speculating and asking dumb questions.
Alex Kirk
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
