PfSense with Gigabyte GA-J1900N-D3V

amunrara

man, this board is a big headache :(

i received it 3 days ago, and after hours of suffering, i got it running.
…and i don´t even know how i made it work lol
soon, i am getting a wifi card, i think its going to be another headache..

godsfshrmn

@nzimmers:

@godsfshrmn:

I received my board today and I wanted to report back. I'm fortunate to have municipal broadband here, and it is 1gbps. I went through the install process and got it to boot from the USB stick. I ran a speed test and was only seeing about 550mbps. I typically see 850+ consistently. I'd like to try checking "disable hardware checksum offload" under System > Advanced > Networking, but it doesn't save on rebooting. I'm getting >80% load on core0 and 30% on core1, while the rest remain idle. System load doesn't really move, but there are a ton of interrupts.

I'm having problems booting from the SSD I have installed. I've saved everything to the SSD and used the quick default settings. When I reboot, I see the "F6 PXE Boot: F1" lines and essentially enter a reboot loop. It does not report any errors. Any thoughts? I've tried all kinds of different BIOS settings without any success.

godsfshrmn, which bios version are you running on the motherboard?

I'm running F3. I decided to try and snatch one of those Lenovo TS130's that have been frequently on sale recently and put an intel nic in it. I don't think the realtek nic is up to handling as much bandwidth.

amunrara

if anybody needs extra nics…this one works fine with 2.2 and giga

http://www.amazon.co.uk/Cable-Matters-SuperSpeed-Gigabit-Ethernet/dp/B00C50FSPU/ref=sr_1_24?ie=UTF8&qid=1417637549&sr=8-24&keywords=Cable+Matters

nzimmers

Just got my board and one of the Beta 2.2 seems to recognize everything including this Intel dual NIC: http://www.amazon.com/gp/product/B00006HX1V/ref=oh_aui_detailpage_o02_s08?ie=UTF8&psc=1

Last time i ran PFSense was back in 2007, so it will take me a bit to figure everything out and see if things are working fine but so far so good.

One thing I will mention is that it's finicky on the ram, has to be 1.35v and can't be faster ram than specified.

tpf

Hi guys,
got my board yesterday and tried to get it working many times. BIOS is on F3, I've read the post about the correct settings here, after getting the described problems every boot. Installation from USB @ HDD stucks at 38%, multi-core support can't be disabled in BIOS, so I installed pfS on another system an put the HDD back on the Gigabyte board. pfS is booting, LAN and webinterface works so far.My WAN get's no IP und don't switch to 1000 MBit. Link goes up und down multiple times und stuck at 10 MBit :-\

I'm not amused :P

stephenw10

What is the WAN connected to? Sounds like it failing to auto-negotiate a link correctly. Try adding a switch between the WAN and whatever device it's connected to. You could try forcing the speed/duplex but Realtek NICs can be a bit difficult in that area.

Steve

tpf

My WAN is connected to a NETGEAR GBit-Switch. The same NIC works great on Windows 7.

fostytou

I just wanted to report that I've been running this board little issue since the end of september.

I was able to do the DOS based BIOS upgrade with ease from a USB stick (F3 I think). The install took some minor creativity but worked pretty smoothly. I was able to install an Intel 32GB SSD and enable TRIM which has been great. 4GB of memory seems like overkill for my household usage. I'm using internal NICs and running 2.2a built on 10/3 for now. Its powered by a PicoPSU 80.

Sips power at 13W most of the time, but I did see fluctuations + 1.5W when installing and doing other heavy activity.

The one catch I have is that a reboot or hard boot after power failure when no monitor is connected will result in an error when booting from the SSD. It has only happened twice so it hasn't been a huge issue. The first time I hooked it to a monitor, did a proper shutdown, and it booted fine. The second time I turned it off after some alert beeps, turned it back on (maybe twice, but I think only once), and eventually heard the familiar PF boot alert.

This thing has been great for me so far, and since I don't expect awesome service speeds any time too soon I think it should serve me well for a few years while paying for itself in power. Thanks for the tips!

nzimmers

I've had this board from the beginning of December and all seems to be working great now - I had some challenges getting the right settings in PfSense (as I'm pretty new to it) which was most of my problems. However, one thing I would like to comment on is that in addition to the bios settings previously listed I had to set CSM to all legacy settings (and disable Network) and for "IDE configuration" I set everything to IDE, and then AFTER install I set it back to AHCI Mode - made a world of difference as did the most recent RC2.2 from Dec 22nd. I'm still in the testing phase (can't hook this up until I know it works and works well otherwise the wife and kids will scowl at me for messing with the home network again!) but thus far, I have Snort, PFblocker, and Squid running fine on it, all services are up and no material issues that I can tell.

I did notice that when I push a 1GB file from the squid proxy cache to a machine snort push up cpu utilization to about 43% at 450Mbps transfer rate, but downloading the same size package over my 50Mbps internet connection the CPU utilization is only 12%….so for stuff over the internet this board has a lot of headroom.

I plan to test out Open VPN soon (learning curve will be a challenge) but very impressed with Pfsense and the GA-J1900N-D3V capabilities.

wolfpackunr

Could someone give step by step instructions on what they did to update the BIOS or even get into it. I'm pretty sure my board came with F1. Every time it boots it goes to the EFI Shell menu.

Things I've tried:

-Clearing CMOS and Reboot, same
-Formatting a USB as FreeDOS with the BIOS files, same
-USB Drive with Windows 8 GPT, same
-USB keyboard attached to PS/2 converter, same
-Pressing Delete as fast as possible on bootup, same

Everything I've come across to try does nothing, still goes to the EFI Shell Version 2.31 screen with yellow text. I can type exit and then it will say insert media and reboot but that is all it will do. Rebooting goes back to the same screen. Did anyone else encounter and find a way around or should I just RMA it?

nzimmers

follow the instructions here: http://www.gigabytenordic.com/wordpress/flash-update-bios-gigabyte-bay-trail-motherboards-j1800-j1900/

it updates automatically If I reall correctly

tw_wff

@wolfpackunr:

Could someone give step by step instructions on what they did to update the BIOS or even get into it. I'm pretty sure my board came with F1. Every time it boots it goes to the EFI Shell menu.

Things I've tried:

-Clearing CMOS and Reboot, same
-Formatting a USB as FreeDOS with the BIOS files, same
-USB Drive with Windows 8 GPT, same
-USB keyboard attached to PS/2 converter, same
-Pressing Delete as fast as possible on bootup, same

Everything I've come across to try does nothing, still goes to the EFI Shell Version 2.31 screen with yellow text. I can type exit and then it will say insert media and reboot but that is all it will do. Rebooting goes back to the same screen. Did anyone else encounter and find a way around or should I just RMA it?

@wolfpackunr I had the same problem, however I finally managed to enter BIOS with a PS/2 keyboard attached instead of a USB one. But even if I remove the EFI shell from the boot priority list, the board still boots into the shell. The only option so far was to disable UEFI support entirely and switch to legacy mode, then it skips the EFI shell and boots normally. Really weird.

tpf

pfS 2.2 RC runs pretty well.

Throughput NAT ~ 850 MBit / sec, one core @ 100%.
Throughput OpenVPN ~ 80 - 100 Mbit

OpenSSL cryptodev:
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
aes-128-cbc 33849.30k 36329.11k 37343.55k 37570.46k 37528.13k

type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
aes-256-cbc 24961.94k 25960.98k 26427.82k 26561.19k 26590.05k

18 Watts power consumption at idle and high load with 3,5" HDD.

FarmerB3d

That's pretty good. What do people get on better hardware with better NICs? If that 850Mb/s is maxing out a core then what is it? pfSense doing it's thing or the NIC drivers having to work hard because of a crappy NIC?

Still, it'll be a while before this is a problem for me :)

nzimmers

@tfp

that's pretty good, better than what I got:

(not using Open VPN, just NAT, but running snort, squid, darkstat)

Iperf Server:
My personal computer
Core i3 4130T
ASUS Mini ITX DDR3 2600 LGA 1150 Motherboards H97I-PLUS
Used on-board Intel(R) Ethernet Connection (2) I218-V

Ipfer Client:
Pfsense
J1900
Gigabyte GA-J1900N-D3V
Used on-board Realtek GbE LAN

Results:
–----------------------------------------------------------
Client connecting to 192.168.1.101, TCP port 5001
TCP window size: 65.0 KByte (default)

[ 3] local 192.168.1.1 port 47614 connected with 192.168.1.101 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 864 MBytes 725 Mbits/sec

tpf

@FarmerB3rd:

That's pretty good. What do people get on better hardware with better NICs? If that 850Mb/s is maxing out a core then what is it? pfSense doing it's thing or the NIC drivers having to work hard because of a crappy NIC?

Crappy NICs in my opinion. My other system:

http://client.mitac.com/products-embedded-board-PD12TI.html Atom D2500 (Intel GBit NIC ;D)

Throughput NAT: full 1000 Mbit
Throughput OpenVPN: Currently can't be tested, sorry. It's a productive system with bandwith limited WAN.

type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
aes-128-cbc 21775.06k 27965.80k 29094.76k 29383.80k 29469.99k

type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
aes-256-cbc 15705.69k 21743.30k 22361.44k 22595.01k 22643.80k

Intel i3 3240 3,4 Ghz: AES 128: 345 MByte / sec, AES 256: 278 Mbyte / sec.

