hello,
Recently I tried to virtualize a pfSense 2.1.5 i386 on pve vm with the following config:
Physical machine consists of 3 nics. 1 for lan access, 1 direclty connected to adsl router1 and 1 directly connected to router2.
Note that the reason I have selected rtl8139 as vm nic is for compatibility reasons (I have also tried e1000 and virtio with same issue).
The problem:
VM works very well for some time. Then suddenly LAN interface of pfSense stops responding to any request (e.g ping). As a consequence, all LAN computers
do not have internet access anymore.
The workaround:
If I stop vm, change a number or letter on vm lan mac address (e.g from 46:79:94:31:4C:39 to 46:79:94:31:4C:38) and finally poweron again the vm everything works again (without reconfiguring interfaces on pfsense) for some time and again the same thing happens.
What I have tried:
1. e1000 as vm nic (same problem)
2. virtio as vm nic (it was recognized by pf by following their guide but for some reason no traffic passes through any of the interfaces)
3. rtl8139 (same problem).
Note: At this point I would like to inform that on this PVE box I have another vm (zimbra for testing) which works all the time correctly without loosing access with lan. It's vm nic is set to e1000. This leads me to think that something is wrong with pfsense.
More info:
WAN1:
LAN:
WAN2:
Anyone that has experiences this issue?
thank you
Recently I tried to virtualize a pfSense 2.1.5 i386 on pve vm with the following config:
Code:
balloon: 512bootdisk: ide0
cores: 1
cpuunits: 5000
ide0: local:100/vm-100-disk-1.qcow2,format=qcow2,cache=directsync,size=10922M
ide2: none,media=cdrom
memory: 1250
name: pfsense
net0: rtl8139=46:79:94:31:4C:39,bridge=vmbr0
net1: rtl8139=36:89:9C:94:F3:00,bridge=vmbr1
net2: rtl8139=1E:56:32:2A:2E:9A,bridge=vmbr2
onboot: 1
ostype: other
smbios1: uuid=a76d6545-0fc2-4bc5-96b9-0b8d87a0d615
sockets: 1
startup: order=1
tablet: 0
vga: stdPhysical machine consists of 3 nics. 1 for lan access, 1 direclty connected to adsl router1 and 1 directly connected to router2.
Note that the reason I have selected rtl8139 as vm nic is for compatibility reasons (I have also tried e1000 and virtio with same issue).
The problem:
VM works very well for some time. Then suddenly LAN interface of pfSense stops responding to any request (e.g ping). As a consequence, all LAN computers
do not have internet access anymore.
The workaround:
If I stop vm, change a number or letter on vm lan mac address (e.g from 46:79:94:31:4C:39 to 46:79:94:31:4C:38) and finally poweron again the vm everything works again (without reconfiguring interfaces on pfsense) for some time and again the same thing happens.
What I have tried:
1. e1000 as vm nic (same problem)
2. virtio as vm nic (it was recognized by pf by following their guide but for some reason no traffic passes through any of the interfaces)
3. rtl8139 (same problem).
Note: At this point I would like to inform that on this PVE box I have another vm (zimbra for testing) which works all the time correctly without loosing access with lan. It's vm nic is set to e1000. This leads me to think that something is wrong with pfsense.
More info:
Code:
pveversion -vproxmox-ve-2.6.32: 3.3-138 (running kernel: 2.6.32-33-pve)
pve-manager: 3.3-2 (running version: 3.3-2/995e687e)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-33-pve: 2.6.32-138
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.1-35
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-9
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
Code:
Linux proxmox1 2.6.32-33-pve #1 SMP Fri Sep 26 08:02:30 CEST 2014 x86_64 GNU/LinuxWAN1:
Code:
ethtool -i eth0
driver: 8139too
version: 0.9.28
firmware-version:
bus-info: 0000:03:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: noLAN:
Code:
ethtool -i eth1
driver: atl1c
version: 1.0.1.0-NAPI
firmware-version:
bus-info: 0000:04:00.0
supports-statistics: no
supports-test: no
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: noWAN2:
Code:
ethtool -i eth2
driver: 8139too
version: 0.9.28
firmware-version:
bus-info: 0000:03:01.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: noAnyone that has experiences this issue?
thank you
