OpenVZ Forum


Home » General » Support » *SOLVED* Moving default NIC
Re: Moving default NIC [message #4602 is a reply to message #4580] Mon, 17 July 2006 17:20 Go to previous messageGo to previous message
jmeek is currently offline  jmeek
Messages: 9
Registered: July 2006
Junior Member

Like I said, I was being dense. Later that day I found that change but had to destroy the VM and create another to effect the change. My current challenge is now (slightly) further down the line in that now that I'm on the right NIC I can see local network but I can't get the default g/w to stick. I have reviewed the forums about "ip route show" and related adjustments but just cannot see the easy way to ensure that the VM gets the default g/w of eth3 (I only get a default g/w of 191.<something> which is not on my network at all) and get the packets to leave the correct interface. As you can see below I am still leaving on the 100 network, not the 102.

(HARPALYKE is the host)

[root@harpalyke ~]$ ip route show
10.30.102.101 dev venet0 scope link src 10.30.100.23
10.30.100.0/24 dev eth0 proto kernel scope link src 10.30.100.23
10.30.102.0/24 dev eth3 proto kernel scope link src 10.30.102.23
169.254.0.0/16 dev eth3 scope link
default via 10.30.100.2 dev eth0

[root@harpalyke ~]$ vzctl exec 101 ip route show
191.255.255.0/24 dev venet0 scope host
169.254.0.0/16 dev venet0 scope link
default via 191.255.255.1 dev venet0

[root@harpalyke ~]$ vzctl exec 101 ping 10.30.102.5
PING 10.30.102.5 (10.30.102.5) 56(84) bytes of data.
64 bytes from 10.30.102.5: icmp_seq=0 ttl=127 time=550 ms
64 bytes from 10.30.102.5: icmp_seq=1 ttl=127 time=0.174 ms

[root@harpalyke ~]$ vzctl exec 101 ping 10.30.100.5

[root@harpalyke ~]$ vzctl exec 101 traceroute 10.30.100.5
traceroute to 10.30.100.5 (10.30.100.5), 30 hops max, 38 byte packets
1 harpalyke.jupiter.private (10.30.100.23) 0.120 ms 0.048 ms 0.034 ms

[root@harpalyke ~]$ vzctl exec 101 ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:84 errors:0 dropped:0 overruns:0 frame:0
TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12139 (11.8 KiB) TX bytes:12139 (11.8 KiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:161 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:13327 (13.0 KiB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.30.102.101 P-t-P:10.30.102.101 Bcast:10.30.102.101 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: multiple NICs on Different Networks with different default gateways
Next Topic: name based routing to VE's possible?
Goto Forum:
  


Current Time: Sat Aug 03 23:19:49 GMT 2024

Total time taken to generate the page: 0.02459 seconds