[PVE-User] Proxmox VE Networking issues

[Shain Miley]

Well what I am trying to do is assign my windows 2003 Guest (KVM) a real 
routable ip address...whenever I do so I am unable to access any 
machines on any network (besides 127.0.0.1).  When I use a dhcp server 
to assign the ip address (and it gets an internal ip) I can of course 
access machines outside the network..but I am unable to access the guest 
OS from another machine outside the network (remote desktop for example).

So there is a misconfiguration somewhere...it works fine on the openVZ 
VE's just not on the KVM side.

cat /etc/network/interfaces

auto br0
iface br0 inet static
address 174.x.x.83
network 174.x.x.0
netmask 255.255.255.0
broadcast 174.x.x.255
gateway 174.x.x.254
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off


Thanks,

Shain



Dietmar Maurer wrote:
>  
>   
>> Hello all,
>> I was wondering if someone could shed some light on how  
>> exactly I am supposed to get public (routable) ip addresses 
>> working for both OpenVZ and KVM guest OS's?
>>     
>
> Should work by default.
>  
>   
>> When I first setup Proxmox I was able to assign a public ip 
>> address to the openVZ guests that I setup...that worked fine.
>>
>> However after I setup a Windows 2003 server on the KVM side 
>> (it's networking working fine if I used the default 
>> non-routable address) I decided that I wanted to enable 
>> remote desktop..which would require that I use a routable address.
>>
>> After setting up a bridge (br0) on the host OS (and following 
>> some online help)..none of the guest os's networking seems to 
>> be working correctly :-(
>>     
>
> What are you doing exactly? By default there is a bridge called
> Vmbr0, and all VM connect to that bridge.
>
> So why do you create a bridge called br0?
>
> - Dietmar
>
>
>   


-- 
Shain Miley | Level IV Unix System Administrator | NPR Digital Media | 202-513-3649