Configure pfSense Embedded



  • Hi,

    I've been reading a few of the tutorials and guides but can't seem to find a solution.

    I have the 4gb NanoBSD version of pfSense written to a 4gb CF card and it boots successfully in my HP Thin Client. From what I can gather you must connect to the machine first by the serial port and configure an IP address?

    Is there anyway to make the LAN interface preconfigured so I dont need a serial cable? e.g just plug in the network cable and access the web interface?

    If not does anyone have a guide or tutorial that will explain how I connect to my system? e.g. what settings I need? Is it even possible to connect to my system?

    Many Thanks



  • You could start here: http://doc.pfsense.org/index.php/Modifying_Embedded
    You would need to change the config to reflect the correct nics.
    If the device has a serial port, it will be easier to get a null modem cable and configure it.
    If you have an add in dual-port nic, boot another machine (that has a serial port) with your CF card and the nic.
    Assign LAN and WAN to the card, then shut down and move it back to the thin client.



  • @dotdash:

    You could start here: http://doc.pfsense.org/index.php/Modifying_Embedded
    You would need to change the config to reflect the correct nics.
    If the device has a serial port, it will be easier to get a null modem cable and configure it.
    If you have an add in dual-port nic, boot another machine (that has a serial port) with your CF card and the nic.
    Assign LAN and WAN to the card, then shut down and move it back to the thin client.

    Ok, I bit the bullet and got a null modem cable. Any tips on how to connect to my thin client? Will it just be auto detected?



  • If you are using Windows on the computer at the other end, one option is the program called PuTTY.  You will want to set the speed in PuTTY to 9600.



  • I got the system up and running (managed to login via the serial port etc). Manage to successfully configure all the interfaces etc, however none of the clients on the network are pulling down an IP address. pfsense is only installed on a HP thinclient with 128mb of memory, of which 16mb is dedicated to the video chip. Is it possible that the lack of memory would be causing the DHCP issue above?



  • @PANiCnz:

    Is it possible that the lack of memory would be causing the DHCP issue above?

    Doubtful, unless it's causing a process to crash.

    I'm running pfSense on an HP Thin Client, with 512MB of memory, which pfSense reports as less than 20% used.

    Is there anything in the DHCP logs.

    Cheers.



  • Your clients are connected to the interface on which you configured and enabled DHCP? (DHCP needs to be configured and enabled through the web GUI so you may need to set a static IP address on one system to do the web configuration.)



  • @wallabybob:

    Your clients are connected to the interface on which you configured and enabled DHCP? (DHCP needs to be configured and enabled through the web GUI so you may need to set a static IP address on one system to do the web configuration.)

    I thought DHCP was enabled by default? That might be the problem. I'm going to upgrade the memory never the less. I will setup a static IP and see what happens. The clients are connected the LAN interface via a switch, the WAN interface is successfully pulling an IP from the modem so I'm nearly there.

    Thanks for the assistance.


  • Rebel Alliance Developer Netgate

    DHCP is enabled by default.

    Is it possible you have the WAN and LAN cables reversed?



  • @jimp:

    DHCP is enabled by default.

    Is it possible you have the WAN and LAN cables reversed?

    Unfortunately not, I've tried switching the NIC's around and tried switching the cables around without success. Have since also tried Monowall to see if it is pfSense specific and I'm having the same problem there also (not surprising since pfSense is a Monowall fork). I've tried 3 different network cards so it doesnt appear to be related to the NIC's, all appear to be detected and installed correctly.

    I assume it can only be a hardware issue? But it seems werid that the mobo/cpu/memory would only affect DHCP on one interface.


Log in to reply