Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/23/2018 02:32 PM, Reco wrote:

Hi.

On Fri, Feb 23, 2018 at 02:24:13PM -0500, Stephen P. Molnar wrote:

Sorry it took me a while to get it, but:

root@Igor:~# netstat -nr -f inet6
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt Iface
0.0.0.0 192.168.1.254   0.0.0.0 UG0 0  0 enp0s12
192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 enp0s12

Hate to break it to you, but it's IPv4 routing table. "-f" does not
designate address family in net-tools' netstat.

What I meant was "ip -6 ro l", although "netstat -rn6" will do.



One, hopefully final, question.  In case I mess up, how do I enable IPv6?

Non-persistent:

echo 0 > /proc/sys/net/ipv6/conf/all/disable_ipv6

Persistent - remove appropriate line from /etc/sysctl.conf.
Invoke "sysctl --system"

Reco



I think I got it right this time:

root@Igor:/home/comp# netstat -rn6
Kernel IPv6 routing table
DestinationNext Hop   Flag Met Ref 
Use If
2600:1700:4280:3690::48/128:: Ue   256 1 
0 enp0s12
2600:1700:4280:3690::/64   :: U100 1 
0 enp0s12
2600:1700:4280:3690::/60   fe80::3e04:61ff:feb3:3c20  UG   100 1 
0 enp0s12
fe80::3e04:61ff:feb3:3c20/128  :: U100 1 
0 enp0s12
fe80::/64  :: U256 1 
0 enp0s12
::/0   fe80::3e04:61ff:feb3:3c20  UG   100 2 
8 enp0s12

::/0   :: !n   -1 1 9 lo
::1/128:: Un   0 3 3 lo
2600:1700:4280:3690::48/128:: Un   0 2 0 
enp0s12
2600:1700:4280:3690:2a0:ccff:fe78:c91f/128 :: 
Un   0   2 0 enp0s12
2600:1700:4280:3690:e0d8:d806:ce55:b634/128 :: 
Un   0   2 0 enp0s12
fe80::2a0:ccff:fe78:c91f/128   :: Un   0 3 3 
enp0s12
ff00::/8   :: U256 2
29 enp0s12

::/0   :: !n   -1 1 9 lo
root@Igor:/home/comp#

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

root@Igor:/home/comp# netstat -rn6
Kernel IPv6 routing table
DestinationNext Hop   Flag Met Ref Use If
2600:1700:4280:3690::48/128:: Ue   256 1 0 
enp0s12
2600:1700:4280:3690::/64   :: U100 1 0 
enp0s12
2600:1700:4280:3690::/60   fe80::3e04:61ff:feb3:3c20  UG   100 1 0 
enp0s12
fe80::3e04:61ff:feb3:3c20/128  :: U100 1 0 
enp0s12
fe80::/64  :: U256 1 0 
enp0s12
::/0   fe80::3e04:61ff:feb3:3c20  UG   100 2 8 
enp0s12
::/0   :: !n   -1  1 9 lo
::1/128:: Un   0   3 3 lo
2600:1700:4280:3690::48/128:: Un   0   2 0 
enp0s12
2600:1700:4280:3690:2a0:ccff:fe78:c91f/128 :: Un   0   
2 0 enp0s12
2600:1700:4280:3690:e0d8:d806:ce55:b634/128 :: Un   0   
2 0 enp0s12
fe80::2a0:ccff:fe78:c91f/128   :: Un   0   3 3 
enp0s12
ff00::/8   :: U256 229 
enp0s12
::/0   :: !n   -1  1 9 lo
root@Igor:/home/comp#

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Fri, Feb 23, 2018 at 02:24:13PM -0500, Stephen P. Molnar wrote:
> Sorry it took me a while to get it, but:
> 
> root@Igor:~# netstat -nr -f inet6
> Kernel IP routing table
> Destination Gateway Genmask Flags   MSS Window  irtt Iface
> 0.0.0.0 192.168.1.254   0.0.0.0 UG0 0  0 
> enp0s12
> 192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
> enp0s12

Hate to break it to you, but it's IPv4 routing table. "-f" does not
designate address family in net-tools' netstat.

What I meant was "ip -6 ro l", although "netstat -rn6" will do.


> One, hopefully final, question.  In case I mess up, how do I enable IPv6?

Non-persistent:

echo 0 > /proc/sys/net/ipv6/conf/all/disable_ipv6

Persistent - remove appropriate line from /etc/sysctl.conf.
Invoke "sysctl --system"

Reco

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/23/2018 01:02 PM, Reco wrote:

Hi.

On Fri, Feb 23, 2018 at 12:55:41PM -0500, Stephen P. Molnar wrote:

On 02/23/2018 12:34 PM, Reco wrote:

Hi.

On Fri, Feb 23, 2018 at 12:10:47PM -0500, Stephen P. Molnar wrote:

Of course, the above becomes moot, after I disable IPV6.

Exactly.



I have three other devices on my router, a Desktop, a Laptop and a Printer.
How will disabling IPv6 on the router affect them?

A printer should live. Assuming that's a good printer, not that modern
kids' toy that comes to Internet just for the heck of it.

A desktop and a laptop should not notice it. It depends on their OS of
course, but as long as you don't need to connect to them from outside
world via IPv6 - nobody will change for them.

What about just disabling IPv6 on the platform that's having the problem?
How can I do that?

echo net.ipv6.conf.all.disable_ipv6 = 1 >> /etc/sysctl.conf



Also, just out of curiosity I installed Stretch in a VirtualBox on this
computer and it isn't having any problems with IPv6.

That's … unexpected. But, assuming you're using VirtualBox NAT -
explainable.
But if you're using VirtualBox's bridged connection - what would be
interesting.



The other Desktop is an older 32 bit computer that used to run WindowsXP on
which I installed the 32 bit version of Stretch  It isn't having any
problems, other than those that can be ascribed to a tired platform way past
it's prime.

Care to share IPv6 routing table from this another host?

Reco



Sorry it took me a while to get it, but:

root@Igor:~# netstat -nr -f inet6
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt Iface
0.0.0.0 192.168.1.254   0.0.0.0 UG0 0  0 enp0s12
192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 enp0s12

One, hopefully final, question.  In case I mess up, how do I enable IPv6?

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Fri, Feb 23, 2018 at 12:55:41PM -0500, Stephen P. Molnar wrote:
> 
> On 02/23/2018 12:34 PM, Reco wrote:
> > Hi.
> > 
> > On Fri, Feb 23, 2018 at 12:10:47PM -0500, Stephen P. Molnar wrote:
> > > Of course, the above becomes moot, after I disable IPV6.
> > Exactly.
> > 
> > 
> > > I have three other devices on my router, a Desktop, a Laptop and a 
> > > Printer.
> > > How will disabling IPv6 on the router affect them?
> > A printer should live. Assuming that's a good printer, not that modern
> > kids' toy that comes to Internet just for the heck of it.
> > 
> > A desktop and a laptop should not notice it. It depends on their OS of
> > course, but as long as you don't need to connect to them from outside
> > world via IPv6 - nobody will change for them.
>
> What about just disabling IPv6 on the platform that's having the problem?
> How can I do that?

echo net.ipv6.conf.all.disable_ipv6 = 1 >> /etc/sysctl.conf


> Also, just out of curiosity I installed Stretch in a VirtualBox on this
> computer and it isn't having any problems with IPv6.

That's … unexpected. But, assuming you're using VirtualBox NAT -
explainable.
But if you're using VirtualBox's bridged connection - what would be
interesting.


> The other Desktop is an older 32 bit computer that used to run WindowsXP on
> which I installed the 32 bit version of Stretch  It isn't having any
> problems, other than those that can be ascribed to a tired platform way past
> it's prime.

Care to share IPv6 routing table from this another host?

Reco

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/23/2018 12:34 PM, Reco wrote:

Hi.

On Fri, Feb 23, 2018 at 12:10:47PM -0500, Stephen P. Molnar wrote:

Of course, the above becomes moot, after I disable IPV6.

Exactly.



I have three other devices on my router, a Desktop, a Laptop and a Printer.
How will disabling IPv6 on the router affect them?

A printer should live. Assuming that's a good printer, not that modern
kids' toy that comes to Internet just for the heck of it.

A desktop and a laptop should not notice it. It depends on their OS of
course, but as long as you don't need to connect to them from outside
world via IPv6 - nobody will change for them.

Reco


What about just disabling IPv6 on the platform that's having the 
problem?  How can I do that?


Also, just out of curiosity I installed Stretch in a VirtualBox on this 
computer and it isn't having any problems with IPv6.


The other Desktop is an older 32 bit computer that used to run WindowsXP 
on which I installed the 32 bit version of Stretch  It isn't having any 
problems, other than those that can be ascribed to a tired platform way 
past it's prime.


--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Fri, Feb 23, 2018 at 12:10:47PM -0500, Stephen P. Molnar wrote:
> Of course, the above becomes moot, after I disable IPV6.

Exactly.


> I have three other devices on my router, a Desktop, a Laptop and a Printer.
> How will disabling IPv6 on the router affect them?

A printer should live. Assuming that's a good printer, not that modern
kids' toy that comes to Internet just for the heck of it.

A desktop and a laptop should not notice it. It depends on their OS of
course, but as long as you don't need to connect to them from outside
world via IPv6 - nobody will change for them.

Reco

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/23/2018 11:30 AM, Reco wrote:

Hi.

On Fri, Feb 23, 2018 at 10:45:24AM -0500, Stephen P. Molnar wrote:

root@AbNormal:/home/comp# ip netns exec test ip a l
3: net0@if2:  mtu 1500 qdisc noqueue state
UP group default qlen 1000
 link/ether be:80:71:d1:8a:96 brd ff:ff:ff:ff:ff:ff link-netnsid 0
 inet6 2600:1700:4280:3690:bc80:71ff:fed1:8a96/64 scope global mngtmpaddr
dynamic
valid_lft 1209450sec preferred_lft 1209450sec
 inet6 fe80::bc80:71ff:fed1:8a96/64 scope link
valid_lft forever preferred_lft forever

So, I have a good news, and a bad news.
Good news being - I honestly don't know how you were able to achieve
*that* IPv6 configuration in a primary network namespace, but in this
separate network namespace things look reasonable.
You have one RA-provided IPv6 address, which is normal if one disables
IPv6 privacy extensions (they are disabled by default, btw).



root@AbNormal:/home/comp# ip netns exec test ip -6 ro l
2600:1700:4280:3690::/64 dev net0 proto kernel metric 256  expires
1209439sec pref medium
fe80::/64 dev net0 proto kernel metric 256  pref medium
default via fe80::3e04:61ff:feb3:3c20 dev net0 proto ra metric 1024 expires
1639sec hoplimit 64 pref medium

And you have perfectly normal IPv6 routing table, with RA-provided
default route.



root@AbNormal:/home/comp# ip netns exec test traceroute -n
2a02:16a8:dc41:100::233
traceroute to 2a02:16a8:dc41:100::233 (2a02:16a8:dc41:100::233), 30 hops
max, 80 byte packets
  1  * * *

Which brings me to the bad news.
Whatever router you're using refuses forwarding your IPv6 packets.

It does not matter if it drops the packets, or sends your host some
"refused" messages via SNMP - the thing fails to perform its primary
function.

I deliberately stay clear from SOHO routers, regardless of whoever
produced them, so I cannot help you here. In fact, I choose mine with
exactly one quality in mind - an ability to run Debian. Which I
installed on it the moment they delivered me the thing.

Best advice I can give - get yourself something that can be flashed with
openwrt.
Until then - disable IPv6 on your router altogether, it's not going to
work.

Reco




I realoly hate to have to send this, but I had occasion to restart the 
OS and this is what Igot:


root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Get:2 http://debian.uchicago.edu/debian stretch-updates InRelease [91.0 kB]
Get:3 http://debian.uchicago.edu/debian stretch-backports InRelease 
[91.8 kB]

Hit:4 http://debian.uchicago.edu/debian stretch Release
Get:5 http://debian.uchicago.edu/debian stretch-backports/main 
Sources.diff/Index [27.8 kB]
Get:6 http://debian.uchicago.edu/debian stretch-backports/main amd64 
Packages.diff/Index [27.8 kB]
Get:7 http://debian.uchicago.edu/debian stretch-backports/main Sources 
2018-02-23-1422.59.pdiff [871 B]
Get:7 http://debian.uchicago.edu/debian stretch-backports/main Sources 
2018-02-23-1422.59.pdiff [871 B]
Get:8 http://debian.uchicago.edu/debian stretch-backports/main amd64 
Packages 2018-02-23-1422.59.pdiff [802 B]
Get:8 http://debian.uchicago.edu/debian stretch-backports/main amd64 
Packages 2018-02-23-1422.59.pdiff [802 B]

