• Doing a new build. Looking at the Lanner FW-7575 with an i3 in it.

    This is the Crystal Forest/Gladden/Cave Creek stuff (8910 chipset).

    What are the most likely pain points of getting this running?

    I had also been considering the similar Portwell CAR-3020 and the Axiomtek NA-360. I have been leaning toward the Lanner because they have a better CPU choice – the others don't actually plan to build an i3 config at all. If there's a reason to prefer one over the others for some other reason, I'd love to know it.


  • I'm thinking none…  The FW-7575 seems like the kind of machine that will work right away.  You will use a SSD?


  • @ohmantics:

    Doing a new build. Looking at the Lanner FW-7575 with an i3 in it.

    Out of curiosity, where are you looking at buying it from (and what's the price)?

  • Netgate Administrator

    Not sure if the i347 will be supported in 2.1 by default. You'd need to investigate that first. A more recent Intel Gigabit driver was backed out before 2.1 was released because it broke altq, traffic shaping. If you don't need that the driver can be used.

    Steve

    Edit: Appears to be defined in 8.3 release: http://svnweb.freebsd.org/base/release/8.3.0/sys/dev/e1000/e1000_defines.h?revision=234063&view=markup
    I'm still unsure though, you'd need to check.


  • @kejianshi:

    I'm thinking none…  The FW-7575 seems like the kind of machine that will work right away.  You will use a SSD?

    Yes, but only because I want better logging than the CF/embedded route.


  • @mapdirection:

    @ohmantics:

    Doing a new build. Looking at the Lanner FW-7575 with an i3 in it.

    Out of curiosity, where are you looking at buying it from (and what's the price)?

    From Lanner. I don't know the price yet, but these front-NIC machines seem to come at a premium.


  • Well - Logging and cache.  I was just wondering.  Its a very nice box.


  • @stephenw10:

    Not sure if the i347 will be supported in 2.1 by default. You'd need to investigate that first. A more recent Intel Gigabit driver was backed out before 2.1 was released because it broke altq, traffic shaping. If you don't need that the driver can be used.

    Steve

    Edit: Appears to be defined in 8.3 release: http://svnweb.freebsd.org/base/release/8.3.0/sys/dev/e1000/e1000_defines.h?revision=234063&view=markup
    I'm still unsure though, you'd need to check.

    The biggest red flag I saw was UEFI. I was wondering if there's a BIOS-compatibility solution, or if I'd be stuck on ESXi or something similar until FreeBSD 10/pfSense 2.2.

    I haven't seen anything that will use the Cave Creek DPDK stuff either.

    This feels too leading-edge for pfSense, but at the same time I want lower power consumption and something from this decade.


  • Sorry for the thread necromancy, but this original thread seems like a better place to migrate the discussion to from https://forum.pfsense.org/index.php?topic=76758.0.

    I've been running this box for several months under ESXi just fine. I've been trying to install natively after I learned that it could indeed boot with pfSense 2.1.

    To summarize the other thread, booting gets stuck indefinitely at "Configuring WAN interface…" which in this case is igb4, an Intel 82580DB. Under ESXi, this interface was virtualized.

    How can I approach debugging this boot problem?

  • Netgate Administrator

    Ok, so you have gone past the initial interface setup screen? Have you tried using different NICs as WAN? I assume the are identical.
    You could try booting verbose to see if any more error info is shown.
    Stuck at configuring WAN would usually mean it's trying to apply some config that can't be applied or waiting foe a DHCP response.

    Steve


  • Here's the verbose boot up to that point. I've tried all the NICs and get the same result.

    pfsense213bootlog.txt


  • you should try a 2.2 snapshot.


  • @gonzopancho:

    you should try a 2.2 snapshot.

    Log attached. It gets farther, but has the issues mentioned in the snapshots threads: no ssh, no webgui, no console menu. nmap shows 53, 80, and 443 open. It seems to offer DHCP and replies to DNS queries for itself (pfsense.localdomain).

    pfsense22boot.log.txt

  • Netgate Administrator

    Ok, so what you're seeing in 2.2 is the result of the current broken snapshots. If you try one of the older (perhaps oldest now) snapshots still on the server you may find it's good. You may have to start ssh manually. Alternatively wait a few days for a working build.

    In 2.1.3 it's hard to say quite what is happening there. I see you have an 8GB USB stick in the box as well as a 250GB HD. The usb stick is not reporting it's geometry correctly. I would remove that unless you have good reason to have it.

    Steve


  • @stephenw10:

    In 2.1.3 it's hard to say quite what is happening there. I see you have an 8GB USB stick in the box as well as a 250GB HD. The usb stick is not reporting it's geometry correctly. I would remove that unless you have good reason to have it.

    The USB stick is what we're booted off. The HD is where we'll install once things are stable. (It currently has ESXi and a 2.1.2 in a guest, which works just fine, even with igb0-igb3 on PCI passthrough.)

  • Netgate Administrator

    Try using the em NIC for WAN.

    Steve