NetBSD, packets don't make it to the tunnel interface?
Shadow Hawkins on Monday, 21 February 2005 04:04:03
hi,
i have setup my tunnel by hand according to the faq. that is, the gif0 interface is setup:
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet <my IPv4> --> <PoP IPv4>
[...]
inet6 <my IPv6> -> <PoP IPv6> prefixlen 128
routing is setup:
default <PoP IPv6> UGS 1 262 - gif0
<PoP IPv6> <my IPv6> UH 1 156 - gif0
<my IPv6> link#8 UHL 1 20 - lo0
everything is working quite well. i can tcpdump the ipv4 interface and see incoming and outgoing packets:
03:53:53.383420 PPPoE [ses 0x7c1] IP 78: <my IPv4> > <PoP IPv4>: <my IPv6> > <PoP IPv6>: icmp6: echo request
03:53:53.463294 PPPoE [ses 0x7c1] IP 78: <PoP IPv4> > <my IPv4>: <PoP IPv6> > <my IPv6>: icmp6: echo reply (DF)
that's a ping to the ipv6 tunnel endpoint.
_however_, the reply does not appear on the gif0 interface. in fact, nothing seems to be arriving on gif0.
something special about my setup is the use of two wan interfaces. one has the default route, the other has an ipf rule:
pass out quick on pppoe0 to pppoe1 from <my IPv4> to any
anyway, i have confirmed through log statements on all blocking rules on the ipv4 side (the ipv6 side of ipf is default allow) that nothing relevant to the tunnel is blocked (hopefully).
is there any other thing that could prevent the packets - that _are_ arriving on the ipv4 interface - from getting to the ipv6 interface?
thanks
ND
NetBSD, packets don't make it to the tunnel interface?
Jeroen Massar on Monday, 21 February 2005 11:13:07
You don't have to hide your IPv6/IPv4 addresses, everybody can find those out based on your nic handle and whois anyway and it sure makes the above completely useless as you have stripped way to much information, thus one can't verify if you really configured it correctly.
Next to that, are you maybe blocking proto-41? Try running it without a firewall.
The other thing to try is... tcpdump ;)
Posting is only allowed when you are logged in. |