I searched but could not find my particular situation, please advise if anyone has seen this.
I have a proxmox server installed on a 64.x.x.138 and then on that server I have created a centos 5 container and assigned the ip range assigned to me of 208.x.x.34 for the eth0 interface. I set this container up using the veth bridge option to vmbr0. That works, and i can ping the .34 ip just fine from outside world. However I was assigned a /28 of ips and when i set up a ifcfg-eth0-range0 file and populate it with the start and end ip, I restart the network service and they all show up fine as if they are active. No errors. but I cannot ping them. Whats weird is, if I change the main ip to .35 or any other ip assigned to me, it then works. So it sounds like something in the range setup not working, but I have another container with the same range set up and it works fine? The only difference with the other container is the subnets on those are /29. Am I missing something?
eth0 Link encap:Ethernet HWaddr 4A:BC:A4:33:FE:E7
inet addr:208.x.x.34 Bcast:208.x.x.47 Mask:255.255.255.240
inet6 addr: fe80::48bc:a4ff:fe33:fee7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:284 errors:0 dropped:0 overruns:0 frame:0
TX packets:311 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
eth0:0 Link encap:Ethernet HWaddr 4A:BC:A4:33:FE:E7
inet addr:208.x.x.35 Bcast:208.x.x.47 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
range file contents:
IPADDR_START=208.x.x.35
IPADDR_END=208.x.x.46
CLONENUM_START=0
I have a proxmox server installed on a 64.x.x.138 and then on that server I have created a centos 5 container and assigned the ip range assigned to me of 208.x.x.34 for the eth0 interface. I set this container up using the veth bridge option to vmbr0. That works, and i can ping the .34 ip just fine from outside world. However I was assigned a /28 of ips and when i set up a ifcfg-eth0-range0 file and populate it with the start and end ip, I restart the network service and they all show up fine as if they are active. No errors. but I cannot ping them. Whats weird is, if I change the main ip to .35 or any other ip assigned to me, it then works. So it sounds like something in the range setup not working, but I have another container with the same range set up and it works fine? The only difference with the other container is the subnets on those are /29. Am I missing something?
eth0 Link encap:Ethernet HWaddr 4A:BC:A4:33:FE:E7
inet addr:208.x.x.34 Bcast:208.x.x.47 Mask:255.255.255.240
inet6 addr: fe80::48bc:a4ff:fe33:fee7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:284 errors:0 dropped:0 overruns:0 frame:0
TX packets:311 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
eth0:0 Link encap:Ethernet HWaddr 4A:BC:A4:33:FE:E7
inet addr:208.x.x.35 Bcast:208.x.x.47 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
range file contents:
IPADDR_START=208.x.x.35
IPADDR_END=208.x.x.46
CLONENUM_START=0