Nic card not working



  • i purchased a preconfigured firewall with m0n0wall preinstalled and it did work fine, thinking i could wipe m0n0wall and install pfsense. install seems to go through fine but i could not ping the default ip on the firewall 192.168.1.1 the wan port recieves a public ip and i can ping yahoo.com from the console on the firewall. i can also ping the lan port (192.168.1.1) from the console only.
    i can not reach the web config for pfsense at all.
    i did some troubleshooting and have figured out to be my nic card may not be supported.
    the on board lan is a via vt6103l ( could not get this port to work at all)
    the daughter card is a AD3RTLANP 3 PORT NIC (realtech rtl8100c). the wan port works but the other 2 do not get anything at all. do i have a driver problem? can anything be done about it? i can return the firewall, but i really would like to get this one working.

    what has me confused is that everything worked with monowall.
    any suggestions thanks in advance



  • @comppuwork:

    the daughter card is a AD3RTLANP 3 PORT NIC (realtech rtl8100c). the wan port works but the other 2 do not get anything at all. do i have a driver problem? can anything be done about it? i can return the firewall, but i really would like to get this one working.

    Sounds like a Jetway motherboard and daughter card. The 3 daughter card interfaces should be all the same. I'm not sure what you mean by "the wan port works but the other 2 do not get anything at all". Do you mean you tried all three daughter card interfaces as the WAN interface but only the one you are currently using registered receiving an IP address from your ISP? If thats what you meant, how did you go about trying the other interfaces as the WAN interface and how did you verify they "did not get anything"?

    What did you directly connect to the LAN port? A switch? A computer?

    what has me confused is that everything worked with monowall.

    I believe monowall is based on an earlier version of FreeBSD than the version used in pfSense. Occasionally there are unintended regressions where a newer version of FreeBSD breaks support for a device supported by an older version of FreeBSD.

    For diagnostic purposes, it would probably be useful to make the working "WAN" port the LAN port so you can connect to the pfSense GUI, complete configuration and more readily provide further system information that can be more easily provided if it can be capture on another computer?

    Are you connected to a cable ISP rather than a xDSL ISP? I've seen reports that it is common for cable modems to remember the MAC address of the downstream device and only talk with that device. This could impact your problem using the other ports as WAN ports.


Log in to reply