[SOLVED] Proxmox VE 4.2 Bug "Default gateway already exists on interface 'vmbr0'."

[naisanza]

Brand new install of Proxmox VE 4.2

The issue is: unable to create new Linux/OVS Bridge, and throws error, "Default gateway already exists on interface 'vmbr0'" when the default gateways are _not_ the same.

Existing gateway: 10.0.1.1
New bridge gateway: 10.240.0.1

How are they the same? Is it a regex that's mis-parsing the inputs?


Screenshot:

The settings for new OVS Bridge:

address 10.240.0.1
netmask 255.240.0.0
gateway 10.240.0.1

/etc/network/interfaces:

root@world:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto vmbr0
iface vmbr0 inet static
address 10.0.1.10
netmask 255.255.255.0
gateway 10.0.1.1
bridge_ports eth0
bridge_stp off
bridge_fd 0

 

[dcsapak]

the gateway parameter is for the "default gateway", of which you can only have one per host.
(this is the gateway which will be used by default, if no other route is specified and has a higher priority)
also you try to set the gateway of the ovs bridge to itself, what would you like to accomplish with that?

 

[naisanza]

the gateway parameter is for the "default gateway", of which you can only have one per host.
(this is the gateway which will be used by default, if no other route is specified and has a higher priority)
also you try to set the gateway of the ovs bridge to itself, what would you like to accomplish with that?

I am creating a Linux/OVS Bridge to use as a virtual network (10.240.0.0/12) within the system. I'm going to create containers within that virtual network, such as a router, DHCP server, and DNS server. It will be a fully virtualized network stack.

A DMZ container (10.0.1.200/24) will be created as the gateway between the LAN (10.0.1.0/24) and the virtual network (10.240.0.0/12)

Firewall/iptable rules will be used to NAT/Proxy the DMZ container to the virtual network.

The virtual network will not be accessible by the LAN, and can only be accessed after authenticating through the DMZ container

 

[naisanza]

the gateway parameter is for the "default gateway", of which you can only have one per host.
(this is the gateway which will be used by default, if no other route is specified and has a higher priority)
also you try to set the gateway of the ovs bridge to itself, what would you like to accomplish with that?

I just needed to keep the Gateway empty

 

[Zaman]

Hello,
the vmbr0 is
IP
192.168.100.*
gateway
192.168.100.1
mask
255.255.255.0
i try to add vmbr1 using these ips( * bridge)
try
192.168.101.*
gateway
192.168.101.1
and try
10.10.10.10
gateway
10.10.10.1
but still get
"Default gateway already exists on interface 'vmbr0'."
so does there is bug as
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1390777
or there is another reason
I need the gateway to access to the service .
best regards

 

[Venkat teja Ravi]

Hello,
the vmbr0 is
IP
192.168.100.*
gateway
192.168.100.1
mask
255.255.255.0
i try to add vmbr1 using these ips( * bridge)
try
192.168.101.*
gateway
192.168.101.1
and try
10.10.10.10
gateway
10.10.10.1
but still get
"Default gateway already exists on interface 'vmbr0'."
so does there is bug as
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1390777
or there is another reason
I need the gateway to access to the service .
best regards

There will be only one default gateway for a host. I think One default gateway is already there with Vmbr0.

 

[wylker]

Falha na verificação de parâmetros. (400)

gateway: O gateway padrão já existe na interface 'enp11s0f0'