* Per Jessen [07-04-17 08:09]:

Patrick Shanahan wrote:

...

why when I set a machine a static ipv4 route using yast do I loose network outside my local net, outside my router. I still have connection locally, machines connect to my router. I know I am missing a step. Do I need to change something in the router configuration?

I have no problem if I let dhcp set the local addr

My guess is you're somehow losing the default route.

changing from dhcp assignment to static does not make a change to /etc/resolve.conf. how to I *regain* the "default route"? tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Per Jessen [07-04-17 08:50]:

Patrick Shanahan wrote:

...

* Per Jessen [07-04-17 08:09]:

...

Patrick Shanahan wrote:

...

why when I set a machine a static ipv4 route using yast do I loose network outside my local net, outside my router. I still have connection locally, machines connect to my router. I know I am missing a step. Do I need to change something in the router configuration?

I have no problem if I let dhcp set the local addr

My guess is you're somehow losing the default route.

changing from dhcp assignment to static does not make a change to /etc/resolve.conf. how to I *regain* the "default route"?

You said you "set a machine a static ipv4 route using yast", that's not the same as switching to static addressing.

If you're switching to statis addressing, you need to add the default route yourself. (like any other route).

bear with me, please. I am very dense in networking. I added my router address, 192.168.1.254 to the "Routing" tab as default ipv4 and I can now access the internet, outside the router. Thanks for pointing me in the right direction. one more question, how do I determine the ipv6 address for the router? tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* James Knott [07-04-17 09:10]:

On 07/04/2017 09:00 AM, Patrick Shanahan wrote:

...

one more question, how do I determine the ipv6 address for the router?

LAN or WAN side? If LAN side, and it's working properly, the command "ip -6 route show" will list it.

whatever the "default ipv6 gateway" address should be for the yast -> lan -> routing tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan wrote:

* Per Jessen [07-04-17 08:50]:

...

Patrick Shanahan wrote:

...

* Per Jessen [07-04-17 08:09]:

...

Patrick Shanahan wrote:

...

why when I set a machine a static ipv4 route using yast do I loose network outside my local net, outside my router. I still have connection locally, machines connect to my router. I know I am missing a step. Do I need to change something in the router configuration?

I have no problem if I let dhcp set the local addr

My guess is you're somehow losing the default route.

changing from dhcp assignment to static does not make a change to /etc/resolve.conf. how to I *regain* the "default route"?

You said you "set a machine a static ipv4 route using yast", that's not the same as switching to static addressing.

If you're switching to statis addressing, you need to add the default route yourself. (like any other route).

bear with me, please. I am very dense in networking.

No problem, we'll get it sorted out.

I added my router address, 192.168.1.254 to the "Routing" tab as default ipv4 and I can now access the internet, outside the router. Thanks for pointing me in the right direction.

one more question, how do I determine the ipv6 address for the router?

