[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fwd: Re: Unknown URL


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&T
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: <LOOPBACK,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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 purge bvi:i386worked as they should.

I really apprecialte your patience and your efforts.

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