Failed to bring up vmbr0 & device vmbr0 already exists;

[ppwicho]

[SOLVED]
Hello Proxmox users and developers .

Sorry for post this, but I really need your help to solve this. I have a problem when I try to move from a segment /29 to a /30 one.
Please take a look of this

root@proxmox:/media/western/FalloProxMox# netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
159.xx.237.136  *               255.255.255.252 U         0 0          0 vmbr0
192.168.1.0     *               255.255.255.0   U         0 0          0 eth1

root@proxmox:/media/western/FalloProxMox#[B] ifup vmbr0[/B]
[B]device vmbr0 already exists; can't create bridge with the same name[/B]
[B]run-parts: /etc/network/if-pre-up.d/bridge exited with return code 1[/B]
SIOCADDRT: No such process
Failed to bring up vmbr0.

And of course I try the classical reboot.

root@proxmox:/media/western/FalloProxMox# /etc/init.d/networking restart
Running /etc/init.d/networking restart is deprecated because it may not enable again some interfaces ... (warning).
Reconfiguring network interfaces...device vmbr0 already exists; can't create bridge with the same name
run-parts: /etc/network/if-pre-up.d/bridge exited with return code 1
SIOCADDRT: No such process
Failed to bring up vmbr0.
done.

And my ifconfig

root@proxmox:/media/western/FalloProxMox# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:25:64:fc:fe:b2  
          inet6 addr: fe80::225:64ff:fefc:feb2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:2026 (1.9 KiB)
          Interrupt:24 Memory:e8000000-e8012800 
 
eth1      Link encap:Ethernet  HWaddr 00:25:64:fc:fe:b4  
          inet addr:192.168.1.30  Bcast:255.255.255.128  Mask:255.255.255.0
          inet6 addr: fe80::225:64ff:fefc:feb4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9020 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5679 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1368085 (1.3 MiB)  TX bytes:1424635 (1.3 MiB)
          Interrupt:25 Memory:ea000000-ea012800 
 
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:28 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3186 (3.1 KiB)  TX bytes:3186 (3.1 KiB)
 
venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 
[B]vmbr0     Link encap:Ethernet  HWaddr 00:25:64:fc:fe:b2  [/B]
[B]          i[I]net addr:1yy.xx.237.138  Bcast:1yy.xx.237.139  Mask:255.255.255.252 <  Something here mabe?. [/I][/B]
[B]          inet6 addr: fe80::225:64ff:fefc:feb2/64 Scope:Link[/B]
[B]          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1[/B]
[B]          RX packets:0 errors:0 dropped:0 overruns:0 frame:0[/B]
[B]          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0[/B]
[B]          collisions:0 txqueuelen:0 [/B]
[B]          RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)[/B]

And I look up at the /etc/nerwork/interfaces and looks like a new proxmox install.
I dont know if its problem of my new segment and proxmox, or I so dummy to see something wrong with the broadcast adress.


Thanks a lot for the proxmox project!!!!.

 

[ppwicho]

SOLVED: My mistake, it was a problem whit my gateway adress, solved when I checked my route -n and I saw that I was using the broadcast adress like a gateway .