2.1 PPPOE vmware issue
-
Not sure if this is the right spot to post but here goes,
I installed 2.1 ova using the June 18 build. I dedicated a Nic in my esxi host to be directly connected to my DSL model, the other nic to my LAN.
ADSL<–----> ESXI vSwitch (WAN) --- PFsense EM0
LAN <------> ESXI vSwitch (LAN) --- PFsense EM1Within PFsense I configured PPPoE and connected to my ISP.
Under Status -> interfaces
The WAN Interface(pppoe0) shows connected and the IP give my by ISP, however it shows the MAC address as 00:00:00:00:00:00.From what I can tell... it is negotiating PPPoE but not passing any traffic
Any suggestions?
-
Can be helpfull especially the Open-VM Tools
http://doc.pfsense.org/index.php/PfSense_2_on_VMware_ESXi_5
-
Thanks for the Doc, I did have a read of it when setting up PFsense, I actually downloaded the VM OVA and imported it into ESXI.
The mapping of NICs to vswitches & VM seems to be working the issue is once the PPPoE session is connected and I get the IP from the ISP I cannot get to the internet. As mention in the previous post it seems weird that the MAC address in showing up 00:00:00:00:00:00 in 1.2.3 it show the MAC of the NIC
-
Try to set a fixed mac address in the vm networkadapter configuration menu
-
I had never noticed it but the MAC address on my ADSL interface (under ESXi 5.1) also shows as zeroes. I have no idea why that might be.
It's definitely passing traffic though. I would certainly hear about it if it wasn't ;)
-
@supermega - Have set the MAC in both pfsense and vmware.
@biggsy - Did you have to do anything particular to get it working? As Mentioned I can get it to connect but it won't pass traffic.
-
You shouldn't have to do anything special. ESXi doesn't even know that PPPOE is there.
Interfaces > WAN
- Enable the interface (I always forget this :-[ )
- Give it a meaningful description
- Under PPPOE - enter your ISP login info
- Block private and bogon networks
You shouldn't have had to set the MAC addresses but it looks like you're making the PPPOE connection OK.
Can you ping the gateway address shown under Status > Interfaces?
I've never used the OVA. What version of pfSense is it?
-
I am unable to ping anything external, google, DNS servers (by IP address), Gateway, etc
I have tried a couple version over the last few months, 1.2.3, 2.0, and now 2.1 (Jun 18)
2.1 was the first version that I was able to get an IP, before that it wouldn't connect all.
-
I am unable to ping anything external, google, DNS servers (by IP address), Gateway, etc
From where… a LAN-side machine, or from pfSense > Diagnostics > Ping (with the interface being WAN)?
-
I have tried pinging from both the diag interface and from a PC on the LAN
-
I have tried pinging from both the diag interface and from a PC on the LAN
I use pfSense almost exclusively under VMware. I use the standard build rather than the OVA appliance and I currently have running pf versions: 32 and 64 bit 1.2.3, 2.0.1-3 and 2.1 at various update points. This on ESXi 4.something, 5.0 and 5.1. Several of these are using PPPoE/A to get their WAN including my main office one which has two WANs over PPPoE. To create the VM I don't do anything special apart from select the OS type as FreeBSD and the arch (32 or 64 bit as required). I tend to allocate 2 processors and 512 - 1024Mb RAM and 5-10Gb disc. I remove the CDROM and floppy devices completely after installation (the CDROM polling can cause a kernel panic).
If I am using CARP I relax the vSwitch security to allow promisc mode etc.
Some of my PFs have OpenVM tools installed and some don't - to be honest I don't really see any noticeable difference in performance and I certainly don't bother with converting the NICs to the paravirtualized driver. I have tested the e1000 NIC under load and routing between two virtual subnets across three ESXis I can achieve wire speed. The last test I did was Linux VM -> pf VM -> Linux VM - each VM on a separate ESXi and a different subnet so being routed.
My PPPoE interfaces also show a MAC of all zeros which is fine because they are not real, physical interfaces.
I create an additional interface for each WAN in PF usually named WANxNIC which is the real physical interface to which I add an internal address to match the subnet that the the PPPoE modem has. I then NAT LAN outbound for that interface so that I can get at the stats on the modem.
Finally, I am based in the UK so I can only say that this works for me here.
I hope the above notes are of some use to help you narrow down things when you are troubleshooting. Basically: keep it simple and forget that you are using a VM!
Cheers
Jon -
You say one of your NICs is connected to the ADSL modem and pfSense is getting an IP from your ISP.
Is it definitely a public IP? Sorry if this seem obvious but sometimes it's worth asking ;)
-
Hi, same issue here, not using VMWare. This happens in the latest builds, I just restored an early image (2.1-RC0 (i386) - built on Tue Jun 18 18:30:16 EDT 2013) and the problem does not occur anymore.
It looks like pfSense is loosing the lease of the IP address after few minutes, the error I see in the PPP log is: "pptp enabled but could not resolve pptpdtarget".
Anyone else with this issue?
-
I have recently upgraded to July 2 version and am now experiencing the same problems.
From the Diag -> Ping on the WAN interface I can get to google… but not from a device on the LAN.