aleatorvb

I bought one in the end - at least to test it, but I am unable to make pppoe to work - i tried both fresh settings and uploading a backup from my current pfsense installation.

Media: usb drive
Pfsense: 2.2-RC (amd64) / built on Tue Dec 09 09:46:36 CST 2014 / FreeBSD 10.1-RELEASE (the 2.2 release candidate)
wan: re0
lan: re1
bios version: F3

Pfsense boots without any obvious issues, ran for 24 hours without missing a ping but pppoe isn't working…

I have attached a screenshot of the interface status.
Sometimes i get in the pppoe logs "Acess denied (external check failed)" but I am 100% sure the usernam/password is correct - I copied (and manually rewrote when copy-pasting did not seem to work) them from the backup file of the current running pfsense firewall.
I also set the wan mac address the same as to make sure it isn't filtered by my isp.

Any hints on what should I try?

wan_error_iface_status.PNG_thumb

aleatorvb

Also good to know:

Logitech K270 wireless kit works with bios
microsoft desktop 800 wireless kit does NOT work (can type at uefi prompt but can't enter bios by pressing DEL)

aleatorvb

Pfsense: pfSense-2.2-RC-1g-amd64-nanobsd-vga-20150115-1212.img
WAN: PPPOE
LINK: Gigabit
Firmware: F3

speed test: upload
CPU: 0.8% user, 0.0% nice, 0.0% system, 31.9% interrupt, 65.3% idle
speed: 500Mbps

speed test: upload
CPU: 0.4% user, 0.0% nice, 0.2% system, 7.2% interrupt, 92.2% idle
speed: 100Mbps

Out of the box, with pppoe set up and lan configured with dhcp
Mem: 69M Active, 32M Inact, 138M Wired, 940K Cache, 63M Buf, 3585M Free

Steps done to install pfsense:

@w00t:

First of all, you need to update the BIOS to F3 since the motherboard probably will ship with F1.

Update BIOS

Power on the MB and reset the BIOS to defaults.

Create a bootable USB of Windows 8/8.1 and install on a spare harddrive (do it on the motherboard itself, not another computer), F1 will kinda only boot to Win8-USB's.

When successfully booted to Win8, visit http://www.gigabyte.us/products/product-page.aspx?pid=4918#utility and change to your installed OS, download and install Microsoft .NET Framework 4 (probably not necessary, the install will thell you) and then APP Center.

Start APP Center from C:\Program\Gigabyte or such, and wait for the shitty program to start. When loaded, update the damn thing.

Use the APP Center program to download @BIOS.

When installed, use @BIOS from the APP Center to download and flash F3, choose "Install from server" or similar, follow the steps and you will be on F3 in a moment.

Reboot and enter BIOS to check that you are on F3, if thats the case, once again do reset BIOS to defaults.

Power off and remove harddrive and Win8 USB.

Create bootable pfSense

Download the memstick or nanobsd-vga version (your choice if you want to install full version to another USB-stick or run the embedded version) from pfSense download-page. I have been using nanobsd-vga for this test.

Flash the .img to you USB-stick, win32 image writer works like a charm.

BIOS settings

Attach the pfSense USB and boot to BIOS.

Reset to default, and ONLY change the following:
Advanced -> CSM Configuration

CSM Support - Enabled
Boot Option filter - Legacy Only
Network - Do not launch
Storage - Legacy Only
Video - UEFI First
Other PCI devices - Legacy Only
Advanced -> USB Configuration

Legacy USB support - Enabled
USB3.0 support - Enabled
XHCI hand-off - Disabled
EHCI hand-off - Disabled
USB Mass storage device support - Enabled
Under USB configuration you should see your USB-stick listed.
Chipset -> South Bridge (I think? If I remembered correctly.)

Restore after AC power loss - Power On
Under boot, change harddrive BBS priority and set you USB-stick to #1, then change first boot option to your USB-stick and disable #2 boot option.

boots on power on straight to pfsense
reboots without issue
26 degrees Celsius (4 degrees over room temp after 4 hours of use)

Will put a zwave power meter on it soon and see how much energy it uses.
Ram: Kingston 4GB, DDR3, 1600MHz, SODIMM P/N KVR16S11S8/4

ak

Has anyone used this with an Intel NIC? I have a spare HP NC360T and thinking about using this with a PCI->PCIe adapter.

PfSense with Gigabyte GA-J1900N-D3V

Results: –---------------------------------------------------------- Client connecting to 192.168.1.101, TCP port 5001 TCP window size: 65.0 KByte (default)

Results:
–----------------------------------------------------------
Client connecting to 192.168.1.101, TCP port 5001
TCP window size: 65.0 KByte (default)