Discussion:
[hercules-390] PTP interface
'Jean-Louis Noel' jln@stben.net [hercules-390]
2017-03-12 20:40:20 UTC
Permalink
Hi Ivan,

0E20.2 PTP 10.149.86.1 10.149.86.2 2001:470:792a:1::101 2001:470:792a:1::102

tun0: flags=81<UP,POINTOPOINT,RUNNING> mtu 1500
inet 10.149.86.2 netmask 255.255.255.255 destination 10.149.86.1
inet6 fe80::a792:91d1:b1ec:a487 prefixlen 64 scopeid 0x20<link>
inet6 2001:470:792a:1::102 prefixlen 128 scopeid 0x0<global>
inet6 fe80::d70c:42bb:a4d3:fc73 prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen
500
(UNSPEC)
RX packets 6 bytes 355 (355.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5 bytes 685 (685.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
default host-109-88-34- 0.0.0.0 UG 100 0 0
enp8s0
10.149.85.0 0.0.0.0 255.255.255.0 U 100 0 0
enp5s0
10.149.86.1 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
109.88.34.48 0.0.0.0 255.255.255.240 U 100 0 0
enp8s0

Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use
If
2001:470:1f14:2d3::/64 [::] Un 256 0 0
sit1
2001:470:792a::/64 [::] U 256 0 0
enp8s0
ns.stben.net/128 [::] U 256 0 0
tun0
2001:470:792a:1::/64 [::] U 256 8 729
enp5s0
fe80::/64 [::] U 256 0 38
enp5s0
fe80::/64 [::] U 256 0 599
enp8s0
fe80::/64 [::] U 256 0 4
tun0
[::]/0 [::] U 1 8 2367
sit1
[::]/0 [::] !n -1 1 3747
lo
localhost/128 [::] Un 0 9 118
lo
2001:470:1f14:2d3::/128 [::] Un 0 1 0
lo
jln-1-pt.tunnel.tserv11.ams1.ipv6.he.net/128 [::] Un
0 8 731 lo
2001:470:792a::/128 [::] Un 0 1 0
lo
ns.stben.net/128 [::] Un 0 9 79
lo
2001:470:792a:1::/128 [::] Un 0 1 0
lo
router.stben.net/128 [::] Un 0 2 74
lo
ns.stben.net/128 [::] Un 0 1 0
lo
fe80::/128 [::] Un 0 1 0
lo
fe80::/128 [::] Un 0 1 0
lo
fe80::/128 [::] Un 0 1 0
lo
ns.stben.net/128 [::] Un 0 2 62
lo
ns.stben.net/128 [::] Un 0 1 0
lo
ns.stben.net/128 [::] Un 0 1 0
lo
ns.stben.net/128 [::] Un 0 1 0
lo
ff00::/8 [::] U 256 0 0
sit1
ff00::/8 [::] U 256 1 2
enp5s0
ff00::/8 [::] U 256 1 1322
enp8s0
ff00::/8 [::] U 256 2 4
tun0
[::]/0 [::] !n -1 1 3747
lo

I wish to have a line like:
zos.stben.net/128 [::] UH 1 0 0
tun0
and not this one:
ns.stben.net/128 [::] U 256 0 0
tun0

-Jean-Louis
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-03-12 21:22:21 UTC
Permalink
Post by 'Jean-Louis Noel' ***@stben.net [hercules-390]
zos.stben.net/128 [::] UH 1 0 0
tun0
ns.stben.net/128 [::] U 256 0 0
tun0
Did you add a route manually ? Because I can ping it from where I am...

--Ivan



[Non-text portions of this message have been removed]
'Jean-Louis Noel' jln@stben.net [hercules-390]
2017-03-12 21:36:48 UTC
Permalink
Hi Ivan,
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Did you add a route manually ? Because I can ping it from where I am...
Yes, after copying the IPV6 routing table I issued:
[***@ns named]# route -6 add 2001:470:792a:1::101 tun0

To have an example of what I am asking for and being able to reach
the IBM's OS from my computer.

-Jean-Louis
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-03-12 22:44:38 UTC
Permalink
Post by 'Jean-Louis Noel' ***@stben.net [hercules-390]
Hi Ivan,
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Did you add a route manually ? Because I can ping it from where I am...
To have an example of what I am asking for and being able to reach
the IBM's OS from my computer.
Jean-Louis,

Then this needs investigation.

Although I am sure any tun supported interface (CTCI, LCS Layer 3,
etc..) do not require adding routes any IPv4 routes (because they are
implied), I am not certain how a Point to Point IPv6 interface is handled.

You certainly have another interface (a IPv6 tunnel ? a network
interface with an an underlying IPv6 router) with a subnet mask greater
than the one for the PtP interface.. This should be done automatically.
But it doesn't seem to be the case.

None of the OS I run support this interface, so it's going to be hard to
fix.

--Ivan



[Non-text portions of this message have been removed]
'Jean-Louis Noel' jln@stben.net [hercules-390]
2017-03-12 23:28:30 UTC
Permalink
Hi Ivan,
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
You certainly have another interface (a IPv6 tunnel ?
I use this script for the tunnel

#!/bin/sh
#
ifconfig sit0 up
ifconfig sit0 inet6 tunnel ::216.66.84.46
ifconfig sit1 up
ifconfig sit1 inet6 add 2001:470:1f14:2d3::2/64
sysctl -w net.ipv6.conf.all.forwarding=1
route -A inet6 add ::/0 dev sit1
route -A inet6 add 2001:470:792a:1::/64 dev enp5s0

-Jean-Louis
'Jean-Louis Noel' jln@stben.net [hercules-390]
2017-03-12 23:39:12 UTC
Permalink
Hi Ivan,
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
I am not certain how a Point to Point IPv6 interface is handled.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Jean-Louis>ping zos.stben.net

Pinging zos.stben.net [2001:470:792a:1::101] with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 2001:470:792a:1::101:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

[***@ns sbin]# route -6 add 2001:470:792a:1::101 tun0

C:\Users\Jean-Louis>ping zos.stben.net

Pinging zos.stben.net [2001:470:792a:1::101] with 32 bytes of data:
Reply from 2001:470:792a:1::101: time=3ms
Reply from 2001:470:792a:1::101: time=1ms
Reply from 2001:470:792a:1::101: time=1ms
Reply from 2001:470:792a:1::101: time=2ms

Ping statistics for 2001:470:792a:1::101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms

C:\Users\Jean-Louis>

-Jean-Louis
mcisho@yahoo.com [hercules-390]
2017-03-13 19:46:37 UTC
Permalink
Jean-Louis has to issue a route command for 2001:470:792a:1::101 because:-
a) the 2001:470:792a:1::/64 subnet is in use with interface enp5s0, and
b) there is no prefix value on the config statement, so the default prefix of /128 is used with tun0.
When the tun0 interface is brought up, a route for 2001:470:792a:1::102/128 is automatically added by the kernel, but a route for 2001:470:792a:1::101 isn't, because the kernel knows nothing of that address. Subsequently, until the route command is issued, traffic destined for 2001:470:792a:1::101 is handed to the interface enp5s0, which doesn't know what to do with the traffic and ignores it.

Possible solutions are:-
1) Subnet the 2001:470:792a:1::/64 subnet, e.g. 2001:470:792a:1:0::/80 and 2001:470:792a:1:1::/80, and use one subnet for interface enp5s0 and the other for tun0.
2) Make tun0 use a different /64 subnet, e.g. 2001:470:792a:2::/64.
3) Continue issuing the route command.
Knowing little of Jean-Louis' network or requirements, it's difficult to say which might be the best solution for him.

