Two Network Cards, Bridging and PFSense VLAN Detection

O

OsloFats

New Member
Oct 5, 2009
7
0
1
Hi ProxMox Team,

I configured a 2nd network card (eth1), added a second bridge pointed at eth1 as described in Martin's tutorial, then added pfSense 1.2.2 as Fully Virtualized KVM and booted the VM. The pfSense installer always looks for two network cards. Only one card was detected, "plip0". My ifconfig looks good and show that below. I also include output from the syslog on the start up. Is this a pfsense specific issue or something on my end or with ProxMox beta? I am using 1.4 beta2.

Syslog Output on the pfSense VM startup:

Oct 6 01:55:20 proxwww 4077 Starting new child 4077
Oct 6 01:55:20 proxwww 4078 Starting new child 4078
Oct 6 01:55:22 proxwww 4077 update ticket
Oct 6 01:55:25 kernel vmbr0: no IPv6 routers present
Oct 6 01:55:25 kernel eth0: no IPv6 routers present
Oct 6 01:55:25 kernel vmbr1: no IPv6 routers present
Oct 6 01:55:30 pvedaemon 4087 starting VM 103 on node 0 (localhost)
Oct 6 01:55:30 qm 4088 VM 103 start
Oct 6 01:55:31 kernel device vmtab103i0 entered promiscuous mode
Oct 6 01:55:31 kernel audit(1254812131.137:4): dev=vmtab103i0 prom=256 old_prom=0 auid=4294967295
Oct 6 01:55:31 kernel vmbr0: port 2(vmtab103i0) entering learning state
Oct 6 01:55:31 kernel vmbr0: topology change detected, propagating
Oct 6 01:55:31 kernel vmbr0: port 2(vmtab103i0) entering forwarding state
Oct 6 01:55:31 kernel device vmtab103i1 entered promiscuous mode
Oct 6 01:55:31 kernel audit(1254812131.149:5): dev=vmtab103i1 prom=256 old_prom=0 auid=4294967295
Oct 6 01:55:31 kernel vmbr1: port 2(vmtab103i1) entering learning state
Oct 6 01:55:31 kernel vmbr1: topology change detected, propagating
Oct 6 01:55:31 kernel vmbr1: port 2(vmtab103i1) entering forwarding state
Oct 6 01:55:31 qm 4088 VM 103 monitor command 'migrate_set_downtime 1'
Oct 6 01:55:31 pvedaemon 4087 VM 103 started
Oct 6 01:55:37 pvedaemon 4119 starting vnc proxy UPID:4119-4364:1254812137:vncproxy:0:103:root:5900:tbGVxAtispfyvpqjxoKiOArq+wM
Oct 6 01:55:37 pvedaemon 4119 CMD: /bin/nc -l -p 5900 -w 30 -c /usr/sbin/qm vncproxy 103 tbGVxAtispfyvpqjxoKiOArq+wM 2>/dev/null
Oct 6 01:55:41 kernel vmtab103i1: no IPv6 routers present
Oct 6 01:55:41 kernel vmtab103i0: no IPv6 routers present
Oct 6 01:59:24 proxwww 4077 update ticket
Oct 6 01:59:25 proxwww 4130 Starting new child 4130
Oct 6 01:59:30 proxwww 4131 Starting new child 4131

ifconfig shows:

eth0 Link encap:Ethernet HWaddr 00:1f:bc:01:32:28
inet6 addr: fe80::21f:bcff:fe01:3228/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15366 errors:0 dropped:0 overruns:0 frame:0
TX packets:16967 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2501494 (2.3 MiB) TX bytes:18934052 (18.0 MiB)
Interrupt:247 Base address:0xa000

eth1 Link encap:Ethernet HWaddr 00:1f:bc:01:32:29
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:246 Base address:0xc000

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:2643 errors:0 dropped:0 overruns:0 frame:0
TX packets:2643 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:704406 (687.8 KiB) TX bytes:704406 (687.8 KiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
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:0 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:1f:bc:01:32:28
inet addr:192.168.1.41 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21f:bcff:fe01:3228/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15366 errors:0 dropped:0 overruns:0 frame:0
TX packets:16961 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2286160 (2.1 MiB) TX bytes:18932432 (18.0 MiB)

vmbr1 Link encap:Ethernet HWaddr 00:1f:bc:01:32:29
inet addr:10.17.50.100 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::21f:bcff:fe01:3229/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:3240 (3.1 KiB)

vmtab103i0 Link encap:Ethernet HWaddr 00:ff:22:ba:64:c8
inet6 addr: fe80::2ff:22ff:feba:64c8/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:1 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vmtab103i1 Link encap:Ethernet HWaddr 00:ff:ef:3f:7e:e7
inet6 addr: fe80::2ff:efff:fe3f:7ee7/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Hope that gives enough info. Thanks.

Jaret Oslo
 
OsloFats said:
Hi ProxMox Team,

I configured a 2nd network card (eth1), added a second bridge pointed at eth1 as described in Martin's tutorial, then added pfSense 1.2.2 as Fully Virtualized KVM and booted the VM. The pfSense installer always looks for two network cards. Only one card was detected, "plip0". My ifconfig looks good and show that below. I also include output from the syslog on the start up. Is this a pfsense specific issue or something on my end or with ProxMox beta? I am using 1.4 beta2.

Syslog Output on the pfSense VM startup:

Oct 6 01:55:20 proxwww 4077 Starting new child 4077
Oct 6 01:55:20 proxwww 4078 Starting new child 4078
Oct 6 01:55:22 proxwww 4077 update ticket
Oct 6 01:55:25 kernel vmbr0: no IPv6 routers present
Oct 6 01:55:25 kernel eth0: no IPv6 routers present
Oct 6 01:55:25 kernel vmbr1: no IPv6 routers present
Oct 6 01:55:30 pvedaemon 4087 starting VM 103 on node 0 (localhost)
Oct 6 01:55:30 qm 4088 VM 103 start
Oct 6 01:55:31 kernel device vmtab103i0 entered promiscuous mode
Oct 6 01:55:31 kernel audit(1254812131.137:4): dev=vmtab103i0 prom=256 old_prom=0 auid=4294967295
Oct 6 01:55:31 kernel vmbr0: port 2(vmtab103i0) entering learning state
Oct 6 01:55:31 kernel vmbr0: topology change detected, propagating
Oct 6 01:55:31 kernel vmbr0: port 2(vmtab103i0) entering forwarding state
Oct 6 01:55:31 kernel device vmtab103i1 entered promiscuous mode
Oct 6 01:55:31 kernel audit(1254812131.149:5): dev=vmtab103i1 prom=256 old_prom=0 auid=4294967295
Oct 6 01:55:31 kernel vmbr1: port 2(vmtab103i1) entering learning state
Oct 6 01:55:31 kernel vmbr1: topology change detected, propagating
Oct 6 01:55:31 kernel vmbr1: port 2(vmtab103i1) entering forwarding state
Oct 6 01:55:31 qm 4088 VM 103 monitor command 'migrate_set_downtime 1'
Oct 6 01:55:31 pvedaemon 4087 VM 103 started
Oct 6 01:55:37 pvedaemon 4119 starting vnc proxy UPID:4119-4364:1254812137:vncproxy:0:103:root:5900:tbGVxAtispfyvpqjxoKiOArq+wM
Oct 6 01:55:37 pvedaemon 4119 CMD: /bin/nc -l -p 5900 -w 30 -c /usr/sbin/qm vncproxy 103 tbGVxAtispfyvpqjxoKiOArq+wM 2>/dev/null
Oct 6 01:55:41 kernel vmtab103i1: no IPv6 routers present
Oct 6 01:55:41 kernel vmtab103i0: no IPv6 routers present
Oct 6 01:59:24 proxwww 4077 update ticket
Oct 6 01:59:25 proxwww 4130 Starting new child 4130
Oct 6 01:59:30 proxwww 4131 Starting new child 4131

ifconfig shows:

eth0 Link encap:Ethernet HWaddr 00:1f:bc:01:32:28
inet6 addr: fe80::21f:bcff:fe01:3228/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15366 errors:0 dropped:0 overruns:0 frame:0
TX packets:16967 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2501494 (2.3 MiB) TX bytes:18934052 (18.0 MiB)
Interrupt:247 Base address:0xa000

eth1 Link encap:Ethernet HWaddr 00:1f:bc:01:32:29
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:246 Base address:0xc000

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:2643 errors:0 dropped:0 overruns:0 frame:0
TX packets:2643 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:704406 (687.8 KiB) TX bytes:704406 (687.8 KiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
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:0 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:1f:bc:01:32:28
inet addr:192.168.1.41 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21f:bcff:fe01:3228/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15366 errors:0 dropped:0 overruns:0 frame:0
TX packets:16961 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2286160 (2.1 MiB) TX bytes:18932432 (18.0 MiB)

vmbr1 Link encap:Ethernet HWaddr 00:1f:bc:01:32:29
inet addr:10.17.50.100 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::21f:bcff:fe01:3229/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:3240 (3.1 KiB)

vmtab103i0 Link encap:Ethernet HWaddr 00:ff:22:ba:64:c8
inet6 addr: fe80::2ff:22ff:feba:64c8/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:1 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vmtab103i1 Link encap:Ethernet HWaddr 00:ff:ef:3f:7e:e7
inet6 addr: fe80::2ff:efff:fe3f:7ee7/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Hope that gives enough info. Thanks.

Jaret Oslo
Click to expand...

did you a power off and start (not a reboot) after you added the second network card via web interface to your VM?

what network emulation do you use? e1000 is a good start.
 
OsloFats said:
Yes, e1000 worked. Thanks Tom. Is there a general rule to know which network driver to use? (Example virtio versus e1000 versus rtl8169?) Speed differences?

I did reference the paravirtualized network driver wiki at

http://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows

and Network Model at

http://pve.proxmox.com/wiki/Network_Model

Thanks,

J Oslo
Click to expand...

e1000 is the best tested. if you are unsure use e1000.

virtio could be better but the drivers are newer and not in every distribution available.
 
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