0% [Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

Then, after about 30 seconds I got:

Hit:10 http://security.debian.org/debian-security stretch/updates InRelease
Fetched 240 kB in 2min 0s (1,991 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

Of course, the above becomes moot, after I disable IPV6.

I have three other devices on my router, a Desktop, a Laptop and a 
Printer.  How will disabling IPv6 on the router affect them?


--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Fri, Feb 23, 2018 at 10:45:24AM -0500, Stephen P. Molnar wrote:
> root@AbNormal:/home/comp# ip netns exec test ip a l
> 3: net0@if2:  mtu 1500 qdisc noqueue state
> UP group default qlen 1000
> link/ether be:80:71:d1:8a:96 brd ff:ff:ff:ff:ff:ff link-netnsid 0
> inet6 2600:1700:4280:3690:bc80:71ff:fed1:8a96/64 scope global mngtmpaddr
> dynamic
>valid_lft 1209450sec preferred_lft 1209450sec
> inet6 fe80::bc80:71ff:fed1:8a96/64 scope link
>valid_lft forever preferred_lft forever

So, I have a good news, and a bad news.
Good news being - I honestly don't know how you were able to achieve
*that* IPv6 configuration in a primary network namespace, but in this
separate network namespace things look reasonable.
You have one RA-provided IPv6 address, which is normal if one disables
IPv6 privacy extensions (they are disabled by default, btw).


> root@AbNormal:/home/comp# ip netns exec test ip -6 ro l
> 2600:1700:4280:3690::/64 dev net0 proto kernel metric 256  expires
> 1209439sec pref medium
> fe80::/64 dev net0 proto kernel metric 256  pref medium
> default via fe80::3e04:61ff:feb3:3c20 dev net0 proto ra metric 1024 expires
> 1639sec hoplimit 64 pref medium

And you have perfectly normal IPv6 routing table, with RA-provided
default route.


> root@AbNormal:/home/comp# ip netns exec test traceroute -n
> 2a02:16a8:dc41:100::233
> traceroute to 2a02:16a8:dc41:100::233 (2a02:16a8:dc41:100::233), 30 hops
> max, 80 byte packets
>  1  * * *

Which brings me to the bad news.
Whatever router you're using refuses forwarding your IPv6 packets.

It does not matter if it drops the packets, or sends your host some
"refused" messages via SNMP - the thing fails to perform its primary
function.

I deliberately stay clear from SOHO routers, regardless of whoever
produced them, so I cannot help you here. In fact, I choose mine with
exactly one quality in mind - an ability to run Debian. Which I
installed on it the moment they delivered me the thing.

Best advice I can give - get yourself something that can be flashed with
openwrt.
Until then - disable IPv6 on your router altogether, it's not going to
work.

Reco

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/23/2018 10:09 AM, Reco wrote:

Hi.

On Fri, Feb 23, 2018 at 09:57:07AM -0500, Stephen P. Molnar wrote:

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://debian.uchicago.edu/debian stretch-backports InRelease
Hit:4 http://debian.uchicago.edu/debian stretch Release
Hit:6 http://security.debian.org/debian-security stretch/updates
InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

with a long pause before it finished.

And now, let's return to the malfunctioning IPv6.

Let's sum it up first:


2600:1700:4280:3690::46 dev enp2s0 proto kernel metric 256  expires
1201893sec pref medium

You have /128 address given you by your router.


2600:1700:4280:3690::/64 dev enp2s0 proto ra metric 100  pref medium

And, you have your usual /64 route from /64 address procured by RA.


2600:1700:4280:3690::/60 via fe80::3e04:61ff:feb3:3c20 dev enp2s0
proto ra metric 100  pref medium

But, you have /60 route with the gateway address, which should serve the
purpose of connecting to *other* IPv6 addresses from /60 block that's
assigned to you. Unusual, but probably OK.


fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 100  pref
medium
fe80::/64 dev enp2s0 proto kernel metric 256  pref medium

These are your usual link-local routes.


default via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric
100 pref medium

And that's fishy. Why is this route is designated as "proto static",
i.e.
added by hand? Kernel RA does not work like this.


Assuming that your router is configured correctly (i.e. the way AT
want it to be configured), that points us to the whatever your host is
using for the network configuration.

So let's put it aside for the moment. A quick test like this should
clear things a bit (everything that's in here requires root):

ip netns add test
ip link add link enp2s0 name net0 type macvlan mode private
ip link set net0 netns test
ip netns exec test ip link set lo up
ip netns exec test ip link set net0 up
sleep 120
ip netns exec test ip a l
ip netns exec test ip -6 ro l
ip netns exec test traceroute -n 2a02:16a8:dc41:100::233
ip netns del test

Basically, that creates a separate network namespace, clones your wired
NIC into it, waits for the kernel RA autoconfiguration to kick in, and
destroys it.

Reco



Here's what happened:

root@AbNormal:/home/comp# ip link add link enp2s0 name net0 type macvlan 
mode private

root@AbNormal:/home/comp# ip link set net0 netns test
root@AbNormal:/home/comp# ip netns exec test ip link set lo up
root@AbNormal:/home/comp# ip netns exec test ip link set net0 up
root@AbNormal:/home/comp# sleep 120
root@AbNormal:/home/comp# ip netns exec test ip a l
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
3: net0@if2:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000

link/ether be:80:71:d1:8a:96 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 2600:1700:4280:3690:bc80:71ff:fed1:8a96/64 scope global 
mngtmpaddr dynamic

   valid_lft 1209450sec preferred_lft 1209450sec
inet6 fe80::bc80:71ff:fed1:8a96/64 scope link
   valid_lft forever preferred_lft forever
root@AbNormal:/home/comp# ip netns exec test ip -6 ro l
2600:1700:4280:3690::/64 dev net0 proto kernel metric 256  expires 
1209439sec pref medium

fe80::/64 dev net0 proto kernel metric 256  pref medium
default via fe80::3e04:61ff:feb3:3c20 dev net0 proto ra metric 1024 
expires 1639sec hoplimit 64 pref medium
root@AbNormal:/home/comp# ip netns exec test traceroute -n 
2a02:16a8:dc41:100::233
traceroute to 2a02:16a8:dc41:100::233 (2a02:16a8:dc41:100::233), 30 hops 
max, 80 byte packets

 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
root@AbNormal:/home/comp# ip netns del test
root@AbNormal:/home/comp#

And then;

root@AbNormal:/home/comp# apt update
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://debian.uchicago.edu/debian stretch InRelease
Hit:3 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:4 http://debian.uchicago.edu/debian stretch-backports InRelease
Hit:5 http://debian.uchicago.edu/debian stretch Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
root@AbNormal:/home/comp#

Oh, yes.

apt-get install bvi:i386 and apt-get 

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Fri, Feb 23, 2018 at 09:57:07AM -0500, Stephen P. Molnar wrote:
> > > root@AbNormal:/home/comp# apt update
> > > Ign:1 http://debian.uchicago.edu/debian stretch InRelease
> > > Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
> > > Hit:3 http://debian.uchicago.edu/debian stretch-backports InRelease
> > > Hit:4 http://debian.uchicago.edu/debian stretch Release
> > > Hit:6 http://security.debian.org/debian-security stretch/updates
> > > InRelease
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > All packages are up to date.
> > > 
> > > with a long pause before it finished.

And now, let's return to the malfunctioning IPv6.

Let's sum it up first:

> 2600:1700:4280:3690::46 dev enp2s0 proto kernel metric 256  expires
> 1201893sec pref medium

You have /128 address given you by your router.

> 2600:1700:4280:3690::/64 dev enp2s0 proto ra metric 100  pref medium

And, you have your usual /64 route from /64 address procured by RA.

> 2600:1700:4280:3690::/60 via fe80::3e04:61ff:feb3:3c20 dev enp2s0
> proto ra metric 100  pref medium

But, you have /60 route with the gateway address, which should serve the
purpose of connecting to *other* IPv6 addresses from /60 block that's
assigned to you. Unusual, but probably OK.

> fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 100  pref
> medium
> fe80::/64 dev enp2s0 proto kernel metric 256  pref medium

These are your usual link-local routes.

> default via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric
> 100 pref medium

And that's fishy. Why is this route is designated as "proto static",
i.e.
added by hand? Kernel RA does not work like this.


Assuming that your router is configured correctly (i.e. the way AT
want it to be configured), that points us to the whatever your host is
using for the network configuration.

So let's put it aside for the moment. A quick test like this should
clear things a bit (everything that's in here requires root):

ip netns add test
ip link add link enp2s0 name net0 type macvlan mode private
ip link set net0 netns test
ip netns exec test ip link set lo up
ip netns exec test ip link set net0 up
sleep 120
ip netns exec test ip a l
ip netns exec test ip -6 ro l
ip netns exec test traceroute -n 2a02:16a8:dc41:100::233
ip netns del test

Basically, that creates a separate network namespace, clones your wired
NIC into it, waits for the kernel RA autoconfiguration to kick in, and
destroys it.

Reco

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Fri, Feb 23, 2018 at 09:57:07AM -0500, Stephen P. Molnar wrote:
> > Therefore, it's no wonder that apt is still broken for you, in regards
> > of downloading.
> > 
> > Second, let's check if your i386 arch is really operational.
> > 
> > apt-cache policy bash:i386
> > 
> Here's what you requested.
> 
> root@AbNormal:/home/comp# apt-cache policy bash:i386
> bash:i386:
>   Installed: (none)
>   Candidate: 4.4-5
>   Version table:
>  4.4-5 500
> 500 http://debian.uchicago.edu/debian stretch/main i386 Packages

And that's a good thing. On my non-multiarch system that gives:

$ apt-cache policy bash:i386
N: Unable to locate package bash:i386

I conclude that you should be able to install i386 packages without any
trouble. Let's test it just to be sure.

apt-get install bvi:i386

apt-get purge bvi:i386

Reco

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/23/2018 09:27 AM, Reco wrote:

Hi.

Moved this to correct thread.


Interesting,

The only entry in Synaptic for DHCP was kea-dhcp6-server. Synaptic
installed:

kea-common (1.1.0-1)
kea-dhcp6-server (1.1.0-1)
liblog4cplus-1.1-9 (1.1.2-3.2)

Now, when I do  apt update I get:

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://security.debian.org/debian-security stretch/updates
InRelease
Hit:4 http://debian.uchicago.edu/debian stretch Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

Although if I do:

root@AbNormal:/home/comp# dpkg --add-architecture i386
root@AbNormal:/home/comp# spt update

then

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://debian.uchicago.edu/debian stretch Release
Hit:4 http://security.debian.org/debian-security stretch/updates
InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

but, gdebi happily installed acroread, which requires i386 libraries,
there were no warning or error messages.  Acroread works notmally.

This is a bit later than the above message.

I added backports to /etc/apt/sources.list

# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD
# Binary-1
20171209-12:11]/ stretch contrib main

# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD
# Binary-1
20171209-12:11]/ stretch main contrib

deb http://debian.uchicago.edu/debian/ stretch main non-free contrib
deb-src http://debian.uchicago.edu/debian/ stretch main non-free contrib

deb http://security.debian.org/debian-security/ stretch/updates main
contrib
non-free
deb-src http://security.debian.org/debian-security/ stretch/updates main
contrib non-free

# stretch-updates, previously known as 'volatile'
deb http://debian.uchicago.edu/debian/ stretch-updates main contrib
non-free
deb-src http://debian.uchicago.edu/debian/ stretch-updates main contrib
non-free

deb http://debian.uchicago.edu/debian/ stretch-backports main contrib
non-free
deb-src http://debian.uchicago.edu/debian/ stretch-backports main
contrib
non-free

the I rebooted the system and got

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://debian.uchicago.edu/debian stretch-backports InRelease
Hit:4 http://debian.uchicago.edu/debian stretch Release
Hit:6 http://security.debian.org/debian-security stretch/updates
InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

with a long pause before it finished.

Then I ran sysctl -w net.ipv6.conf.all.disable_ipv6=1 (as root) and got
the
same result from apt update, but without the pause.  Still no listing
for
i386.

So, first things first. Your setup is different from Roger Price's.
Whenever you have DHCPv6-capable client or not is not relevant, as
you're using in-kernel RA for that (presumably).

Therefore, it's no wonder that apt is still broken for you, in regards
of downloading.

Second, let's check if your i386 arch is really operational.

apt-cache policy bash:i386

Reco



Sorry about picking the wrong thread.   Unfortunately, I resent the 
message to this thread before seeing this reply.


My apologies to the debian-users list for wasting the bandwidth.

Here's what you requested.

root@AbNormal:/home/comp# apt-cache policy bash:i386
bash:i386:
  Installed: (none)
  Candidate: 4.4-5
  Version table:
 4.4-5 500
500 http://debian.uchicago.edu/debian stretch/main i386 Packages
root@AbNormal:/home/comp#





--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/23/2018 08:38 AM, Stephen P. Molnar wrote:


On 02/23/2018 07:12 AM, Reco wrote:

Hi.

On Fri, Feb 23, 2018 at 12:22:26PM +0100, Roger Price wrote:

On Thu, 22 Feb 2018, Reco wrote:


On the EeePC Ctl-Alt-F3 /dev/tty3:
  ~ # ip address
  3: enp0s4:  ...
...
inet 10.218.0.100 scope global enp0s4
inet6 fe80::22cf:30ff:fe10:43fd/64 scope link

The "fe" at the beginning of the IPv6 address says that this is 
not capable

of working with the public IPv6 network.

There's one crucial detail that's missing here. I agree that fe80
designates link-local IPv6 (they don't put "scope link" there for
nothing), but what about routing?
I.e. I'm curious about the output of "ip -6 ro l".

rprice@kananga:~$ ip -6 ro l
fe80::/64 dev wlan0 proto kernel metric 256  pref medium

Now *that* actually means it should be impossible for this host to
connect to 2001:41d0:202:100:213:32:5:7.

So either we have a little wonder here, or ... do you have DHCP6 client
installed there by chance? Installer most certainly should include one,
and that could explain the difference in behavior between your current
host and d-i.

Reco



Interesting,

The only entry in Synaptic for DHCP was kea-dhcp6-server. Synaptic 
installed:


kea-common (1.1.0-1)
kea-dhcp6-server (1.1.0-1)
liblog4cplus-1.1-9 (1.1.2-3.2)

Now, when I do  apt update I get:

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://security.debian.org/debian-security stretch/updates 
InRelease

Hit:4 http://debian.uchicago.edu/debian stretch Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

Although if I do:

root@AbNormal:/home/comp# dpkg --add-architecture i386
root@AbNormal:/home/comp# spt update

then

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://debian.uchicago.edu/debian stretch Release
Hit:4 http://security.debian.org/debian-security stretch/updates 
InRelease

Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

but, gdebi happily installed acroread, which requires i386 libraries, 
there were no warning or error messages.  Acroread works notmally.



This is a bit later than the above message.

I added backports to /etc/apt/sources.list

# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD 
Binary-1 20171209-12:11]/ stretch contrib main


# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD 
Binary-1 20171209-12:11]/ stretch main contrib


deb http://debian.uchicago.edu/debian/ stretch main non-free contrib
deb-src http://debian.uchicago.edu/debian/ stretch main non-free contrib

deb http://security.debian.org/debian-security/ stretch/updates main 
contrib non-free
deb-src http://security.debian.org/debian-security/ stretch/updates main 
contrib non-free


# stretch-updates, previously known as 'volatile'
deb http://debian.uchicago.edu/debian/ stretch-updates main contrib 
non-free
deb-src http://debian.uchicago.edu/debian/ stretch-updates main contrib 
non-free


deb http://debian.uchicago.edu/debian/ stretch-backports main contrib 
non-free
deb-src http://debian.uchicago.edu/debian/ stretch-backports main 
contrib non-free


the I rebooted the system and got

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://debian.uchicago.edu/debian stretch-backports InRelease
Hit:4 http://debian.uchicago.edu/debian stretch Release
Hit:6 http://security.debian.org/debian-security stretch/updates InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

with a long pause before it finished.

Then I ran sysctl -w net.ipv6.conf.all.disable_ipv6=1 (as root) and got 
the same result from apt update, but without the pause.  Still no 
listing for i386.




--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

Moved this to correct thread.

> Interesting,
>
> The only entry in Synaptic for DHCP was kea-dhcp6-server. Synaptic
> installed:
>
> kea-common (1.1.0-1)
> kea-dhcp6-server (1.1.0-1)
> liblog4cplus-1.1-9 (1.1.2-3.2)
>
> Now, when I do  apt update I get:
>
> root@AbNormal:/home/comp# apt update
> Ign:1 http://debian.uchicago.edu/debian stretch InRelease
> Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
> Hit:3 http://security.debian.org/debian-security stretch/updates
> InRelease
> Hit:4 http://debian.uchicago.edu/debian stretch Release
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> All packages are up to date.
>
> Although if I do:
>
> root@AbNormal:/home/comp# dpkg --add-architecture i386
> root@AbNormal:/home/comp# spt update
>
> then
>
> root@AbNormal:/home/comp# apt update
> Ign:1 http://debian.uchicago.edu/debian stretch InRelease
> Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
> Hit:3 http://debian.uchicago.edu/debian stretch Release
> Hit:4 http://security.debian.org/debian-security stretch/updates
> InRelease
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> All packages are up to date.
>
> but, gdebi happily installed acroread, which requires i386 libraries,
> there were no warning or error messages.  Acroread works notmally.
>

