Network problem with new VE3.2 Install

A

auser

Renowned Member
Jul 17, 2014
37
7
73
Hello everyone.
I have been using Proxmox VE 3.1 for over a year and it is GREAT!
So thanks to all the team. :-)

Now I have repurposed a known working HP server and installed VE 3.2

I can use the web interface, spice and ssh console.
But there is some problem with network configuration
From the CLI I can ping the default gateway. :-)

Code: 
root@proxmox:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.240.0   U     0      0        0 vmbr0
default         192.168.4.1     0.0.0.0         UG    0      0        0 vmbr0

root@proxmox:~# ping 192.168.4.1
PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.
64 bytes from 192.168.4.1: icmp_req=1 ttl=64 time=16.4 ms
64 bytes from 192.168.4.1: icmp_req=2 ttl=64 time=9.73 ms
^C
--- 192.168.4.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 9.731/13.110/16.489/3.379 ms
So I commented out the broken .deb configuration so that I could
run aptitude update and aptitude upgrade :-)

I copied in backups of 2 VMs and restored them, with no errors reported.

This server has 4 ethernet ports.
For now I am using only 1.

Code: 
root@proxmox:~# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:1b:78:57:24:ea  
          inet6 addr: fe80::21b:78ff:fe57:24ea/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:202091 errors:0 dropped:0 overruns:0 frame:0
          TX packets:354878 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:55978086 (53.3 MiB)  TX bytes:157477482 (150.1 MiB)
          Interrupt:17 Memory:fdfe0000-fe000000 

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:1172521 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1172521 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:193337445 (184.3 MiB)  TX bytes:193337445 (184.3 MiB)

tap109i0  Link encap:Ethernet  HWaddr ae:07:1f:2e:ff:31  
          inet6 addr: fe80::ac07:1fff:fe2e:ff31/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:12220 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32494 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:882150 (861.4 KiB)  TX bytes:24497049 (23.3 MiB)

tap109i1  Link encap:Ethernet  HWaddr 46:4e:7a:d8:dc:31  
          inet6 addr: fe80::444e:7aff:fed8:dc31/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:8780 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8559 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:474304 (463.1 KiB)  TX bytes:555707 (542.6 KiB)

tap110i0  Link encap:Ethernet  HWaddr d6:0f:6d:08:80:2f  
          inet6 addr: fe80::d40f:6dff:fe08:802f/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:852 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19425 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:80393 (78.5 KiB)  TX bytes:1298170 (1.2 MiB)

tap110i1  Link encap:Ethernet  HWaddr b6:1a:72:80:db:8c  
          inet6 addr: fe80::b41a:72ff:fe80:db8c/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7914 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:1180 (1.1 KiB)  TX bytes:472594 (461.5 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)

vmbr0     Link encap:Ethernet  HWaddr 00:1b:78:57:24:ea  
          inet addr:192.168.4.222  Bcast:192.168.15.255  Mask:255.255.240.0
          inet6 addr: fe80::21b:78ff:fe57:24ea/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:148990 errors:0 dropped:0 overruns:0 frame:0
          TX packets:307342 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:17023486 (16.2 MiB)  TX bytes:154401272 (147.2 MiB)

The VMs IPs are not visible from the LAN. :-(

and nmap seems to be broken too. :-(

Code: 
root@proxmox:~# nmap 192.168.4.1

Starting Nmap 6.00 ( http://nmap.org ) at 2014-07-24 15:50 BST
route_dst_netlink: can't find interface "vmbr0"
root@proxmox:~# nmap -e vmbr0 192.168.4.1

Starting Nmap 6.00 ( http://nmap.org ) at 2014-07-24 15:54 BST
I cannot figure out what source address to use for device vmbr0, does it even exist?
QUITTING!
root@proxmox:~#

Can anyone help with this?

thankyou. :)
 
I see from my post that the MAC address of eth0 is _not_ a MAC address form any of the 4 ethernet ports.

Is this a problem?

Should the installer not have created eth0 using the first ethernet port tap109i0 and then created the bridge vmbr0 using that MAC adrress?

Code: 
root@proxmox:~# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:1b:78:57:24:ea  

tap109i0  Link encap:Ethernet  HWaddr ae:07:1f:2e:ff:31  

tap109i1  Link encap:Ethernet  HWaddr 46:4e:7a:d8:dc:31  

tap110i0  Link encap:Ethernet  HWaddr d6:0f:6d:08:80:2f  

tap110i1  Link encap:Ethernet  HWaddr b6:1a:72:80:db:8c  

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  

vmbr0     Link encap:Ethernet  HWaddr 00:1b:78:57:24:ea  
          inet addr:192.168.4.222  Bcast:192.168.15.255  Mask:255.255.240.0
          inet6 addr: fe80::21b:78ff:fe57:24ea/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:148990 errors:0 dropped:0 overruns:0 frame:0
          TX packets:307342 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:17023486 (16.2 MiB)  TX bytes:154401272 (147.2 MiB)
[/CODE]

I can however see from the above that vmbr0 has been TXing and RXing packets ok.
 
m.ardito said:
you should probably post your /etc/network/interfaces file

Marco
Click to expand...
Thanks marco.
will do so here.

Code: 
root@proxmox:~# cat /etc/network/interfaces 
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 192.168.4.222
        netmask 255.255.240.0
        gateway 192.168.4.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
root@proxmox:~#
 
Update: VM issue solved - I can see the VM IP from the LAN now.

I cannot see a way for me to edit the title of this thread to 'nmap error'.

The nmap error is still there though.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom