SixXS::Sunset 2017-06-06

IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[de] Shadow Hawkins on Monday, 01 December 2003 18:42:46
Hi all, i tried to get a IPv6 tunnel to work on my OpenBSD 3.3 router. After having some difficulties compiling the heartbeat client I followed the instructions but it does not work. Executing "/usr/local/bin/heartbeat-client /etc/heartbeat.conf" gives me: IP address change to 217.82.76.90 detected, reconfiguring ifconfig: SIOCGIFFLAGS: Device not configured [HB] HEARTBEAT TUNNEL 2001:6f8:900:8c::2 217.82.76.90 1070299285 xxx (and so on) I guess it complains about gif0 which is existing and previously worked with another tunnelbroker. Which interface is the right one to specify in the conf file (as ipv4_interface)? Below is a part of the ifconfig output: rl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:e0:7d:dd:0a:a2 media: Ethernet 10baseT status: active inet6 fe80::2e0:7dff:fedd:aa2%rl1 prefixlen 64 scopeid 0x2 pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33224 ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 tun0: flags=8011<UP,POINTOPOINT,MULTICAST> mtu 1492 inet 217.82.76.90 --> 217.5.98.83 netmask 0xffffffff I tried all of the above interfaces, but the 'heartbeat' output is always the same with the SIOCGIFFLAGS: Device not configured error. ping6 gives me: ping6: UDP connect: No route to host traceroute6 gives me: connect: No route to host And adding a route to SixXS manually (route -n add -inet6 default 2001:6f8:900:8c::1) quits with: writing to routing socket: No such process add net default: gateway 2001:6f8:900:8c::1: not in table I hope anyone can help me on this issue. Thanks in advance, Floh
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[ch] Jeroen Massar SixXS Staff on Monday, 01 December 2003 19:10:07
The heartbeat client does work with OpenBSD, but you are just providing it the wrong configuration settings. the ipv4_interface setting should be set to the interface over which you are going creating the IPv6 tunnel, aka the interface which has your public IPv4 address assigned. The ipv6_interface should be set to the device that is going to be your tunnel, typically gif0, which you have to setup yourself, as is stated in the README and like many people before you done correctly.
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[de] Shadow Hawkins on Monday, 01 December 2003 23:45:13
Okay, I had a configuration problem with the gif0 interface. This solves the SIOCGIFFLAGS issue. But what about the routing? Setting a route manually still gives me the error above. Regards, Floh
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[ch] Jeroen Massar SixXS Staff on Tuesday, 02 December 2003 12:23:28
Maybe if you can show the outputs of ifconfig, netstat etc we can help or do you have a public root account on your machine?
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[de] Shadow Hawkins on Tuesday, 02 December 2003 15:02:26
% route -n add -inet6 default 2001:6f8:900:8c::1 writing to routing socket: No such process add net default: gateway 2001:6f8:900:8c::1: not in table %
% ifconfig -a lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 lo1: flags=8008<LOOPBACK,MULTICAST> mtu 33224 rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:e0:7d:dd:99:f3 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.0.123 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::2e0:7dff:fedd:99f3%rl0 prefixlen 64 scopeid 0x1 rl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:e0:7d:dd:0a:a2 media: Ethernet 10baseT status: active inet6 fe80::2e0:7dff:fedd:aa2%rl1 prefixlen 64 scopeid 0x2 pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33224 pfsync0: flags=0<> mtu 2020 sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296 sl1: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296 ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 ppp1: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 tun0: flags=8011<UP,POINTOPOINT,MULTICAST> mtu 1492 inet 217.224.66.174 --> 217.5.98.83 netmask 0xffffffff tun1: flags=10<POINTOPOINT> mtu 3000 enc0: flags=0<> mtu 1536 bridge0: flags=0<> mtu 1500 bridge1: flags=0<> mtu 1500 vlan0: flags=0<> mtu 1500 address: 00:00:00:00:00:00 vlan1: flags=0<> mtu 1500 address: 00:00:00:00:00:00 gre0: flags=9010<POINTOPOINT,LINK0,MULTICAST> mtu 1450 gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 gif2: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 gif3: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 %
% netstat -ra Routing tables Internet: Destination Gateway Flags Refs Use Mtu Interface default 217.5.98.83 UGS 3 258 1492 tun0 loopback localhost UGRS 0 0 33224 lo0 localhost localhost UH 2 2 33224 lo0 192.168.0/24 link#1 UC 0 0 - rl0 dominik 0:0:cb:59:1f:31 UHL 1 71 - rl0 camouflage 0:0:cb:58:5:70 UHL 1 338 - rl0 paratrooper localhost UGHS 1 4 33224 lo0 217.5.98.83 pD9E042AE.dip.t-di UH 1 0 1492 tun0 BASE-ADDRESS.MCAST localhost URS 0 0 33224 lo0 Internet6: Destination Gateway Flags Refs Use Mtu Interface ::/104 ::1 UGRS 0 0 - lo0 => ::/96 ::1 UGRS 0 0 - lo0 ::1 ::1 UH 12 22 33224 lo0 ::127.0.0.0/104 ::1 UGRS 0 0 - lo0 ::224.0.0.0/100 ::1 UGRS 0 0 - lo0 ::255.0.0.0/104 ::1 UGRS 0 0 - lo0 ::ffff:0.0.0.0/96 ::1 UGRS 0 0 - lo0 2002::/24 ::1 UGRS 0 0 - lo0 2002:7f00::/24 ::1 UGRS 0 0 - lo0 2002:e000::/20 ::1 UGRS 0 0 - lo0 2002:ff00::/24 ::1 UGRS 0 0 - lo0 fe80::/10 ::1 UGRS 0 0 - lo0 fe80::%rl0/64 link#1 UC 0 0 - rl0 fe80::2e0:7dff:fed 0:e0:7d:dd:99:f3 UHL 0 0 - lo0 fe80::%rl1/64 link#2 UC 0 0 - rl1 fe80::2e0:7dff:fed 0:e0:7d:dd:a:a2 UHL 0 0 - lo0 fe80::%lo0/64 fe80::1%lo0 U 0 0 - lo0 fe80::1%lo0 link#6 UHL 0 0 - lo0 fec0::/10 ::1 UGRS 0 0 - lo0 ff01::/32 ::1 UC 0 0 - lo0 ff02::%rl0/32 link#1 UC 0 0 - rl0 ff02::%rl1/32 link#2 UC 0 0 - rl1 ff02::%lo0/32 ::1 UC 0 0 - lo0 ff02::%tun0/32 link#11 UC 0 0 1492 tun0 Encap: Source Port Destination Port Proto SA(Address/Proto/Type/Direction) %
I don't have a public root account, so here are the ifconfig/netstat outputs.
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[ch] Jeroen Massar SixXS Staff on Tuesday, 02 December 2003 16:45:48
From heartbeat/doc/HOWTO: 8<---------- What to do: - Check your user home for the tunnel. - Configure the IPv6 in IPv4 tunnel as normal. ---------->8 Complete that step, which you have not as gif0 is still unconfigured and then procede...
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[de] Shadow Hawkins on Tuesday, 02 December 2003 19:34:22
I'm sorry, but the output above was taken while _not_ running the heartbeat client. With the hearbeat client running the following additional information appears:
% ifconfig gif0 gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 physical address inet 217.224.66.174 --> 212.224.0.188 inet6 fe80::2e0:7dff:fedd:99f3%gif0 -> prefixlen 64 scopeid 0x13 %
% netstat -ra | grep link#19 fe80::%gif0/64 link#19 UC 0 0 - gif0 fe80::2e0:7dff:fed link#19 UHL 0 0 - lo0 ff02::%gif0/32 link#19 UC 0 0 - gif0 %
The routing problem described above still appears. Regards, Floh
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[de] Shadow Hawkins on Tuesday, 02 December 2003 20:29:11
->% ifconfig gif0 ->gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 -> physical address inet 217.224.66.174 --> 212.224.0.188 -> inet6 fe80::2e0:7dff:fedd:99f3%gif0 -> prefixlen 64 scopeid 0x13 This is a half configured gif tunnel. Check your ipv6 tunnel endpoints in heartbeat.conf. Without a proper tunnel interface you can't assign a route throuht it.
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[ch] Jeroen Massar SixXS Staff on Tuesday, 02 December 2003 20:38:14
The unix version of the heartbeat client doesn't configure the tunnel at all, it does correctly configure the local and remote IPv4 endpoints of the tunnel though.
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[de] Shadow Hawkins on Tuesday, 02 December 2003 21:14:18
Which are the necessary steps to configure the tunnel? The ones described in http://www.sixxs.net/faq/connectivity/?faq=ossetup&os=openbsd ? If I got it right, this is only for tunnels with static IPv4, thus without heartbeat.
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[de] Shadow Hawkins on Tuesday, 02 December 2003 21:14:00
@ Jeroen: Never used heartbeat, just a thought that it would do it itselfs. @ Florian Just take your current external IP as <your IPv4 Endpoint> decribed in your obove posted link.
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3 [solved]
[de] Shadow Hawkins on Tuesday, 02 December 2003 21:23:41
Okay, it works now. Thank you very much, Jeroen and Veit, for your help. @Jeroen: Does the heartbeat client now the care for IPv4 changes (on my side)? Regards, Floh
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3 [solved]
[ch] Jeroen Massar SixXS Staff on Tuesday, 02 December 2003 22:43:29
@Jeroen: Does the heartbeat client now the care for IPv4 changes (on my side)?
That is the only thing that the unix version of the heartbeat client does.
IPv6 tunnel with heartbeat client won't work with OpenBSD 3.3
[de] Shadow Hawkins on Tuesday, 02 December 2003 20:44:25
@Veit: Do you mean 'ipv6_pop' with endpoints? I configured as listed in the suggested config file. To be more exactly:
ipv6_pop "2001:6f8:900:8c::1"

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker