* James Knott [08-09-19 15:09]:

On 2019-08-09 02:59 PM, Patrick Shanahan wrote:

...

wtf is ping default ipv6 now

I now have two wireless systems and four wired systems that fail pinging yahoo.com (or anywhere else except locally) unless "-4" is specified.

previously, two days ago, all systems worked w/o a problem and w/o the need to specify ipv4.

I even had to deny ipv6 in "yast lan" in order to connect to yahoo/google/... which seem to default to ipv6 addresses.

It has been for quite some time.  Unless you specify otherwise, the IPv6 address will be used, if available.

so why was ipv6 addressing working until yesterday? if I close firefox and restart it and it tries to reconnect to previous pages, it fails, cannot connect (unless I disable ipv6 in 'yast lan' and reboot). I have never had this problem. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri 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

On 09/08/2019 21.13, Patrick Shanahan wrote:

* James Knott <> [08-09-19 15:09]:

...

On 2019-08-09 02:59 PM, Patrick Shanahan wrote:

...

wtf is ping default ipv6 now

I now have two wireless systems and four wired systems that fail pinging yahoo.com (or anywhere else except locally) unless "-4" is specified.

previously, two days ago, all systems worked w/o a problem and w/o the need to specify ipv4.

I even had to deny ipv6 in "yast lan" in order to connect to yahoo/google/... which seem to default to ipv6 addresses.

It has been for quite some time.  Unless you specify otherwise, the IPv6 address will be used, if available.

so why was ipv6 addressing working until yesterday? if I close firefox and restart it and it tries to reconnect to previous pages, it fails, cannot connect (unless I disable ipv6 in 'yast lan' and reboot). I have never had this problem.

I don't know about TW, but in my machines I have this: /etc/gai.conf: # precedence <mask> <value> # Add another rule to the RFC 3484 precedence table. See section 2.1 # and 10.3 in RFC 3484. The default is: # #precedence ::1/128 50 #precedence ::/0 40 #precedence 2002::/16 30 #precedence ::/96 20 #precedence ::ffff:0:0/96 10 # # For sites which prefer IPv4 connections change the last line to # precedence ::ffff:0:0/96 100 #CER -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

* Per Jessen [08-09-19 15:28]:

Patrick Shanahan wrote:

...

14:43 crash2:~ > ping -v yahoo.com PING yahoo.com(media-router-fp2.prod1.media.vip.bf1.yahoo.com (2001:4998:58:1836::11)) 56 data bytes From 2600:1702:1031:3f90::1 (2600:1702:1031:3f90::1) icmp_seq=1 Destination unreachable: Address unreachable From 2600:1702:1031:3f90::1 (2600:1702:1031:3f90::1) icmp_seq=2 Destination unreachable: Address unreachable From 2600:1702:1031:3f90::1 (2600:1702:1031:3f90::1) icmp_seq=3 Destination unreachable: Address unreachable From 2600:1702:1031:3f90::1 (2600:1702:1031:3f90::1) icmp_seq=4 Destination unreachable: Address unreachable From 2600:1702:1031:3f90::1 (2600:1702:1031:3f90::1) icmp_seq=5 Destination unreachable: Address unreachable ^C --- yahoo.com ping statistics --- 6 packets transmitted, 0 received, +5 errors, 100% packet loss, time 5067ms

What does "ip -6 route show" say ?

ip -6 route show ::1 dev lo proto kernel metric 256 pref medium 2600:1702:1031:3f90::46d dev wlp7s0 proto kernel metric 600 pref medium 2600:1702:1031:3f90::4e4 dev wlp7s0 proto kernel metric 600 pref medium 2600:1702:1031:3f90::/64 dev wlp7s0 proto ra metric 600 pref medium 2600:1702:1031:3f90::/60 via fe80::de7f:a4ff:fe21:cd8d dev wlp7s0 proto ra metric 600 pref high fe80::/64 dev wlp7s0 proto kernel metric 600 pref medium default via fe80::de7f:a4ff:fe21:cd8d dev wlp7s0 proto ra metric 20600 pref medium

...

wtf is ping default ipv6 now

Has been for years.

...

I now have two wireless systems and four wired systems that fail pinging yahoo.com (or anywhere else except locally) unless "-4" is specified.

I guess you don't have ipv6 connectivity?

well, I did until yesterday :( tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri 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

On 09/08/2019 21.51, Patrick Shanahan wrote:

* Per Jessen <> [08-09-19 15:28]:

...

Patrick Shanahan wrote:

...

What does "ip -6 route show" say ?

ip -6 route show ::1 dev lo proto kernel metric 256 pref medium 2600:1702:1031:3f90::46d dev wlp7s0 proto kernel metric 600 pref medium 2600:1702:1031:3f90::4e4 dev wlp7s0 proto kernel metric 600 pref medium 2600:1702:1031:3f90::/64 dev wlp7s0 proto ra metric 600 pref medium 2600:1702:1031:3f90::/60 via fe80::de7f:a4ff:fe21:cd8d dev wlp7s0 proto ra metric 600 pref high fe80::/64 dev wlp7s0 proto kernel metric 600 pref medium default via fe80::de7f:a4ff:fe21:cd8d dev wlp7s0 proto ra metric 20600 pref medium

So you do have IPv6 to outside. From AT&T Corp. In that case, it does not matter if software prefers IPv6 or 4.

...

...

wtf is ping default ipv6 now

Has been for years.

...

I now have two wireless systems and four wired systems that fail pinging yahoo.com (or anywhere else except locally) unless "-4" is specified.

I guess you don't have ipv6 connectivity?

well, I did until yesterday :(

So, you have a problem with AT&T Corp, not with TW. Or your router. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

On 2019-08-09 03:51 PM, Patrick Shanahan wrote:

...

I guess you don't have ipv6 connectivity? well, I did until yesterday :(

What does traceroute show? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* James Knott [08-09-19 16:14]:

On 2019-08-09 03:51 PM, Patrick Shanahan wrote:

...

...

I guess you don't have ipv6 connectivity? well, I did until yesterday :(

What does traceroute show?

17:04 toshiba: ~ # traceroute yahoo.com traceroute to yahoo.com (98.137.246.7), 30 hops max, 60 byte packets 1 192.168.1.254 (192.168.1.254) 75.097 ms 87.902 ms 88.202 ms 2 75-30-84-1.lightspeed.plfdil.sbcglobal.net (75.30.84.1) 88.619 ms 88.604 ms 88.586 ms 3 71.152.198.37 (71.152.198.37) 88.568 ms 88.550 ms 88.532 ms 4 12.123.7.198 (12.123.7.198) 88.742 ms 98.528 ms 99.977 ms 5 cgcil403igs.ip.att.net (12.122.132.121) 98.442 ms 100.211 ms 100.196 ms 6 chi-b21-link.telia.net (213.248.87.253) 100.161 ms 67.918 ms 107.359 ms 7 sea-b2-link.telia.net (62.115.117.48) 159.482 ms 159.474 ms 159.452 ms 8 yahoo-ic-328471-sea-b2.c.telia.net (62.115.36.197) 159.432 ms 159.412 ms 159.383 ms 9 ae-5.pat1.gqb.yahoo.com (216.115.101.111) 178.379 ms ae-7.pat1.gqb.yahoo.com (216.115.96.45) 178.376 ms 178.354 ms 10 et-1-0-0.msr1.gq1.yahoo.com (66.196.67.101) 178.333 ms et-1-0-0.msr2.gq1.yahoo.com (66.196.67.113) 178.317 ms et-0-0-0.msr2.gq1.yahoo.com (66.196.67.109) 178.304 ms 11 et-19-1-0.clr2-a-gdc.gq1.yahoo.com (67.195.37.99) 178.293 ms et-1-1-0.clr2-a-gdc.gq1.yahoo.com (67.195.37.75) 178.264 ms et-19-1-0.clr1-a-gdc.gq1.yahoo.com (67.195.37.95) 178.214 ms 12 et-16-6.bas1-2-flk.gq1.yahoo.com (98.137.120.6) 100.840 ms 103.957 ms et-18-6.bas1-2-flk.gq1.yahoo.com (98.137.120.25) 103.911 ms 13 media-router-fp1.prod1.media.vip.gq1.yahoo.com (98.137.246.7) 103.866 ms 103.826 ms 103.783 ms -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri 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 [08-09-19 17:15]:

Try traceroute -6.

On 2019-08-09 05:07 PM, Patrick Shanahan wrote:

...

* James Knott [08-09-19 16:14]:

...

On 2019-08-09 03:51 PM, Patrick Shanahan wrote:

...

...

I guess you don't have ipv6 connectivity? well, I did until yesterday :( What does traceroute show?

17:04 toshiba: ~ # traceroute yahoo.com traceroute to yahoo.com (98.137.246.7), 30 hops max, 60 byte packets 1 192.168.1.254 (192.168.1.254) 75.097 ms 87.902 ms 88.202 ms 2 75-30-84-1.lightspeed.plfdil.sbcglobal.net (75.30.84.1) 88.619 ms 88.604 ms 88.586 ms 3 71.152.198.37 (71.152.198.37) 88.568 ms 88.550 ms 88.532 ms 4 12.123.7.198 (12.123.7.198) 88.742 ms 98.528 ms 99.977 ms 5 cgcil403igs.ip.att.net (12.122.132.121) 98.442 ms 100.211 ms 100.196 ms 6 chi-b21-link.telia.net (213.248.87.253) 100.161 ms 67.918 ms 107.359 ms 7 sea-b2-link.telia.net (62.115.117.48) 159.482 ms 159.474 ms 159.452 ms 8 yahoo-ic-328471-sea-b2.c.telia.net (62.115.36.197) 159.432 ms 159.412 ms 159.383 ms 9 ae-5.pat1.gqb.yahoo.com (216.115.101.111) 178.379 ms ae-7.pat1.gqb.yahoo.com (216.115.96.45) 178.376 ms 178.354 ms 10 et-1-0-0.msr1.gq1.yahoo.com (66.196.67.101) 178.333 ms et-1-0-0.msr2.gq1.yahoo.com (66.196.67.113) 178.317 ms et-0-0-0.msr2.gq1.yahoo.com (66.196.67.109) 178.304 ms 11 et-19-1-0.clr2-a-gdc.gq1.yahoo.com (67.195.37.99) 178.293 ms et-1-1-0.clr2-a-gdc.gq1.yahoo.com (67.195.37.75) 178.264 ms et-19-1-0.clr1-a-gdc.gq1.yahoo.com (67.195.37.95) 178.214 ms 12 et-16-6.bas1-2-flk.gq1.yahoo.com (98.137.120.6) 100.840 ms 103.957 ms et-18-6.bas1-2-flk.gq1.yahoo.com (98.137.120.25) 103.911 ms 13 media-router-fp1.prod1.media.vip.gq1.yahoo.com (98.137.246.7) 103.866 ms 103.826 ms 103.783 ms

traceroute to yahoo.com (2001:4998:44:41d::4), 30 hops max, 80 byte packets 1 2600:1702:1031:3f90::1 (2600:1702:1031:3f90::1) 13.736 ms 14.391 ms 71.196 ms 2 2001:506:6000:130:69:235:126:70 (2001:506:6000:130:69:235:126:70) 68.324 ms 77.807 ms 77.807 ms 3 2001:506:6000:130:69:235:126:67 (2001:506:6000:130:69:235:126:67) 77.776 ms 77.760 ms 77.738 ms 4 cgcil403igs.ipv6.att.net (2001:1890:ff:ffff:12:122:132:121) 71.047 ms 71.028 ms * 5 chi-b21-link.telia.net (2001:2000:3080:56f::1) 80.469 ms 80.461 ms 84.412 ms 6 yahoo-ic-314777-chi-b21.c.telia.net (2001:2000:3080:e6a::2) 87.082 ms 40.540 ms 75.615 ms 7 ae-7.pat2.nez.yahoo.com (2001:4998:f000:205::) 79.502 ms 79.487 ms ae-5.pat1.nez.yahoo.com (2001:4998:f000:3::) 116.298 ms 8 2001:4998:f000:10::1 (2001:4998:f000:10::1) 116.410 ms 2001:4998:f000:210::1 (2001:4998:f000:210::1) 79.404 ms 80.553 ms 9 2001:4998:44:fe1a::1 (2001:4998:44:fe1a::1) 81.086 ms 2001:4998:44:fc1c::1 (2001:4998:44:fc1c::1) 133.861 ms 2001:4998:44:fe1b::1 (2001:4998:44:fe1b::1) 87.893 ms 10 2001:4998:44:1::a2 (2001:4998:44:1::a2) 116.026 ms 2001:4998:44:fa13::1 (2001:4998:44:fa13::1) 115.906 ms 115.880 ms 11 media-router-fp2.prod1.media.vip.ne1.yahoo.com (2001:4998:44:41d::4) 115.714 ms 114.882 ms 115.032 ms I just reset the gateway. appears to have ?solved? the problem. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri 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

On 2019-08-09 05:50 PM, Patrick Shanahan wrote:

in 4 years I have gone thru 6 modem/routers and none performed acceptably the router functions. present one most acceptable but still lacking. when I complain they send me another and I test it before returning the older. currect count is 3 newer ones returned.

I use pfSense.  It works well and if you have multiple /64s, I have 256, you can split them off for whatever networks you want. PfSense is a free download, that you can run on a PC. https://www.pfsense.org You'll have to put your modem in bridge mode. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2019-08-09 06:53 PM, Patrick Shanahan wrote:

...

You'll have to put your modem in bridge mode. and what do you do for wireless?

I have a separate access point, which is about in the middle of my condo.  If I used the one in the modem, it would be at one end, with poor signal at the other. -- 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, 2019-08-09 at 17:03 -0400, Patrick Shanahan wrote:

* Carlos E. R. <> [08-09-19 16:02]:

...

On 09/08/2019 21.51, Patrick Shanahan wrote:

...

* Per Jessen <> [08-09-19 15:28]:

...

Patrick Shanahan wrote:

...

So you do have IPv6 to outside. From AT&T Corp.

In that case, it does not matter if software prefers IPv6 or 4.

but it does as unless I specify "ping -4" ping fails :(

Because your router failed, not openSUSE :-p

...

...

...

...

I now have two wireless systems and four wired systems that fail pinging yahoo.com (or anywhere else except locally) unless "-4" is specified.

I guess you don't have ipv6 connectivity?

well, I did until yesterday :(

So, you have a problem with AT&T Corp, not with TW. Or your router.

so you are saying my provider is faulty?

Or your router - and it was your router ;-) - -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXU5hqBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVOiEAn3EN0MOlv5HGQWPpiyer yQogIiCkAJ0WzgGVf9nIpc8TfX+qrZEoL4PmxQ== =/YqE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 10/08/2019 03:56, Patrick Shanahan wrote:

* James Knott [08-09-19 20:49]:

...

On 2019-08-09 06:53 PM, Patrick Shanahan wrote:

...

...

You'll have to put your modem in bridge mode. and what do you do for wireless?

I have a separate access point, which is about in the middle of my condo.  If I used the one in the modem, it would be at one end, with poor signal at the other.

I have a linksys repeater at the opposite end of the house from the modem which works "most" of the time

Side question: are linksys considered the 'goto' router brand for Linux users? I may need to replace a misbehaving router and it seems almost everything on the market now is linksys or tp-link, even Netgear has taken a back seat. Are there any brands to avoid? Is there any brand that still manufactures normal-looking routers not designed primarily to appeal to 14-year-old boys who dream of spaceships and 1980s supercars? gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

gumb wrote:

On 10/08/2019 03:56, Patrick Shanahan wrote:

...

* James Knott [08-09-19 20:49]:

...

On 2019-08-09 06:53 PM, Patrick Shanahan wrote:

...

...

You'll have to put your modem in bridge mode. and what do you do for wireless?

I have a separate access point, which is about in the middle of my condo.  If I used the one in the modem, it would be at one end, with poor signal at the other.

I have a linksys repeater at the opposite end of the house from the modem which works "most" of the time

Side question: are linksys considered the 'goto' router brand for Linux users? I may need to replace a misbehaving router and it seems almost everything on the market now is linksys or tp-link, even Netgear has taken a back seat. Are there any brands to avoid?

Is there any brand that still manufactures normal-looking routers not designed primarily to appeal to 14-year-old boys who dream of spaceships and 1980s supercars?

Zyxel, AVM (Fritz), Mikrotik, Lancom. -- Per Jessen, Zürich (18.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 Sat, 10 Aug 2019 10:12:38 +0200 gumb wrote:

On 10/08/2019 03:56, Patrick Shanahan wrote:

...

I have a linksys repeater at the opposite end of the house from the modem which works "most" of the time

Side question: are linksys considered the 'goto' router brand for Linux users? I may need to replace a misbehaving router and it seems almost everything on the market now is linksys or tp-link, even Netgear has taken a back seat. Are there any brands to avoid?

In this house, I won't ever buy anything from Linksys. I once used one of their products as an Internet router and it failed. When I phoned them, they agreed it was a warranty issue but insisted I had to send the failed unit back to them before they would send me a replacement. Since I wanted a working Internet connection, I went out and bought another router instead (a Belkin if memory serves), and resolved never to touch a Linksys product again. Since then I've used routers provided by my ISP - a Technicolor, followed by a Fritz!Box. They've both been trouble free. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Dave Howorth wrote:

On Sat, 10 Aug 2019 10:12:38 +0200 gumb wrote:

...

On 10/08/2019 03:56, Patrick Shanahan wrote:

...

...

I have a linksys repeater at the opposite end of the house from the modem which works "most" of the time

Side question: are linksys considered the 'goto' router brand for Linux users? I may need to replace a misbehaving router and it seems almost everything on the market now is linksys or tp-link, even Netgear has taken a back seat. Are there any brands to avoid?

In this house, I won't ever buy anything from Linksys. I once used one of their products as an Internet router and it failed. When I phoned them, they agreed it was a warranty issue but insisted I had to send the failed unit back to them before they would send me a replacement.

That is how most shops work here - get an RMA, send back failed, receive new. Linksys - I have used Linksys VoIP phones for the office and for home offices for years, SPA941 and SPA942. Brilliant kit. -- Per Jessen, Zürich (18.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 2019-08-10 06:37 AM, Dave Howorth wrote:

Since then I've used routers provided by my ISP - a Technicolor, followed by a Fritz!Box. They've both been trouble free.

The problem with that is they may be limited in what they can do.  For example, the firewall on my Hitron modem is very poor.  Also, I'd be limited to using only 1 of my 256 /64 prefixes and no IPv6 at all on the guest WiFi. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/10/2019 03:12 AM, gumb wrote:

Side question: are linksys considered the 'goto' router brand for Linux users? I may need to replace a misbehaving router and it seems almost everything on the market now is linksys or tp-link, even Netgear has taken a back seat. Are there any brands to avoid?

Is there any brand that still manufactures normal-looking routers not designed primarily to appeal to 14-year-old boys who dream of spaceships and 1980s supercars?

Netgear stands behind their products no-questions asked (well very few), I've run linksys, netgear, TEW and now tp-link Archer C7 AC1750 (best bang for the buck in 2019 router/wireless AP review - Amazon $71 w/free shipping) All I require wireless mac filtering and port-forwarding (for smtp, ssh, imaps, tls, http, https, and whatever else I happen to need) Pretty much all will have the basic functionality, though some limit mac filters to 20 addresses, etc. that can be a pain. All were pretty much the same. The couple of TEW I had were fine, but one lost the ability to forward port 80 -- it just died. The rest of the ports continued to work, who knows. I just gave https://www.pcmag.com/roundup/292110/the-best-wireless-routers a look and found the cheapest that met my needs. Read the review and it had fine throughput. You have two price groups. The ~$80 group and the $200-$400 group. Unless I need something that the cheaper ones can't provide, I can buy 3 for the price of one of the more expensive ones. I've always gotten 5-8 years out of each box, and by then, the next two or three versions of chips have come out making them practically obsolete. I have an easier time dealing with cheap obsolescence that the expensive type :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org