Hello,
I changed the IP configuration form DHCP to static. The problem is, that after I changed the the configuration from DHCP to static it also changes routes. I have only one network interface (eth0). Which is connected to netowork 10.142.0.0/20.
By default (DHCP) the VM comes with the following routes:
And in this configuration I am able to ping and access e.g. server 10.142.0.3, but when I changed the ip address to static, I see the following routes:
And since that time I am not able to ping or access any other servers in the same network. I found, that when remove the route created by ClearOS, it again starts to work.
It is possible to access the VM from public IP address, but not possible to work with the other VMs in the same subnet.
Later I installed OpenVPN which gave me the following routes:
When I remove the latest route above...
Does exists any way how to remove the route created by ClearOS or solve it anyhow?
Thank you
Ondrej
I changed the IP configuration form DHCP to static. The problem is, that after I changed the the configuration from DHCP to static it also changes routes. I have only one network interface (eth0). Which is connected to netowork 10.142.0.0/20.
By default (DHCP) the VM comes with the following routes:
[root@instance-3 ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default gateway 0.0.0.0 UG 0 0 0 eth0
gateway 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
And in this configuration I am able to ping and access e.g. server 10.142.0.3, but when I changed the ip address to static, I see the following routes:
[root@instance-3 ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default gateway 0.0.0.0 UG 0 0 0 eth0
10.142.0.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0
And since that time I am not able to ping or access any other servers in the same network. I found, that when remove the route created by ClearOS, it again starts to work.
It is possible to access the VM from public IP address, but not possible to work with the other VMs in the same subnet.
Later I installed OpenVPN which gave me the following routes:
[root@instance-3 ~]$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.142.0.1 0.0.0.0 UG 0 0 0 eth0
10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun1
10.8.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun1
10.8.10.0 10.8.10.2 255.255.255.0 UG 0 0 0 tun0
10.8.10.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
10.142.0.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0
[root@instance-3 ~]$ ping 10.142.0.3
PING 10.142.0.3 (10.142.0.3) 56(84) bytes of data.
From 10.142.0.4 icmp_seq=1 Destination Host Unreachable
From 10.142.0.4 icmp_seq=2 Destination Host Unreachable
From 10.142.0.4 icmp_seq=3 Destination Host Unreachable
From 10.142.0.4 icmp_seq=4 Destination Host Unreachable
^C
--- 10.142.0.3 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4001ms
pipe 4
When I remove the latest route above...
[root@instance-3 ~]$ ip route del 10.142.0.0/20
[root@instance-3 ~]$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.142.0.1 0.0.0.0 UG 0 0 0 eth0
10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun1
10.8.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun1
10.8.10.0 10.8.10.2 255.255.255.0 UG 0 0 0 tun0
10.8.10.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
[root@instance-3 ~]$ ping 10.142.0.3
PING 10.142.0.3 (10.142.0.3) 56(84) bytes of data.
64 bytes from 10.142.0.3: icmp_seq=1 ttl=128 time=1.44 ms
64 bytes from 10.142.0.3: icmp_seq=2 ttl=128 time=0.272 ms
64 bytes from 10.142.0.3: icmp_seq=3 ttl=128 time=0.342 ms
^C
--- 10.142.0.3 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.272/0.686/1.446/0.538 ms
Does exists any way how to remove the route created by ClearOS or solve it anyhow?
Thank you
Ondrej
Share this post:
Responses (9)
-
Accepted Answer
Hello Nick,
I did some investigation and found, that this route is pushed by Google and can't be changed. This route is pushed only when the NIC is configured with static IP address instead of DHCP. For DHCP, there is no problem with communication inside the network. I used the static configuration to solve some issues, but it looks it caused more issues than the DHCP.
I think we can close this topic. Thank you for your help.
Best regards
Ondrej -
Accepted Answer
-
Accepted Answer
OK. My comment about UH is invalid but on my real box with multiple NIC's but configured as standalone, I have no problems setting the WAN to Static and pinging the rest of my WAN. My routing table looks like:
Docker0 is a bridge device and enp2s0f1 is a LAN NIC but the server is in Standalone - No Firewall mode for this test.[root@microserver ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default gateway 0.0.0.0 UG 0 0 0 enp2s0f0
172.17.0.0 0.0.0.0 255.255.240.0 U 0 0 0 enp2s0f0
172.18.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
172.22.22.0 0.0.0.0 255.255.255.0 U 0 0 0 enp2s0f1 -
Accepted Answer
Hello Nick,
The problematic route does not have UH flag. It has just U flag.
10.142.0.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0
When I remove this route from the list of routes I am able to ping the local network VMs then.
Screenshots attached.
Here is once again problem with the route:
[root@clearos ~]$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.142.0.1 0.0.0.0 UG 0 0 0 eth0
10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun1
10.8.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun1
10.8.10.0 10.8.10.2 255.255.255.0 UG 0 0 0 tun0
10.8.10.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
10.142.0.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0 # This is the problematic route
[root@clearos ~]$ ping 10.142.0.3
PING 10.142.0.3 (10.142.0.3) 56(84) bytes of data.
^C
--- 10.142.0.3 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms
[root@clearos ~]$ sudo ip route del 10.142.0.0/20
[root@clearos ~]$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.142.0.1 0.0.0.0 UG 0 0 0 eth0
10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun1
10.8.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun1
10.8.10.0 10.8.10.2 255.255.255.0 UG 0 0 0 tun0
10.8.10.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
[root@clearos ~]$ ping 10.142.0.3
PING 10.142.0.3 (10.142.0.3) 56(84) bytes of data.
64 bytes from 10.142.0.3: icmp_seq=1 ttl=128 time=13.4 ms
64 bytes from 10.142.0.3: icmp_seq=2 ttl=128 time=0.345 ms
64 bytes from 10.142.0.3: icmp_seq=3 ttl=128 time=0.343 ms
^C
--- 10.142.0.3 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.343/4.700/13.412/6.160 ms
[root@clearos ~]$
Thank you for your help.
Ondrej -
Accepted Answer
Sorry but I cannot reproduce. I've tried in a VM and in a live box. The only difference is that they both had LAN NIC's installed, but in both cases I could not get a route with a UH flag set in standalone mode with a static IP - testing with both a 255.255.255.0 and 255.255.240.0 netmask.
Can you make some screen dumps of the IP Settings screen? -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
[root@clearos ~]# cat /etc/clearos/network.conf
# Network mode
MODE="standalone"
# Network interface roles
EXTIF="eth0"
LANIF=""
DMZIF=""
HOTIF=""
# Domain and Internet Hostname
DEFAULT_DOMAIN="clearos.host.net"
INTERNET_HOSTNAME="clearos.host.net"
# Extra LANS
EXTRALANS=""
# ISP Maximum Speeds
ETH0_MAX_DOWNSTREAM=0
ETH0_MAX_UPSTREAM=0
[root@clearos ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.142.0.4 netmask 255.255.240.0 broadcast 10.142.15.255
inet6 fe80::4001:aff:fe8e:4 prefixlen 64 scopeid 0x20<link>
ether 42:01:0a:8e:00:04 txqueuelen 1000 (Ethernet)
RX packets 4963 bytes 1187486 (1.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4501 bytes 1062522 (1.0 MiB)
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 1000 (Local Loopback)
RX packets 2523 bytes 279571 (273.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2523 bytes 279571 (273.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.8.10.1 netmask 255.255.255.255 destination 10.8.10.2
inet6 fe80::8af1:d5e0:30a6:452f prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 144 (144.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tun1: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.8.0.1 netmask 255.255.255.255 destination 10.8.0.2
inet6 fe80::3b77:8bc9:ade:777a prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 144 (144.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[root@clearos ~]#
-
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »