Re: dhcpcd / IPv6 question
On Wed, 8 Apr 2015, Niels Dettenbach (Syndicat IT & Internet) wrote: Am 8. April 2015 14:40:14 MESZ, schrieb Greg Troxel : I have tunnels from sixxs, and aside from occasional POP issues they have been pretty reliable. With SIXX i have (sorry) very bad experiences - mainly regarding their support (just silence or no help in regaining an access to a misconfigured tunnel on SIXX side, inflexibility to just ignorance...) and partly their register policies. I wouldn't recommend it for applications require any kind of "reliability", but may OK for playing around with IPv6, where bandwidth and reliability are secondly or tertiary... I think I understand - I filled out the sign-up form, and about four hours later I received a "rejection" notice. The reason given was (paraphrased) "give us complete details or don't bother to apply." Rather rude, even making allowances for their being from a different culture... I've tried to resubmit my info to SixXS but I don't have much hope. HEnet isn't really viable since I'm not only at a dynamic IP, but also behind a NAT box. So I'd really need someone running aiccu/ayiya to handle the tunnels (at least, this is what I understand). A worst-case possibility is for me to set up my own OpenVPN tunnel back to a virtual machine I've got running in California. But I suspect that round-trip delays would make it nearly unuseable. - | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com| | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net | | Kernel Developer | | pgoyette at netbsd.org | -
Re: dhcpcd / IPv6 question
Am 8. April 2015 14:40:14 MESZ, schrieb Greg Troxel : >I have tunnels from >sixxs, and aside from occasional POP issues they have been pretty >reliable. With SIXX i have (sorry) very bad experiences - mainly regarding their support (just silence or no help in regaining an access to a misconfigured tunnel on SIXX side, inflexibility to just ignorance...) and partly their register policies. I wouldn't recommend it for applications require any kind of "reliability", but may OK for playing around with IPv6, where bandwidth and reliability are secondly or tertiary... I'm in the luck of having an access provider (VDSL) now who offers IPv6 natively within their products over a dual stack by default - so the user can decide what IP to use for what in his network. Before i've runned my own IPv6 tunnels over some of our noc locations with dual stack uplink. If you have similiar options (or i.e. some access to a machine/system on an IPv6), i would recommend to prefer them too over SIXX. Not at least - if you want to prevent third party snooping of your traffic activities by i.e. services or whatever - i would avoid such well known / costless "quasi anonymous" tunnel services because they are much more easy to watchover by services - with or without the help of the provider (if the tunnel services is not runned by a service directly...). And if you come not around a tunnel service, try to prefer one which is usable with any proven standard open source solutions / completely open protocol standards. just my two cents, Niels. -- Niels Dettenbach Syndicat IT & Internet http://www.syndicat.com
Re: dhcpcd / IPv6 question
Paul Goyette writes: > OK, then off to plan B - let's see if I can get a tunnel broker to > work with my dynamic IP address. (Fixed/Static IP not available here > in the Philippines for residential service, as far as I can tell.) > (If that doesn't work, I'll just disable IPv6...) > > Anyone got suggestions for a simple tunnel set-up? Two tunnel providers that come to mind are he.net (which I hear good things about but have not used) and sixxs.net. I have tunnels from sixxs, and aside from occasional POP issues they have been pretty reliable. One can have a tunnel with a dynamic address and use tunnel setup protocol to establish it; I have one like this for my notebook, for when I'm on networks without v6. There is net/aiccu in pkgsrc that does the client half of this. pgp4As0ISuQOs.pgp Description: PGP signature
Re: dhcpcd / IPv6 question
In article <20150408010854.536a9115...@xen1.duzan.org>, Gary Duzan wrote: >In Message , > Paul Goyette wrote: > >=>I'm finally getting my NetBSD environment reestablished, and am running >=>into a little problem. I started dhcpcd from /etc/rc.d without any >=>special options, and this is what I get in /var/run/rc.log >=> >=>... >=>[running /etc/rc.d/dhcpcd] >=>Starting dhcpcd. >=>DUID 00:01:00:01:1c:b2:4c:b2:78:24:af:3d:64:10 >=>re0: IAID af:3d:64:10 >=>re0: rebinding lease of 192.168.1.7 >=>re0: soliciting an IPv6 router >=>re0: Router Advertisement from fe80::1a1e:78ff:fe97:11ad >=>re0: requesting DHCPv6 information >=>re0: leased 192.168.1.7 for 86400 seconds >=>re0: adding route to 192.168.1.0/24 >=>re0: adding default route via 192.168.1.1 >=>forked to background, child pid 412 >=>... >=> >=>It appears that I got a RouterAdvert from somewhere, but never got any >=>IPv6 routing information. My IPv6 route table looks like this: Try using dhcpcd... christos
Re: dhcpcd / IPv6 question
In Message , Paul Goyette wrote: =>OK, then off to plan B - let's see if I can get a tunnel broker to work =>with my dynamic IP address. (Fixed/Static IP not available here in the =>Philippines for residential service, as far as I can tell.) (If that =>doesn't work, I'll just disable IPv6...) => =>Anyone got suggestions for a simple tunnel set-up? With tunnelbroker.net (Hurricane Electric, which has PoPs in Hong Kong and Singapore) I use the following /etc/ifconfig.gif0 file: create tunnel a.b.c.d w.x.y.z inet6 2001:feed:dead:beef::2 2001:feed:dead:beef::1 prefixlen 128 !route add -inet6 default ::1 !route change -inet6 default -ifp $int where a.b.c.d is your local IPv4 address, w.x.y.z is the tunnel endpoint IPv4 address, 2001:feed:dead:beef::2 is your local IPv6 address, and 2001:feed:dead:beef::1 is the IPv6 address of the other end of the tunnel. Gary Duzan
Re: dhcpcd / IPv6 question
On Tue, 7 Apr 2015, Gary Duzan wrote: =>I have no idea where the 2001:... and 2002:...entries came from... Those are standard routes; I have those, too. OK, then I won't worry about them! =>Any clue on how to get a valid IPv6 default route? I don't think you have a real IPv6 address yet. "ifconfig re0" will most likely show a fe80::7a24:afff:fe3d:6410%re0 link local address, which is generated from your MAC, but nothing else. It looks like your router is IPv6 capable, but isn't actually providing IPv6 service. Ah, that makes sense. I do indeed have the link-local address as you surmised. OK, then off to plan B - let's see if I can get a tunnel broker to work with my dynamic IP address. (Fixed/Static IP not available here in the Philippines for residential service, as far as I can tell.) (If that doesn't work, I'll just disable IPv6...) Anyone got suggestions for a simple tunnel set-up? - | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com| | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net | | Kernel Developer | | pgoyette at netbsd.org | -
Re: dhcpcd / IPv6 question
In Message , Paul Goyette wrote: =>I'm finally getting my NetBSD environment reestablished, and am running =>into a little problem. I started dhcpcd from /etc/rc.d without any =>special options, and this is what I get in /var/run/rc.log => =>... =>[running /etc/rc.d/dhcpcd] =>Starting dhcpcd. =>DUID 00:01:00:01:1c:b2:4c:b2:78:24:af:3d:64:10 =>re0: IAID af:3d:64:10 =>re0: rebinding lease of 192.168.1.7 =>re0: soliciting an IPv6 router =>re0: Router Advertisement from fe80::1a1e:78ff:fe97:11ad =>re0: requesting DHCPv6 information =>re0: leased 192.168.1.7 for 86400 seconds =>re0: adding route to 192.168.1.0/24 =>re0: adding default route via 192.168.1.1 =>forked to background, child pid 412 =>... => =>It appears that I got a RouterAdvert from somewhere, but never got any =>IPv6 routing information. My IPv6 route table looks like this: => => =>Destination Gateway Flags Refs UseMtu =>Interface =>::/104::1 UGRS - - 33648 lo0 =>::/96 ::1 UGRS - - 33648 lo0 =>::1 ::1 UH - - 33648 lo0 =>::127.0.0.0/104 ::1 UGRS - - 33648 lo0 =>::224.0.0.0/100 ::1 UGRS - - 33648 lo0 =>::255.0.0.0/104 ::1 UGRS - - 33648 lo0 =>:::0.0.0.0/96 ::1 UGRS - - 33648 lo0 =>2001:db8::/32 ::1 UGRS - - 33648 lo0 =>2002::/24 ::1 UGRS - - 33648 lo0 =>2002:7f00::/24::1 UGRS - - 33648 lo0 =>2002:e000::/20::1 UGRS - - 33648 lo0 =>2002:ff00::/24::1 UGRS - - 33648 lo0 =>fe80::/10 ::1 UGRS - - 33648 lo0 =>fe80::%re0/64 link#1UC - - - re0 =>fe80::7a24:afff:fe3d:6410 78:24:af:3d:64:10 UHLl - - - lo0 =>fe80::%lo0/64 fe80::1 U- - - lo0 =>fe80::1 fe80::1 UHl - - - lo0 =>ff01:1::/32 link#1UC - - - re0 =>ff01:2::/32 ::1 UC - - 33648 lo0 =>ff02::%re0/32 link#1UC - - - re0 =>ff02::%lo0/32 ::1 UC - - 33648 lo0 => => =>I have no idea where the 2001:... and 2002:...entries came from... Those are standard routes; I have those, too. =>Any clue on how to get a valid IPv6 default route? I don't think you have a real IPv6 address yet. "ifconfig re0" will most likely show a fe80::7a24:afff:fe3d:6410%re0 link local address, which is generated from your MAC, but nothing else. It looks like your router is IPv6 capable, but isn't actually providing IPv6 service. Gary Duzan
dhcpcd / IPv6 question
I'm finally getting my NetBSD environment reestablished, and am running into a little problem. I started dhcpcd from /etc/rc.d without any special options, and this is what I get in /var/run/rc.log ... [running /etc/rc.d/dhcpcd] Starting dhcpcd. DUID 00:01:00:01:1c:b2:4c:b2:78:24:af:3d:64:10 re0: IAID af:3d:64:10 re0: rebinding lease of 192.168.1.7 re0: soliciting an IPv6 router re0: Router Advertisement from fe80::1a1e:78ff:fe97:11ad re0: requesting DHCPv6 information re0: leased 192.168.1.7 for 86400 seconds re0: adding route to 192.168.1.0/24 re0: adding default route via 192.168.1.1 forked to background, child pid 412 ... It appears that I got a RouterAdvert from somewhere, but never got any IPv6 routing information. My IPv6 route table looks like this: Destination Gateway Flags Refs UseMtu Interface ::/104::1 UGRS - - 33648 lo0 ::/96 ::1 UGRS - - 33648 lo0 ::1 ::1 UH - - 33648 lo0 ::127.0.0.0/104 ::1 UGRS - - 33648 lo0 ::224.0.0.0/100 ::1 UGRS - - 33648 lo0 ::255.0.0.0/104 ::1 UGRS - - 33648 lo0 :::0.0.0.0/96 ::1 UGRS - - 33648 lo0 2001:db8::/32 ::1 UGRS - - 33648 lo0 2002::/24 ::1 UGRS - - 33648 lo0 2002:7f00::/24::1 UGRS - - 33648 lo0 2002:e000::/20::1 UGRS - - 33648 lo0 2002:ff00::/24::1 UGRS - - 33648 lo0 fe80::/10 ::1 UGRS - - 33648 lo0 fe80::%re0/64 link#1UC - - - re0 fe80::7a24:afff:fe3d:6410 78:24:af:3d:64:10 UHLl - - - lo0 fe80::%lo0/64 fe80::1 U- - - lo0 fe80::1 fe80::1 UHl - - - lo0 ff01:1::/32 link#1UC - - - re0 ff01:2::/32 ::1 UC - - 33648 lo0 ff02::%re0/32 link#1UC - - - re0 ff02::%lo0/32 ::1 UC - - 33648 lo0 I have no idea where the 2001:... and 2002:...entries came from... Any clue on how to get a valid IPv6 default route? - | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com| | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net | | Kernel Developer | | pgoyette at netbsd.org | -