try 'ip -6 route show' -- Per Jessen, Zürich (24.8°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

Patrick Shanahan wrote:

* Per Jessen [07-04-17 09:21]:

...

Patrick Shanahan wrote: [...]

...

I added my router address, 192.168.1.254 to the "Routing" tab as default ipv4 and I can now access the internet, outside the router. Thanks for pointing me in the right direction.

...

one more question, how do I determine the ipv6 address for the router?

try 'ip -6 route show'

...

ip -6 route show 2602:306:cf6d:10c0::/64 dev enp0s25 proto kernel metric 256 expires 2591821sec pref medium

Okay, that tells us that you have been allocated 2602:306:cf6d:10c0::/64. If you look up enp0s25, you can see which exact address it has been given: ip addr show dev enp0s25

fe80::/64 dev enp0s25 proto kernel metric 256 pref medium default via fe80::e222:2ff:fe5d:2485 dev enp0s25 proto ra metric 1024

That is your default IPv6 address, link-local (fe:80) address of your router. Looks good, I would say. -- Per Jessen, Zürich (25.1°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 2017-07-04 15:38, Per Jessen wrote:

Patrick Shanahan wrote:

...

* Per Jessen [07-04-17 09:21]:

...

Patrick Shanahan wrote: [...]

...

I added my router address, 192.168.1.254 to the "Routing" tab as default ipv4 and I can now access the internet, outside the router. Thanks for pointing me in the right direction.

...

one more question, how do I determine the ipv6 address for the router?

try 'ip -6 route show'

...

ip -6 route show 2602:306:cf6d:10c0::/64 dev enp0s25 proto kernel metric 256 expires 2591821sec pref medium

Okay, that tells us that you have been allocated 2602:306:cf6d:10c0::/64. If you look up enp0s25, you can see which exact address it has been given:

ip addr show dev enp0s25

...

fe80::/64 dev enp0s25 proto kernel metric 256 pref medium default via fe80::e222:2ff:fe5d:2485 dev enp0s25 proto ra metric 1024

That is your default IPv6 address, link-local (fe:80) address of your router.

Looks good, I would say.

I just looked in YaST. It doesn't seem possible to set a fixed IPv4, and a dynamic IPv6. That way I would find out when/if my ISP starts giving IPv6 addresses. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

On 07/04/2017 09:11 PM, James Knott wrote:

However, I haven't tried connecting with a computer that has a static address. So, just enable DHCP to test to see what happens.

That's incorrect. I forgot my main computer has a static IPv4 address and it gets an IPv6 address automagically. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/04/2017 10:18 PM, Carlos E. R. wrote:

On 2017-07-05 03:37, James Knott wrote:

...

On 07/04/2017 09:11 PM, James Knott wrote:

...

However, I haven't tried connecting with a computer that has a static address. So, just enable DHCP to test to see what happens. That's incorrect. I forgot my main computer has a static IPv4 address and it gets an IPv6 address automagically. Oh. Curious!

How does it do that, what component listens for it? If one sets a static IPv4 address in yast it also expects one to write an IPv6 address there. I don't expect a dhcp6 client to be listening unless specified.

As I mentioned, router advertisements are used. The operating system receives them to find the prefix and router address and then creates an address.

Anyway, I don't get any from the router:

Telcontar:~ # ip -6 route show fc00::/64 dev eth0 proto kernel metric 256 mtu 1492 pref medium fe80::/64 dev eth0 proto kernel metric 256 mtu 1492 pref medium fe80::/64 dev vmnet1 proto kernel metric 256 pref medium fe80::/64 dev vmnet8 proto kernel metric 256 pref medium

Where's that fc00: coming from? That's one of the Unique Local Address ranges. Perhaps you should call your ISP to find out if they're offering IPv6 and, if so, what's required to use it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-07-08 16:53, Carlos E. R. wrote:

On 2017-07-05 04:29, James Knott wrote:

...

On 07/04/2017 10:18 PM, Carlos E. R. wrote:

...

On 2017-07-05 03:37, James Knott wrote:

...

...

Anyway, I don't get any from the router:

Telcontar:~ # ip -6 route show fc00::/64 dev eth0 proto kernel metric 256 mtu 1492 pref medium fe80::/64 dev eth0 proto kernel metric 256 mtu 1492 pref medium fe80::/64 dev vmnet1 proto kernel metric 256 pref medium fe80::/64 dev vmnet8 proto kernel metric 256 pref medium

Where's that fc00: coming from? That's one of the Unique Local Address ranges.

No idea.

Ah. Apparently I added it manually some years ago. The address is "fC00:0:0:0::14/64", similar to the IPv4 address of 192.168.1.14. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

On 2017-07-08 20:42, James Knott wrote:

On 07/08/2017 10:53 AM, Carlos E. R. wrote:

...

...

Where's that fc00: coming from? That's one of the Unique Local Address

...

ranges. No idea.

Well, it's coming from somewhere, unless you manually created it.

Yes, I did, see my other post.

...

...

...

Perhaps you should call your ISP to find out if they're offering IPv6 and, if so, what's required to use it. People ask now and then, the answer is no answer or not for the moment.

Maybe they're not offering it yet. However, in some ways it appears they are. For example they have an IPv6 address for their website.

Well, they did a test with a few customers. I only know they did it, not what was the results. I found some threads on the official support site, dated a year ago, and they (the ISP) says there is nothing. Comments say that our routers do get an IPv6/128 address, but unusable, there is no prefix (don't ask me what that means). Seems they use 2A02:9100: Some Spanish links, just to record them somewhere: http://comunidad.movistar.es/t5/Soporte-T%C3%A9cnico-de-Fibra-%C3%93ptica/Co... http://comunidad.movistar.es/t5/Soporte-T%C3%A9cnico-de-Fibra-%C3%93ptica/So... https://www.telefonica.com/es/web/public-policy/blog/articulo/-/blogs/descub... The last one was a test done at Sevilla (29/06/2016). It mentions they assigned /64 to mobile clients. SLAAC. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

On 2017-07-08 23:10, James Knott wrote:

On 07/08/2017 05:00 PM, Carlos E. R. wrote:

However, you can get a /48 prefix from Hurricane Electric for free, but you'll have to set up a 6in4 tunnel. A prefix is like an IPv4 subnet mask, in that it determines how many bits are yours. So, if you have a /48 prefix, you have 128-48=80 bits to yourself, for 2^80 addresses or 65536 /64s. LANs normally have a /64 prefix. My ISP gives me a /56 for 256 /64s.

Yes, I can set a tunnel, but I don't need IPv6 for myself now ;-)

...

The last one was a test done at Sevilla (29/06/2016). It mentions they assigned /64 to mobile clients. SLAAC.

I don't read Spanish, but my ISP also provides IPv6 to their cell network. My phone has an IPv6 address and all IPv4 traffic uses 464XLAT to send it over IPv6. With some phone models, even tethered devices get an IPv6 address.

Apparently they only did that during the test. My mobile gets a 10.*.*.* address often. Like this instant. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

09.07.2017 00:10, James Knott пишет:

However, you can get a /48 prefix from Hurricane Electric for free,

6in4 tunneling requires direct Internet connection (or at least ability to forward incoming traffic to your endpoint) and so is out of question for many (if not most) users. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/09/2017 06:59 AM, Carlos E. R. wrote:

On 2017-07-09 07:50, Andrei Borzenkov wrote:

...

09.07.2017 00:10, James Knott пишет:

...

However, you can get a /48 prefix from Hurricane Electric for free, 6in4 tunneling requires direct Internet connection (or at least ability to forward incoming traffic to your endpoint) and so is out of question for many (if not most) users. I don't quite follow this.

I suppose that if I browse the web via this tunnel, the replies will automatically go back via the same tunnel, no problem there.

The problem would be if some one tries to contact me on IPv6: Hurricane (or other) has to open a connection to my IPv4 address via the tunnel. I don't see the problem there, as long as the tunnel is connected at both ends.

Or is it something else? :-?

I think he was referring to the fact that some people are behind carrier grade NAT, which means they don't have any public IPv4 address and so have nothing for the tunnel to connect to. 6in4 use IP protocol 41 and you have to provide a valid IPv4 address for those packets to be sent to. You can't do that, if your ISP uses NAT. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/09/2017 01:50 AM, Andrei Borzenkov wrote:

09.07.2017 00:10, James Knott пишет:

...

However, you can get a /48 prefix from Hurricane Electric for free, 6in4 tunneling requires direct Internet connection (or at least ability to forward incoming traffic to your endpoint) and so is out of question for many (if not most) users.

Yep. I used a 6in4 tunnel for 6 years and know some people can't because they're behind NAT. However, I don't think Carlos said he was. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-07-05 04:18, Carlos E. R. wrote:

On 2017-07-05 03:37, James Knott wrote:

...

On 07/04/2017 09:11 PM, James Knott wrote:

...

However, I haven't tried connecting with a computer that has a static address. So, just enable DHCP to test to see what happens.

That's incorrect. I forgot my main computer has a static IPv4 address and it gets an IPv6 address automagically.

Oh. Curious!

How does it do that, what component listens for it? If one sets a static IPv4 address in yast it also expects one to write an IPv6 address there. I don't expect a dhcp6 client to be listening unless specified.

Anyway, I don't get any from the router:

Telcontar:~ # ip -6 route show fc00::/64 dev eth0 proto kernel metric 256 mtu 1492 pref medium fe80::/64 dev eth0 proto kernel metric 256 mtu 1492 pref medium fe80::/64 dev vmnet1 proto kernel metric 256 pref medium fe80::/64 dev vmnet8 proto kernel metric 256 pref medium

I booted another partition with 42.1, which is using dhcp, and it is not getting an IPv6 from the router. Gestor:~ # ip -6 route show fe80::/64 dev eth0 proto kernel metric 256 mtu 1492 pref medium Gestor:~ # -- Cheers / Saludos, Carlos E. R. (from openSUSE Leap 42.1 x86_64 (test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Op dinsdag 4 juli 2017 14:46:27 CEST schreef Per Jessen:

Patrick Shanahan wrote:

...

* Per Jessen [07-04-17 08:09]:

...

Patrick Shanahan wrote:

...

why when I set a machine a static ipv4 route using yast do I loose network outside my local net, outside my router. I still have connection locally, machines connect to my router. I know I am missing a step. Do I need to change something in the router configuration?

I have no problem if I let dhcp set the local addr

My guess is you're somehow losing the default route.

changing from dhcp assignment to static does not make a change to /etc/resolve.conf. how to I *regain* the "default route"?

You said you "set a machine a static ipv4 route using yast", that's not the same as switching to static addressing.

If you're switching to statis addressing, you need to add the default route yourself. (like any other route).

You also need to set the DNS. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* James Knott [07-04-17 09:07]:

On 07/04/2017 08:15 AM, Patrick Shanahan wrote:

...

* Per Jessen [07-04-17 08:09]:

...

Patrick Shanahan wrote:

...

why when I set a machine a static ipv4 route using yast do I loose network outside my local net, outside my router. I still have connection locally, machines connect to my router. I know I am missing a step. Do I need to change something in the router configuration?

I have no problem if I let dhcp set the local addr My guess is you're somehow losing the default route. changing from dhcp assignment to static does not make a change to /etc/resolve.conf. how to I *regain* the "default route"?

tks

????

Resolv.conf has nothing to do with routing. Only host name lookup. First you were setting static route, then dhcp vs static address and now resolv.conf. Which is it?

I want to switch from dhcp setting machine addr to static and not depend on router as the att router I have doesn't always provide what I expect to be the correct machine ip. when I changed the machine to static, I could access local addresses, inside router, but not internet, outside. Adding the router addr as gateway (yast -> lan -> routing) provided internet, outside router, access. 192.168.1.254 but what do I assign as the default ipv6 gateway address? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* James Knott [07-04-17 09:21]:

On 07/04/2017 09:13 AM, Patrick Shanahan wrote:

...

but what do I assign as the default ipv6 gateway address?

You don't it should happen automagically. An IPv6 router uses router advertisements to inform devices of it's address and the network prefix. To see if this has happened, use the ifconfig command. If you see an IPv6 address, other than the link local address, then it's working.

ok, yes, I do. wondering why yast asks for it tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org