On Sun, Aug 31, 2014 at 4:54 PM, Reindl Harald h.reindl@thelounge.net wrote:
who knows - looking at other threads - why did you assign *two* network interfaces to your virtual machine at all?
Because if for any reason WAN is down then I can reach the VM trough the DHCP assigned IP I though
who knows? why don't you just restart your network service in the guest?
Because this is not the problem, as I mention before I have another VM running on the same Vmware and all of them has Internet access so the problem is here with this one at some part but I'm able to find it
Ok, now I've fixed the Internet connection by running this command: ip route replace default via 192.168.1.1 but now I have two default routes:
# ip route show default via 192.168.1.1 dev eno16780032 default via 192.168.3.1 dev eno33555200 proto static metric 1024 192.168.1.0/24 dev eno16780032 proto kernel scope link src 192.168.1.112 192.168.3.0/24 dev eno33555200 proto kernel scope link src 192.168.3.131
Is that right? How do I remove the second one? (default via 192.168.3.1 dev eno33555200 proto static metric 1024)
On Sun, Aug 31, 2014 at 4:57 PM, reynierpm@gmail.com reynierpm@gmail.com wrote:
On Sun, Aug 31, 2014 at 4:54 PM, Reindl Harald h.reindl@thelounge.net wrote:
who knows - looking at other threads - why did you assign *two* network interfaces to your virtual machine at all?
Because if for any reason WAN is down then I can reach the VM trough the DHCP assigned IP I though
who knows? why don't you just restart your network service in the guest?
Because this is not the problem, as I mention before I have another VM running on the same Vmware and all of them has Internet access so the problem is here with this one at some part but I'm able to find it
On 8/31/2014 2:27 PM, reynierpm@gmail.com wrote:
Because this is not the problem, as I mention before I have another VM running on the same Vmware and all of them has Internet access so the problem is here with this one at some part but I'm able to find it
grep 192.168.3.1 /etc/sysconfig/network-scripts/*
alternately, is the 192.168.3.x interface being configured by DHCP? perhaps its DHCP server is handing out that gateway.
On Sun, Aug 31, 2014 at 5:03 PM, John R Pierce pierce@hogranch.com wrote:
grep 192.168.3.1 /etc/sysconfig/network-scripts/*
# grep 192.168.3.1 /etc/sysconfig/network-scripts/* /etc/sysconfig/network-scripts/ifcfg-local:IPADDR=192.168.3.131 /etc/sysconfig/network-scripts/ifcfg-local:GATEWAY=192.168.3.1
alternately, is the 192.168.3.x interface being configured by DHCP? perhaps its DHCP server is handing out that gateway.
No, it's handled static:
TYPE=Ethernet ONBOOT=yes BOOTPROTO=static IPADDR=192.168.3.131 GATEWAY=192.168.3.1 NETMASK=255.255.255.0 NAME="Local Eth1" UUID=0a79e5fc-ee8a-41eb-93dd-a76e3cb8c7c1 HWADDR=00:50:56:3F:86:30
On 8/31/2014 2:35 PM, reynierpm@gmail.com wrote:
# grep 192.168.3.1/etc/sysconfig/network-scripts/* /etc/sysconfig/network-scripts/ifcfg-local:IPADDR=192.168.3.131 /etc/sysconfig/network-scripts/ifcfg-local:GATEWAY=192.168.3.1
localhost shouldn't have a gateway. or that IP
hmm, I don't even have a ifconfig-local, just a ifcfg-lo, and it reads...
[root@new network-scripts]# more ifcfg-lo DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 # If you're having problems with gated making 127.0.0.0/8 a martian, # you can change this to something else (255.255.255.255, for example) BROADCAST=127.255.255.255 ONBOOT=yes NAME=loopback
-
John R Pierce -
reynierpm＠gmail.com