>This is a bit later than the above message.
>
>I added backports to /etc/apt/sources.list
>
># deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD
># Binary-1
>20171209-12:11]/ stretch contrib main
>
># deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD
># Binary-1
>20171209-12:11]/ stretch main contrib
>
>deb http://debian.uchicago.edu/debian/ stretch main non-free contrib
>deb-src http://debian.uchicago.edu/debian/ stretch main non-free contrib
>
>deb http://security.debian.org/debian-security/ stretch/updates main
>contrib
>non-free
>deb-src http://security.debian.org/debian-security/ stretch/updates main
>contrib non-free
>
># stretch-updates, previously known as 'volatile'
>deb http://debian.uchicago.edu/debian/ stretch-updates main contrib
>non-free
>deb-src http://debian.uchicago.edu/debian/ stretch-updates main contrib
>non-free
>
>deb http://debian.uchicago.edu/debian/ stretch-backports main contrib
>non-free
>deb-src http://debian.uchicago.edu/debian/ stretch-backports main
>contrib
>non-free
>
>the I rebooted the system and got
>
>root@AbNormal:/home/comp# apt update
>Ign:1 http://debian.uchicago.edu/debian stretch InRelease
>Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
>Hit:3 http://debian.uchicago.edu/debian stretch-backports InRelease
>Hit:4 http://debian.uchicago.edu/debian stretch Release
>Hit:6 http://security.debian.org/debian-security stretch/updates
>InRelease
>Reading package lists... Done
>Building dependency tree
>Reading state information... Done
>All packages are up to date.
>
>with a long pause before it finished.
>
>Then I ran sysctl -w net.ipv6.conf.all.disable_ipv6=1 (as root) and got
>the
>same result from apt update, but without the pause.  Still no listing
>for
>i386.

So, first things first. Your setup is different from Roger Price's.
Whenever you have DHCPv6-capable client or not is not relevant, as
you're using in-kernel RA for that (presumably).

Therefore, it's no wonder that apt is still broken for you, in regards
of downloading.

Second, let's check if your i386 arch is really operational.

apt-cache policy bash:i386

Reco

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Thu, Feb 22, 2018 at 03:48:13PM -0500, Stephen P. Molnar wrote:
> > I need to think about it. I have that feeling that I'm missing something
> > trivial.

> I will appreciate your further thoughts.
> 
> Frankly, I don't have much confidence as far as AT being of any help.  The
> installer that Upgraded us to a fiber optic network was quite knowledgeable,
> but had played with Linux a bit in the past but got discouraged.
> 
> At this ;point by day is done.
> 
> More tomorrow.

So, a new day, new thoughts.

Let's sum it up first:

> 2600:1700:4280:3690::46 dev enp2s0 proto kernel metric 256  expires 
> 1201893sec pref medium

You have /128 address given you by your router.

> 2600:1700:4280:3690::/64 dev enp2s0 proto ra metric 100  pref medium

And, you have your usual /64 route from /64 address procured by RA.

> 2600:1700:4280:3690::/60 via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto ra 
> metric 100  pref medium

But, you have /60 route with the gateway address, which should serve the
purpose of connecting to *other* IPv6 addresses from /60 block that's
assigned to you. Unusual, but probably OK.

> fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 100  pref medium
> fe80::/64 dev enp2s0 proto kernel metric 256  pref medium

These are your usual link-local routes.

> default via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 100 pref 
> medium

And that's fishy. Why is this route is designated as "proto static", i.e.
added by hand? Kernel RA does not work like this.


Assuming that your router is configured correctly (i.e. the way AT
want it to be configured), that points us to the whatever your host is
using for the network configuration.

So let's put it aside for the moment. A quick test like this should
clear things a bit (everything that's in here requires root):

ip netns add test
ip link add link enp2s0 name net0 type macvlan mode private
ip link set net0 netns test
ip netns exec test ip link set lo up
ip netns exec test ip link set net0 up
sleep 120
ip netns exec test ip a l
ip netns exec test ip -6 ro l
ip netns exec test traceroute -n 2a02:16a8:dc41:100::233
ip netns del test

Basically, that creates a separate network namespace, clones your wired
NIC into it, waits for the kernel RA autoconfiguration to kick in, and
destroys it.

Reco

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/22/2018 03:13 PM, Reco wrote:

Hi.

On Thu, Feb 22, 2018 at 02:36:36PM -0500, Stephen P. Molnar wrote:

On 02/22/2018 01:59 PM, Reco wrote:

Hi.

On Thu, Feb 22, 2018 at 01:40:45PM -0500, Stephen P. Molnar wrote:

2) redone:

root@AbNormal:/home/comp#
root@AbNormal:/home/comp# ip a d 2600:1700:4280:3690::46/128 dev enp2s0
root@AbNormal:/home/comp#
root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
packets
   1  * * *

That either means that AT is doing something very clever, or I
don't understand what's going on. Or both.

Ok, next part. Reset your network settings.

Check your IPv6 "readiness" by visiting [1] and performing appropriate
link clicks according to [2].

Oh, and the file - /tmp/fastly.pcap . I'm still interested in it.

[1] http://www.att.com/esupport/ipv6.jsp

[2] 
https://rolande.wordpress.com/2014/05/16/enabling-ipv6-on-my-home-network-part-2-att/

The missing file is attached.

The contents are different from what I hoped for. Two TCP IPv4 packets,
and that's it. Does not clarify things at all.



OK.

I went to URL #1  and ran their compatibility test.  The result was:

Alert!
Unfortunately, we are unable to access Troubleshoot & Resolve at this time.
For further assistance, please visit att.com/esupport
.

Translating from AT lingua that's probably means that you should not
have IPv6, or that /60 block they assigned to you does not function.
Or not. I suggest you to clear it with them.



However, when I logged in to my router it showed the Broadband configured
rot all ports 1 through 4 and being 'Auto', and IPv6 is shown as 'On' for
IPv6, DHCPv6 and DHPv6 Prefix Delegation and with the Router Advertisement
MTU WITH A VALUE OF 1500.

That's unusual. For IPv6 it should be 1480 if they are still using
tunnel. But it does not explain traceroute problem (a typical traceroute
packet size is much smaller).


I need to think about it. I have that feeling that I'm missing something
trivial.

Reco



I will appreciate your further thoughts.

Frankly, I don't have much confidence as far as AT being of any help.  
The installer that Upgraded us to a fiber optic network was quite 
knowledgeable, but had played with Linux a bit in the past but got 
discouraged.


At this ;point by day is done.

More tomorrow.

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Thu, Feb 22, 2018 at 02:36:36PM -0500, Stephen P. Molnar wrote:
> 
> On 02/22/2018 01:59 PM, Reco wrote:
> > Hi.
> > 
> > On Thu, Feb 22, 2018 at 01:40:45PM -0500, Stephen P. Molnar wrote:
> > >2) redone:
> > > 
> > > root@AbNormal:/home/comp#
> > > root@AbNormal:/home/comp# ip a d 2600:1700:4280:3690::46/128 dev enp2s0
> > > root@AbNormal:/home/comp#
> > > root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
> > > traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
> > > packets
> > >   1  * * *
> > That either means that AT is doing something very clever, or I
> > don't understand what's going on. Or both.
> > 
> > Ok, next part. Reset your network settings.
> > 
> > Check your IPv6 "readiness" by visiting [1] and performing appropriate
> > link clicks according to [2].
> > 
> > Oh, and the file - /tmp/fastly.pcap . I'm still interested in it.
> > 
> > [1] http://www.att.com/esupport/ipv6.jsp
> > 
> > [2] 
> > https://rolande.wordpress.com/2014/05/16/enabling-ipv6-on-my-home-network-part-2-att/
> 
> The missing file is attached.

The contents are different from what I hoped for. Two TCP IPv4 packets,
and that's it. Does not clarify things at all.


> OK.
> 
> I went to URL #1  and ran their compatibility test.  The result was:
> 
> Alert!
> Unfortunately, we are unable to access Troubleshoot & Resolve at this time.
> For further assistance, please visit att.com/esupport
> .

Translating from AT lingua that's probably means that you should not
have IPv6, or that /60 block they assigned to you does not function.
Or not. I suggest you to clear it with them.


> However, when I logged in to my router it showed the Broadband configured
> rot all ports 1 through 4 and being 'Auto', and IPv6 is shown as 'On' for
> IPv6, DHCPv6 and DHPv6 Prefix Delegation and with the Router Advertisement
> MTU WITH A VALUE OF 1500.

That's unusual. For IPv6 it should be 1480 if they are still using
tunnel. But it does not explain traceroute problem (a typical traceroute
packet size is much smaller).


I need to think about it. I have that feeling that I'm missing something
trivial.

Reco

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/22/2018 01:59 PM, Reco wrote:

Hi.

On Thu, Feb 22, 2018 at 01:40:45PM -0500, Stephen P. Molnar wrote:

   2) redone:

root@AbNormal:/home/comp#
root@AbNormal:/home/comp# ip a d 2600:1700:4280:3690::46/128 dev enp2s0
root@AbNormal:/home/comp#
root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
packets
  1  * * *

That either means that AT is doing something very clever, or I
don't understand what's going on. Or both.

Ok, next part. Reset your network settings.

Check your IPv6 "readiness" by visiting [1] and performing appropriate
link clicks according to [2].

Oh, and the file - /tmp/fastly.pcap . I'm still interested in it.

[1] http://www.att.com/esupport/ipv6.jsp

[2] 
https://rolande.wordpress.com/2014/05/16/enabling-ipv6-on-my-home-network-part-2-att/

Reco



Reco

The missing file is attached.

OK.

I went to URL #1  and ran their compatibility test.  The result was:

Alert!
Unfortunately, we are unable to access Troubleshoot & Resolve at this 
time. For further assistance, please visit att.com/esupport 
.


