[opensuse] ipv6 and wicked
Hi, Has anyone experience with ipv6 on Leap 42.1 ? I'm trying to setup an ipv6 router. I installed Leap without a gui. My external address is automatically configured. That's OK. Trying with yast, I found after searching and trying you only can assign a static ipv6 address by specifying it in the IP-address box. You then can add an ipv4 address. The next step is configuring the internal addess with prefix delegation, but I can't find information how the do that. I found a document for SUSE Linux Enterprise 12 GA. There I found a command /usr/lib/wicked/bin/wickedd-dhcp6 --test eth0 I didn't get any response, but I sniffed the interface and I found a valid dhcpv6 transaction, but no PD-request. /usr/lib/wicked/bin/wickedd-dhcp4 --test eth0 gave me all the information of the ipv4 lease. So how could I add the PD-request, and configure the internal interface using the result ? Any pointers ? Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/02/2016 11:15 AM, Koenraad Lelong wrote:
Has anyone experience with ipv6 on Leap 42.1 ? I'm trying to setup an ipv6 router. I installed Leap without a gui. My external address is automatically configured. That's OK. Trying with yast, I found after searching and trying you only can assign a static ipv6 address by specifying it in the IP-address box. You then can add an ipv4 address.
I did. After years of using openSUSE for my router, I gave up on it and switched to pfsense, which works well. The problem is that openSUSE does not support dhcpv6-pd, which is required for getting the local network prefix from the ISP. Wicked does not support dhcpv6-pd, so I tried the latest dhcpcd, which does. Unfortunately, after a couple of frustrating weeks, I had to give up on it. My recommendation is to go with pfsense, at least until the openSUSE developers quit putting eye candy ahead of function. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/02/2016 11:15 AM, Koenraad Lelong wrote:
Has anyone experience with ipv6 on Leap 42.1 ? I'm trying to setup an ipv6 router. I installed Leap without a gui. My external address is automatically configured. That's OK. Trying with yast, I found after searching and trying you only can assign a static ipv6 address by specifying it in the IP-address box. You then can add an ipv4 address.
I did. After years of using openSUSE for my router, I gave up on it and switched to pfsense, which works well. The problem is that openSUSE does not support dhcpv6-pd, which is required for getting the local network prefix from the ISP. Wicked does not support dhcpv6-pd, so I tried the latest dhcpcd, which does. Unfortunately, after a couple of frustrating weeks, I had to give up on it.
My recommendation is to go with pfsense, at least until the openSUSE developers quit putting eye candy ahead of function.
James, be a little reasonable - the guys writing e.g. wicked and the network support have little need for eye candy. Most of the people out there on IPv6 probably have a router supplied by the provider which happily takes of it. Needing/wanting to build your own IPv6 router with this support is a bit of a cornercase, I would say. Might also be difficult to find a suitable test environment. -- Per Jessen, Zürich (17.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/02/2016 03:13 PM, Per Jessen wrote:
James, be a little reasonable - the guys writing e.g. wicked and the network support have little need for eye candy. Most of the people out there on IPv6 probably have a router supplied by the provider which happily takes of it. Needing/wanting to build your own IPv6 router with this support is a bit of a cornercase, I would say. Might also be difficult to find a suitable test environment.
OpenSUSE works well as an IPv6 router and I used it as such for 6 years. However, ISPs are moving to dhcpv6-pd to hand out prefixes and that doesn't work with openSUSE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 02-06-16 om 21:13 schreef Per Jessen:
My recommendation is to go with pfsense, at least until the openSUSE developers quit putting eye candy ahead of function.
Just to learn about it, I might well do that.
James, be a little reasonable - the guys writing e.g. wicked and the network support have little need for eye candy. Most of the people out there on IPv6 probably have a router supplied by the provider which happily takes of it. Needing/wanting to build your own IPv6 router with this support is a bit of a cornercase, I would say. Might also be difficult to find a suitable test environment.
My dsl-modem gets a /56 prefix. Afther that I put another box, namely the suse-box. After that I have an internal network. In that situation you have to use PD when the ISP does not hand out static prefixes. IMHO not a cornercase. I used my setup to try this also with Ubuntu (14.04LTS). AFAIK it's the same problem, it does not support PD. James, I read the thread, or at least I tried to follow it, but it diverted to Voip and more. I couldn't find a conclusion. Now I know you chose pfsense. Thanks all, Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/02/2016 03:43 PM, Koenraad Lelong wrote:
James, I read the thread, or at least I tried to follow it, but it diverted to Voip and more. I couldn't find a conclusion. Now I know you chose pfsense.
I had posted a message stating I gave up and had pfsense up & running in no time. Pfsense works well. My only complaint is I haven't been able to get Wireshark running on it yet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong wrote:
Op 02-06-16 om 21:13 schreef Per Jessen:
My recommendation is to go with pfsense, at least until the openSUSE developers quit putting eye candy ahead of function.
Just to learn about it, I might well do that.
James, be a little reasonable - the guys writing e.g. wicked and the network support have little need for eye candy. Most of the people out there on IPv6 probably have a router supplied by the provider whichyo happily takes of it. Needing/wanting to build your own IPv6 router with this support is a bit of a cornercase, I would say. Might also be difficult to find a suitable test environment.
My dsl-modem gets a /56 prefix. Afther that I put another box, namely the suse-box. After that I have an internal network. In that situation you have to use PD when the ISP does not hand out static prefixes. IMHO not a cornercase.
I can only judge by the current, apparently very minor demand for such setups. Here we have sofar seen two people asking/needing this support, I don't know about the openSUSE fora, but one would think the issue would have appeared much earlier - if there was much of an issue. Of course we should support IPv6 PD, but as you say below, we (openSUSE) are not exactly behind in this aspect. I guess you and James have both volunteered to test when the supporting code becomes available. -- Per Jessen, Zürich (15.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Donnerstag, 2. Juni 2016, 22:20:57 CEST schrieb Per Jessen:
Koenraad Lelong wrote:
Op 02-06-16 om 21:13 schreef Per Jessen:
My recommendation is to go with pfsense, at least until the openSUSE developers quit putting eye candy ahead of function.
Just to learn about it, I might well do that.
James, be a little reasonable - the guys writing e.g. wicked and the network support have little need for eye candy. Most of the people out there on IPv6 probably have a router supplied by the provider whichyo happily takes of it. Needing/wanting to build your own IPv6 router with this support is a bit of a cornercase, I would say. Might also be difficult to find a suitable test environment.
My dsl-modem gets a /56 prefix. Afther that I put another box, namely the suse-box. After that I have an internal network. In that situation you have to use PD when the ISP does not hand out static prefixes. IMHO not a cornercase.
I can only judge by the current, apparently very minor demand for such setups. Here we have sofar seen two people asking/needing this support, I don't know about the openSUSE fora, but one would think the issue would have appeared much earlier - if there was much of an issue.
I am looking for a solution for IPv6 PD, too. But I must admit I was scared by thas monster mail thread over the last days, which was mostly off topic. Maybe there are more openSUSE users who felt the same and skipped that thread.
Of course we should support IPv6 PD, but as you say below, we (openSUSE) are not exactly behind in this aspect. I guess you and James have both volunteered to test when the supporting code becomes available.
When there is something to test, I will have a look, too. Herbert -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
03.06.2016 18:21, Herbert Graeber пишет:
When there is something to test, I will have a look, too.
There is dhcpcd which should support requesting delegated prefix and assigning it to another interface. You can start with testing this. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/03/2016 11:21 AM, Herbert Graeber wrote:
I am looking for a solution for IPv6 PD, too. But I must admit I was scared by thas monster mail thread over the last days, which was mostly off topic. Maybe there are more openSUSE users who felt the same and skipped that thread.
As mentioned, openSUSE doesn't yet handle dhcpv6-pd. I switched to pfsense and it works well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/03/2016 11:21 AM, Herbert Graeber wrote:
I am looking for a solution for IPv6 PD, too. But I must admit I was scared by thas monster mail thread over the last days, which was mostly off topic. Maybe there are more openSUSE users who felt the same and skipped that thread.
As mentioned, openSUSE doesn't yet handle dhcpv6-pd. I switched to pfsense and it works well.
What does pfsense use? dhcpcd? Whatever it is should work just as well on openSUSE. -- Per Jessen, Zürich (16.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/03/2016 03:39 PM, Per Jessen wrote:
James Knott wrote:
I am looking for a solution for IPv6 PD, too. But I must admit I was scared by thas monster mail thread over the last days, which was mostly off topic. Maybe there are more openSUSE users who felt the same and skipped that thread. As mentioned, openSUSE doesn't yet handle dhcpv6-pd. I switched to
On 06/03/2016 11:21 AM, Herbert Graeber wrote: pfsense and it works well. What does pfsense use? dhcpcd? Whatever it is should work just as well on openSUSE.
I installed the latest version of dpcpcd, which supports dhpcv6-pd. However, no matter what I tried, I couldn't get it to obtain the prefix. Often it wouldn't even get the IPv6 address for the WAN interface. I had wicked configured for IPv4 dhcp and dhcpcd configured for IPv6 dhcp. pfsense is build on FreeBSD, but I'm not sure what method it uses to deal with dhcpv6-pd. It just works. I downloaded it, burned the CD, installed it and had it working in under 2 hours. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/03/2016 03:49 PM, James Knott wrote:
On 06/03/2016 03:39 PM, Per Jessen wrote:
James Knott wrote:
I am looking for a solution for IPv6 PD, too. But I must admit I was scared by thas monster mail thread over the last days, which was mostly off topic. Maybe there are more openSUSE users who felt the same and skipped that thread. As mentioned, openSUSE doesn't yet handle dhcpv6-pd. I switched to
On 06/03/2016 11:21 AM, Herbert Graeber wrote: pfsense and it works well. What does pfsense use? dhcpcd? Whatever it is should work just as well on openSUSE.
I installed the latest version of dpcpcd, which supports dhpcv6-pd. However, no matter what I tried, I couldn't get it to obtain the prefix. Often it wouldn't even get the IPv6 address for the WAN interface. I had wicked configured for IPv4 dhcp and dhcpcd configured for IPv6 dhcp.
pfsense is build on FreeBSD, but I'm not sure what method it uses to deal with dhcpv6-pd. It just works. I downloaded it, burned the CD, installed it and had it working in under 2 hours.
I had no trouble getting dhcpcd to work on Leap, but my connection was
pppoe with teksavvy and handled entirely outside of the standard suse
configuration - wicked only know about the underlying network interface,
not ppp0
--
Jeremy Baker
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0
How did you get your prefix? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/03/2016 05:28 PM, James Knott wrote:
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 How did you get your prefix?
my /etc/ppp/ip-up script was as follows
echo 2 > /proc/sys/net/ipv6/conf/ppp0/accept_ra
echo 1 > /proc/sys/net/ipv6/conf/ppp0/forwarding
dhcpcd -6 --noipv4ll -t 0 ppp0 &
sleep 20
service radvd restart
--
Jeremy Baker
On 06/03/2016 05:52 PM, Jeremy Baker wrote:
On 06/03/2016 05:28 PM, James Knott wrote:
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 How did you get your prefix?
my /etc/ppp/ip-up script was as follows
echo 2 > /proc/sys/net/ipv6/conf/ppp0/accept_ra echo 1 > /proc/sys/net/ipv6/conf/ppp0/forwarding dhcpcd -6 --noipv4ll -t 0 ppp0 & sleep 20 service radvd restart
So you're not using dhcpv6-pd. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/03/2016 05:59 PM, James Knott wrote:
On 06/03/2016 05:52 PM, Jeremy Baker wrote:
On 06/03/2016 05:28 PM, James Knott wrote:
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 How did you get your prefix?
my /etc/ppp/ip-up script was as follows
echo 2 > /proc/sys/net/ipv6/conf/ppp0/accept_ra echo 1 > /proc/sys/net/ipv6/conf/ppp0/forwarding dhcpcd -6 --noipv4ll -t 0 ppp0 & sleep 20 service radvd restart
So you're not using dhcpv6-pd.
Yes I am. What makes you think I'm not?
--
Jeremy Baker
On 06/03/2016 08:01 PM, Jeremy Baker wrote:
On 06/03/2016 05:59 PM, James Knott wrote:
On 06/03/2016 05:52 PM, Jeremy Baker wrote:
On 06/03/2016 05:28 PM, James Knott wrote:
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 How did you get your prefix?
my /etc/ppp/ip-up script was as follows
echo 2 > /proc/sys/net/ipv6/conf/ppp0/accept_ra echo 1 > /proc/sys/net/ipv6/conf/ppp0/forwarding dhcpcd -6 --noipv4ll -t 0 ppp0 & sleep 20 service radvd restart
So you're not using dhcpv6-pd.
Yes I am. What makes you think I'm not?
Well, you said:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0
Implying that something else was doing it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/03/2016 09:51 PM, James Knott wrote:
On 06/03/2016 08:01 PM, Jeremy Baker wrote:
On 06/03/2016 05:59 PM, James Knott wrote:
On 06/03/2016 05:52 PM, Jeremy Baker wrote:
On 06/03/2016 05:28 PM, James Knott wrote:
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 How did you get your prefix?
my /etc/ppp/ip-up script was as follows
echo 2 > /proc/sys/net/ipv6/conf/ppp0/accept_ra echo 1 > /proc/sys/net/ipv6/conf/ppp0/forwarding dhcpcd -6 --noipv4ll -t 0 ppp0 & sleep 20 service radvd restart
So you're not using dhcpv6-pd.
Yes I am. What makes you think I'm not?
Well, you said:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 Implying that something else was doing it.
What I was attempting to imply was that I was using dhcpcd to get my
ipv6 prefix delegation, but it was happening outside of suse's
"automated" configuration. The only part of my config that was done
with yast was for the underlying ethernet interface that is connected to
my dsl modem. Since suse no longer has a dsl option in yast, even my
call to pppd to setup my adsl connection is done from a script I wrote.
--
Jeremy Baker
04.06.2016 00:52, Jeremy Baker пишет:
On 06/03/2016 05:28 PM, James Knott wrote:
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 How did you get your prefix?
my /etc/ppp/ip-up script was as follows
echo 2 > /proc/sys/net/ipv6/conf/ppp0/accept_ra echo 1 > /proc/sys/net/ipv6/conf/ppp0/forwarding dhcpcd -6 --noipv4ll -t 0 ppp0 & sleep 20 service radvd restart
What openSUSE version? Do you use radvd to redistribute prefix received by dhcpcd? Could you show config files for dhcpcd and radvd? Why do you restart radvd? Ny understanding is, it should be notified of new address on interface and automatically pick it for prefix distribution. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/04/2016 01:07 AM, Andrei Borzenkov wrote:
04.06.2016 00:52, Jeremy Baker пишет:
On 06/03/2016 05:28 PM, James Knott wrote:
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 How did you get your prefix?
my /etc/ppp/ip-up script was as follows
echo 2 > /proc/sys/net/ipv6/conf/ppp0/accept_ra echo 1 > /proc/sys/net/ipv6/conf/ppp0/forwarding dhcpcd -6 --noipv4ll -t 0 ppp0 & sleep 20 service radvd restart
What openSUSE version?
Do you use radvd to redistribute prefix received by dhcpcd? Could you show config files for dhcpcd and radvd?
Why do you restart radvd? Ny understanding is, it should be notified of new address on interface and automatically pick it for prefix distribution. My version is Leap 42.1
I am using radvd to distribute prefix to clients. I would restart it
after a brief wait because there were times when it would start before
the prefix was assigned, and it didn't appear to have the functionality
you describe above.
my dhcpcd.conf:
noipv6rs
interface ppp0
ipv6rs
ipv6only
iaid 1
ia_pd 1 int_mb/5
duid
persistent
option rapid_commit
option classless_static_routes
my radvd.conf:
interface int_mb
{
AdvSendAdvert on;
AdvManagedFlag off;
AdvOtherConfigFlag off;
prefix ::/64 {
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
}; # End of interface definition
--
Jeremy Baker
04.06.2016 16:40, Jeremy Baker пишет:
On 06/04/2016 01:07 AM, Andrei Borzenkov wrote:
04.06.2016 00:52, Jeremy Baker пишет:
On 06/03/2016 05:28 PM, James Knott wrote:
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 How did you get your prefix?
my /etc/ppp/ip-up script was as follows
echo 2 > /proc/sys/net/ipv6/conf/ppp0/accept_ra echo 1 > /proc/sys/net/ipv6/conf/ppp0/forwarding dhcpcd -6 --noipv4ll -t 0 ppp0 & sleep 20 service radvd restart
What openSUSE version?
Do you use radvd to redistribute prefix received by dhcpcd? Could you show config files for dhcpcd and radvd?
Why do you restart radvd? Ny understanding is, it should be notified of new address on interface and automatically pick it for prefix distribution.
Thanks! (Although I see now you already posted it in the other mega-thread :)
My version is Leap 42.1
I am using radvd to distribute prefix to clients. I would restart it after a brief wait because there were times when it would start before the prefix was assigned, and it didn't appear to have the functionality you describe above.
Hmm ... I rechecked sources and build log and radvd is built with netlink support so it should do it. Pity I do not have real life infrastructure for IPv6 to test.
my dhcpcd.conf:
noipv6rs interface ppp0 ipv6rs ipv6only iaid 1 ia_pd 1 int_mb/5 duid persistent option rapid_commit option classless_static_routes
my radvd.conf:
interface int_mb { AdvSendAdvert on; AdvManagedFlag off; AdvOtherConfigFlag off; prefix ::/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr on;
I wonder why you need it? Normally it is used for Mobile IPv6, for standard case it is enough to advertise prefix.
}; }; # End of interface definition
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong wrote:
Op 02-06-16 om 21:13 schreef Per Jessen:
My recommendation is to go with pfsense, at least until the openSUSE developers quit putting eye candy ahead of function.
Just to learn about it, I might well do that.
James, be a little reasonable - the guys writing e.g. wicked and the network support have little need for eye candy. Most of the people out there on IPv6 probably have a router supplied by the provider which happily takes of it. Needing/wanting to build your own IPv6 router with this support is a bit of a cornercase, I would say. Might also be difficult to find a suitable test environment.
My dsl-modem gets a /56 prefix. Afther that I put another box, namely the suse-box. After that I have an internal network. In that situation you have to use PD when the ISP does not hand out static prefixes.
Does your suse-box actually get a PD from your provider when your DSL modem is in the way? Just being curious - I guess your suse-box is a firewall which you prefer over the one in your dsl modem?
IMHO not a cornercase.
Perhaps not, but hardly mainstream either :-)
I used my setup to try this also with Ubuntu (14.04LTS). AFAIK it's the same problem, it does not support PD.
It's a very interesting topic - I guess your dsl modem runs the dhcp client which receives the PD from your provider. In a normal setup, ie. without another box in the middle, I guess the dsl modem runs radvd and that's it? I'd love to be able to explore this in depth, but I have had a static ipv6 setup for years. -- Per Jessen, Zürich (14.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/03/2016 02:41 AM, Per Jessen wrote:
IMHO not a cornercase. Perhaps not, but hardly mainstream either :-)
From https://en.wikipedia.org/wiki/Prefix_delegation "DHCPv6 Prefix Delegation is supported by most ISPs who provide native IPv6 for consumers on fixed networks."
Also, another ISP in my area, that's been providing IPv6 for a while has switched from static configuration to dhcpv6-pd, https://www.bidon.ca/fr/random/2014-01-02-teksavvy-ipv6-dhcpv6pd Comcast, a major U.S. ISP, also uses it. So, it's certainly will be mainstream, if not already. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/03/2016 02:41 AM, Per Jessen wrote:
IMHO not a cornercase. Perhaps not, but hardly mainstream either :-)
From https://en.wikipedia.org/wiki/Prefix_delegation "DHCPv6 Prefix Delegation is supported by most ISPs who provide native IPv6 for consumers on fixed networks."
Also, another ISP in my area, that's been providing IPv6 for a while has switched from static configuration to dhcpv6-pd, https://www.bidon.ca/fr/random/2014-01-02-teksavvy-ipv6-dhcpv6pd
Comcast, a major U.S. ISP, also uses it. So, it's certainly will be mainstream, if not already.
I meant running one's own ipv6 router is not mainstream, not whether PD is used by the provider. I'm sure the latter is already mainstream. -- Per Jessen, Zürich (18.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 03-06-16 om 13:49 schreef Per Jessen:
I meant running one's own ipv6 router is not mainstream, not whether PD is used by the provider. I'm sure the latter is already mainstream.
Was busy trying with pfSense ;-). Maybe the setup is not mainstream, but what's the point of getting a /56 prefix when you can't use all of the subnets ? At the moment I don't really need all the subnets, but how I'm going to use ipv6 on my internal network when at any moment my addresses can change ? Of course I could just use the network right behind the dsl-modem/router but I prefer having a linux firewall between my internal network and the wild wide web. An extra problem is my dsl-modem/router. Its firewall is too limited. Standard all inboud traffic is blocked which is OK. You can allow traffic through for a host (all or individual ports). But you can only specify the host-part of the ipv6-address. That means hosts on a different subnet are not reachable. But that's not on topic here. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong wrote:
Op 03-06-16 om 13:49 schreef Per Jessen:
I meant running one's own ipv6 router is not mainstream, not whether PD is used by the provider. I'm sure the latter is already mainstream.
Was busy trying with pfSense ;-).
Maybe the setup is not mainstream, but what's the point of getting a /56 prefix when you can't use all of the subnets ?
There is no problem in that - as long as you use a static config. I've been doing that for 6-7 years. The problem is purely in using the PD on your Linux router box, and that, I suspect, is not mainstream. (otherwise we would have heard the hordes of people by now). Btw, I think I saw someone mention a code fix already, but I can't find the reference now. Might be in github/wicked. -- Per Jessen, Zürich (19.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 03:56 AM, Per Jessen wrote:
Koenraad Lelong wrote:
Op 03-06-16 om 13:49 schreef Per Jessen:
I meant running one's own ipv6 router is not mainstream, not whether PD is used by the provider. I'm sure the latter is already mainstream.
Was busy trying with pfSense ;-).
Maybe the setup is not mainstream, but what's the point of getting a /56 prefix when you can't use all of the subnets ? There is no problem in that - as long as you use a static config. I've been doing that for 6-7 years. The problem is purely in using the PD on your Linux router box, and that, I suspect, is not mainstream. (otherwise we would have heard the hordes of people by now).
You can't use a static config, if your ISP uses dhcpv6-pd. You have to use the prefix they assign. However, dhcpv6-pd has a mechanism to tie the prefix to your hardware.
Btw, I think I saw someone mention a code fix already, but I can't find the reference now. Might be in github/wicked.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I had exactly that problem: ISP gives me a /56 but reserves the right to assign a new prefix without previous notice. Solution: I'm using a prefix from the nonroutable fc::/7 range, and i use NAT. Yes, I know, one shall not NAT IPv6, but what else can I do. Cheers MH Am 07.06.2016 um 09:37 schrieb Koenraad Lelong:
Op 03-06-16 om 13:49 schreef Per Jessen:
I meant running one's own ipv6 router is not mainstream, not whether PD is used by the provider. I'm sure the latter is already mainstream.
Was busy trying with pfSense ;-).
Maybe the setup is not mainstream, but what's the point of getting a /56 prefix when you can't use all of the subnets ? At the moment I don't really need all the subnets, but how I'm going to use ipv6 on my internal network when at any moment my addresses can change ? Of course I could just use the network right behind the dsl-modem/router but I prefer having a linux firewall between my internal network and the wild wide web.
An extra problem is my dsl-modem/router. Its firewall is too limited. Standard all inboud traffic is blocked which is OK. You can allow traffic through for a host (all or individual ports). But you can only specify the host-part of the ipv6-address. That means hosts on a different subnet are not reachable. But that's not on topic here.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Mathias Homann wrote:
I had exactly that problem:
ISP gives me a /56 but reserves the right to assign a new prefix without previous notice.
Solution: I'm using a prefix from the nonroutable fc::/7 range, and i use NAT.
Yes, I know, one shall not NAT IPv6, but what else can I do.
It looks like Jeremy Baker has got it working: https://lists.opensuse.org/opensuse/2016-06/msg00092.html He's using ppp, but surely someone can adapt his solution. -- Per Jessen, Zürich (20.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-07 09:37, Koenraad Lelong wrote:
An extra problem is my dsl-modem/router. Its firewall is too limited. Standard all inboud traffic is blocked which is OK. You can allow traffic through for a host (all or individual ports). But you can only specify the host-part of the ipv6-address. That means hosts on a different subnet are not reachable. But that's not on topic here.
You specify only the host, because the network part changes, and the router knows it. You don't. At least that is how I understand it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Op 07-06-16 om 11:56 schreef Carlos E. R.:
You specify only the host, because the network part changes, and the router knows it. You don't.
Would the router know on which prefix the host lives ? I'm going to try. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-07 12:13, Koenraad Lelong wrote:
Op 07-06-16 om 11:56 schreef Carlos E. R.:
You specify only the host, because the network part changes, and the router knows it. You don't.
Would the router know on which prefix the host lives ? I'm going to try.
The router gets the prefix from the ISP, I understand. Everything connected to the router should get that prefix. Or, everything gets a non-routable prefix instead, and the router does NAT (or something). -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Op 07-06-16 om 12:17 schreef Carlos E. R.:
The router gets the prefix from the ISP, I understand. Everything connected to the router should get that prefix.
Or, everything gets a non-routable prefix instead, and the router does NAT (or something).
I think there is a misunderstanding. I get a /56 prefix from my ISP, i.e. 256 /64 subnets. Hosts directly attached to the router get an address in some /64 subnet (say #00). There I can add another router (my linux-firewall), so its "external" interface gets an address in that first prefix (#00). The "internal" interface gets an address in another /64 subnet (via PD, some subnet other than #00)). And these internal addresses are unknown to the first router (I think, or is there some ipv6 magic ?). radvd should only emit to the internal interface, isn't it ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-07 12:38, Koenraad Lelong wrote:
Op 07-06-16 om 12:17 schreef Carlos E. R.:
The router gets the prefix from the ISP, I understand. Everything connected to the router should get that prefix.
Or, everything gets a non-routable prefix instead, and the router does NAT (or something).
I think there is a misunderstanding. I get a /56 prefix from my ISP, i.e. 256 /64 subnets. Hosts directly attached to the router get an address in some /64 subnet (say #00).
Ah! I see.
There I can add another router (my linux-firewall), so its "external" interface gets an address in that first prefix (#00). The "internal" interface gets an address in another /64 subnet (via PD, some subnet other than #00)). And these internal addresses are unknown to the first router (I think, or is there some ipv6 magic ?). radvd should only emit to the internal interface, isn't it ?
I don't know. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Koenraad Lelong wrote:
Op 07-06-16 om 12:17 schreef Carlos E. R.:
The router gets the prefix from the ISP, I understand. Everything connected to the router should get that prefix.
Or, everything gets a non-routable prefix instead, and the router does NAT (or something).
I think there is a misunderstanding. I get a /56 prefix from my ISP, i.e. 256 /64 subnets. Hosts directly attached to the router get an address in some /64 subnet (say #00).
Right. 2001:db8::
There I can add another router (my linux-firewall), so its "external" interface gets an address in that first prefix (#00).
2001:db8::2
The "internal" interface gets an address in another /64 subnet (via PD, some subnet other than #00)).
2001:db8::1:1
And these internal addresses are unknown to the first router (I think, or is there some ipv6 magic ?).
How does your internal network get a /64 network?
radvd should only emit to the internal interface, isn't it ?
radvd will use whatever interfaces it's configured for. Is it your radvd or the one of the dsl router? -- Per Jessen, Zürich (22.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 06:58 AM, Per Jessen wrote:
Koenraad Lelong wrote:
Op 07-06-16 om 12:17 schreef Carlos E. R.:
The router gets the prefix from the ISP, I understand. Everything connected to the router should get that prefix.
Or, everything gets a non-routable prefix instead, and the router does NAT (or something).
I think there is a misunderstanding. I get a /56 prefix from my ISP, i.e. 256 /64 subnets. Hosts directly attached to the router get an address in some /64 subnet (say #00). Right. 2001:db8::
There I can add another router (my linux-firewall), so its "external" interface gets an address in that first prefix (#00). 2001:db8::2
The "internal" interface gets an address in another /64 subnet (via PD, some subnet other than #00)). 2001:db8::1:1
And these internal addresses are unknown to the first router (I think, or is there some ipv6 magic ?). How does your internal network get a /64 network?
radvd should only emit to the internal interface, isn't it ?
radvd will use whatever interfaces it's configured for. Is it your radvd or the one of the dsl router?
When I was getting a /56 via 6in4 tunnel, I was able to configure openSUSE to pass a 2nd /64 to a VLAN and updated radvd accordingly to hand out the appropriate prefix. So, it's not a problem for a Linux based or commercial grade router to handle. I'm currently running pfsense and it also supports multiple local interfaces, including VLANs. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/07/2016 06:58 AM, Per Jessen wrote:
Koenraad Lelong wrote:
Op 07-06-16 om 12:17 schreef Carlos E. R.:
The router gets the prefix from the ISP, I understand. Everything connected to the router should get that prefix.
Or, everything gets a non-routable prefix instead, and the router does NAT (or something).
I think there is a misunderstanding. I get a /56 prefix from my ISP, i.e. 256 /64 subnets. Hosts directly attached to the router get an address in some /64 subnet (say #00). Right. 2001:db8::
There I can add another router (my linux-firewall), so its "external" interface gets an address in that first prefix (#00). 2001:db8::2
The "internal" interface gets an address in another /64 subnet (via PD, some subnet other than #00)). 2001:db8::1:1
And these internal addresses are unknown to the first router (I think, or is there some ipv6 magic ?). How does your internal network get a /64 network?
radvd should only emit to the internal interface, isn't it ?
radvd will use whatever interfaces it's configured for. Is it your radvd or the one of the dsl router?
When I was getting a /56 via 6in4 tunnel, I was able to configure openSUSE to pass a 2nd /64 to a VLAN and updated radvd accordingly to hand out the appropriate prefix. So, it's not a problem for a Linux based or commercial grade router to handle. I'm currently running pfsense and it also supports multiple local interfaces, including VLANs.
This doesn't sound overly relevant when you weren't using DHCPv6-PD with your tunnel? -- Per Jessen, Zürich (22.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 07:20 AM, Per Jessen wrote:
When I was getting a /56 via 6in4 tunnel, I was able to configure
openSUSE to pass a 2nd /64 to a VLAN and updated radvd accordingly to hand out the appropriate prefix. So, it's not a problem for a Linux based or commercial grade router to handle. I'm currently running pfsense and it also supports multiple local interfaces, including VLANs. This doesn't sound overly relevant when you weren't using DHCPv6-PD with your tunnel?
I was referring to splitting up a /56, which is what the quoted part was about. However you get a /56, it has to be spit up to be useful. In the most basic setup, the 1st /64 is used and the others are not. In this context, how I get the /56 is irrelevant. If when my ISP gets around to providing bigger prefixes than a /64, I will again be able split that prefix. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 06:38 AM, Koenraad Lelong wrote:
Op 07-06-16 om 12:17 schreef Carlos E. R.:
The router gets the prefix from the ISP, I understand. Everything connected to the router should get that prefix.
Or, everything gets a non-routable prefix instead, and the router does NAT (or something).
I think there is a misunderstanding. I get a /56 prefix from my ISP, i.e. 256 /64 subnets. Hosts directly attached to the router get an address in some /64 subnet (say #00). There I can add another router (my linux-firewall), so its "external" interface gets an address in that first prefix (#00). The "internal" interface gets an address in another /64 subnet (via PD, some subnet other than #00)). And these internal addresses are unknown to the first router (I think, or is there some ipv6 magic ?). radvd should only emit to the internal interface, isn't it ?
You'd have to involve the 1st router in splitting the /56. It's easy enough to do with a proper router, such as one created with Linux or commercial routers from Cisco etc.. However, consumer grade routers are not likely to be able to do that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 07-06-16 om 12:38 schreef Koenraad Lelong: ...
interface gets an address in another /64 subnet (via PD, some subnet other than #00)). And these internal addresses are unknown to the first router (I think, or is there some ipv6 magic ?). radvd should only emit to the internal interface, isn't it ?
Got a response from AVM (my modem/router is a Fritzbox 7490). It seems I have to announce routes also on the "WAN" side of my linux-router (so "internal" side of the modem/router). Will test when I can. Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 09:51 AM, Koenraad Lelong wrote:
Got a response from AVM (my modem/router is a Fritzbox 7490). It seems I have to announce routes also on the "WAN" side of my linux-router (so "internal" side of the modem/router).
How are you supposed to announce routes? That's normally done with a routing protocol, such as OSPF, RIP etc.. Linux supports a few methods. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/07/2016 09:51 AM, Koenraad Lelong wrote:
Got a response from AVM (my modem/router is a Fritzbox 7490). It seems I have to announce routes also on the "WAN" side of my linux-router (so "internal" side of the modem/router).
How are you supposed to announce routes? That's normally done with a routing protocol, such as OSPF, RIP etc.. Linux supports a few methods.
Probably with radvd. -- Per Jessen, Zürich (21.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 12:24 PM, Per Jessen wrote:
How are you supposed to announce routes? That's normally done with a
routing protocol, such as OSPF, RIP etc.. Linux supports a few methods. Probably with radvd.
Radvd announces the prefix to the local LAN, not back to the ISP. It's routing protocols that announce local networks to the rest of the Internet. However, I have absolutely no idea why it should be necessary when something like dhcpv6-pd is used, as the ISP should know what it handed out. If this were a business network, where a company arranges for it's own prefix, they would configure the router with their prefix. The local LAN would get the prefix via radvd and a routing protocol would make that prefix known to the rest of the world. IPv4 has worked this way for many years and it doesn't change with IPv6. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/07/2016 12:24 PM, Per Jessen wrote:
How are you supposed to announce routes? That's normally done with a
routing protocol, such as OSPF, RIP etc.. Linux supports a few methods. Probably with radvd.
Radvd announces the prefix to the local LAN, not back to the ISP.
Nobody is talking about announcing anything "back" - Koenraad said :
Got a response from AVM (my modem/router is a Fritzbox 7490). It seems I have to announce routes also on the "WAN" side of my linux-router (so "internal" side of the modem/router). ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-- Per Jessen, Zürich (22.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 01:35 PM, Per Jessen wrote:
James Knott wrote:
On 06/07/2016 12:24 PM, Per Jessen wrote:
How are you supposed to announce routes? That's normally done with a
routing protocol, such as OSPF, RIP etc.. Linux supports a few methods. Probably with radvd. Radvd announces the prefix to the local LAN, not back to the ISP. Nobody is talking about announcing anything "back" - Koenraad said :
Got a response from AVM (my modem/router is a Fritzbox 7490). It seems I have to announce routes also on the "WAN" side of my linux-router (so "internal" side of the modem/router). ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ummm... He was talking about announcing back to the WAN. That means back to the ISP. I don't know how you read it otherwise. Regardless, his setup doesn't make sense for more than one reason.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/07/2016 01:35 PM, Per Jessen wrote:
James Knott wrote:
On 06/07/2016 12:24 PM, Per Jessen wrote:
How are you supposed to announce routes? That's normally done with a
routing protocol, such as OSPF, RIP etc.. Linux supports a few methods. Probably with radvd. Radvd announces the prefix to the local LAN, not back to the ISP. Nobody is talking about announcing anything "back" - Koenraad said :
Got a response from AVM (my modem/router is a Fritzbox 7490). It seems I have to announce routes also ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ummm...
He was talking about announcing back to the WAN. That means back to the ISP. I don't know how you read it otherwise.
Umm..., I just read his prose.
on the "WAN" side of my linux-router (so "internal" side of the modem/router).
I don't see how I can paraphrase that to make it any clearer. -- Per Jessen, Zürich (20.3°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 03:06 PM, Per Jessen wrote:
James Knott wrote:
On 06/07/2016 01:35 PM, Per Jessen wrote:
James Knott wrote:
On 06/07/2016 12:24 PM, Per Jessen wrote:
How are you supposed to announce routes? That's normally done with a > routing protocol, such as OSPF, RIP etc.. Linux supports a few > methods. Probably with radvd. Radvd announces the prefix to the local LAN, not back to the ISP. Nobody is talking about announcing anything "back" - Koenraad said :
Got a response from AVM (my modem/router is a Fritzbox 7490). It seems I have to announce routes also ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ummm...
He was talking about announcing back to the WAN. That means back to the ISP. I don't know how you read it otherwise. Umm..., I just read his prose.
on the "WAN" side of my linux-router (so "internal" side of the modem/router). I don't see how I can paraphrase that to make it any clearer.
In this instance, there are 2 sides of a router, the LAN side and the WAN. LAN means the local network and WAN faces the ISP. He says he has to advertise to the WAN side. That means he has to send info back to the ISP. There is no other possible meaning of that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-07 20:54, James Knott wrote:
Nobody is talking about announcing anything "back" - Koenraad said :
Got a response from AVM (my modem/router is a Fritzbox 7490). It seems I have to announce routes also on the "WAN" side of my linux-router (so "internal" side of the modem/router). ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ummm...
He was talking about announcing back to the WAN. That means back to the ISP. I don't know how you read it otherwise.
WAN in this case refers to the socket labelled "WAN" in that internal router, not to the real "WAN". It connects to LAN-1 -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 06/07/2016 03:16 PM, Carlos E. R. wrote:
He was talking about announcing back to the WAN. That means back to the
ISP. I don't know how you read it otherwise. WAN in this case refers to the socket labelled "WAN" in that internal router, not to the real "WAN". It connects to LAN-1
And what does that "WAN" connect to? Unless I'm seriously mistaken, it connects to his ADSL modem, which in turn connects back to the ISP? Is there some other "WAN" in this context? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-07 21:19, James Knott wrote:
On 06/07/2016 03:16 PM, Carlos E. R. wrote:
He was talking about announcing back to the WAN. That means back to the
ISP. I don't know how you read it otherwise. WAN in this case refers to the socket labelled "WAN" in that internal router, not to the real "WAN". It connects to LAN-1
And what does that "WAN" connect to? Unless I'm seriously mistaken, it connects to his ADSL modem, which in turn connects back to the ISP? Is there some other "WAN" in this context?
The WAN of the internal router connects to the LAN of the ISP facing router. LAN-1 LAN-2 internet---Router 1------------Router 2------ ISP WAN ··· LAN WAN ··· LAN ]> In this instance, there are 2 sides of a router, the LAN side and the ]> WAN. LAN means the local network and WAN faces the ISP. He says he has ]> to advertise to the WAN side. That means he has to send info back to ]> the ISP. There is no other possible meaning of that. The WAN of router 2 advertises to LAN-1, not to the ISP. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 06/07/2016 03:25 PM, Carlos E. R. wrote:
On 2016-06-07 21:19, James Knott wrote:
He was talking about announcing back to the WAN. That means back to the
ISP. I don't know how you read it otherwise. WAN in this case refers to the socket labelled "WAN" in that internal router, not to the real "WAN". It connects to LAN-1 And what does that "WAN" connect to? Unless I'm seriously mistaken, it connects to his ADSL modem, which in turn connects back to the ISP? Is
On 06/07/2016 03:16 PM, Carlos E. R. wrote: there some other "WAN" in this context? The WAN of the internal router connects to the LAN of the ISP facing router.
LAN-1 LAN-2 internet---Router 1------------Router 2------ ISP WAN ··· LAN WAN ··· LAN
]> In this instance, there are 2 sides of a router, the LAN side and the ]> WAN. LAN means the local network and WAN faces the ISP. He says he has ]> to advertise to the WAN side. That means he has to send info back to ]> the ISP. There is no other possible meaning of that.
The WAN of router 2 advertises to LAN-1, not to the ISP.
Where does he say he has 2 routers? All I see is a question about using a /56. Even if he did have 2 routers, what does that have to do with the changing prefixes. If he in fact has 2 routers, then he has to split off the relevant /64 prefixes. You can't just connect a 2nd router into the first and expect it to work, without some method of assigning it a /64 prefix. Then the first router has to know how to reach the 2nd. That doesn't just happen. Either it has to be manually configured or some routing protocol has to be used. Now, as I mentioned earlier, I have split off a 2nd /64 as an experiment, with a VLAN as an interface. I don't recall any mention from Koenraad about anything like a 2nd router, VLAN etc., just a question about getting a /56. BTW, just so you know where I'm coming from, I work with routers almost daily in my job. I have also worked with IPv6 for 6 years and am a Cisco CCNA. So, if something doesn't make sense to me, then it's likely due to bad info from the other person. That is, what they're saying just doesn't make sense. Now he mentioned an ADSL modem that's up & down like a yo-yo. That might be the cause of at least some of his problems. He also mentioned advertising routes to the WAN side. Unless presented with something that says otherwise, I must conclude he's talking about back to the ISP. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-07 21:49, James Knott wrote:
On 06/07/2016 03:25 PM, Carlos E. R. wrote:
Where does he say he has 2 routers?
Yes, he did :-) A bit confusing, but it is there. See his last post confirming the setup. All I see is a question about using
a /56. Even if he did have 2 routers, what does that have to do with the changing prefixes. If he in fact has 2 routers, then he has to split off the relevant /64 prefixes. You can't just connect a 2nd router into the first and expect it to work, without some method of assigning it a /64 prefix. Then the first router has to know how to reach the 2nd. That doesn't just happen. Either it has to be manually configured or some routing protocol has to be used.
Well, that's what he was asking about ;-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
James Knott wrote:
On 06/07/2016 03:25 PM, Carlos E. R. wrote:
On 2016-06-07 21:19, James Knott wrote:
He was talking about announcing back to the WAN. That means back to the
ISP. I don't know how you read it otherwise. WAN in this case refers to the socket labelled "WAN" in that internal router, not to the real "WAN". It connects to LAN-1 And what does that "WAN" connect to? Unless I'm seriously mistaken, it connects to his ADSL modem, which in turn connects back to the ISP? Is
On 06/07/2016 03:16 PM, Carlos E. R. wrote: there some other "WAN" in this context? The WAN of the internal router connects to the LAN of the ISP facing router.
LAN-1 LAN-2 internet---Router 1------------Router 2------ ISP WAN ··· LAN WAN ··· LAN
]> In this instance, there are 2 sides of a router, the LAN side and the ]> WAN. LAN means the local network and WAN faces the ISP. He says he has ]> to advertise to the WAN side. That means he has to send info back to ]> the ISP. There is no other possible meaning of that.
The WAN of router 2 advertises to LAN-1, not to the ISP.
Where does he say he has 2 routers?
https://lists.opensuse.org/opensuse/2016-06/msg00056.html https://lists.opensuse.org/opensuse/2016-06/msg00236.html -- Per Jessen, Zürich (17.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 07-06-16 om 21:25 schreef Carlos E. R.:
The WAN of the internal router connects to the LAN of the ISP facing router.
LAN-1 LAN-2 internet---Router 1------------Router 2------ ISP WAN ··· LAN WAN ··· LAN
Sorry if there was confusion. Carlos made a fine drawing of my setup. I asked my ISP when they would provide "consumer"-users with static ipv6 prefixes. They answered : no plans. Can we closed the thread if it generates so much heat ? Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-07 23:07, Koenraad Lelong wrote:
Op 07-06-16 om 21:25 schreef Carlos E. R.:
I asked my ISP when they would provide "consumer"-users with static ipv6 prefixes. They answered : no plans.
Sigh. Unless we force the authorities to force the ISPs to do the good thing and not be so greedy. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 06/07/2016 09:35 PM, Carlos E. R. wrote:
On 2016-06-07 23:07, Koenraad Lelong wrote:
Op 07-06-16 om 21:25 schreef Carlos E. R.:
I asked my ISP when they would provide "consumer"-users with static ipv6 prefixes. They answered : no plans. Sigh.
Unless we force the authorities to force the ISPs to do the good thing and not be so greedy.
Of course, by "static", does the ISP mean addresses permanently assigned to the customer, rather than just not likely to change? Those are 2 different things. As I mentioned, my address, though dhcp, is virtually static. A business user would like have a permanent address that will never change. I'd like to know what happens when he resolves the unstable ADSL modem issue. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-06-08 03:46, James Knott wrote:
On 06/07/2016 09:35 PM, Carlos E. R. wrote:
On 2016-06-07 23:07, Koenraad Lelong wrote:
Op 07-06-16 om 21:25 schreef Carlos E. R.:
Of course, by "static", does the ISP mean addresses permanently assigned to the customer, rather than just not likely to change? Those are 2 different things. As I mentioned, my address, though dhcp, is virtually static. A business user would like have a permanent address that will never change. I'd like to know what happens when he resolves the unstable ADSL modem issue.
Yes, virtually static would suffice for most people. We would have to use the equivalent to dyndns if we wanted to, say, give some one a link on our computers to a file or photo or whatever. Which means an extra step (an intermediary) anytime we want any IoT service. Most people, with our current Ipv4 connections, get a new IP the instant there is a glitch in the connection. Be it the wind moving the copper cables or the router being unplugged. This is not what was supposed to be internet when it was invented. Everyone was supposed to have a fixed IP, so that we could connect with anyone we sished for whatever reason we wanted. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAldXgsQACgkQja8UbcUWM1ygEAD/S1Ph/cObaGAD1ILkaOEPNcE7 m2Vs/Xp0DAgsvtanEm8A+wYw/TPjG0Nz9X0q7q6xPpSmAOHfv5r8aogzIW3MXic1 =uw4a -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2016-06-08 03:46, James Knott wrote:
On 06/07/2016 09:35 PM, Carlos E. R. wrote:
On 2016-06-07 23:07, Koenraad Lelong wrote:
Op 07-06-16 om 21:25 schreef Carlos E. R.:
Of course, by "static", does the ISP mean addresses permanently assigned to the customer, rather than just not likely to change? Those are 2 different things. As I mentioned, my address, though dhcp, is virtually static. A business user would like have a permanent address that will never change. I'd like to know what happens when he resolves the unstable ADSL modem issue.
Yes, virtually static would suffice for most people. We would have to use the equivalent to dyndns if we wanted to, say, give some one a link on our computers to a file or photo or whatever. Which means an extra step (an intermediary) anytime we want any IoT service.
Most people, with our current Ipv4 connections, get a new IP the instant there is a glitch in the connection. Be it the wind moving the copper cables or the router being unplugged.
This is not what was supposed to be internet when it was invented. Everyone was supposed to have a fixed IP, so that we could connect with anyone we sished for whatever reason we wanted.
The internet when it was created was never supposed to connect every man and his dog (and its fleas) :-) -- Per Jessen, Zürich (17.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/08/2016 01:46 AM, Per Jessen wrote:
This is not what was supposed to be internet when it was invented.
Everyone was supposed to have a fixed IP, so that we could connect with anyone we sished for whatever reason we wanted. The internet when it was created was never supposed to connect every man and his dog (and its fleas) :-)
It was also experimental and the plan was to have longer addresses when released. At least that's what Vint Cerf says. He is also strongly in favour of moving to IPv6 as fast as possible. BTW, it was Vint Cerf who's a father of the Internet, not Al Gore. ;-) https://en.wikipedia.org/wiki/Vint_Cerf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 10:28 PM, Carlos E. R. wrote:
On 2016-06-08 03:46, James Knott wrote:
On 06/07/2016 09:35 PM, Carlos E. R. wrote:
On 2016-06-07 23:07, Koenraad Lelong wrote:
Op 07-06-16 om 21:25 schreef Carlos E. R.:
Of course, by "static", does the ISP mean addresses permanently assigned to the customer, rather than just not likely to change? Those are 2 different things. As I mentioned, my address, though dhcp, is virtually static. A business user would like have a permanent address that will never change. I'd like to know what happens when he resolves the unstable ADSL modem issue.
Yes, virtually static would suffice for most people. We would have to use the equivalent to dyndns if we wanted to, say, give some one a link on our computers to a file or photo or whatever. Which means an extra step (an intermediary) anytime we want any IoT service.
I use a regular DNS server, not dyndns. While my IPv4 address is DHCP, the host name if fixed, dependent on modem and router MAC addresses. So, I just use an alias on the DNS server that points to that host name. Works fine. So far, for IPv6, I've just used the actual addresses to create AAAA records.
Most people, with our current Ipv4 connections, get a new IP the instant there is a glitch in the connection. Be it the wind moving the copper cables or the router being unplugged.
That is not the way DHCP is supposed to work. You're supposed to have a lease time, during which you "own" the address. As long as you renew before the lease expires, you should retain the same address. As mentioned, my IPv4 address is virtually static. But even if it wasn't, as long as the host name is fixed, it doesn't matter. The alias will still work.
This is not what was supposed to be internet when it was invented. Everyone was supposed to have a fixed IP, so that we could connect with anyone we sished for whatever reason we wanted.
That's one of the reasons NAT is bad. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-08 13:06, James Knott wrote:
On 06/07/2016 10:28 PM, Carlos E. R. wrote:
On 2016-06-08 03:46, James Knott wrote:
On 06/07/2016 09:35 PM, Carlos E. R. wrote:
Yes, virtually static would suffice for most people. We would have to use the equivalent to dyndns if we wanted to, say, give some one a link on our computers to a file or photo or whatever. Which means an extra step (an intermediary) anytime we want any IoT service.
I use a regular DNS server, not dyndns. While my IPv4 address is DHCP, the host name if fixed, dependent on modem and router MAC addresses. So, I just use an alias on the DNS server that points to that host name. Works fine. So far, for IPv6, I've just used the actual addresses to create AAAA records.
You can, because you get a practically static IP. We can't, because we don't.
Most people, with our current Ipv4 connections, get a new IP the instant there is a glitch in the connection. Be it the wind moving the copper cables or the router being unplugged.
That is not the way DHCP is supposed to work. You're supposed to have a lease time, during which you "own" the address. As long as you renew before the lease expires, you should retain the same address.
I know, but ISPs perverted that on most places. Yours is highly unusual. Of course, they have the excuse (on IPv4) that the pool of addresses was too scarce, so they have to reuse as soon as possible. But they could have a grace period of 5 minutes, to allow for glitches. They choose not to. And they will do the same on IPv6. Because they can. Very funny when on police movies they find the IP of the bad guy and correlate to a house on seconds. Ha!
As mentioned, my IPv4 address is virtually static. But even if it wasn't, as long as the host name is fixed, it doesn't matter. The alias will still work.
You have to update the DNS server fast enough, and the expiration time of the DNS entry must also be short, for this to work.
This is not what was supposed to be internet when it was invented. Everyone was supposed to have a fixed IP, so that we could connect with anyone we wished for whatever reason we wanted.
That's one of the reasons NAT is bad.
Yep. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
Most people, with our current Ipv4 connections, get a new IP the instant there is a glitch in the connection. Be it the wind moving the copper cables or the router being unplugged.
That is not the way DHCP is supposed to work. You're supposed to have a lease time, during which you "own" the address. As long as you renew before the lease expires, you should retain the same address.
I know, but ISPs perverted that on most places. Yours is highly unusual.
I'm not so totally sure about that - Bluewin, the provider of the incumbent Swiss telco does the same. What's unusual is that James's connection has a fixed hostname, specific to his hardware.
Very funny when on police movies they find the IP of the bad guy and correlate to a house on seconds. Ha!
You mean that's not how it works?? :-) -- Per Jessen, Zürich (17.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-08 13:39, Per Jessen wrote:
Carlos E. R. wrote:
Most people, with our current Ipv4 connections, get a new IP the instant there is a glitch in the connection. Be it the wind moving the copper cables or the router being unplugged.
That is not the way DHCP is supposed to work. You're supposed to have a lease time, during which you "own" the address. As long as you renew before the lease expires, you should retain the same address.
I know, but ISPs perverted that on most places. Yours is highly unusual.
I'm not so totally sure about that - Bluewin, the provider of the incumbent Swiss telco does the same. What's unusual is that James's connection has a fixed hostname, specific to his hardware.
We could do a poll to find out how many of us get "pseudo-fixed" IPs :-) Huh, I know my ADSL IP changed instantly and often. I wonder about now that I'm on fibre. [...] Apparently I keep the same one for the last month. Now I have to find out if it changes when my router goes down. But not exactly now :-)
Very funny when on police movies they find the IP of the bad guy and correlate to a house on seconds. Ha!
You mean that's not how it works?? :-)
LOL, no. You need access to the radius server of that ISP, and correlate the time stamp with the moment they captured the traffic. Then you need the client database, to correlate the radius file with the the actual street address (including the flat and apartment!). It is surprising, though, how accurate google locates people without using GPS. I don't know how they do it. I don't know if it happens to everybody. If I were using WiFi I know they have them mapped, but cable? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 06/08/2016 08:29 AM, Carlos E. R. wrote:
Huh, I know my ADSL IP changed instantly and often.
Doesn't that break TCP connections, so that you have to reload pages? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-08 14:42, James Knott wrote:
On 06/08/2016 08:29 AM, Carlos E. R. wrote:
Huh, I know my ADSL IP changed instantly and often.
Doesn't that break TCP connections, so that you have to reload pages?
Well, the ADSL modem had to retrain. It came with many seconds actual disconnect. Just disconnect the phone jack for a second to move the thing around, and it happened. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wed, Jun 8, 2016 at 3:42 PM, James Knott
On 06/08/2016 08:29 AM, Carlos E. R. wrote:
Huh, I know my ADSL IP changed instantly and often.
Doesn't that break TCP connections, so that you have to reload pages?
And your point is ... ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On June 8, 2016 9:14:04 AM EDT, Andrei Borzenkov
On 06/08/2016 07:20 AM, Carlos E. R. wrote:
I use a regular DNS server, not dyndns. While my IPv4 address is DHCP,
the host name if fixed, dependent on modem and router MAC addresses. So, I just use an alias on the DNS server that points to that host name. Works fine. So far, for IPv6, I've just used the actual addresses to create AAAA records. You can, because you get a practically static IP. We can't, because we don't.
Most people, with our current Ipv4 connections, get a new IP the instant there is a glitch in the connection. Be it the wind moving the copper cables or the router being unplugged.
That is not the way DHCP is supposed to work. You're supposed to have a lease time, during which you "own" the address. As long as you renew before the lease expires, you should retain the same address. I know, but ISPs perverted that on most places. Yours is highly unusual. Of course, they have the excuse (on IPv4) that the pool of addresses was too scarce, so they have to reuse as soon as possible. But they could have a grace period of 5 minutes, to allow for glitches. They choose not to. And they will do the same on IPv6. Because they can.
Very funny when on police movies they find the IP of the bad guy and correlate to a house on seconds. Ha!
As mentioned, my IPv4 address is virtually static. But even if it wasn't, as long as the host name is fixed, it doesn't matter. The alias will still work. You have to update the DNS server fast enough, and the expiration time of the DNS entry must also be short, for this to work.
Please note what I said about my host name. It never changes, so no matter how often the address changes, it shouldn't be a problem, so long as the ISP keeps the DNS in sync with the DHCP server. Anyone with a consistent host name should be able to do the same. As an experiment, check your current IP address and do a host look up. Then check again, after the address changes. If you have the same host name, you can use an alias. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-06-08 14:29, James Knott wrote:
On 06/08/2016 07:20 AM, Carlos E. R. wrote:
Please note what I said about my host name. It never changes, so no matter how often the address changes, it shouldn't be a problem, so long as the ISP keeps the DNS in sync with the DHCP server. Anyone with a consistent host name should be able to do the same.
Ahh... I see.
As an experiment, check your current IP address and do a host look up.
Not found. 3(NXDOMAIN) :-( The one I had early May, is built from the IP, not the MAC:
cer@AmonLanc:~> host 88.1.245.4 4.245.1.88.in-addr.arpa domain name pointer 4.red-88-1-245.dynamicip.rima-tde.net.
-- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
James Knott wrote:
Please note what I said about my host name. It never changes, so no matter how often the address changes, it shouldn't be a problem, so long as the ISP keeps the DNS in sync with the DHCP server. Anyone with a consistent host name should be able to do the same.
As an experiment, check your current IP address and do a host look up. Then check again, after the address changes. If you have the same host name, you can use an alias.
I see lots of a dynamic range IP-addresses, I would say the majority are of the standard form "192.168.99.88.[ppoe|adsl|dyn].something.etc". Might be hard to notice a fixed one. I tried finding yours James, but in one of your emails, I only see yahoo addresses. -- Per Jessen, Zürich (17.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On June 8, 2016 9:46:52 AM EDT, Per Jessen
On 06/07/2016 03:37 AM, Koenraad Lelong wrote:
Op 03-06-16 om 13:49 schreef Per Jessen:
I meant running one's own ipv6 router is not mainstream, not whether PD is used by the provider. I'm sure the latter is already mainstream.
Was busy trying with pfSense ;-).
Maybe the setup is not mainstream, but what's the point of getting a /56 prefix when you can't use all of the subnets ? At the moment I don't really need all the subnets, but how I'm going to use ipv6 on my internal network when at any moment my addresses can change ? Of course I could just use the network right behind the dsl-modem/router but I prefer having a linux firewall between my internal network and the wild wide web.
You can split that /56 into multiple /64s with openSUSE as a router. Also, why do you think your addresses will change? Dhcpv6-pd uses something called DUID which ties your prefix to the hardware, so it shouldn't change.
An extra problem is my dsl-modem/router. Its firewall is too limited. Standard all inboud traffic is blocked which is OK. You can allow traffic through for a host (all or individual ports). But you can only specify the host-part of the ipv6-address. That means hosts on a different subnet are not reachable. But that's not on topic here.
The firewall/modem my ISP provides is also very limiting. That's why I put it in bridge mode and created my own router/firewall. I tried to use openSUSE, but wound up going with pfsense. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/07/2016 03:37 AM, Koenraad Lelong wrote:
Op 03-06-16 om 13:49 schreef Per Jessen:
I meant running one's own ipv6 router is not mainstream, not whether PD is used by the provider. I'm sure the latter is already mainstream.
Was busy trying with pfSense ;-).
Maybe the setup is not mainstream, but what's the point of getting a /56 prefix when you can't use all of the subnets ? At the moment I don't really need all the subnets, but how I'm going to use ipv6 on my internal network when at any moment my addresses can change ? Of course I could just use the network right behind the dsl-modem/router but I prefer having a linux firewall between my internal network and the wild wide web.
You can split that /56 into multiple /64s with openSUSE as a router. Also, why do you think your addresses will change? Dhcpv6-pd uses something called DUID which ties your prefix to the hardware, so it shouldn't change.
If it doesn't change why are we even bothering with this whole discussion? Just configure your IPv6 prefix it statically and you're done. -- Per Jessen, Zürich (22.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 07:18 AM, Per Jessen wrote:
You can split that /56 into multiple /64s with openSUSE as a router.
Also, why do you think your addresses will change? Dhcpv6-pd uses something called DUID which ties your prefix to the hardware, so it shouldn't change. If it doesn't change why are we even bothering with this whole discussion? Just configure your IPv6 prefix it statically and you're done.
On IPv4, my dhcp address changed so seldom, it was virtually static. However, on rare occasion, my ISP did network changes that required address changes. If I had done used static config, I might find myself without a working address or conflicting with someone else. The same applies with dhcpv6-pd. The aprefix will likely not change, but you don't do anything to keep it from happening if necessary. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/07/2016 07:18 AM, Per Jessen wrote:
You can split that /56 into multiple /64s with openSUSE as a router.
Also, why do you think your addresses will change? Dhcpv6-pd uses something called DUID which ties your prefix to the hardware, so it shouldn't change. If it doesn't change why are we even bothering with this whole discussion? Just configure your IPv6 prefix it statically and you're done.
On IPv4, my dhcp address changed so seldom, it was virtually static. However, on rare occasion, my ISP did network changes that required address changes. If I had done used static config, I might find myself without a working address or conflicting with someone else. The same applies with dhcpv6-pd. The aprefix will likely not change, but you don't do anything to keep it from happening if necessary.
To answer your own question - that is precisely why Koenraad thinks his "addresses will change". -- Per Jessen, Zürich (24.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 08:14 AM, Per Jessen wrote:
James Knott wrote:
On 06/07/2016 07:18 AM, Per Jessen wrote:
You can split that /56 into multiple /64s with openSUSE as a router.
Also, why do you think your addresses will change? Dhcpv6-pd uses something called DUID which ties your prefix to the hardware, so it shouldn't change. If it doesn't change why are we even bothering with this whole discussion? Just configure your IPv6 prefix it statically and you're done. On IPv4, my dhcp address changed so seldom, it was virtually static. However, on rare occasion, my ISP did network changes that required address changes. If I had done used static config, I might find myself without a working address or conflicting with someone else. The same applies with dhcpv6-pd. The aprefix will likely not change, but you don't do anything to keep it from happening if necessary. To answer your own question - that is precisely why Koenraad thinks his "addresses will change".
The question is how often. If frequently, as some ISPs do with IPv4, then yes he has a problem. If seldom, as is the case with my IPv4 address, then no, it's not, as changes will be rare. Incidentally, with my ISP, the IPv4 lease time is 7 days. That means I could power off my modem or router for almost a week and still retain the address, as my ISP does not force unnecessary changes. I expect the same will apply with my IPv6 prefix. Here's some info on this: http://ipv6friday.org/blog/2011/12/dhcpv6/ As long as the ISP maps the prefix to the DUID, the prefixes should stay the same, unless it becomes necessary for the ISP to make some change. For example, this might happen when my ISP switches from /64 to another prefix. It would also change, if I change hardware. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 07-06-16 om 14:14 schreef Per Jessen:
To answer your own question - that is precisely why Koenraad thinks his "addresses will change".
To clarify things : My dsl-line isn't absolutely stable. Every time the dsl-signal syncs again, I get a new prefix. E.g. today I already have received two different addresses : 2a02:a03f:2400:7527:3631:c4ff:fe5c:1427 2a02:a03f:2400:7b80:3631:c4ff:fe5c:1427 Host address is the same, but the prefix changes. Those are the external address of the modem/router, but for the internal addesses, it's the same. So I *know* my addresses change. That's my frustration, besides the fact my dsl-signal is not stable (whole other story, don't ask me). Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong wrote:
Op 07-06-16 om 14:14 schreef Per Jessen:
To answer your own question - that is precisely why Koenraad thinks his "addresses will change".
To clarify things : My dsl-line isn't absolutely stable. Every time the dsl-signal syncs again, I get a new prefix. E.g. today I already have received two different addresses : 2a02:a03f:2400:7527:3631:c4ff:fe5c:1427 2a02:a03f:2400:7b80:3631:c4ff:fe5c:1427
Which means your ISP does not try to hand out the same prefix to the same DUID. I wonder what they use for this sort of thing. -- Per Jessen, Zürich (23.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 09:27 AM, Koenraad Lelong wrote:
To answer your own question - that is precisely why Koenraad thinks his "addresses will change".
To clarify things : My dsl-line isn't absolutely stable. Every time the dsl-signal syncs again, I get a new prefix. E.g. today I already have received two different addresses : 2a02:a03f:2400:7527:3631:c4ff:fe5c:1427 2a02:a03f:2400:7b80:3631:c4ff:fe5c:1427
That sounds like you may have a problem. Have you contacted your ISP about this? It's certainly not normal. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 07-06-16 om 17:48 schreef James Knott:
On 06/07/2016 09:27 AM, Koenraad Lelong wrote:
To answer your own question - that is precisely why Koenraad thinks his "addresses will change".
To clarify things : My dsl-line isn't absolutely stable. Every time the dsl-signal syncs again, I get a new prefix. E.g. today I already have received two different addresses : 2a02:a03f:2400:7527:3631:c4ff:fe5c:1427 2a02:a03f:2400:7b80:3631:c4ff:fe5c:1427
That sounds like you may have a problem. Have you contacted your ISP about this? It's certainly not normal.
What's not normal ? The prefixes, or the instability ? The prefixes : they want money to have a fixed prefix. The instablility : long story. Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong wrote:
Op 07-06-16 om 17:48 schreef James Knott:
On 06/07/2016 09:27 AM, Koenraad Lelong wrote:
To answer your own question - that is precisely why Koenraad thinks his "addresses will change".
To clarify things : My dsl-line isn't absolutely stable. Every time the dsl-signal syncs again, I get a new prefix. E.g. today I already have received two different addresses : 2a02:a03f:2400:7527:3631:c4ff:fe5c:1427 2a02:a03f:2400:7b80:3631:c4ff:fe5c:1427
That sounds like you may have a problem. Have you contacted your ISP about this? It's certainly not normal.
What's not normal ? The prefixes, or the instability ? The prefixes : they want money to have a fixed prefix.
Clever.
The instablility : long story.
ISTR having such issues with adsl too, in the very beginning, maybe ten years ago. I think I ended up with some sort of keep-alive script. (the IPs were fixed anyway). Not sure what the real problem was. -- Per Jessen, Zürich (21.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 12:10 PM, Koenraad Lelong wrote:
Op 07-06-16 om 17:48 schreef James Knott:
On 06/07/2016 09:27 AM, Koenraad Lelong wrote:
To answer your own question - that is precisely why Koenraad thinks his "addresses will change".
To clarify things : My dsl-line isn't absolutely stable. Every time the dsl-signal syncs again, I get a new prefix. E.g. today I already have received two different addresses : 2a02:a03f:2400:7527:3631:c4ff:fe5c:1427 2a02:a03f:2400:7b80:3631:c4ff:fe5c:1427
That sounds like you may have a problem. Have you contacted your ISP about this? It's certainly not normal.
What's not normal ? The prefixes, or the instability ? The prefixes : they want money to have a fixed prefix. The instablility : long story.
The instability that may also be causing your address issues. One reason for changing addresses on IPv4 was the shortage of addresses. So, drop an idle system and give the address to someone else. Then when the first is working again, give it an address, any address. With IPv6, there is no such shortage. In fact, some advocate ISPs handing out nothing smaller than a /48. There are enough /48s to give every person on earth well over 4000 of them and that with 3/4 of the IPv6 address space not being allocated for anything. Bottom line, there is no valid reason for an ISP to keep changing prefixes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
Bottom line, there is no valid reason for an ISP to keep changing IPv6 prefixes.
Except what Koenraad wrote - they want to continue to ask a fee for static addresses, so making sure the prefix changes on every new connection will perhaps push customers with such needs to pay the extra fee. -- Per Jessen, Zürich (22.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/2016 12:57 PM, Per Jessen wrote:
James Knott wrote:
Bottom line, there is no valid reason for an ISP to keep changing IPv6 prefixes. Except what Koenraad wrote - they want to continue to ask a fee for static addresses, so making sure the prefix changes on every new connection will perhaps push customers with such needs to pay the extra fee.
Then it's time to find a new ISP and let the old one know why he's leaving. This is predatory behaviour, in that they're deliberately harming a customer, in order to squeeze more out of them. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/07/2016 12:57 PM, Per Jessen wrote:
James Knott wrote:
Bottom line, there is no valid reason for an ISP to keep changing IPv6 prefixes. Except what Koenraad wrote - they want to continue to ask a fee for static addresses, so making sure the prefix changes on every new connection will perhaps push customers with such needs to pay the extra fee.
Then it's time to find a new ISP and let the old one know why he's leaving. This is predatory behaviour, in that they're deliberately harming a customer, in order to squeeze more out of them.
They're not harming anyone. They're almost certainly delivering exactly the service the customer is paying for. I am sure they are operating according to their T&Cs - nobody dishing dynamic addresses will give a guarantee that it remains the same over any period of time. That it might happen anyway is pure luck, but if a customer relies on what was not promised .... -- Per Jessen, Zürich (22.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Bottom line, there is no valid reason for an ISP to keep changing prefixes.
You are preaching to the wrong choir. It does not matter what you think about it - this is the fact of life outside of our control.-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong wrote:
Hi,
Has anyone experience with ipv6 on Leap 42.1 ?
Yes. Works very well.
I'm trying to setup an ipv6 router. I installed Leap without a gui. My external address is automatically configured. That's OK. Trying with yast, I found after searching and trying you only can assign a static ipv6 address by specifying it in the IP-address box.
Is there any other way to assign a static address on a local system? (i.e. ignoring fixed assignments by DHCP).
You then can add an ipv4 address.
Right - or you can do it beforehand. Mind you, I don't think I have tried using a static IPv6 address on a Leap system.
The next step is configuring the internal addess with prefix delegation, but I can't find information how the do that.
We have very recently had a long thread, with many branches on exactly that topic. You may (or may not) want to read that.
So how could I add the PD-request, and configure the internal interface using the result ?
If you are getting a PD from your provider, it currently does not work. There is at least one bugreport open. -- Per Jessen, Zürich (17.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/02/2016 03:09 PM, Per Jessen wrote:
Has anyone experience with ipv6 on Leap 42.1 ? Yes. Works very well.
IIRC, you're using a static configuration. Many ISPs are now using dhcpv6-pd to hand out prefixes. Leap definitely doesn't support that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/02/2016 03:09 PM, Per Jessen wrote:
Has anyone experience with ipv6 on Leap 42.1 ? Yes. Works very well.
IIRC, you're using a static configuration.
No, it also works very well in a dynamic setup, you have to a little more precise about exactly which setup. (my dynamic setup = radvd+dhcpv6 with a statically configured router). -- Per Jessen, Zürich (16.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/02/2016 03:16 PM, Per Jessen wrote:
James Knott wrote:
On 06/02/2016 03:09 PM, Per Jessen wrote:
Has anyone experience with ipv6 on Leap 42.1 ? Yes. Works very well.
IIRC, you're using a static configuration. No, it also works very well in a dynamic setup, you have to a little more precise about exactly which setup.
(my dynamic setup = radvd+dhcpv6 with a statically configured router).
As I said, yours is a static configuration, as you show above. No doubt it works well that way, as it did for me, when I was running a 6in4 tunnel. But it will not work with dhcpv6-pd. I tried for 2 weeks to get it to, before giving up. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 06/02/2016 03:16 PM, Per Jessen wrote:
James Knott wrote:
On 06/02/2016 03:09 PM, Per Jessen wrote:
Has anyone experience with ipv6 on Leap 42.1 ? Yes. Works very well.
IIRC, you're using a static configuration. No, it also works very well in a dynamic setup, you have to a little more precise about exactly which setup.
(my dynamic setup = radvd+dhcpv6 with a statically configured router).
As I said, yours is a static configuration, as you show above.
Yes, the router is, every other non-server systen is dynamically configured.
No doubt it works well that way, as it did for me, when I was running a 6in4 tunnel. But it will not work with dhcpv6-pd. I tried for 2 weeks to get it to, before giving up.
Yep, agree. Koenraad's initial question was a little too open :-) -- Per Jessen, Zürich (16.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Andrei Borzenkov -
Carlos E. R. -
Herbert Graeber -
James Knott -
Jeremy Baker -
Koenraad Lelong -
Mathias Homann -
Per Jessen