pfSense WAN issue

Today I received my Intel NICs, put them in my pfSense machine and I cannot get an IP on the WAN interface via DHCP. So I tested both NICs and both work. Previously, I was using an on-board NIC so for the sake of testing, I plugged an Ethernet cable from the WAN into the on-board NIC and I can get an IP from DHCP. I unplugged my modem for 20 minutes and plugged it back in and tried again on the new Intel NIC but the same thing happens, WAN interface shows 0.0.0.0 (DHCP). At this point, I'm not sure what is wrong unless these new Intel NICs are not compatable.

Just to add, I'm using the latest release of pfSense 1.2.1.

These are the Intel NICs:
http://www.newegg.com/Product/Product.aspx?Item=N82E16833106121

From what you have said, I assume you plugged this box directly into your cable or DSL modem. Your ISP probably limits which MAC addresses are on their network. If this is the case, then call your ISP and have them add your new MAC address to their system.

Dawizman said:

From what you have said, I assume you plugged this box directly into your cable or DSL modem. Your ISP probably limits which MAC addresses are on their network. If this is the case, then call your ISP and have them add your new MAC address to their system.

Click to expand...

This isn't the case.

My same setup, with the new NICS works with IPCop but not with pfSense.

did you try reseting your modem AND then the pfsense box?

Are you using the Auto Detect utility on the box itself? I had a similar issue once where it would detect fine, but would never get an IP. LAN worked fine but WAN would never map correctly. I entered in the port name manually ("x10" or something if I recall, it was a while back) and it worked. Might be worth a shot.

OmegaAvenger said:

did you try reseting your modem AND then the pfsense box?

Click to expand...

I only tried power cycling my modem with my pfSense box still on. I'll give this a shot.

Karlos said:

Are you using the Auto Detect utility on the box itself? I had a similar issue once where it would detect fine, but would never get an IP. LAN worked fine but WAN would never map correctly. I entered in the port name manually ("x10" or something if I recall, it was a while back) and it worked. Might be worth a shot.

Click to expand...

Hmm, that'd be an odd issue. I can try this and see what happens. Auto-detect picks up my NICs and hands out a IP on my on-board NIC but not with the Intel NICs. I'll input the interface names manually to see if this helps.

Thanks.