However, when I logged in to my router it showed the Broadband 
configured rot all ports 1 through 4 and being 'Auto', and IPv6 is shown 
as 'On' for IPv6, DHCPv6 and DHPv6 Prefix Delegation and with the Router 
Advertisement MTU WITH A VALUE OF 1500.


Broadband Status shows:

Broadband Connection Source ETHERNET
Broadband ConnectionUp
Broadband IPv4 Address  162.237.98.238
Gateway IPv4 Address162.237.96.1
MAC Address 3c:04:61:b3:3c:21
Primary DNS 
Secondary DNS   
Primary DNS Name
Secondary DNS Name  
MTU 1500

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1



fastly.pcap
Description: application/vnd.tcpdump.pcap

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Thu, Feb 22, 2018 at 01:40:45PM -0500, Stephen P. Molnar wrote:
>   2) redone:
> 
> root@AbNormal:/home/comp#
> root@AbNormal:/home/comp# ip a d 2600:1700:4280:3690::46/128 dev enp2s0
> root@AbNormal:/home/comp#
> root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
> traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
> packets
>  1  * * *

That either means that AT is doing something very clever, or I
don't understand what's going on. Or both.

Ok, next part. Reset your network settings.

Check your IPv6 "readiness" by visiting [1] and performing appropriate
link clicks according to [2].

Oh, and the file - /tmp/fastly.pcap . I'm still interested in it.

[1] http://www.att.com/esupport/ipv6.jsp

[2] 
https://rolande.wordpress.com/2014/05/16/enabling-ipv6-on-my-home-network-part-2-att/

Reco

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/22/2018 01:37 PM, Reco wrote:

Hi.

On Thu, Feb 22, 2018 at 01:17:58PM -0500, Stephen P. Molnar wrote:

The next lies are keyed to you numbered request:

1)  root@AbNormal:/home/comp# ping -c2 fe80::3e04:61ff:feb3:3c20%enp2s0
PING fe80::3e04:61ff:feb3:3c20%enp2s0(fe80::3e04:61ff:feb3:3c20%enp2s0) 56
data bytes
64 bytes from fe80::3e04:61ff:feb3:3c20%enp2s0: icmp_seq=1 ttl=64 time=0.258
ms
64 bytes from fe80::3e04:61ff:feb3:3c20%enp2s0: icmp_seq=2 ttl=64 time=0.201
ms

--- fe80::3e04:61ff:feb3:3c20%enp2s0 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1003ms
rtt min/avg/max/mdev = 0.201/0.229/0.258/0.032 ms

So, that seems ok.


2)  root@AbNormal:/home/comp# ip a d 2600:1700:4280:3690::46/128
Not enough information: "dev" argument is required.
root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
packets

And that's my mistake. Should be this:

ip a d 2600:1700:4280:3690::46/128 dev enp2s0

traceroute -n 2a04:4e42:b::204


3)  root@AbNormal:/home/comp# ip -6 ro d 2600:1700:4280:3690::/60
root@AbNormal:/home/comp#
root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
packets
  1  * * *

Was worth a try, but this is not it.

Come thinking about it, please also run this:

ip ro get 2a04:4e42:b::204

Reco



  2) redone:

root@AbNormal:/home/comp#
root@AbNormal:/home/comp# ip a d 2600:1700:4280:3690::46/128 dev enp2s0
root@AbNormal:/home/comp#
root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte 
packets

 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


root@AbNormal:/home/comp# ip ro get 2a04:4e42:b::204
2a04:4e42:b::204 from :: via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto 
static src 2600:1700:4280:3690:800c:68fc:ea2c:23c0 metric 100 pref medium

root@AbNormal:/home/comp#

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Thu, Feb 22, 2018 at 01:17:58PM -0500, Stephen P. Molnar wrote:
> The next lies are keyed to you numbered request:
> 
> 1)  root@AbNormal:/home/comp# ping -c2 fe80::3e04:61ff:feb3:3c20%enp2s0
> PING fe80::3e04:61ff:feb3:3c20%enp2s0(fe80::3e04:61ff:feb3:3c20%enp2s0) 56
> data bytes
> 64 bytes from fe80::3e04:61ff:feb3:3c20%enp2s0: icmp_seq=1 ttl=64 time=0.258
> ms
> 64 bytes from fe80::3e04:61ff:feb3:3c20%enp2s0: icmp_seq=2 ttl=64 time=0.201
> ms
> 
> --- fe80::3e04:61ff:feb3:3c20%enp2s0 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1003ms
> rtt min/avg/max/mdev = 0.201/0.229/0.258/0.032 ms

So, that seems ok.

> 2)  root@AbNormal:/home/comp# ip a d 2600:1700:4280:3690::46/128
> Not enough information: "dev" argument is required.
> root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
> traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
> packets

And that's my mistake. Should be this:

ip a d 2600:1700:4280:3690::46/128 dev enp2s0

traceroute -n 2a04:4e42:b::204

> 3)  root@AbNormal:/home/comp# ip -6 ro d 2600:1700:4280:3690::/60
> root@AbNormal:/home/comp#
> root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
> traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
> packets
>  1  * * *

Was worth a try, but this is not it.

Come thinking about it, please also run this:

ip ro get 2a04:4e42:b::204

Reco

Re: Fwd: Re: Unknown URL

[The Wanderer]

On 2018-02-22 at 13:17, Stephen P. Molnar wrote:

> On 02/22/2018 12:52 PM, Reco wrote:

>>  Hi.
>>
>> On Thu, Feb 22, 2018 at 12:29:12PM -0500, Stephen P. Molnar wrote:
>>
>>> After installing tcpdump I got:
>>> root@AbNormal:/home/comp# tcpdump -ni any -s0 -w /tmp/fastly.pcap tcp port
>>> 80 or icmp6 or \
 udp port 53
>>> tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size
>>> 262144 bytes
>>> ^C6 packets captured
>>> 6 packets received by filter
>>> 0 packets dropped by kernel
>>> root@AbNormal:/home/comp#
>>
>> The file. Please send the file.

> what file?

At a guess, the file created by that command:
/tmp/fastly.pcap

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/22/2018 12:52 PM, Reco wrote:

Hi.

On Thu, Feb 22, 2018 at 12:29:12PM -0500, Stephen P. Molnar wrote:

After installing tcpdump I got:
root@AbNormal:/home/comp# tcpdump -ni any -s0 -w /tmp/fastly.pcap tcp port
80 or icmp6 or \

udp port 53

tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size
262144 bytes
^C6 packets captured
6 packets received by filter
0 packets dropped by kernel
root@AbNormal:/home/comp#

The file. Please send the file.   < what file?


The next part *looks* normal, but it ain't.


root@AbNormal:/home/comp# ip a l
2: enp2s0:  mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
 link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff

..

 inet6 2600:1700:4280:3690::46/128 scope global dynamic
valid_lft 1201940sec preferred_lft 1201940sec
 inet6 2600:1700:4280:3690:800c:68fc:ea2c:23c0/64 scope global temporary
dynamic
valid_lft 597140sec preferred_lft 78692sec
 inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global mngtmpaddr
noprefixroute dynamic
valid_lft 1209054sec preferred_lft 1209054sec

These are your usual run-of-the-mill IPv6 addresses procured via RA,
except for 2600:1700:4280:3690::46/128.
I fail to imagine why would *anyone* provide a /128 address via RA.
Unless they are controlled by aliens or work for IBM, of course.



root@AbNormal:/home/comp# ip ro l table all

..

2600:1700:4280:3690::46 dev enp2s0 proto kernel metric 256  expires
1201893sec pref medium
2600:1700:4280:3690::/64 dev enp2s0 proto ra metric 100  pref medium
2600:1700:4280:3690::/60 via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto ra
metric 100  pref medium

..

These are, well, uncommon.
2600:1700:4280:3690::46 is there because you have /128 address.
/64 route is there because you have IPv6 addresses with the same mask
assigned.
/60 route was provided you by RA. Probably means that your ISP is
generous, and by itself it could be the source of your trouble.



default via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 100
pref medium

And this is your "default gateway" route.



root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
packets
  1  * * *

This is bad. Your IPv6 traffic cannot pass even a default gateway.

Meaning, I require a couple of additional tests.

1) ping -c2 fe80::3e04:61ff:feb3:3c20%enp2s0

Should work, but never hurts to check.

2) ip a d 2600:1700:4280:3690::46/128

traceroute -n 2a04:4e42:b::204

3) ip -6 ro d 2600:1700:4280:3690::/60

traceroute -n 2a04:4e42:b::204




Reco



Reco

Please see comment at top of your reply.

The next lies are keyed to you numbered request:

1)  root@AbNormal:/home/comp# ping -c2 fe80::3e04:61ff:feb3:3c20%enp2s0
PING fe80::3e04:61ff:feb3:3c20%enp2s0(fe80::3e04:61ff:feb3:3c20%enp2s0) 
56 data bytes
64 bytes from fe80::3e04:61ff:feb3:3c20%enp2s0: icmp_seq=1 ttl=64 
time=0.258 ms
64 bytes from fe80::3e04:61ff:feb3:3c20%enp2s0: icmp_seq=2 ttl=64 
time=0.201 ms


--- fe80::3e04:61ff:feb3:3c20%enp2s0 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1003ms
rtt min/avg/max/mdev = 0.201/0.229/0.258/0.032 ms


2)  root@AbNormal:/home/comp# ip a d 2600:1700:4280:3690::46/128
Not enough information: "dev" argument is required.
root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte 
packets

 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

3)  root@AbNormal:/home/comp# ip -6 ro d 2600:1700:4280:3690::/60
root@AbNormal:/home/comp#
root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte 
packets

 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

I'm not sure if I got the  2) commands correctly

Steve

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Thu, Feb 22, 2018 at 12:29:12PM -0500, Stephen P. Molnar wrote:
> After installing tcpdump I got:
> root@AbNormal:/home/comp# tcpdump -ni any -s0 -w /tmp/fastly.pcap tcp port
> 80 or icmp6 or \
> > udp port 53
> tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size
> 262144 bytes
> ^C6 packets captured
> 6 packets received by filter
> 0 packets dropped by kernel
> root@AbNormal:/home/comp#

The file. Please send the file.


The next part *looks* normal, but it ain't.

> root@AbNormal:/home/comp# ip a l
> 2: enp2s0:  mtu 1500 qdisc pfifo_fast state
> UP group default qlen 1000
> link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff
...
> inet6 2600:1700:4280:3690::46/128 scope global dynamic
>valid_lft 1201940sec preferred_lft 1201940sec
> inet6 2600:1700:4280:3690:800c:68fc:ea2c:23c0/64 scope global temporary
> dynamic
>valid_lft 597140sec preferred_lft 78692sec
> inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global mngtmpaddr
> noprefixroute dynamic
>valid_lft 1209054sec preferred_lft 1209054sec

These are your usual run-of-the-mill IPv6 addresses procured via RA,
except for 2600:1700:4280:3690::46/128.
I fail to imagine why would *anyone* provide a /128 address via RA.
Unless they are controlled by aliens or work for IBM, of course.


> root@AbNormal:/home/comp# ip ro l table all
...
> 2600:1700:4280:3690::46 dev enp2s0 proto kernel metric 256  expires
> 1201893sec pref medium
> 2600:1700:4280:3690::/64 dev enp2s0 proto ra metric 100  pref medium
> 2600:1700:4280:3690::/60 via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto ra
> metric 100  pref medium
...

These are, well, uncommon.
2600:1700:4280:3690::46 is there because you have /128 address.
/64 route is there because you have IPv6 addresses with the same mask
assigned.
/60 route was provided you by RA. Probably means that your ISP is
generous, and by itself it could be the source of your trouble.


> default via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 100
> pref medium

And this is your "default gateway" route.


> root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
> traceroute to 2a04:4e42:b::204 (2a04:4e42:b::204), 30 hops max, 80 byte
> packets
>  1  * * *

This is bad. Your IPv6 traffic cannot pass even a default gateway.

Meaning, I require a couple of additional tests.

1) ping -c2 fe80::3e04:61ff:feb3:3c20%enp2s0

Should work, but never hurts to check.

2) ip a d 2600:1700:4280:3690::46/128

traceroute -n 2a04:4e42:b::204

3) ip -6 ro d 2600:1700:4280:3690::/60

traceroute -n 2a04:4e42:b::204

Reco

Re: Fwd: Re: Unknown URL

[Stephen P. Molnar]

On 02/22/2018 12:02 PM, Reco wrote:

Hi.

On Thu, Feb 22, 2018 at 11:41:35AM -0500, Stephen P. Molnar wrote:

Then

root@AbNormal:/home/comp# apt-get update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:3 http://debian.uchicago.edu/debian stretch Release
Get:2 http://debian.uchicago.edu/debian stretch-updates InRelease [91.0 kB]
0% [Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

Perfect.



and

root@AbNormal:/home/comp# dpkg --print-foreign-architectures
i386

That looks about right.



Always glad to be able to help remove boredom!  Other than my comp chem
calculations, I find boredom to very boring.

At least one of us doing real science. I'm ashamed to mention what I do
for the living ???.

And now to the fun part. Please provide these:

tcpdump -ni any -s0 -w /tmp/fastly.pcap tcp port 80 or icmp6 or \
udp port 53

ip a l

ip ro l table all

traceroute -n 2a04:4e42:b::204


It should be noted that:

1) tcpdump should be run while you're invoking apt-get, with IPv6 stack
operational (i.e. no disable_ipv6 trick).

2) To terminate tcpdump use Ctrl+C. All its output will to to a file.

3) tcpdump will capture all tcp:80 (i.e. - HTTP), that's intentional.
This may, or may not be a privacy issue.

4) tcpdump requires CAP_NET_RAW and CAP_NET_ADMIN to function properly.
Meaning - you run it as root. Other commands should not require root.

5) If tcpdump is not installed there, use disable_ipv6 trick temporarily
to apt-get it.

Reco


Reco

After installing tcpdump I got:
root@AbNormal:/home/comp# tcpdump -ni any -s0 -w /tmp/fastly.pcap tcp 
port 80 or icmp6 or \

> udp port 53
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture 
size 262144 bytes

^C6 packets captured
6 packets received by filter
0 packets dropped by kernel
root@AbNormal:/home/comp#


root@AbNormal:/home/comp# ip a l
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp2s0:  mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000

link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.122/24 brd 192.168.1.255 scope global dynamic enp2s0
   valid_lft 78740sec preferred_lft 78740sec
inet6 2600:1700:4280:3690::46/128 scope global dynamic
   valid_lft 1201940sec preferred_lft 1201940sec
inet6 2600:1700:4280:3690:800c:68fc:ea2c:23c0/64 scope global 
temporary dynamic

   valid_lft 597140sec preferred_lft 78692sec
inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global 
mngtmpaddr noprefixroute dynamic

   valid_lft 1209054sec preferred_lft 1209054sec
inet6 fe80::beee:7bff:fe5e:8336/64 scope link
   valid_lft forever preferred_lft forever
root@AbNormal:/home/comp#


root@AbNormal:/home/comp# ip ro l table all
default via 192.168.1.254 dev enp2s0 proto static metric 100
192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.122 
metric 100
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 
127.0.0.1

local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 
127.0.0.1
broadcast 192.168.1.0 dev enp2s0 table local proto kernel scope link src 
192.168.1.122
local 192.168.1.122 dev enp2s0 table local proto kernel scope host src 
192.168.1.122
broadcast 192.168.1.255 dev enp2s0 table local proto kernel scope link 
src 192.168.1.122
2600:1700:4280:3690::46 dev enp2s0 proto kernel metric 256  expires 
1201893sec pref medium

2600:1700:4280:3690::/64 dev enp2s0 proto ra metric 100  pref medium
2600:1700:4280:3690::/60 via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto 
ra metric 100  pref medium

fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 100  pref medium
fe80::/64 dev enp2s0 proto kernel metric 256  pref medium
default via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 
100  pref medium
unreachable default dev lo proto kernel metric 4294967295  error -101 
pref medium

local ::1 dev lo table local proto none metric 0  pref medium
local 2600:1700:4280:3690::46 dev lo table local proto none metric 0  
pref medium
local 2600:1700:4280:3690:800c:68fc:ea2c:23c0 dev lo table local proto 
none metric 0  pref medium
local 2600:1700:4280:3690:beee:7bff:fe5e:8336 dev lo table local proto 
none metric 0  pref medium
local fe80::beee:7bff:fe5e:8336 dev lo table local proto none metric 0  
pref medium

ff00::/8 dev enp2s0 table local metric 256  pref medium
unreachable default dev lo proto kernel metric 4294967295  error -101 
pref medium

root@AbNormal:/home/comp#


root@AbNormal:/home/comp# traceroute -n 2a04:4e42:b::204
traceroute to 

Re: Fwd: Re: Unknown URL

[Reco]

Hi.

On Thu, Feb 22, 2018 at 11:41:35AM -0500, Stephen P. Molnar wrote:
> Then
> 
> root@AbNormal:/home/comp# apt-get update
> Ign:1 http://debian.uchicago.edu/debian stretch InRelease
> Hit:3 http://debian.uchicago.edu/debian stretch Release
> Get:2 http://debian.uchicago.edu/debian stretch-updates InRelease [91.0 kB]
> 0% [Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

Perfect.


> and
> 
> root@AbNormal:/home/comp# dpkg --print-foreign-architectures
> i386

That looks about right.


> Always glad to be able to help remove boredom!  Other than my comp chem
> calculations, I find boredom to very boring.

At least one of us doing real science. I'm ashamed to mention what I do
for the living ☺.

And now to the fun part. Please provide these:

tcpdump -ni any -s0 -w /tmp/fastly.pcap tcp port 80 or icmp6 or \
udp port 53

ip a l

ip ro l table all

traceroute -n 2a04:4e42:b::204


It should be noted that:

1) tcpdump should be run while you're invoking apt-get, with IPv6 stack
operational (i.e. no disable_ipv6 trick).

2) To terminate tcpdump use Ctrl+C. All its output will to to a file.

3) tcpdump will capture all tcp:80 (i.e. - HTTP), that's intentional.
This may, or may not be a privacy issue.

4) tcpdump requires CAP_NET_RAW and CAP_NET_ADMIN to function properly.
Meaning - you run it as root. Other commands should not require root.

5) If tcpdump is not installed there, use disable_ipv6 trick temporarily
to apt-get it.

Reco

Fwd: Re: Unknown URL

[Stephen P. Molnar]

 Original Message 
Subject:Re: Unknown URL
Date:   Thu, 22 Feb 2018 11:31:08 -0500
From:   Stephen P. Molnar <s.mol...@sbcglobal.net>
To: debian-user@lists.debian.org



On 02/22/2018 10:10 AM, Reco wrote:

Hi.

On Thu, Feb 22, 2018 at 10:04:30AM -0500, Stephen P. Molnar wrote:

The only reason I have it
is so that my wife can browse.  Here is my sources.list:

Check the contents of /etc/apt/sources.list.d . It's definitely there.

Just for the fun of it, invoke "dpkg -S" on the problematic file.



I definitely want the other two problems to be solved.

  I have some computational chemistry software that needs i386 libraries.

One thing at a time. First, purge the faulty Opera repo.

Then run "apt-get update". I'm interested in the new output.

Next provide the output of "dpkg --print-foreign-architectures", please.


Your help is really appreciated.

You're welcome. It's been a boring week, I could use some fun.

Reco



Reco

I had already removed Opera from /etc/apt/sources.list.d

/etc/apt/sources.list.dis empty.

Then

root@AbNormal:/home/comp# apt-get update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:3 http://debian.uchicago.edu/debian stretch Release
Get:2 http://debian.uchicago.edu/debian stretch-updates InRelease [91.0 kB]
0% [Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

and

root@AbNormal:/home/comp# dpkg --print-foreign-architectures
i386
root@AbNormal:/home/comp#

Always glad to be able to help remove boredom!  Other than my comp chem
calculations, I find boredom to very boring.


To add to my conclusion, I just i stalled Google Earth, 32 bit, with gdebi
(as root) and it installed all of the required 32 bit libraries!  Might this be 
a clue?
 --
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Unknown URL

[Stephen P. Molnar]

On 02/22/2018 10:10 AM, Reco wrote:

Hi.

On Thu, Feb 22, 2018 at 10:04:30AM -0500, Stephen P. Molnar wrote:

The only reason I have it
is so that my wife can browse.  Here is my sources.list:

Check the contents of /etc/apt/sources.list.d . It's definitely there.

Just for the fun of it, invoke "dpkg -S" on the problematic file.



I definitely want the other two problems to be solved.

  I have some computational chemistry software that needs i386 libraries.

One thing at a time. First, purge the faulty Opera repo.

Then run "apt-get update". I'm interested in the new output.

Next provide the output of "dpkg --print-foreign-architectures", please.


Your help is really appreciated.

You're welcome. It's been a boring week, I could use some fun.

Reco



Reco

I had already removed Opera from /etc/apt/sources.list.d

/etc/apt/sources.list.dis empty.

Then

root@AbNormal:/home/comp# apt-get update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:3 http://debian.uchicago.edu/debian stretch Release
Get:2 http://debian.uchicago.edu/debian stretch-updates InRelease [91.0 kB]
0% [Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

and

root@AbNormal:/home/comp# dpkg --print-foreign-architectures
i386
root@AbNormal:/home/comp#

Always glad to be able to help remove boredom!  Other than my comp chem 
calculations, I find boredom to very boring.


--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Unknown URL

[Stephen P. Molnar]

On 02/22/2018 10:07 AM, Greg Wooledge wrote:

On Thu, Feb 22, 2018 at 10:04:30AM -0500, Stephen P. Molnar wrote:

I don't want the Opera repository, where is it?  The only reason I have it
is so that my wife can browse.  Here is my sources.list:

Look in /etc/apt/sources.list.d/*.list also.



That was it.

Thanks.

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Unknown URL

[Reco]

Hi.

On Thu, Feb 22, 2018 at 10:04:30AM -0500, Stephen P. Molnar wrote:
> The only reason I have it
> is so that my wife can browse.  Here is my sources.list:

Check the contents of /etc/apt/sources.list.d . It's definitely there.

Just for the fun of it, invoke "dpkg -S" on the problematic file.


> I definitely want the other two problems to be solved.
> 
>  I have some computational chemistry software that needs i386 libraries.

One thing at a time. First, purge the faulty Opera repo.

Then run "apt-get update". I'm interested in the new output.

Next provide the output of "dpkg --print-foreign-architectures", please.

> Your help is really appreciated.

You're welcome. It's been a boring week, I could use some fun.

Reco

Re: Unknown URL

[Greg Wooledge]

On Thu, Feb 22, 2018 at 10:04:30AM -0500, Stephen P. Molnar wrote:
> I don't want the Opera repository, where is it?  The only reason I have it
> is so that my wife can browse.  Here is my sources.list:

Look in /etc/apt/sources.list.d/*.list also.

Re: Unknown URL

[Stephen P. Molnar]

On 02/22/2018 09:42 AM, Reco wrote:

Hi.

On Thu, Feb 22, 2018 at 09:19:38AM -0500, Stephen P. Molnar wrote:

Simple.

If you configured radvd or dhcpv6 - double-check your setup. You did it
wrong.
If you don't, but used "iface ??? inet6" stanzas in
/etc/network/interfaces - remove them.
If you use NetworkManager, so some other nonsense - convince it not no
configure IPv6 for you, or stop using them.
If anything else fails, try this:

sysctl -w net.ipv6.conf.all.disable_ipv6=1


Thanks for the detailed reply.

I used the installer defaults to configure the network interface.

"Installer defaults" is a very broad term, and the contents of your
installation can differ dramatically depending on the type of install
media used.
Besides it's really been awhile since I used Debian Installer CD1. I
prefer d-i over TFTP these days. More flexibility, less cruft this way.



Here are the contents of /etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

and /etc/networks/interfaces.d is empty.

And that means you're using NetworkManager, wicd, systemd-networkd,
connman or whatever they put in there by default. Not the conventional
ifupdown.



It would seem that there is another problem:  dpkg --add-architecture i386
(as root) no longer seems to work, although it did when I ran it yesterday
after reinstalling the OS.

To my best knowledge this particular invocation of dpkg does not involve
network communication in any way. Therefore it's a different problem.



However I just ran

sysctl -w net.ipv6.conf.all.disable_ipv6=1, as per your suggestion and got:


root@AbNormal:/home/comp# sysctl -w net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.all.disable_ipv6 = 1
root@AbNormal:/home/comp# aprt update
-bash: aprt: command not found
root@AbNormal:/home/comp# apt update
Get:1 http://security.debian.org/debian-security stretch/updates InRelease 
[63.0 kB]
Ign:2 http://debian.uchicago.edu/debian stretch InRelease
Hit:3 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:4 http://debian.uchicago.edu/debian stretch Release
Get:5 http://security.debian.org/debian-security stretch/updates/contrib 
Sources [1,384 B]
Get:7 http://security.debian.org/debian-security stretch/updates/non-free 
Sources [772 B]
Get:8 http://security.debian.org/debian-security stretch/updates/main Sources 
[116 kB]
Get:9 http://security.debian.org/debian-security stretch/updates/main amd64 
Packages [325 kB]
Get:10 http://security.debian.org/debian-security stretch/updates/main i386 
Packages [326 kB]
Get:11 http://security.debian.org/debian-security stretch/updates/main 
Translation-en [144 kB]
Get:12 http://security.debian.org/debian-security stretch/updates/contrib i386 
Packages [1,776 B]
Get:13 http://security.debian.org/debian-security stretch/updates/contrib amd64 
Packages [1,776 B]
Get:14 http://security.debian.org/debian-security stretch/updates/contrib 
Translation-en [1,759 B]
Get:15 http://security.debian.org/debian-security stretch/updates/non-free 
amd64 Packages [1,268 B]
Get:16 http://security.debian.org/debian-security stretch/updates/non-free i386 
Packages [1,268 B]
Get:17 http://security.debian.org/debian-security stretch/updates/non-free 
Translation-en [481 B]
Get:19 https://deb.opera.com/opera-stable stable/non-free amd64 Packages [1,827 
B]
Err:19 https://deb.opera.com/opera-stable stable/non-free amd64 Packages
   Writing more data than expected (1832 > 1827)
   Hashes of expected file:
- Filesize:1827 [weak]
- SHA256:e53101f11ac6677a265465dc4ebcb85fc1de696d88ddc5440db29f448758a6ae
- SHA1:24da563907645d73682c218bffe94ebefa0ce284 [weak]
- MD5Sum:f339dab9748f817a448f3bf401e76b3a [weak]
   Release file created at: Thu, 22 Feb 2018 07:26:36 +
Fetched 985 kB in 1s (538 kB/s)
Reading package lists... Done
E: Failed to fetch 
https://deb.opera.com/opera-stable/dists/stable/non-free/binary-amd64/Packages.gz  
Writing more data than expected (1832 > 1827)
Hashes of expected file:
 - Filesize:1827 [weak]
 - SHA256:e53101f11ac6677a265465dc4ebcb85fc1de696d88ddc5440db29f448758a6ae
 - SHA1:24da563907645d73682c218bffe94ebefa0ce284 [weak]
 - MD5Sum:f339dab9748f817a448f3bf401e76b3a [weak]
Release file created at: Thu, 22 Feb 2018 07:26:36 +
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

And that, ladies and gentlemen, shows us two things.
First one being - you IPv4 settings are working.
Second - those corporate drones at Opera are unable to setup a proper
Debian repository.



Then I ran apt update and got:

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://debian.uchicago.edu/debian stretch Release

Re: Unknown URL

[Reco]

Hi.

On Thu, Feb 22, 2018 at 09:19:38AM -0500, Stephen P. Molnar wrote:
> > Simple.
> > 
> > If you configured radvd or dhcpv6 - double-check your setup. You did it
> > wrong.
> > If you don't, but used "iface ??? inet6" stanzas in
> > /etc/network/interfaces - remove them.
> > If you use NetworkManager, so some other nonsense - convince it not no
> > configure IPv6 for you, or stop using them.
> > If anything else fails, try this:
> > 
> > sysctl -w net.ipv6.conf.all.disable_ipv6=1
> > 
> 
> Thanks for the detailed reply.
> 
> I used the installer defaults to configure the network interface.

"Installer defaults" is a very broad term, and the contents of your
installation can differ dramatically depending on the type of install
media used.
Besides it's really been awhile since I used Debian Installer CD1. I
prefer d-i over TFTP these days. More flexibility, less cruft this way.


> Here are the contents of /etc/network/interfaces:
> 
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> source /etc/network/interfaces.d/*
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> and /etc/networks/interfaces.d is empty.

And that means you're using NetworkManager, wicd, systemd-networkd,
connman or whatever they put in there by default. Not the conventional
ifupdown.


> It would seem that there is another problem:  dpkg --add-architecture i386
> (as root) no longer seems to work, although it did when I ran it yesterday
> after reinstalling the OS.

To my best knowledge this particular invocation of dpkg does not involve
network communication in any way. Therefore it's a different problem.


> However I just ran
> 
> sysctl -w net.ipv6.conf.all.disable_ipv6=1, as per your suggestion and got:
> 
> 
> root@AbNormal:/home/comp# sysctl -w net.ipv6.conf.all.disable_ipv6=1
> net.ipv6.conf.all.disable_ipv6 = 1
> root@AbNormal:/home/comp# aprt update
> -bash: aprt: command not found
> root@AbNormal:/home/comp# apt update
> Get:1 http://security.debian.org/debian-security stretch/updates InRelease 
> [63.0 kB]
> Ign:2 http://debian.uchicago.edu/debian stretch InRelease
> Hit:3 http://debian.uchicago.edu/debian stretch-updates InRelease
> Hit:4 http://debian.uchicago.edu/debian stretch Release
> Get:5 http://security.debian.org/debian-security stretch/updates/contrib 
> Sources [1,384 B]
> Get:7 http://security.debian.org/debian-security stretch/updates/non-free 
> Sources [772 B]
> Get:8 http://security.debian.org/debian-security stretch/updates/main Sources 
> [116 kB]
> Get:9 http://security.debian.org/debian-security stretch/updates/main amd64 
> Packages [325 kB]
> Get:10 http://security.debian.org/debian-security stretch/updates/main i386 
> Packages [326 kB]
> Get:11 http://security.debian.org/debian-security stretch/updates/main 
> Translation-en [144 kB]
> Get:12 http://security.debian.org/debian-security stretch/updates/contrib 
> i386 Packages [1,776 B]
> Get:13 http://security.debian.org/debian-security stretch/updates/contrib 
> amd64 Packages [1,776 B]
> Get:14 http://security.debian.org/debian-security stretch/updates/contrib 
> Translation-en [1,759 B]
> Get:15 http://security.debian.org/debian-security stretch/updates/non-free 
> amd64 Packages [1,268 B]
> Get:16 http://security.debian.org/debian-security stretch/updates/non-free 
> i386 Packages [1,268 B]
> Get:17 http://security.debian.org/debian-security stretch/updates/non-free 
> Translation-en [481 B]
> Get:19 https://deb.opera.com/opera-stable stable/non-free amd64 Packages 
> [1,827 B]
> Err:19 https://deb.opera.com/opera-stable stable/non-free amd64 Packages
>   Writing more data than expected (1832 > 1827)
>   Hashes of expected file:
>- Filesize:1827 [weak]
>- SHA256:e53101f11ac6677a265465dc4ebcb85fc1de696d88ddc5440db29f448758a6ae
>- SHA1:24da563907645d73682c218bffe94ebefa0ce284 [weak]
>- MD5Sum:f339dab9748f817a448f3bf401e76b3a [weak]
>   Release file created at: Thu, 22 Feb 2018 07:26:36 +
> Fetched 985 kB in 1s (538 kB/s)
> Reading package lists... Done
> E: Failed to fetch 
> https://deb.opera.com/opera-stable/dists/stable/non-free/binary-amd64/Packages.gz
>   Writing more data than expected (1832 > 1827)
>Hashes of expected file:
> - Filesize:1827 [weak]
> - SHA256:e53101f11ac6677a265465dc4ebcb85fc1de696d88ddc5440db29f448758a6ae
> - SHA1:24da563907645d73682c218bffe94ebefa0ce284 [weak]
> - MD5Sum:f339dab9748f817a448f3bf401e76b3a [weak]
>Release file created at: Thu, 22 Feb 2018 07:26:36 +
> E: Some index files failed to download. They have been ignored, or old ones 
> used instead.

And that, ladies and gentlemen, shows us two things.
First one being - you IPv4 settings are working.
Second - those corporate drones at Opera are unable to setup a proper
Debian repository.


> Then I ran apt update and got:
> 
> root@AbNormal:/home/comp# apt update
> Ign:1 

Re: Unknown URL

[Stephen P. Molnar]

On 02/21/2018 11:23 PM, Reco wrote:

Hi.

I prefer on-list communication.

On Wed, Feb 21, 2018 at 06:26:37PM -0500, Stephen P. Molnar wrote:

On 02/21/2018 04:03 PM, Reco wrote:

Hi.

On Wed, Feb 21, 2018 at 03:41:08PM -0500, Stephen P. Molnar wrote:

I have just installed Stretch and have what, to me at least, is an unknown
URL when I do apt update (as root).

[Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

That's because you have this in your sources.list:


debhttp://security.debian.org/debian-security/  stretch/updates main contrib

security.debian.org tries to redirect you to the mirrors that are
nearest to you.

It just so happens that your host has IPv6 address from somewhere, so
apt tries IPv6 first, then another, and finally falls back to IPv4.

For example, from here it looks like this:

$ wget -S --spiderhttp://security.debian.org
Spider mode enabled. Check if remote file exists.
--2018-02-21 23:56:33--http://security.debian.org/
Resolving security.debian.org (security.debian.org)...
2001:a78:5:1:216:35ff:fe7f:6ceb, 2a02:16a8:dc41:100::233,
217.196.149.233, ..
.
Connecting to security.debian.org
(security.debian.org)|2001:a78:5:1:216:35ff:fe7f:6ceb|:80
..

$ getent hosts 2001:a78:5:1:216:35ff:fe7f:6ceb
2001:a78:5:1:216:35ff:fe7f:6ceb lobos.debian.org

Therefore here security.debian.org = lobos.debian.org


Since prod.debian.map.fastly.net is reachable from here, I suggest you
to fix your IPv6 setup, or squash it altogether in case you don't
control it.

Reco



While I am most appreciative of your response, I don't have the fainest idea
as to what you are suggesting that I do when you say "Since
prod.debian.map.fastly.net is reachable from here, I suggest you to fix your
IPv6 setup, or squash it altogether in case you don't control it.

Simple.

If you configured radvd or dhcpv6 - double-check your setup. You did it
wrong.
If you don't, but used "iface ??? inet6" stanzas in
/etc/network/interfaces - remove them.
If you use NetworkManager, so some other nonsense - convince it not no
configure IPv6 for you, or stop using them.
If anything else fails, try this:

sysctl -w net.ipv6.conf.all.disable_ipv6=1

Reco


Reco

Thanks for the detailed reply.

I used the installer defaults to configure the network interface.

Here are the contents of /etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

and /etc/networks/interfaces.d is empty.

It would seem that there is another problem:  dpkg --add-architecture 
i386 (as root) no longer seems to work, although it did when I ran it 
yesterday after reinstalling the OS.


However I just ran

sysctl -w net.ipv6.conf.all.disable_ipv6=1, as per your suggestion and got:


root@AbNormal:/home/comp# sysctl -w net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.all.disable_ipv6 = 1
root@AbNormal:/home/comp# aprt update
-bash: aprt: command not found
root@AbNormal:/home/comp# apt update
Get:1 http://security.debian.org/debian-security stretch/updates InRelease 
[63.0 kB]
Ign:2 http://debian.uchicago.edu/debian stretch InRelease
Hit:3 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:4 http://debian.uchicago.edu/debian stretch Release
Get:5 http://security.debian.org/debian-security stretch/updates/contrib 
Sources [1,384 B]
Get:7 http://security.debian.org/debian-security stretch/updates/non-free 
Sources [772 B]
Get:8 http://security.debian.org/debian-security stretch/updates/main Sources 
[116 kB]
Get:9 http://security.debian.org/debian-security stretch/updates/main amd64 
Packages [325 kB]
Get:10 http://security.debian.org/debian-security stretch/updates/main i386 
Packages [326 kB]
Get:11 http://security.debian.org/debian-security stretch/updates/main 
Translation-en [144 kB]
Get:12 http://security.debian.org/debian-security stretch/updates/contrib i386 
Packages [1,776 B]
Get:13 http://security.debian.org/debian-security stretch/updates/contrib amd64 
Packages [1,776 B]
Get:14 http://security.debian.org/debian-security stretch/updates/contrib 
Translation-en [1,759 B]
Get:15 http://security.debian.org/debian-security stretch/updates/non-free 
amd64 Packages [1,268 B]
Get:16 http://security.debian.org/debian-security stretch/updates/non-free i386 
Packages [1,268 B]
Get:17 http://security.debian.org/debian-security stretch/updates/non-free 
Translation-en [481 B]
Get:19 https://deb.opera.com/opera-stable stable/non-free amd64 Packages [1,827 
B]
Err:19 https://deb.opera.com/opera-stable stable/non-free amd64 Packages
  Writing more data than expected (1832 > 1827)
  Hashes of expected file:
   - Filesize:1827 [weak]
   - SHA256:e53101f11ac6677a265465dc4ebcb85fc1de696d88ddc5440db29f448758a6ae
   - SHA1:24da563907645d73682c218bffe94ebefa0ce284 [weak]
   - MD5Sum:f339dab9748f817a448f3bf401e76b3a [weak]
  Release 

Re: Unknown URL

[Reco]

Hi.

On Wed, Feb 21, 2018 at 03:41:08PM -0500, Stephen P. Molnar wrote:
> I have just installed Stretch and have what, to me at least, is an unknown
> URL when I do apt update (as root).
> 
> [Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

That's because you have this in your sources.list:

> deb http://security.debian.org/debian-security/ stretch/updates main contrib

security.debian.org tries to redirect you to the mirrors that are
nearest to you.

It just so happens that your host has IPv6 address from somewhere, so
apt tries IPv6 first, then another, and finally falls back to IPv4.

For example, from here it looks like this:

$ wget -S --spider http://security.debian.org
Spider mode enabled. Check if remote file exists.
--2018-02-21 23:56:33--  http://security.debian.org/
Resolving security.debian.org (security.debian.org)...
2001:a78:5:1:216:35ff:fe7f:6ceb, 2a02:16a8:dc41:100::233,
217.196.149.233, ..
.
Connecting to security.debian.org
(security.debian.org)|2001:a78:5:1:216:35ff:fe7f:6ceb|:80
...

$ getent hosts 2001:a78:5:1:216:35ff:fe7f:6ceb
2001:a78:5:1:216:35ff:fe7f:6ceb lobos.debian.org

Therefore here security.debian.org = lobos.debian.org


Since prod.debian.map.fastly.net is reachable from here, I suggest you
to fix your IPv6 setup, or squash it altogether in case you don't
control it.

Reco

Re: Unknown URL

[Brian]

On Wed 21 Feb 2018 at 15:41:08 -0500, Stephen P. Molnar wrote:

> I have just installed Stretch and have what, to me at least, is an unknown
> URL when I do apt update (as root).
> 
> [Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

Is this this the unknown URL you are talking about? What's the problem?

> 
> apt hangs for a couple of minutes and finally finishes without any errors.

That's good.

-- 
Brian.