PfSense with Gigabyte GA-J1900N-D3V
-
Does it work better with Bios F3 version?
-
Looks like it should be:
@http://www.silentpcreview.com/forums/viewtopic.php?p=585025&sid=956a29819e12154d85832fd26f45d365#p585025:I have to say that the F3C BIOS seems quite stable, it provides a lot of previously missing options (working PXE legacy boot, USB support, advanced options)
Steve
-
did pfsense support the onboard nic.
gigabyte website did not state the model of the nic chip. (i think it may be 8111G??? not sure :'() -
@pete.s.:
I just wanted to add that I'm running the GA-C1037UN-EU board earlier mentioned in this thread.
I'm running it with an additional NIC in the PCI port, so have three NICs all in all. I also use vlans and everything is working great.
I run it of an SSD and everything is very low temperature. I have a slow running 120mm case fan but I think it is not needed.
It's been running it 24/7 since last year, so about 6-7 months now. Highly recommended. ;D ;D ;D
The only drawback is that it's PCI and not PCIe if you want to add a dual or quad network card. A regular pci slot can handle one gigabit without trouble. But perhaps it's academic anyway since there are usually data bottlenecks elsewhere in the chipset and the cpu.
I've bought the GA-C1037UN-EU under the impression that it would be no problem, but now the NIC's don't get an IP from the DHCP server. Do I have to copy the if_re.ko from topics in this forum (see https://forum.pfsense.org/index.php?topic=65355.30) ?
uname0u gives FreeBSD 8.3-RELEASE-p16
How did you install this c1037un board?
-
If you've assigned the interface as type DHCP then it is appearing correctly, the driver is not the problem.
What have you done so far?Steve
-
If you've assigned the interface as type DHCP then it is appearing correctly, the driver is not the problem.
What have you done so far?Steve
I've installed pfSense, assigned the re0 to the WAN interface (DHCP) an plugged in the cable modem (after properly powercycling it). Alas…no IP. Then I've connected the WAN to my old pfSense LAN and I can see in the old pfSense log that it is indeed giving out a DHCP ip, but all the c1037un does is sending more requests for an IP.
Then I've changed the etc.conf with the following :synchronous_dhclient="YES". Still no IP...
Then I've loaded the if_re.ko from various posts in this forum (https://forum.pfsense.org/index.php?topic=65355.45) to /boot/kernel and /boot/modules. Also added if_re_load="YES" to /boot/loader.conf.local.
Still no IP :-X
From what I gather Realtek changes it hardware sometimes without changing the model number, thus it might work for one person but not for the next >:(
I'm at a loss now, with the Ubuntu live CD the nics work flawlessly and get an IP. Maybe I have to virtualize pfSense just to get it working?
-
Hmm, well that's odd behaviour. You could well be right, Realtek do like to change hardware.
What does pciconf list the NIC as? The PCI revision usually indicates what the NIC type is.Steve
-
Hmm, well that's odd behaviour. You could well be right, Realtek do like to change hardware.
What does pciconf list the NIC as? The PCI revision usually indicates what the NIC type is.Steve
Due to the problems with the nic on bare-metal pfSense I've decided to use esxi and run pfSense on top of that. As it turns out this is something I should've done right from the beginning, it works perfect.
-
Any new information regarding this board? Does the NIC's works out of the box?
-
Which board? There are two being discussed here.
Steve
-
Which board? There are two being discussed here.
Steve
Oh, the topic board, GA-J1900N-D3V. But GA-C1037UN-EU as well then.
@pete.s.:
I just wanted to add that I'm running the GA-C1037UN-EU board earlier mentioned in this thread.
I'm running it with an additional NIC in the PCI port, so have three NICs all in all. I also use vlans and everything is working great.
Due to the problems with the nic on bare-metal pfSense I've decided to use esxi and run pfSense on top of that. As it turns out this is something I should've done right from the beginning, it works perfect.
So I'm kinda torn here if it's working or not. At the moment these two motherboard are the only ones I can get my hands on in my area that have 2x onboard NIC's :/
-
It's hard to know. It appears from the comments here that Gigabyte may have changed the chip on the board or Realtek updated it somehow on the GA-C1037UN.
The GA-J1900N-D3V doesn't have any reported issues with the NIC if you can get pfSense installed in the first place. ::)Steve
-
It's hard to know. It appears from the comments here that Gigabyte may have changed the chip on the board or Realtek updated it somehow on the GA-C1037UN.
The GA-J1900N-D3V doesn't have any reported issues with the NIC if you can get pfSense installed in the first place. ::)Steve
Heh, I see. I will then order the GA-J1900N-D3V and report back in a few days ;)
-
Have you read this whole thread?
There are people who have failed to make pfSense boot at all on that board.Steve
-
Have you read this whole thread?
There are people who have failed to make pfSense boot at all on that board.Steve
Yes! I know there is a lot of problems. I'll try and follow this guy. Also there is a new F3 BIOS that I would like to try.
I bought this board (only found out about this thread afterwards) last Monday, together with 2 x 4GB Crucial Ballistix @ 1.35V and a 60GB Kingston (SSDNow). After having upgraded to F2 (which was indeed a bit of a pain) I got 2.2-ALPHA running without further issues. I followed the guides elsewhere on the forum and enabled CSM as well as disabling C-State. I've also enabled TRIM support by rebooting into single-user mode and running 'tunefs -t enable /'.
As mentioned, running smooth now and not seeing any issues (yet). Will keep it running for another night before replacing my old firewall though (m0n0wall on an ancient Nokia IP110), just to be sure :)
Just thought I'd share some positive news, hope this helps somebody!
-
Have you read this whole thread?
There are people who have failed to make pfSense boot at all on that board.Steve
Successfully booted pfSense on GA-J1900N-D3V. Will update this post later with tutorial and BIOS settings. EDIT2: After you are on F3 BIOS, pfSense alpha 2.2 seems to boot with no issues.
EDIT: Alright got everything working, almost..
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.
Thats it, now reboot and hopefully your pfSense-stick will boot. As I said, got everything working, almost. It seems like the first boot, you will always get an acpi panic error. I havn't been able to pinpoint what's causing it, but it seems to NOT be related to speedstep/power technology(Energi efficient)/cpu c-states. When you get the prompt within pfSense with the panic error, just type "reboot" and everything will boot just fine (or hit the physical reset switch). A reboot within pfSense (from the WebUI or promt) will work with no panic error. When you halt the machine and boot it up again, you will stuck on acpi panic error and need to reboot from the prompt (or hit the physical reset switch).
Also, pfSense will not get WAN IP from DHCP after the initial setup, when the initial wizard is done, just reboot and you will get IP from DHCP. What I have seen, this problem only occured right after the initial wizard.
If anyone got any input regarding the strange acpi panic error at first boot, please comment.
Sidenote: When doin a speedtest on my home connection (250/100Mbit) the CPU-usage is around 15-18%. Great board for home usage! (not so great for producation as long as we got the strange first boot problem) :)
-
-
Hi,
I bought this board on Friday and had no luck with it.
I was on F2 and it worked but unstable. After upgrading to F3 I get a Bogus Interrupt panic on boot. Trying your reboot and bios settings did not help me. :(I don't want to give up on it though…
-
Is there a revision or some other build info on your mobo? I'm curious about why yours came with F1 bios and mine with F2. There must be something different between the boards.
-
Hi,
I bought this board on Friday and had no luck with it.
I was on F2 and it worked but unstable. After upgrading to F3 I get a Bogus Interrupt panic on boot. Trying your reboot and bios settings did not help me. :(I don't want to give up on it though…
Check my previous post and reset BIOS to defaults and only change the settings listed in the post.
Is there a revision or some other build info on your mobo? I'm curious about why yours came with F1 bios and mine with F2. There must be something different between the boards.
AFAIK there is only one revision, rev1.0. It could just be the case that you got a motherboard from a newer batch from Gigabyte that shipped with F2.
-
Yup, always reset to default. Dud apply only the changes you suggested but still same result.
My board also rev 1.0.
I wonder why there is a difference? Grasping at straws but I wonder if there is a difference in the bios version? Any chance you could email me the file you have?
I'm collecting straws so might as well continue… :( -
Yup, always reset to default. Dud apply only the changes you suggested but still same result.
My board also rev 1.0.
I wonder why there is a difference? Grasping at straws but I wonder if there is a difference in the bios version? Any chance you could email me the file you have?
I'm collecting straws so might as well continue… :(Hm, I can't send you the BIOS-version I have since chose "Download BIOS from server and flash" within the @BIOS application. You read the whole comment right? I also get the acpi panic error at first boot, and need to manually reboot from the pfsense terminal prompt.
-
ok, so the difference is that I don't have win8 so to update the bios I downloaded the latest (F3 - 2014/04/14) and made a boot disk with Rufus and applied it. It took it without a problem. I've since flashed it again and it's happy.
No amount of disabling stuff made a difference - it had the panic time after time. :(
However….
I found another post somewhere about 2.2 and that some got it working. I downloaded the latest beta version (30th July) and booted into that without a problem.
Obviously, this leaves me in a weird place as I don't really want to be using beta but I'll see how it goes in the coming weeks. There are a number of people who say 2.2 is just fine for them and they've had no problems so here's hoping....I would have loved for it to work easily from the word go but hey ho.... This should be ok :)
-
ok, so the difference is that I don't have win8 so to update the bios I downloaded the latest (F3 - 2014/04/14) and made a boot disk with Rufus and applied it. It took it without a problem. I've since flashed it again and it's happy.
No amount of disabling stuff made a difference - it had the panic time after time. :(
However….
I found another post somewhere about 2.2 and that some got it working. I downloaded the latest beta version (30th July) and booted into that without a problem.
Obviously, this leaves me in a weird place as I don't really want to be using beta but I'll see how it goes in the coming weeks. There are a number of people who say 2.2 is just fine for them and they've had no problems so here's hoping....I would have loved for it to work easily from the word go but hey ho.... This should be ok :)
Strange, works fine for me after the first reboot. I just tested 2.2 nanobsd (30th july) and can confirm, it boots just fine.
-
I just tested 2.2 nanobsd (30th july) and can confirm, it boots just fine.
Yup, I'm sticking with that for now and seeing how it goes. Happy it at least works :)
-
So, nearly two weeks on and I am super happy with how it's working. It's a full install on a 32GB SD I had lying around.
I am on 125Mb down / 10 up and speed test shows me 125 down and 10 up :D The CPU goes to 3% but can't really say if that is the download load or not.
Something unexpected though, I set up a VPN with PIA and routed traffic through there. Works very well and very quick. I actually get faster speeds (150 / 32) when ging via the VPN than I do normally. I am guessing it's because I have compression turned on.
When doing a speedtest via the VPN the CPU goes to 8%.In a nutshell, the board is ideal for home (and soho?) it seems to have more grunt than is needed.
When I get my wifi setup as I want it and various subnets doing their thing then it might load up a bit but if this is anything to go by… I can't see me having a problem.happy Camper...
-
Thank you FarmerB3d for your comments, I'm in the process of setting up a similar config, it's great to hear that it works fine.
The only bummer with this board would be the PCI slot, no PCI-e network cards can be installed.
I don't know how effective the USB3.0 is with network adapters.
For now I'll just stick with a PCI two ports Broadcom network card for a total of 4 ports.Cheers.
-
The PCI thing is a bit of a bummer - why the still put 1980's tech on these boards I don't know :o
I wonder if something like this would work?
http://linitx.com/product/mini-pci-express-card-to-pci-express-x1-socket-9cm-cable-left-sided/12894 -
Yeah it probably will, still only 1-port network cards can be conected but that makes three in total, better than only two
For example, this Intel card will fit:http://www.newegg.com/Product/Product.aspx?Item=N82E16833106033
Good find, not found on Ebay sadly, I came up with this:
http://amfeltec.com/products/flexible-minipci-express-to-pci-express-adapter/
It has to conform to PCI-e 2.0 spec though, the website does not specify that.As far as bandwidth concerns, PCI-e 2.0 can transfer 500MB per lane, so that should be enough for a 1 port LAN card.
The J1900 Celeron supports 4 PCI-e x1 lanes, but I suspect those are taken by the two SATA connectors and the two LAN ports.
Best way is to try and see how it holds up at giga speeds.Edit:
Why bother? On the same site there is a Mini PCI-e LAN card with two ports. And the best thing, it's Intel:http://linitx.com/product/jetway-dual-gigabit-lan-mini-pci-express-card/13534
http://www.logicsupply.com/components/expansion-cards/admpeidla/
Easiest way to expand the LAN ports.
Cheers.
-
You might be better off getting a mobo fit for purpose rather than shoe-horning the bits in.
I got that mobo because it was fine for my requirements - small, low power consumption, two NICs. Everything else is nice-to-have.Why not get a "normal" board with two PCIe x 8 on and get a couple of Intel dual cards or a quad card. Job done.
-
Why bother? On the same site there is a Mini PCI-e LAN card with two ports. And the best thing, it's Intel:
http://linitx.com/product/jetway-dual-gigabit-lan-mini-pci-express-card/13534
http://www.logicsupply.com/components/expansion-cards/admpeidla/
Easiest way to expand the LAN ports.
Cheers.
Yes that is a nice card, I have two of them. :)
Unfortunately I don't think it will fit here. It is a full length PCI-E Mini card and the board in the topic of this thread to me appears to only have a half length PCI-E Mini card slot.
-
You might be better off getting a mobo fit for purpose rather than shoe-horning the bits in.
I got that mobo because it was fine for my requirements - small, low power consumption, two NICs. Everything else is nice-to-have.Why not get a "normal" board with two PCIe x 8 on and get a couple of Intel dual cards or a quad card. Job done.
Sure, that would be the easiest option. Only one problem: None of the J1900 boards have two PCI-e x8.
Only the Asrock mATX Q1900M has a full length PCI-e slot, that still operates in x1 mode.
In my case, space is not a problem so I might as well get the Asrock mATX.
If I can find the right Intel PCI-e LAN cards to work with.Also, I agree that trying to stuff in a full-size mini PCI-e card in a half-size mini PCI-e slot is less then ideal.
For me that's pretty much back to the drawing board again. Oh well.Cheers.
-
Decided to do some testing, WAN->LAN.
C:\iperf>iperf.exe -c 213.x.x.x -u -b 200000000 -P 6 -t 30
–----------------------------------------------------------
Client connecting to 213.x.x.x, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size: 64.0 KByte (default)[ 8] local 10.0.0.50 port 54846 connected with 213.x.x.x port 5001
[ 6] local 10.0.0.50 port 54844 connected with 213.x.x.x port 5001
[ 7] local 10.0.0.50 port 54845 connected with 213.x.x.x port 5001
[ 5] local 10.0.0.50 port 54843 connected with 213.x.x.x port 5001
[ 4] local 10.0.0.50 port 54842 connected with 213.x.x.x port 5001
[ 3] local 10.0.0.50 port 54841 connected with 213.x.x.x port 5001
[ ID] Interval Transfer Bandwidth
[ 8] 0.0-30.0 sec 671 MBytes 188 Mbits/sec
[ 8] Sent 478742 datagrams
[ 6] 0.0-30.0 sec 671 MBytes 188 Mbits/sec
[ 6] Sent 478793 datagrams
[ 7] 0.0-30.0 sec 671 MBytes 188 Mbits/sec
[ 7] Sent 478715 datagrams
[ 5] 0.0-30.0 sec 672 MBytes 188 Mbits/sec
[ 5] Sent 479377 datagrams
[ 4] 0.0-30.0 sec 671 MBytes 188 Mbits/sec
[ 4] Sent 478965 datagrams
[ 3] 0.0-30.0 sec 671 MBytes 188 Mbits/sec
[ 3] Sent 478753 datagrams
[SUM] 0.0-30.0 sec 3.93 GBytes 1.13 Gbits/sec -
You might be better off getting a mobo fit for purpose rather than shoe-horning the bits in.
I got that mobo because it was fine for my requirements - small, low power consumption, two NICs. Everything else is nice-to-have.Why not get a "normal" board with two PCIe x 8 on and get a couple of Intel dual cards or a quad card. Job done.
Sure, that would be the easiest option. Only one problem: None of the J1900 boards have two PCI-e x8.
Only the Asrock mATX Q1900M has a full length PCI-e slot, that still operates in x1 mode.
In my case, space is not a problem so I might as well get the Asrock mATX.
If I can find the right Intel PCI-e LAN cards to work with.Also, I agree that trying to stuff in a full-size mini PCI-e card in a half-size mini PCI-e slot is less then ideal.
For me that's pretty much back to the drawing board again. Oh well.Cheers.
Not that you want to drop the cash, but the supermicro x10sba/x10sba-l both work solidly out of the box, have two intel intel nics built in (i210s, they work fine on 2.1.4) & have a physical pci-e x8 slot that runs at x2. That's another option, albeit, $150 option. It's supermirco, they cost a pretty penny, but are some of the most solid boards in the world. This'll be my 3rd & I have had no hick ups besides a temp sensor issue & I think it's a pfsense problem as the bios reports it properly.
One of the more positive aspects concerning a no-tinker attitude about the board is that you have Lan/Wan working out of the box. You'll have the freedom to experiment with dual & quad nic cards w/o bringing the whole system down for longer than a simple pcie card install & reboot would take.
FarmerB3rd, don't be all that concerned with beta bioses from Gigabyte. I ran one on an ITX rig I built that was focused on gaming & overclocking. No hickups, no instability (once I dialed the overclock in). If the beta is stable in all testing methods you throw at it, you're set. Sometimes, the final version is not as good as the beta. I've had that happen a few times in the past from different vendors.
-
Only just seen your reply…
Well, a few weeks in and I have had a few problems - I'm not overly bright it would seem :D.
The board though is working perfectly. Temp (reported) is 28C with no fans in the case (case is very perforated though).
Throughput tops out at 125Mb/s (ISP cap) and when using OpenPVN for certain traffic it musters 185Mb/s (VPN compression).
I've never seen the CPU go above 5%.The supermicros are nice but they cost more - double the price of what I paid (in the UK). Looking at the charts of packets per second, you get about 20% more through the Intel NICs but seeing as I am still way under what the board is capable of, this is not a worry for me…
For those thinking of getting one, well worth it for the price :D
-
@FarmerB3rd:
Only just seen your reply…
Well, a few weeks in and I have had a few problems - I'm not overly bright it would seem :D.
The board though is working perfectly. Temp (reported) is 28C with no fans in the case (case is very perforated though).
Throughput tops out at 125Mb/s (ISP cap) and when using OpenPVN for certain traffic it musters 185Mb/s (VPN compression).
I've never seen the CPU go above 5%.The supermicros are nice but they cost more - double the price of what I paid (in the UK). Looking at the charts of packets per second, you get about 20% more through the Intel NICs but seeing as I am still way under what the board is capable of, this is not a worry for me…
For those thinking of getting one, well worth it for the price :D
I have been watching this thread due to the desire of wanting to get a j1900 board for a low power build to replace a power hungry I5 that is overkill for my use.
Since I only need 1 Wan and 2 Lan (1 regular, 1 management), this seems like a great option since I do not need high throughput for the management interface and can use a slower NIC. With that being said, have you tested any packages to see what type of load they place on the board? I currently use snort but have been trying to find time to test others.
I am also on 50/10 teir with my ISP but 1Gb is being talked about within the next year or so for my area.
Thanks
-
I've got snort running (only just added it) and the CPU is not moving. It nearly always sits at 0% with normal "stuff".
Doing a speed test though excites it a bit. 150Mb/s down via VPN (compression is turned on) makes it hit 12-13%.If you're looking at a Gb WAN then perhaps this board would not be right for you. What a First World problem you have ;)
-
@FarmerB3rd:
I've got snort running (only just added it) and the CPU is not moving. It nearly always sits at 0% with normal "stuff".
Doing a speed test though excites it a bit. 150Mb/s down via VPN (compression is turned on) makes it hit 12-13%.If you're looking at a Gb WAN then perhaps this board would not be right for you. What a First World problem you have ;)
Thanks for the update friend, my last question for you would be what kind of power do you think your setup is pulling from the wall?
-
Due to the problems with the nic on bare-metal pfSense I've decided to use esxi and run pfSense on top of that. As it turns out this is something I should've done right from the beginning, it works perfect.
Have you run into any issues after you've had some time with this config? What kind of link do you have it connected to? What kind of CPU usage? How's the power consumption?
I've used this method in the past to get around some driver issues and didn't have any issues before…then again I was on 0.7.1 with ESX 3.5 (it's been a few years).
-
@pete.s.:
The only drawback is that it's PCI and not PCIe if you want to add a dual or quad network card. A regular pci slot can handle one gigabit without trouble. But perhaps it's academic anyway since there are usually data bottlenecks elsewhere in the chipset and the cpu.
In theory one could use the mini-pcie slot available. There are adapters out to pin-covert it to a pci-e 1x slot (http://amzn.com/B00JIV9AZS) which then you can use any multi-port pci-e nic that is in a 1x form factor.
-
I was tempted to buy this Gigabyte board, but just like FarmerB3rd said, shoe-horning the bits in (Mini-PCI-e cards) is far from ideal.
Another show stopper was the absence of any sata-3 ports, and no PCI-e slot.I like to be able to re-purpose hardware if the need arises.
When searching for some alternatives, the only (cheap) board with sata-3 connectors is the Asrock Q1900 itx.
The Asrock Q1900M has some PCI-e slots, but lacks sata-3 as most other brands.But in the end I decided for the Supermicro X10SBA (as noted by Synthetickiller), it has everything I needed.
Yes, it costs nearly twice as much as the other boards, but at least I can re-purpose later on as a Linux/BSD based file server.
I plan to use 2x4GB SuperTalent sodimm 1.35v with micron D9 chips.
The idea is to have a solid piece of hardware that keeps me online 24/7.Wolly mentioned esxi and PFSense on top of that. I'd like to avoid that (probably not even needed with the X10SBA) because it adds another layer
of complexity. Plus the fact that I like PFSense to run independent from other servers, so that Internet connectivity won't be affected if something goes south on the file server for example.When it comes to PFSense I'm a complete n00b, please correct me if I'm mistaken.
Cheers.