[SOLVED] Problems with NF9HQL-525 and pfSense-LiveCD-2.1-RC0-amd64-20130609-2130



  • I am finding it impossible to configure pfSense 2.1 RC0 with the JetWay NF9HQL-525.

    I have two ports configured re0 and re1, re0 is wan re1 is lan.

    For some reason, I can't get any incoming packets on re0 (WAN). I've added wide open rules to allow all traffic from any to any, still no incoming packets. There are no block messages for the interface, it just wont accept packets in.

    for example, when I try to ping an external IP, I will see the packets out increasing, but nothing on the packets in.

    The odd part is that it gets the DHCP configuration from FIOS fine, but thats it.

    Any ideas?



  • Please post a screenshot showing the firewall rules on the WAN interface. The order of rules is significant.

    @joeya:

    IFor some reason, I can't get any incoming packets on re0 (WAN).

    I presume you mean packets arriving on the WAN interface seem to disappear rather than you have done a packet capture on the WAN interface and verified nothing is arriving.



  • @wallabybob:

    Please post a screenshot showing the firewall rules on the WAN interface. The order of rules is significant.

    I presume you mean packets arriving on the WAN interface seem to disappear rather than you have done a packet capture on the WAN interface and verified nothing is arriving.

    Sure, there is only one rule on the WAN interface though and it is allow any to any with any protocol on ipv4 (I have to wait to post a screen shot, on my laptop using my phone for internet)

    And yes you are correct, I did not do a packet capture. The stats I am referring to are via the interface statistics screen. There is 1 packet in when I start up pfsense, and eventually several thousand packets out, but packet in never changes.

    EDIT
    Attached rule




  • @joeya:

    And yes you are correct, I did not do a packet capture. The stats I am referring to are via the interface statistics screen. There is 1 packet in when I start up pfsense, and eventually several thousand packets out, but packet in never changes.

    That suggests there aren't any packets arriving at the interface or the hardware is broken. But if the hardware was broken it is unlikely any incoming packets would be noted.

    If you don't have any other means of checking traffic arriving at the WAN interface perhaps your ISP can help provide some verification. However the fact they send packets to your system doesn't mean they arrive, for example, your "modem" might not be working correctly.

    Have you tried switch cables connected to the LAN and WAN interfaces?

    Have you tried swapping the interface assignment?



  • I thought the same.

    I put my old device with pfsense 2.0.3 back and all works fine and there is no modem, it is a direct connection from my ont.

    I fortunately I can't test another build on the jetway since only 2.1 has the nic drivers for this device.

    What I did do was swap re0 and re1 from wan to lan. At this point re0 started sending and receiving packets on the lan subnet and re1 (wan) exhibited the same behavior as when it was re0, meaning no incoming only outgoing.

    So I know its not the ont, nor the cables, and the above test makes me feel confident that its not the device alone.

    It appears to be something specific to this release + this device on the wan config only.

    I'll post some logs and captures tomorrow, hopefully that might shed some light on this.



  • I have such this model of board and I was waiting for the version 2.1 of pfSense as it supposes to support NIC driver of such board!
    I didn't try it with 2.1 yet but I am sad to hear that it didn't work well with you :(
    Hopefully will hear good news about the solution soon :)



  • Ok I got it working, and its working REALLY well.

    Very very odd behavior though.

    When I put in a cloned mac address, it was able to get the dhcp lease from verizon, BUT as stated earlier there were no incoming packets (ton of outgoing).

    Switched back to the original device with pfsense 2.0.3, which also uses a cloned mac address (I've been cloning for a while =), and everything worked fine.

    So just for giggles I set the mac address back to the JetWays original mac, and called fios to have them break my dhcp lease and then renewed my ip, it got the same IP address again, and all the same settings (gateway, dns, etc), BUT incoming and outgoing packets started flowing normally.

    So I don't know if there is something that goes screwy when trying to clone a mac on this device with 2.1.

    I should also mention that just clearing the cloned mac address doesn't actually reset the mac address to the the devices original, I had to "clone" the address to the devices original mac address and then clear it out again.

    I wonder if someone can test this scenario out and confirm if it is indeed an actual bug.

    Thanks for trying to help Wallabybob.

    -Joe
    ;D



  • Bizzare!



  • @Joe

    By default this board has intel Atom CPU, can I know from where you bought AMD version?



  • @ASGH:

    @Joe

    By default this board has intel Atom CPU, can I know from where you bought AMD version?

    Mine is also has an Atom CPU, this is the one I purchased: http://www.amazon.com/Jetway-NF9HQL-525-Intel-Quad-LAN-Mini-ITX/dp/B00CQBQZ3C/ref=sr_1_1?ie=UTF8&qid=1370987829&sr=8-1&keywords=jetway+quad

    It came with a ddr3 2gb sodimm, case and power brick. I need to purchase another 2gb sodimm, and I will eventually move from the 20gb 2.5 inch HD to a 4gb compact flash card.

    But honestly, as is, the device works incredible (now that I figured out the kinks with the build/device). I now have it configured with my vlans, and my additional business internet connection that I have 1:1 to a VIP subnet block.

    It handles it all like a champ, I have not seen the CPU go above 20% with me saturating both connections, and memory has not gone past 10%.