Proxmox adding a bad route?

[isparks_curtis]

I've got several Proxmox 3.1 machines that have a peculiar problem. After booting them up, an extra route is created that has to be deleted before the machine can talk to others on the same subnet. After booting, the routes look like this (public IPs masked):

# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
208.XXX.XXX.0 * 255.255.255.0 U 0 0 0 vmbr0
default 208.XXX.XXX.1 0.0.0.0 UG 0 0 0 vmbr0


The 208.XXX.XXX.0 route blocks the server from communicating with any other servers in this same subnet. After deleting this route, everything is fine again. But, after rebooting, this route is back again. What is creating this route?

 

[Richard]

The 208.XXX.XXX.0 route blocks the server from communicating with any other servers in this same subnet. After deleting this route, everything is fine again. But, after rebooting, this route is back again. What is creating this route?

Usually it comes from the entry with the keyword "gateway" in file /etc/network/interfaces

 

[wbumiller]

Almost, the gatway would be 208.*.1. The 208.*.0/24 route comes from the address and netmask properties in that file.

 

[isparks_curtis]

Thanks guys. Since I'm not getting any "me too" responses, I'm guessing this is not a Proxmox issue, but something being configured wrong on our network. I'm moving this discussion to ServerFault: http://serverfault.com/questions/777103/linux-adding-a-bad-route-on-startup

And since posting this to ServerFault, I've realized that the route that is being added is not a bad route, but that something else on the network is causing this route not to work. Deleting the route fixes the problem, but it's causing all traffic to go through the router, which is obviously undesirable.