Ian
'Jean-Louis Noel' jln@stben.net [hercules-390]
2017-03-14 00:33:38 UTC
Permalink
Hi Ian,
Post by ***@yahoo.com [hercules-390]
there is no prefix value on the config statement, so the default prefix
of /128 is used with tun0.
Thank you Ian, you are a life saver! ;-)

0E20.2 PTP 10.149.86.1 10.149.86.2/30 2001:470:792a:2::1
2001:470:792a:2::2/126

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
default host-109-88-34- 0.0.0.0 UG 100 0 0
enp8s0
10.149.85.0 0.0.0.0 255.255.255.0 U 100 0 0
enp5s0
10.149.86.0 0.0.0.0 255.255.255.252 U 0 0 0 tun0
109.88.34.48 0.0.0.0 255.255.255.240 U 100 0 0
enp8s0

Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use
If
[::]/96 [::] Un 256 0 0
sit0
2001:470:1f14:2d3::/64 [::] Un 256 0 0
sit1
2001:470:792a::/64 [::] U 256 1 1
enp8s0
2001:470:792a:1::/64 [::] U 256 8 1659
enp5s0
2001:470:792a:2::/126 [::] U 256 1 5
tun0
fe80::/64 [::] U 256 0 22
enp5s0
fe80::/64 [::] U 256 0 52
enp8s0
fe80::/64 [::] U 256 0 4
tun0
[::]/0 [::] U 1 8 3166
sit1
[::]/0 [::] !n -1 1 4918
lo
localhost/128 [::] Un 0 8 73
lo
ns.stben.net/128 [::] Un 0 1 0
lo
2001:470:1f14:2d3::/128 [::] Un 0 1 0
lo
jln-1-pt.tunnel.tserv11.ams1.ipv6.he.net/128 [::] Un
0 9 681 lo
2001:470:792a::/128 [::] Un 0 1 0
lo
ns.stben.net/128 [::] Un 0 7 52
lo
2001:470:792a:1::/128 [::] Un 0 1 0
lo
router.stben.net/128 [::] Un 0 2 120
lo
2001:470:792a:2::/128 [::] Un 0 1 0
lo
ns.stben.net/128 [::] Un 0 1 0
lo
fe80::/128 [::] Un 0 1 0
lo
fe80::/128 [::] Un 0 1 0
lo
fe80::/128 [::] Un 0 1 0
lo
ns.stben.net/128 [::] Un 0 2 35
lo
ns.stben.net/128 [::] Un 0 1 0
lo
ns.stben.net/128 [::] Un 0 1 0
lo
ns.stben.net/128 [::] Un 0 1 0
lo
ff00::/8 [::] U 256 0 0
sit1
ff00::/8 [::] U 256 1 2
enp5s
0
ff00::/8 [::] U 256 1 401
enp8s
0
ff00::/8 [::] U 256 3 5
tun0
[::]/0 [::] !n -1 1 4918
lo
Post by ***@yahoo.com [hercules-390]
Knowing little of Jean-Louis' network or requirements
NS is running fedora 25 and acts as router and hosts all servers; you can
monitor it
at : http://www.stben.net/phpsysinfo/index.php?disp=dynamic

enp8s0 is connected to internet in IPV4.
enp5s0 is connected to our internal lan.
sit1 is an IPV4/IPV6 tunnel
and tun0 is used by Hercules.

Loading...