Re: [opensuse] postfix refused to run ipv6? opensuse tumbleweed
Simon Becherer wrote:
Thank you,
Edit /etc/hosts and remove the entry that maps '::1' as 'localhost'. i removed all ipv6 related entries.
service now running :-))
Or just enable ipv6 - doesn't matter if you don't use it.
mh, if i do not use, why it should run? (and send packets in background...)
Because, as you have seen, disabling ipv6 only causes problems. Besides, ipv6 does not 'run', it's only a protocol. It doesn't send anything in the background either. Brgds Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi per,
Because, as you have seen, disabling ipv6 only causes problems. Besides, ipv6 does not 'run', it's only a protocol. It doesn't send anything in the background either.
mh, your arguments are ok, - - it makes problems. - - but if its running a lot of stuff is sendet across my lan with ipv6 adesses, i dont know who (kernel/program), i do not knwo why. main reason to disable is i do not understand the ipv6 behavior, i actually only know its NOT only more address-space than ipv4 its much more, and i have no time to read all the stuff for ipv6 and so i do not know how to gave them static addresses, check / set firewall (iptables) for it etc.... so i decide better not use (at least at long it is possible). thanks, simoN Am 19.01.2018 um 09:39 schrieb Per Jessen:
Simon Becherer wrote:
Thank you,
Edit /etc/hosts and remove the entry that maps '::1' as 'localhost'. i removed all ipv6 related entries.
service now running :-))
Or just enable ipv6 - doesn't matter if you don't use it.
mh, if i do not use, why it should run? (and send packets in background...)
Because, as you have seen, disabling ipv6 only causes problems. Besides, ipv6 does not 'run', it's only a protocol. It doesn't send anything in the background either.
Brgds Per
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJaYbMtAAoJEOuDxDCJWQG+HHQP/RiMjx3bjkDOMmKuitD8d2jp 5KOTX2hHobrGdyQEduVNiNDhC9+CLsblVzUj3AZEtPDNNn/VVMJAtvxPyKwhKppy dfG7lsBCO7A+ecBE5DteIwJibeNfraRAKHd4zfq9/w5mz2g+EAhtcbD6VDaFoqI9 2jlg5KXKmVJ5Trv5VMfFjQ92XhdxnGrNOd+v+xMBxt+1Z9VB6Dse1a/fdTlZq+Ua cw8qWZS2yXSVBZsTroYlDg2uj+j6SZgSWIIaDsk2D6m22wEYKKiNQFliukq0gNqK cc7VGDN4mybIDdjXJaHruhnAARLsyTX02fkOINu9AJhNS9JB9p2rIF2q0JuxuIkg qO9qE1bfL3TBD6wY0M8qPHH1MKwmTZFzm5MHRAijrL7an0z1jqolgRozfCiltc6a xSUVasEFaPoVN8BupDICBa7yefjVPXH5H0eVlrUwDGHdzJXvT8MD0n2Bf80j/uX7 jHwlGZ/4i80i0y06OFkA9vpShFksNIeZ0Eq+ySwDt/L1uOEE1HoND4FAakQL1lfD 6c13AMLapGd6D5xXASoR+llY2IBJaChM77GvEJ78ttOdY2zxyME1tsf8fPg5MgVs CiN3rtSSiCUC9hkX+ESVPZe5V6MhhLO9Ias9OgDXecQjTjFl4dXl92Ycdyvx1ahx vWkRATmruDxB0VM3Tm0R =WIAX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-19 09:58, Simon Becherer wrote:
Hi per,
Because, as you have seen, disabling ipv6 only causes problems. Besides, ipv6 does not 'run', it's only a protocol. It doesn't send anything in the background either.
mh, your arguments are ok, - it makes problems. - but if its running a lot of stuff is sendet across my lan with ipv6 adesses, i dont know who (kernel/program), i do not knwo why.
main reason to disable is i do not understand the ipv6 behavior, i actually only know its NOT only more address-space than ipv4 its much more, and i have no time to read all the stuff for ipv6 and so i do not know how to gave them static addresses, check / set firewall (iptables) for it etc.... so i decide better not use (at least at long it is possible).
But it does not matter if it works :-) If you are using SuSEfirewall2, you don't have to care. No need to assign static IPv6 addresses (yet). Only if it tries to connect to some computer and it doesn't work and causes problems, is remove IPv6 support a consideration. But the first thing is finding why it does not work and solving that part instead. Anyway, if your ISP and router don't have an IPv6 address, that traffic doesn't go outside, so no worries. I have IPv6 enabled on the computer and I have no issues with it. In "/etc/gai.conf" I changed: precedence ::ffff:0:0/96 100 which makes the system to prefer IPv4, I understand. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-01-19 09:58, Simon Becherer wrote:
Hi per,
Because, as you have seen, disabling ipv6 only causes problems. Besides, ipv6 does not 'run', it's only a protocol. It doesn't send anything in the background either.
mh, your arguments are ok, - it makes problems. - but if its running a lot of stuff is sendet across my lan with ipv6 adesses, i dont know who (kernel/program), i do not knwo why.
main reason to disable is i do not understand the ipv6 behavior, i actually only know its NOT only more address-space than ipv4 its much more, and i have no time to read all the stuff for ipv6 and so i do not know how to gave them static addresses, check / set firewall (iptables) for it etc.... so i decide better not use (at least at long it is possible).
But it does not matter if it works :-)
If you are using SuSEfirewall2, you don't have to care.
No need to assign static IPv6 addresses (yet).
Only if it tries to connect to some computer and it doesn't work and causes problems, is remove IPv6 support a consideration. But the first thing is finding why it does not work and solving that part instead.
Anyway, if your ISP and router don't have an IPv6 address, that traffic doesn't go outside, so no worries.
I have IPv6 enabled on the computer and I have no issues with it. In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
which makes the system to prefer IPv4, I understand.
Yes, that is what the comments say. When you don't have ipv6, it is unnecessary to change it though. -- Per Jessen, Zürich (5.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 2018-01-19 13:06, Per Jessen wrote:
Carlos E. R. wrote:
...
I have IPv6 enabled on the computer and I have no issues with it. In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
which makes the system to prefer IPv4, I understand.
Yes, that is what the comments say. When you don't have ipv6, it is unnecessary to change it though.
I found sometimes that zypper would try to use IPv6 and error out. Since I did that edit, no more problems :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-01-19 13:06, Per Jessen wrote:
Carlos E. R. wrote:
...
I have IPv6 enabled on the computer and I have no issues with it. In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
which makes the system to prefer IPv4, I understand.
Yes, that is what the comments say. When you don't have ipv6, it is unnecessary to change it though.
I found sometimes that zypper would try to use IPv6 and error out. Since I did that edit, no more problems :-)
ISTR that being due to a faulty/partially working ipv6 setup on your side. -- Per Jessen, Zürich (5.7°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 2018-01-19 13:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:06, Per Jessen wrote:
Carlos E. R. wrote:
...
I have IPv6 enabled on the computer and I have no issues with it. In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
which makes the system to prefer IPv4, I understand.
Yes, that is what the comments say. When you don't have ipv6, it is unnecessary to change it though.
I found sometimes that zypper would try to use IPv6 and error out. Since I did that edit, no more problems :-)
ISTR that being due to a faulty/partially working ipv6 setup on your side.
Obviously! My router doesn't have IPv6 to Internet. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-01-19 13:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:06, Per Jessen wrote:
Carlos E. R. wrote:
...
I have IPv6 enabled on the computer and I have no issues with it. In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
which makes the system to prefer IPv4, I understand.
Yes, that is what the comments say. When you don't have ipv6, it is unnecessary to change it though.
I found sometimes that zypper would try to use IPv6 and error out. Since I did that edit, no more problems :-)
ISTR that being due to a faulty/partially working ipv6 setup on your side.
Obviously! My router doesn't have IPv6 to Internet.
No, that is not obvious, Carlos - if you don't have _any_ ipv6 setup, your setup is not faulty nor partial. In that case, no need to edit /etc/gai.conf. Otherwise we would be shipping a very poor default. -- Per Jessen, Zürich (5.8°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 2018-01-19 13:28, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:06, Per Jessen wrote:
Carlos E. R. wrote:
...
I have IPv6 enabled on the computer and I have no issues with it. In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
which makes the system to prefer IPv4, I understand.
Yes, that is what the comments say. When you don't have ipv6, it is unnecessary to change it though.
I found sometimes that zypper would try to use IPv6 and error out. Since I did that edit, no more problems :-)
ISTR that being due to a faulty/partially working ipv6 setup on your side.
Obviously! My router doesn't have IPv6 to Internet.
No, that is not obvious, Carlos - if you don't have _any_ ipv6 setup, your setup is not faulty nor partial. In that case, no need to edit /etc/gai.conf. Otherwise we would be shipping a very poor default.
But it should be obvious to you, I have commented with you that my router doesn't have IPv6 connectivity :-) The computer itself is correctly configured, it can ssh to other local computer on IPv6. I tried years ago. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-01-19 13:28, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:06, Per Jessen wrote:
Carlos E. R. wrote:
...
> I have IPv6 enabled on the computer and I have no issues with > it. In "/etc/gai.conf" I changed: > > precedence ::ffff:0:0/96 100 > > which makes the system to prefer IPv4, I understand.
Yes, that is what the comments say. When you don't have ipv6, it is unnecessary to change it though.
I found sometimes that zypper would try to use IPv6 and error out. Since I did that edit, no more problems :-)
ISTR that being due to a faulty/partially working ipv6 setup on your side.
Obviously! My router doesn't have IPv6 to Internet.
No, that is not obvious, Carlos - if you don't have _any_ ipv6 setup, your setup is not faulty nor partial. In that case, no need to edit /etc/gai.conf. Otherwise we would be shipping a very poor default.
But it should be obvious to you, I have commented with you that my router doesn't have IPv6 connectivity :-)
In which case there is no need to amend /etc/gai.conf. That's all I'm saying. As I said, ISTR going through this a couple years back and discovering you had a partial or faulty IPv6 setup. -- Per Jessen, Zürich (5.1°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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2018-01-19 at 13:55 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:28, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:06, Per Jessen wrote: > Carlos E. R. wrote:
...
>> I have IPv6 enabled on the computer and I have no issues with >> it. In "/etc/gai.conf" I changed: >> >> precedence ::ffff:0:0/96 100 >> >> which makes the system to prefer IPv4, I understand. > > Yes, that is what the comments say. When you don't have ipv6, it > is unnecessary to change it though.
I found sometimes that zypper would try to use IPv6 and error out. Since I did that edit, no more problems :-)
ISTR that being due to a faulty/partially working ipv6 setup on your side.
Obviously! My router doesn't have IPv6 to Internet.
No, that is not obvious, Carlos - if you don't have _any_ ipv6 setup, your setup is not faulty nor partial. In that case, no need to edit /etc/gai.conf. Otherwise we would be shipping a very poor default.
But it should be obvious to you, I have commented with you that my router doesn't have IPv6 connectivity :-)
In which case there is no need to amend /etc/gai.conf. That's all I'm saying. As I said, ISTR going through this a couple years back and discovering you had a partial or faulty IPv6 setup.
But I do need it. I have problems without doing that change. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpjIUcACgkQtTMYHG2NR9Xs5wCghjOufXK6QjSOiPvCWRHC3xrh XmMAni7uvWfk327YjRMlaQzKocP0NQ4V =u5J4 -----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: SHA1
On Friday, 2018-01-19 at 13:55 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:28, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:16, Per Jessen wrote:
Carlos E. R. wrote: > On 2018-01-19 13:06, Per Jessen wrote: >> Carlos E. R. wrote: > > ... > >>> I have IPv6 enabled on the computer and I have no issues with >>> it. In "/etc/gai.conf" I changed: >>> >>> precedence ::ffff:0:0/96 100 >>> >>> which makes the system to prefer IPv4, I understand. >> >> Yes, that is what the comments say. When you don't have ipv6, >> it is unnecessary to change it though. > > I found sometimes that zypper would try to use IPv6 and error > out. Since I did that edit, no more problems :-)
ISTR that being due to a faulty/partially working ipv6 setup on your side.
Obviously! My router doesn't have IPv6 to Internet.
No, that is not obvious, Carlos - if you don't have _any_ ipv6 setup, your setup is not faulty nor partial. In that case, no need to edit /etc/gai.conf. Otherwise we would be shipping a very poor default.
But it should be obvious to you, I have commented with you that my router doesn't have IPv6 connectivity :-)
In which case there is no need to amend /etc/gai.conf. That's all I'm saying. As I said, ISTR going through this a couple years back and discovering you had a partial or faulty IPv6 setup.
But I do need it. I have problems without doing that change.
Well, there is something not quite right with your setup then. I'm sure we've been over this before. Something about your router "pretending" it has IPv6, but with no ipv6 uplink. Yes, the thread is here: https://lists.opensuse.org/opensuse/2015-10/msg00235.html long thread, you might have to go back and forth a bit. -- Per Jessen, Zürich (4.6°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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2018-01-20 at 12:33 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On Friday, 2018-01-19 at 13:55 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:28, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-01-19 13:16, Per Jessen wrote: > Carlos E. R. wrote: >> On 2018-01-19 13:06, Per Jessen wrote: >>> Carlos E. R. wrote: >> >> ... >> >>>> I have IPv6 enabled on the computer and I have no issues with >>>> it. In "/etc/gai.conf" I changed: >>>> >>>> precedence ::ffff:0:0/96 100 >>>> >>>> which makes the system to prefer IPv4, I understand. >>> >>> Yes, that is what the comments say. When you don't have ipv6, >>> it is unnecessary to change it though. >> >> I found sometimes that zypper would try to use IPv6 and error >> out. Since I did that edit, no more problems :-) > > ISTR that being due to a faulty/partially working ipv6 setup on > your side.
Obviously! My router doesn't have IPv6 to Internet.
No, that is not obvious, Carlos - if you don't have _any_ ipv6 setup, your setup is not faulty nor partial. In that case, no need to edit /etc/gai.conf. Otherwise we would be shipping a very poor default.
But it should be obvious to you, I have commented with you that my router doesn't have IPv6 connectivity :-)
In which case there is no need to amend /etc/gai.conf. That's all I'm saying. As I said, ISTR going through this a couple years back and discovering you had a partial or faulty IPv6 setup.
But I do need it. I have problems without doing that change.
Well, there is something not quite right with your setup then. I'm sure we've been over this before. Something about your router "pretending" it has IPv6, but with no ipv6 uplink.
Yes, the thread is here: https://lists.opensuse.org/opensuse/2015-10/msg00235.html
long thread, you might have to go back and forth a bit.
Ok, I read it again in full. Yes, that is exactly the case. The computer has IPv6, has a fixed IPv6 entered manually, and another it gets automatically, (Scope:Link), related to the MAC: Telcontar:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:21:85:16:2D:0B <········ inet addr:192.168.1.14 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::221:85ff:fe16:2d0b/64 Scope:Link <-------- inet6 addr: fc00::14/64 Scope:Global <======== UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:75909 errors:0 dropped:6 overruns:0 frame:0 TX packets:62364 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23320676 (22.2 Mb) TX bytes:5771448 (5.5 Mb) The router doesn't have external IPv6, doesn't give IPv6 to machines (yes, there is another thread with suggestions to try about this, it is in my ToDo List). So the computer thinks there is IPv6, but there is not Internet access on IPv6. This is typical. Thus I change gai.conf so that it tries IPv4 preferably. And things work :-) The other solution we spoke on that thread is changing the code of the dns server so that it doesn't hand out IPv6 responses. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpjM28ACgkQtTMYHG2NR9XSpwCfcV5fYcoP7cX3g/31BTX/gtJS ZasAn1yPZEsu5bWjFrhPfKNjblfT+fui =YOmJ -----END PGP SIGNATURE-----
Carlos E. R. wrote:
Yes, the thread is here: https://lists.opensuse.org/opensuse/2015-10/msg00235.html
long thread, you might have to go back and forth a bit.
Ok, I read it again in full. Yes, that is exactly the case.
The computer has IPv6, has a fixed IPv6 entered manually, and another it gets automatically, (Scope:Link), related to the MAC:
Yes, the link-local address is created automagically, derived from the MAC address. It is the global address that causes the "problem".
So the computer thinks there is IPv6, but there is not Internet access on IPv6.
That is the problem in a nutshell. Like I said, a faulty or incomplete config.
This is typical.
It is very atypical. If it were typical, many more people would want to amend /etc/gai.conf.
Thus I change gai.conf so that it tries IPv4 preferably. And things work :-)
Yes, it is a reasonable way to work around an incomplete setup, although I wouldn't want to do it everywhere. -- Per Jessen, Zürich (5.2°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 01/20/2018 07:17 AM, Carlos E. R. wrote:
eth0 Link encap:Ethernet HWaddr 00:21:85:16:2D:0B <········ inet addr:192.168.1.14 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::221:85ff:fe16:2d0b/64 Scope:Link <-------- inet6 addr: fc00::14/64 Scope:Global <======== UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:75909 errors:0 dropped:6 overruns:0 frame:0 TX packets:62364 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23320676 (22.2 Mb) TX bytes:5771448 (5.5 Mb)
The router doesn't have external IPv6, doesn't give IPv6 to machines (yes, there is another thread with suggestions to try about this, it is in my ToDo List).
So the computer thinks there is IPv6, but there is not Internet access on IPv6.
You have a unique local address (starts with fc00:). Where's it coming from. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/20/2018 07:17 AM, Carlos E. R. wrote:
eth0 Link encap:Ethernet HWaddr 00:21:85:16:2D:0B <········ inet addr:192.168.1.14 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::221:85ff:fe16:2d0b/64 Scope:Link <-------- inet6 addr: fc00::14/64 Scope:Global <======== UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:75909 errors:0 dropped:6 overruns:0 frame:0 TX packets:62364 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23320676 (22.2 Mb) TX bytes:5771448 (5.5 Mb)
The router doesn't have external IPv6, doesn't give IPv6 to machines (yes, there is another thread with suggestions to try about this, it is in my ToDo List).
So the computer thinks there is IPv6, but there is not Internet access on IPv6.
You have a unique local address (starts with fc00:). Where's it coming from.
Must be a static assignment. -- Per Jessen, Zürich (3.4°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 01/20/2018 12:30 PM, Per Jessen wrote:
You have a unique local address (starts with fc00:). Where's it
coming from. Must be a static assignment.
Not necessarily. It could be the router is configured to provide a unique local address. I have done that here with pfSense. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/20/2018 12:30 PM, Per Jessen wrote:
You have a unique local address (starts with fc00:). Where's it
coming from. Must be a static assignment.
Not necessarily. It could be the router is configured to provide a unique local address. I have done that here with pfSense.
Wouldn't that show as "dynamic" ? -- Per Jessen, Zürich (6.3°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/20/2018 02:13 PM, Per Jessen wrote:
James Knott wrote:
On 01/20/2018 12:30 PM, Per Jessen wrote:
You have a unique local address (starts with fc00:). Where's it
coming from. Must be a static assignment. Not necessarily. It could be the router is configured to provide a unique local address. I have done that here with pfSense. Wouldn't that show as "dynamic" ?
No, it just shows as another address. My computer has both global addresses and unique local. Both types are assigned via router advertisements and show the same link local address for the router. As far as the computer is concerned there's no difference, in that both are routeable. However, only the global addresses are routeable to the Internet. BTW, after my computer has been up for a week, it will have 8 of each type, in addition to the link local address. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/20/2018 02:13 PM, Per Jessen wrote:
James Knott wrote:
On 01/20/2018 12:30 PM, Per Jessen wrote:
You have a unique local address (starts with fc00:). Where's it
coming from. Must be a static assignment. Not necessarily. It could be the router is configured to provide a unique local address. I have done that here with pfSense. Wouldn't that show as "dynamic" ?
No, it just shows as another address. My computer has both global addresses and unique local. Both types are assigned via router advertisements and show the same link local address for the router. As far as the computer is concerned there's no difference, in that both are routeable. However, only the global addresses are routeable to the Internet.
BTW, after my computer has been up for a week, it will have 8 of each type, in addition to the link local address.
On my boxes, every non-static address (apart from link-local) says 'dynamic'. Is unique-local treated differently? -- Per Jessen, Zürich (5.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 01/21/2018 02:05 AM, Per Jessen wrote:
BTW, after my computer has been up for a week, it will have 8 of each type, in addition to the link local address. On my boxes, every non-static address (apart from link-local) says 'dynamic'. Is unique-local treated differently? Carlos used ifconfig which does not show dynamic, so you can't tell. You use ip, which does show dynamic.
Try both commands and you'll see the difference. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/21/2018 02:05 AM, Per Jessen wrote:
BTW, after my computer has been up for a week, it will have 8 of each type, in addition to the link local address. On my boxes, every non-static address (apart from link-local) says 'dynamic'. Is unique-local treated differently? Carlos used ifconfig which does not show dynamic, so you can't tell. You use ip, which does show dynamic.
Try both commands and you'll see the difference.
Ah, I didn't realise. I rarely use ifconfig. -- Per Jessen, Zürich (3.3°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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2018-01-21 at 07:05 -0500, James Knott wrote:
On 01/21/2018 02:05 AM, Per Jessen wrote:
BTW, after my computer has been up for a week, it will have 8 of each type, in addition to the link local address. On my boxes, every non-static address (apart from link-local) says 'dynamic'. Is unique-local treated differently? Carlos used ifconfig which does not show dynamic, so you can't tell. You use ip, which does show dynamic.
Try both commands and you'll see the difference.
Sorry, what command is that one? I missed it. I went back the thread but failed to locate it? Perhaps "ip addr"? 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:21:85:16:2d:0b brd ff:ff:ff:ff:ff:ff inet 192.168.1.14/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc00::14/64 scope global valid_lft forever preferred_lft forever inet6 fe80::221:85ff:fe16:2d0b/64 scope link valid_lft forever preferred_lft forever - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpkhS4ACgkQtTMYHG2NR9U/fQCglCHDgrfLIFHrE9qGd/txoUcI rdQAnRLKEAoAHprD3ruqUN+vTtv3lkRL =Wy6W -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/21/2018 07:18 AM, Carlos E. R. wrote:
Sorry, what command is that one? I missed it. I went back the thread but failed to locate it?
Perhaps "ip addr"?
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:21:85:16:2d:0b brd ff:ff:ff:ff:ff:ff inet 192.168.1.14/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc00::14/64 scope global valid_lft forever preferred_lft forever inet6 fe80::221:85ff:fe16:2d0b/64 scope link valid_lft forever preferred_lft forever
The commands are ifconfig and ip -6 address show. The question was about your unique local address, which you had listed earlier being "dynamic". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-21 14:12, James Knott wrote:
On 01/21/2018 07:18 AM, Carlos E. R. wrote:
Sorry, what command is that one? I missed it. I went back the thread but failed to locate it?
Perhaps "ip addr"?
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:21:85:16:2d:0b brd ff:ff:ff:ff:ff:ff inet 192.168.1.14/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc00::14/64 scope global valid_lft forever preferred_lft forever inet6 fe80::221:85ff:fe16:2d0b/64 scope link valid_lft forever preferred_lft forever
The commands are ifconfig and ip -6 address show.
The question was about your unique local address, which you had listed earlier being "dynamic".
Telcontar:~ # ip -6 address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 fc00::14/64 scope global valid_lft forever preferred_lft forever inet6 fe80::221:85ff:fe16:2d0b/64 scope link valid_lft forever preferred_lft forever Telcontar:~ # But I don't remember having a dynamic address on this machine :-? I was trying dynamic on the home server the other day, with wlan0; I still have things to try that I think you suggested. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-01-21 14:12, James Knott wrote:
On 01/21/2018 07:18 AM, Carlos E. R. wrote:
Sorry, what command is that one? I missed it. I went back the thread but failed to locate it?
Perhaps "ip addr"?
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:21:85:16:2d:0b brd ff:ff:ff:ff:ff:ff inet 192.168.1.14/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc00::14/64 scope global valid_lft forever preferred_lft forever inet6 fe80::221:85ff:fe16:2d0b/64 scope link valid_lft forever preferred_lft forever
The commands are ifconfig and ip -6 address show.
The question was about your unique local address, which you had listed earlier being "dynamic".
Telcontar:~ # ip -6 address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 fc00::14/64 scope global valid_lft forever preferred_lft forever inet6 fe80::221:85ff:fe16:2d0b/64 scope link valid_lft forever preferred_lft forever Telcontar:~ #
But I don't remember having a dynamic address on this machine :-?
I was just deducing that your fc00:: address as statically assigned because it didn't say 'dynamic', but as James says, 'ifconfig' wouldn't have shown that anyway. -- Per Jessen, Zürich (3.4°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 01/21/2018 08:53 AM, Per Jessen wrote:
But I don't remember having a dynamic address on this machine :-? I was just deducing that your fc00:: address as statically assigned because it didn't say 'dynamic', but as James says, 'ifconfig' wouldn't have shown that anyway.
In addition, random number based SLAAC addresses also have temporary dynamic and temporary deprecated dynamic. There's a new one every day, with older ones deprecated. After 7 days, the oldest falls off the list. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/21/2018 08:36 AM, Carlos E. R. wrote:
But I don't remember having a dynamic address on this machine :-?
I was trying dynamic on the home server the other day, with wlan0; I still have things to try that I think you suggested.
With the ip command, the output will list "forever" or "dynamic". The link local address, for example, is forever, but SLAAC addresses are dynamic. Manually configured address are also forever. Dynamic addresses would be assigned automatically, either via DHCP or SLAAC. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2018-01-20 at 11:51 -0500, James Knott wrote:
On 01/20/2018 07:17 AM, Carlos E. R. wrote:
...
So the computer thinks there is IPv6, but there is not Internet access on IPv6.
You have a unique local address (starts with fc00:). Where's it coming from.
I said: |> The computer has IPv6, has a fixed IPv6 entered manually, and another ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ |> it gets automatically, (Scope:Link), related to the MAC: :-) Someone here told me to use the fc00: prefix years ago. But I had problems with zypper before setting that address, IIRC. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpjmYYACgkQtTMYHG2NR9VZgQCgmYzMQTElVShxGn7HsGe7Cy03 e3QAn0uHnN3E4YaReDDrQGESekylFBkw =WBS5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/20/2018 02:33 PM, Carlos E. R. wrote:
Someone here told me to use the fc00: prefix years ago. But I had problems with zypper before setting that address, IIRC.
Those unique local addresses are the IPv6 equivalent of the IPv4 RFC 1918 addresses. They're routeable, but not over the Internet. You could use them for things you don't want to connect directly to the Internet, such as IoT devices, security cameras etc.. With those, you would typically have a controller or recorder that is reachable via the Internet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi carlos,
If you are using SuSEfirewall2, you don't have to care. mh i read "somewhere" that susefirewall will in future releases not be installed as default? may i am wrong? and if this is correct it's only a matter of time it will be dropped...
AND, i have also some "raspian" (debian based for raspberry pi) running in the same net so susefirewall will not be the only firewall i have.
In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
ok, this would be a option, but what is with (as example) ssh connections, i normally have inside hosts.deny and host.allow things related to ipv4, did this also work with ipv6? and where did i get static addresses to set such things? you see i do not know much.... examples: deny: sshd : ALL : deny allow: sshd : 192.168.0.81 : allow ...snip fro per jessen...
Did you really know everything you needed to know about ipv4 the first time you used that too?
you are right, answer is NO but there somehow in 1989 there was no need to look for holes...... only lan, without connection to the world..... simoN Am 19.01.2018 um 12:13 schrieb Carlos E. R.:
On 2018-01-19 09:58, Simon Becherer wrote:
Hi per,
Because, as you have seen, disabling ipv6 only causes problems. Besides, ipv6 does not 'run', it's only a protocol. It doesn't send anything in the background either.
mh, your arguments are ok, - it makes problems. - but if its running a lot of stuff is sendet across my lan with ipv6 adesses, i dont know who (kernel/program), i do not knwo why.
main reason to disable is i do not understand the ipv6 behavior, i actually only know its NOT only more address-space than ipv4 its much more, and i have no time to read all the stuff for ipv6 and so i do not know how to gave them static addresses, check / set firewall (iptables) for it etc.... so i decide better not use (at least at long it is possible).
But it does not matter if it works :-)
If you are using SuSEfirewall2, you don't have to care.
No need to assign static IPv6 addresses (yet).
Only if it tries to connect to some computer and it doesn't work and causes problems, is remove IPv6 support a consideration. But the first thing is finding why it does not work and solving that part instead.
Anyway, if your ISP and router don't have an IPv6 address, that traffic doesn't go outside, so no worries.
I have IPv6 enabled on the computer and I have no issues with it. In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
which makes the system to prefer IPv4, I understand.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJaYfiEAAoJEOuDxDCJWQG+FpcP/i0WYlnjzZ1HvxrHYf1Lw3v2 3qrmccm1AZAjefdzFQwtjtRn9XbY44CyfXQr9RkEj0pSpA72CVu71JtcTFnsmY/v eGeP+WB1Pcrae3MsGq//+3P6aUwS5gdJZxAWfjYVHqThCQlH7QuUY9ZzYY07ZYhV 1+CAZ51TQwRq0msz8hmq7EU4wWwk5TGmP2jokmz+BKp6xtREz9v9Fc3eQrLwmoIa hcgXfFpiGh10nX3itaP9g/l4YdieuAHcLsLwPwzob1ZxmyeSjXw9oYCNW86jJFaI qfbTtNv+6GWsxu3Xbr0sg1UrDmP9V2tB+wH5sbpwYe9N2/bHtSirZyOJUUDKBYEo GFJLxvhLnCeALfk3pIHkpy8Uvi8o1LrpggcuYLDhduoGGpQEcdFp9K/FXd89NhyJ cUPLaZknv+fo6L3k7Fnt4rmeYa5vuIruCel4OPaRK35TaUBulYLsM1n6O+ULcmy7 Ce5LEODjM4kKTg1N5pOIg/KzBArhSgZ7przG8q4+aEHIDiWKYJOuZADlAoZHx1AY aa06UZrUYD0dH2XvNBdLQw2qyv+Z3ky5bMxY6YBpsJB6WhTJMTOfcUYoWZyxCBQH aMgOjoiWrJlBu4C+EC9QcWC0K+5bEmibnaDOkCliMU1gU+pG1ItqwCDyewdAtWyn TIhU64rTLF5haPfHGC+q =gkvP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Simon Becherer wrote:
In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
ok, this would be a option, but what is with (as example) ssh connections, i normally have inside hosts.deny and host.allow things related to ipv4, did this also work with ipv6?
Have you checked if that actually works / makes a difference? I could be wrong, but I thought tcp wrappers were deprecated quite some time ago. -- Per Jessen, Zürich (6.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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi per,
hosts.deny and host.allow
working on opensuse 11.4 (running in a kvm) working on raspbian (raspberry pi) and you are correct, NOT working on opensuse tumbleweed. mh, not known up to now. and, because i have installed last tumbleweed system fresh in summer 2017, do you know since when this is function is deprecated? the files hosts.allow and hosts.deny still exist with text who says this will work. (package "netcfg" writes the files) and i see a package "tcpd" who could be installed. will this bring function back? or something else? may i should asked at opensuse factory list?: i personally think if this function is switched off, then the files should not be installed automatically. (you see i am falling in this trap) simoN Am 19.01.2018 um 15:37 schrieb Per Jessen:
Simon Becherer wrote:
In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
ok, this would be a option, but what is with (as example) ssh connections, i normally have inside hosts.deny and host.allow things related to ipv4, did this also work with ipv6?
Have you checked if that actually works / makes a difference? I could be wrong, but I thought tcp wrappers were deprecated quite some time ago.
- -- B e c h e r e r GmbH Sondermaschinenbau Mauermatten Strasse 22 79183 Waldkirch Germany Tel.: (+49) (0)7681 3134 Fax: (+49) (0)7681 4378 Mail: info@becherer.de Web: www.becherer.de USt-ID-Nr.: DE 814912198 Registergericht: Freiburg HRB 701860 Geschäftsführer: Dipl.-Ing. (FH), EWE Simon H. Becherer Gerichtsstand / Sitz: Waldkirch Es gelten ausschließlich unsere allgemeinen Liefer- und Zahlungsbedingungen / Einkaufsbedingungen: www.becherer.de/AGB -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJaYh22AAoJEOuDxDCJWQG+iAwP/2BNZdnvn0L/VD7YLZAglyqA pJcQIpn4gBk57PIQIs84wfSifU+DGPd0vx3GraleSz6h/UplMjVXD6mlI3GVSkb4 0k35B+v7dAm6XhJPoqwcTvrOWK0PZChXxDej1UMf+LCu1oh+mreCFU9fxhL2H4Jo HgFfmOJKemQxzdqLwXM64or04xWcDMwHzFVDu50f8tEJPqyLXmz2Za9lZuK3MSwG SWcVyDRSXWAbjVHZlxGam5m0uDT2wFlq42qNu9ESW9XfDkbveTkjXRoU/NRYLo+H UHCV5tWGtOIKmg/tWVStmK7JDMkiDzKoRRRX0n4mxFDsK8AU/sDL/A61Tg2gHTc/ YJnrUbtnBUXhh1B2ccwglR4a985phdyylgTqIfgnP3TDn+C9vrXE8N9iPVu1nYpe KLR5K7nREetug4WZ3F4jZdXAjn1blAhr7dj8Kq2Zx26sOdYAU3PdIC2IYnB4vfYr YxiBaI1051Wkhhp+0vpXwZTpgjlb0TDGd1HnxkRnQ8bOiLGHkeoDVsbh46nno7aA S0XIJmQqzcIppdWs8hKD4pYaIOFUzYflqklst1JN42nu+Y7DZVLNiqH4f1Mji7BW 2M/OLz4SI9IPMOlfR4uifFNlgTWdF34hNL8cYblnZRCMt1TpL7P7UV/Xv7UjwNCi O+jcq10f05DWub1RCjRJ =1dyM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Simon Becherer wrote:
Hi per,
hosts.deny and host.allow
working on opensuse 11.4 (running in a kvm) working on raspbian (raspberry pi)
and you are correct, NOT working on opensuse tumbleweed.
mh, not known up to now.
and, because i have installed last tumbleweed system fresh in summer 2017, do you know since when this is function is deprecated?
I'm not sure since when - using tcp wrappers is quite old fashioned, it is easier & better to run a firewall.
the files hosts.allow and hosts.deny still exist with text who says this will work. (package "netcfg" writes the files) and i see a package "tcpd" who could be installed. will this bring function back? or something else?
To my knowledge, the applications need to be built with support for tcp wrappers (libwrap). xinetd has libwrap support, if you invoke everything via xinetd, your /etc/hosts.{deny,allow} will still work.
may i should asked at opensuse factory list?:
I'm not sure if opensuse-factory is the right place for end-user support, but maybe. -- Per Jessen, Zürich (5.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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi per,
hosts.deny and host.allow
working on opensuse 11.4 (running in a kvm) working on raspbian (raspberry pi) and you are correct, NOT working on opensuse tumbleweed. mh, not known up to now. and, because i have installed last tumbleweed system fresh in summer 2017, do you know since when this is function is deprecated? the files hosts.allow and hosts.deny still exist with text who says this will work. (package "netcfg" writes the files) and i see a package "tcpd" who could be installed. will this bring function back? or something else? may i should asked at opensuse factory list?: i personally think if this function is switched off, then the files should not be installed automatically. (you see i am falling in this trap) simoN Am 19.01.2018 um 15:37 schrieb Per Jessen:
Simon Becherer wrote:
In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
ok, this would be a option, but what is with (as example) ssh connections, i normally have inside hosts.deny and host.allow things related to ipv4, did this also work with ipv6?
Have you checked if that actually works / makes a difference? I could be wrong, but I thought tcp wrappers were deprecated quite some time ago.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJaYh3AAAoJEOuDxDCJWQG+IhMQALs2yrfudh9I3OjvN8yJi7qV fZ09TBvCx5KRxlxraQwSzH6x+1Cf1Dp6TwCYWqtrXBPVXO5jLToac04lR1L1il/l JpxxbOUbgrdQOj70SAnLCgTm1TDgOKlrk6VVEYjRjzBmNZuf3Bloloo5jO8QqTm8 8UduZnbfbJMwRjClKoMh3V6NTt4OsfEoNQQ5Ui7xHe/4rFLITp/MQHflqVzNKkgQ GNgNBJtMNQuKv0TI9T/5KW0X0n35E+lnz4By/5Wqw6qHSRJjtbLerCU8ddGHne0L Hu+JGnFLLULP9FAemnlu5wjkLCtPtR+jluK9nMpvvhrkP5jtmmXAbFoB3IPAx1VW WV6bR8BEAjcCwiTKzFs1y9D1LrQMfCT+dGLXk6ewybytzswBeIKo0PrvzaDzpK4C mO2BALd436B1o6rCLY8BGi5Os1TPSzNYxai05hvGyqAdXeAht7hPJbeLYm8zfPO6 yz7SGD23CXlkA7Nuq7zXP1PZBWhDXxzFMcsZP742XuHWiUfWwxNUYcBLjvOvGc1E rg3M+XG0B5Vrb5+zr2r98h7T4ZGxlQKUe1xwutanddrUXw19YScoMQBuqEJaEKSP ouNO3ryJ/L7JGy6gsrOl2bCnurE1hb/O4zh+kGtNY+jk0eBxTm9FrTOjv8ALnYxj vUtSp413tOYnlBct3dFP =/qPy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-01-19 a las 14:54 +0100, Simon Becherer escribió:
Hi carlos,
If you are using SuSEfirewall2, you don't have to care. mh i read "somewhere" that susefirewall will in future releases not be installed as default? may i am wrong? and if this is correct it's only a matter of time it will be dropped...
AND, i have also some "raspian" (debian based for raspberry pi) running in the same net so susefirewall will not be the only firewall i have.
Yes, but this doesn't affect your openSUSE machine.
In "/etc/gai.conf" I changed:
precedence ::ffff:0:0/96 100
ok, this would be a option, but what is with (as example) ssh connections, i normally have inside hosts.deny and host.allow things related to ipv4, did this also work with ipv6?
But we are assuming that your ISP doesn't give you IPv6 access, so you do not have to do anything. There will not be any incoming IPv6 connection incoming to your openSUSE machine.
and where did i get static addresses to set such things? you see i do not know much....
As your router doesn't have external IPv6 access, you get no IPv6 address to set. You don't have to do anything :-) And if your router has external IPv6 address, then everything changes, because you may get incomings. Then you do have to configure IPv6 in your machines. - -- Cheers Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlpiD/kACgkQja8UbcUWM1ykSgD+OAcgT53D4AzfHfnYycyuUc/K K3R+uzY2K76uv1aveGoBAJ7zXbdNoS4KBr5N5wAXQyEHzSMjkABp0gkzwoNoOC0j =TQlh -----END PGP SIGNATURE-----
Simon Becherer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi per,
Because, as you have seen, disabling ipv6 only causes problems. Besides, ipv6 does not 'run', it's only a protocol. It doesn't send anything in the background either.
mh, your arguments are ok, - - it makes problems. - - but if its running a lot of stuff is sendet across my lan with ipv6 adesses, i dont know who (kernel/program), i do not knwo why.
Hi Simon Unless you have something (a router for instance) on your network that provides the right ipv6 infrastructure, you'll see very little ipv6 traffic.
main reason to disable is i do not understand the ipv6 behavior, i actually only know its NOT only more address-space than ipv4 its much more,
It works/behaves much like ipv4 - the differences are minor. (depending on your point of view).
and i have no time to read all the stuff for ipv6 and so i do not know how to gave them static addresses, check / set firewall (iptables) for it etc.... so i decide better not use (at least at long it is possible).
Did you really know everything you needed to know about ipv4 the first time you used that too? :-) -- Per Jessen, Zürich (5.6°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 01/19/2018 03:58 AM, Simon Becherer wrote:
main reason to disable is i do not understand the ipv6 behavior, i actually only know its NOT only more address-space than ipv4 its much more, and i have no time to read all the stuff for ipv6 and so i do not know how to gave them static addresses, check / set firewall (iptables) for it etc.... so i decide better not use (at least at long it is possible).
Actually, IPv6 workes the same as IPv4. Beyond the much larger address space, there is little difference. These tend to be things designed to improve performance or management. For example things like fixed header size and no checksum at the IP level are designed to improve router performance. Others, such as router adverisements and neighbour soliciation bring management together under ICMP etc. There are also no broadcasts. However, as far as using it goes, TCP and UDP work on it as with IPv4 and it's transparent to applications. I strongly suggest you learn about IPv6, as that's where the world is moving. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R. -
James Knott -
Per Jessen -
Simon Becherer