I have setup pfsense on a different machine sometime ago, with no such problems, it was working flawlessly, and that was an exercise I have to go through, deciding whether I should go with CISCO ASA 5XXX Series, or buy a good server, and run an Open Source Firewall, in my case, I found that the best one would be pfsense after reading different reviews. I also noticed, that when a cable is removed from the socket, a message is displayed that bge0 or bge1 is down, when connected, is shows it is up, but it cannot be detected through the installer when configuring the network interface. Only users with topic management privileges can see it. This sort of problem report is too vague for anyone to be able to help without asking further questions. Regarding documentation, could you send me a link for the startup guide as I couldn’t find one, only installation guides, which I have already completed. Home Questions Tags Users Unanswered. I tried first pfsense 1.
||1 January 2016
||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
||Free* [*Free Regsitration Required]
ICMP echo request, idseq 66, length 64 I found that there is a patch to netxteeme applied to the driver, from FreeBSD, but I need to compile against the kernel. However, when pinging from the Wan to the box using the ip address, and running tcpdump -i bge0, I can see the echo request, but no echo reply from the pfsense box! As per ethdrnet email, my problem is: I’ve already get this kind of problem with broadcom integrated nic, the problem is not pfsense itself but freebsd 8.
Dell-IMSourcing Broadcom | Networking RR |
By default for security reasons the OPT interfaces don’t have firewall rules allowing traffic. It may be that you came to conclusion that bge1 as a LAN interface wasn’t working because you were looking for a particular form of “working” before you had advanced sufficiently far broafcom the configuration and setup. They are using a Broadcom Driver To sum up, after doing your suggestions and swapping the WAN with the LAN, and changing the cables, the problems seems to be in the driver.
Hi Wallabybob, Thanks for your detailed reply. I listened on the bge1 interface, when pinging from With rare exceptions stuff doesn’t get enabled unless it is specifically enabled. Then work through the previous paragraph if you haven’t already.
Dell HF692 Broadcom NetXtreme Gigabit PCIe Network Adapter 0hf692
I may be using them very early in initial setup but they are updated by the server vendor’s drivers pretty much first thing. Regarding documentation, could you send me a link for the startup guide as I couldn’t find one, only installation guides, which I have already completed. I can ping from the pfsense box other boxes on my wan with their ip address. So lets go with something simple: If you see incoming DHCP requests in a packet trace then you should see those requests logged.
The standard Interface, bge0 now works. Make sure your computers interface is in the Just so we know what FreeBSD thinks you have in your system, please provide the output of the shell commands on a pfSense 2. With rare exceptions, pfSense includes all the supported NIC drivers in the kernel, so its generally not necessary to configure special directives to load drivers. The couple of links you sent, I had already went through them, and they were irrelevant to my problem, of a card not working!
Not sure if that means that the interface is working but misconfigured, or is there another problem? I appreciate your help: This sort of problem report is too vague for anyone to be able to help without asking further questions.
As host of the pfSense open source firewall project, Netgate believes in enhancing network connectivity that maintains both security and privacy. I would appreciate if you beoadcom help me by pointing me to the right direction to fix this problem, as this computer has two built-in Network cards, bge0 and bge1.
I’m sure I got started initially by reading at least one clear “getting started” explanation in netztreme document somewhere in the pfSense web site follow the documentation link from the pfSense home page.
Product information, software announcements, and special offers. Would appreciate your help, Thanks, Dan.
For the time being then you would be better off making the pfSense interface closest to your local machines ethernef LAN interface then you should get responses to your pings. Just did some tests on the WAN. We also believe everyone should be able to afford it.
Unless you set rules to allow traffic, pfSense will block pretty much all inbound traffic on your WAN interface.