search

tdeheurles / homecores

1 stars 3 forks source link

Network comportment #5

Open tdeheurles opened 9 years ago

tdeheurles commented 9 years ago

from @potgieterdl : Question on the public_ip, my assumption was that if I make the public ip same as my local network I should be able to ping the server from my local pc as well as from a network pc?

network_mask="192.168.1"
core@master1 ~ $ ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 10.2.15.1  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 02:42:bc:3c:e7:d7  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
        inet6 fe80::a00:27ff:fea1:41b4  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:a1:41:b4  txqueuelen 1000  (Ethernet)
        RX packets 151993  bytes 120688481 (115.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 88331  bytes 4997410 (4.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.0.131  netmask 255.255.255.0  broadcast 10.0.0.255
        inet6 fe80::a00:27ff:feae:46ef  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:ae:46:ef  txqueuelen 1000  (Ethernet)
        RX packets 335  bytes 31145 (30.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 124  bytes 10989 (10.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.1.100  netmask 255.255.255.0  broadcast 172.16.1.255
        inet6 fe80::a00:27ff:fe14:71cf  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:14:71:cf  txqueuelen 1000  (Ethernet)
        RX packets 89  bytes 13945 (13.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 45  bytes 4861 (4.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

flannel0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1472
        inet 10.2.15.0  netmask 255.255.0.0  destination 10.2.15.0
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 50923  bytes 5730027 (5.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 50923  bytes 5730027 (5.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
{lamb} ping 10.0.0.131
Pinging 10.0.0.131 with 32 bytes of data:
Request timed out.

{lamb} ping 172.16.1.100
Pinging 172.16.1.100 with 32 bytes of data:
Reply from 172.16.1.100: bytes=32 time<1ms TTL=64
tdeheurles commented 9 years ago

Yes you should be able to ping your VM on 192.168.1.X

potgieterdl commented 9 years ago

strange, so...I changed the ip mask to 10.0.0, boots up fine but I cant ping it from my local pc. I can ping it from my nas. I restarted twice and got two different dhcp allocated ip`s.

But cant ping them locally, only from other devices?

tdeheurles commented 9 years ago

No it's normal. 10.0.0.x is the flanneldVPN created for the kubernetes pods. What is your local network mask ? 192.168.1.x ?

potgieterdl commented 9 years ago

o buy the way....great support. Can I send you beer?

potgieterdl commented 9 years ago

10.0.0.x, my local lan ip range

tdeheurles commented 9 years ago

lol. thanks. I had so much problems going into kubernetes world ^^

So config seems fine and ping 10.0.0.131 should work. You didn't have issue configurating the VirtualBox network name ?

potgieterdl commented 9 years ago

nope. I can ping the master from another pc on my network, but not the actual host. weird.

But....If I ping on the host with ping master I get what looks like ip6 response.

C:\dev\vagrant\kubernetes-vagrant-coreos-cluster {git}
{lamb} ping master1

Pinging master1 [10.0.0.141] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.0.0.141:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\dev\vagrant\kubernetes-vagrant-coreos-cluster {git}
{lamb}

C:\dev\vagrant\kubernetes-vagrant-coreos-cluster {git}
{lamb} ping master1

Pinging master1 [fe80::a00:27ff:fe00:ae5e%5] with 32 bytes of data:
Reply from fe80::a00:27ff:fe00:ae5e%5: time<1ms
Reply from fe80::a00:27ff:fe00:ae5e%5: time<1ms
Reply from fe80::a00:27ff:fe00:ae5e%5: time<1ms
Reply from fe80::a00:27ff:fe00:ae5e%5: time<1ms

Ping statistics for fe80::a00:27ff:fe00:ae5e%5:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
tdeheurles commented 9 years ago

It switch to ipv6 when DHCP have no more address to give (can appear after lots of try). It special that ou can't reach from HOST. Are you sure the process didn't duplicate a network ?

what's your host ipconfig plz ?

potgieterdl commented 9 years ago

restarted everything. windows host

{lamb} ipconfig

Windows IP Configuration

Ethernet adapter Ethernet 3:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::501e:97a:d3c2:6c8d%5
   IPv4 Address. . . . . . . . . . . : 10.0.0.117
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.0.1

Ethernet adapter Ethernet 4:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::9cd:c72e:53e7:f401%9
   Autoconfiguration IPv4 Address. . : 169.254.244.1
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :

Ethernet adapter Ethernet 5:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::5d9c:64a:ba89:c6b7%16
   IPv4 Address. . . . . . . . . . . : 172.17.8.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::b07c:bb95:6cc1:d379%6
   IPv4 Address. . . . . . . . . . . : 192.168.253.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VirtualBox Host-Only Network #4:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::d568:9510:ece7:7701%11
   IPv4 Address. . . . . . . . . . . : 192.168.99.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VirtualBox Host-Only Network #5:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::f43d:2a2f:e1ea:9fa%17
   Autoconfiguration IPv4 Address. . : 169.254.9.250
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VirtualBox Host-Only Network #6:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::f060:1f9:cfbd:cc85%43
   IPv4 Address. . . . . . . . . . . : 172.16.1.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{F90B6351-391E-49DF-ADA5-09B0269A115C}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:1854:229f:f5ff:ff8a
   Link-local IPv6 Address . . . . . : fe80::1854:229f:f5ff:ff8a%4
   Default Gateway . . . . . . . . . : ::

Tunnel adapter isatap.{5E984923-0CE3-46B3-AF4E-926BDE0D25BC}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{8C03C4A9-CBAA-449E-980F-EDB68C228D64}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{F4E9EE4D-C08F-43B1-989C-49E045A7FB56}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{B2493391-7300-4C05-888B-E398CAFF9281}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{7A9F1CEB-4282-4B91-AE78-ED8093BD61ED}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{B5A1D5EA-7AD8-45CC-8717-9B9B8F8D388E}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

master1

core@master1 ~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
        inet6 fe80::a00:27ff:fea1:41b4  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:a1:41:b4  txqueuelen 1000  (Ethernet)
        RX packets 1711  bytes 206768 (201.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1160  bytes 145199 (141.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.0.119  netmask 255.255.255.0  broadcast 10.0.0.255
        inet6 fe80::a00:27ff:feb3:a0ce  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:b3:a0:ce  txqueuelen 1000  (Ethernet)
        RX packets 67  bytes 6715 (6.5 KiB)
        RX errors 0  dropped 3  overruns 0  frame 0
        TX packets 68  bytes 6795 (6.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.1.100  netmask 255.255.255.0  broadcast 172.16.1.255
        inet6 fe80::a00:27ff:fe08:cd2  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:08:0c:d2  txqueuelen 1000  (Ethernet)
        RX packets 2  bytes 378 (378.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 32  bytes 3834 (3.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 91  bytes 8752 (8.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 91  bytes 8752 (8.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pinging on master1

core@master1 ~ $ ping 10.0.0.119
PING 10.0.0.119 (10.0.0.119) 56(84) bytes of data.
64 bytes from 10.0.0.119: icmp_seq=1 ttl=64 time=0.000 ms

ping from windows

C:\Program Files\Oracle\VirtualBox {git}
{lamb} ping 10.0.0.119

Pinging 10.0.0.119 with 32 bytes of data:
Request timed out.

ping from nas (Ubuntu server)

potgietdl@nas:~$ ping 10.0.0.119
PING 10.0.0.119 (10.0.0.119) 56(84) bytes of data.
64 bytes from 10.0.0.119: icmp_seq=1 ttl=64 time=5.28 ms
64 bytes from 10.0.0.119: icmp_seq=2 ttl=64 time=0.392 ms
^C
--- 10.0.0.119 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.392/2.840/5.289/2.449 ms
tdeheurles commented 9 years ago

Working from an other HOST (nas) seems really good. I suppose a problem from windows (one more time :p).

I don't know for now ... strange ... There seems to have no other network like this one.

potgieterdl commented 9 years ago

np, can work around it.