Installing PFsense on a VIA EPIA-M- and Compact Flash, no dhcp/access
Hi Everyone, I have been fighting installing PFsense on a small ITX appliance I built years ago for another purpose.
Via Epia M motherboard, 512mgs DDR, intergrated 10/100 as WAN
Intel Pro 100 NIC as LAN
1gb CF card +Adapter
Embedded image- hacked to allow VGA.
Now, I got the system to post, load, configure interfaces, and finish the basic install. When I connect my WAN and LAN interfaces, my WAN does NOT get a DHCP address and my LAN gets no DHCP assigned address. Nor can it ping 192.168.1.1.
If I take this exact config and replace the MB with a Intel MATX/Celeron 1.7, 512mgs and use the CF card, it works. Perfectly.
I have disabled everything in the VIA bios, updated its bios, tried different NICS (added a riser with 2 Linksys, still nothing.)
Am I missing something?
Thanks for the help. I cant wait to get this back up, my linksys enterprise 440n is starting to go out.
wallabybob last edited by
Is the WAN link up? (Check the LEDs at both ends. Check the interface status from the console by # ifconfig -a or from the WEB GUI by Status -> Interfaces.) If it is not UP consider whether you need a cross over cable or a straight through cable. Do you have the correct cable? (If you are connecting together two things that normally talk through a switch or hub you often need a cross over cable.)
Check your WAN interface type is DHCP (Interface -> WAN). Check the firewall log (Status -> System Logs, Firewall tab for DHCP packets) - perhaps you have a firewall rule blocking DHCP packets.
WAN card shows activity, Web GUI is NOT accessible.
WAN-> Via Onboard -> PFSENSE -> Intel Pro 100 -> Dlink switch -> laptop.
Even if I give my laptop a static 192.168.1.5 address, I still cant even ping the routers default 192.168.1.1 address.
Gave up and used a Celeron 1.7, 256mgs, and a Via board. 3 Intel Pro 100 nics.
All I did was plug the CF card+adapter into the other system, ran the basic config, and BAM. Works great.