NIC onboard Realtek 8111E
-
Hi All,
I just buy a new mainboard with NIC onboard ( Realtek 8111E), When i install Pfsense V2, this version cannot detect my NIC onboard, I also try to install FreeNAS new realease version for test and it success, so i wonder how i can bring Pfsense V2 Detect my NIC as FreeNAS ( copy some file from FreeNAS to Pfsense… or do something for this).
Thanks for any help. -
Based on fast search i didn't found that nic on supported hardwarelist
-
I don't know much about compile new driver from Realtek with FreeBSD and still trying to…
-
Strange, my NC9C has RTL8111E PCIe and both onboard NIC's are detected, re0 re1.
-
I just buy a new mainboard with NIC onboard ( Realtek 8111E), When i install Pfsense V2, this version cannot detect my NIC onboard,
In the light of:@onhel:
Strange, my NC9C has RTL8111E PCIe and both onboard NIC's are detected, re0 re1.
please explain how you determined the pfSense can't detect the onboard NIC.
What mainboard are you using?
-
My new mainboard is ASUS P8H61-V with new update bios version and still not auto recognize NIC onboard. I also try to load some driver into kernel and now continue find solution…If don't want to buy another mainboard.
-
My new mainboard is ASUS P8H61-V with new update bios version and still not auto recognize NIC onboard.
By auto recognize NIC onboard I presume you mean the automatic assignment option to pfSense console dialog Assign Interfaces in which pfSense prompts for the interface and you insert an active cable into the appropriate socket. Is that correct?
Can you get past that to interface to the web GUI? If not, what is stopping you? (I would like to see the output from the pfSense shell command pciconf -l -v; dmesg to determine the identification codes in the onboard NIC).
-
I just find more infor about it
dmesg | grep 're0"
Re0: <realtek 8111="" 8168="" b="" c="" cp="" dp="" e="" pcie="" gigabit="" ethernet="">Port 0xe000-0xe0ff mem 0xd0004000-0xd0004fff, 0xd0000000 - 0xd0003fff irq 18 at device 0.0 on pci 4
Re0: Using 1 MSI Messages
Re0 : Chip Rev. 0x2c800000
Re0 : MAC Rev. 0x00000000
Re0: Unknow H/W Revison : 0x2c800000
Device_attach: re0 attach returned 6…and
picconf -lv | grep 're0"
re0@pci0:4:0:0: class=0x020000 card=0x84321043 chip=0x816810ec rev=0x06 hdr=0x06
So any suggest for more?
Thanks alot...!</realtek>
-
If you do a ifconfig re0, what is the output?
Since re0 is present, the NIC is detected and a driver loaded. However, you might have to manually assign the interface?
-
Thanks for reply,
I try to find re0 but no interface return so how can i manual assign this interface?
-
I try to find re0 but no interface return so how can i manual assign this interface?
You can't. The re driver is recognising the NIC but (cautiously?) refusing to take ownership of it (Device_attach: re0 attach returned 6) apparently because Re0: Unknow H/W Revison : 0x2c800000
You need an updated driver. Without some investigation it is not possible to say whether a more recent re driver than the re driver built into pfSense 2.0 fixes the problem nor is it possible to say (without investigation) if it is a trivial task to backport a suitable driver to pfSense 2.0 (FreeBSD 8.1).
Since you are set on using the motherboard you have I think the best (least hassle to you) solution is buy another NIC and not use the onboard NIC for the time being. If you already have one or more expansion NICs you might be able to use a VLAN capable switch to get additional interfaces: search the forums for VLAN port multiplier to see some posts that discuss this.
-
My mainboard is running success with FreeNAS new version so can i copy some thing form FreeNAS to Pfsense or recompile with this kernel? for help pfsense to recognize this NIC?
Thanks
-
can i copy some thing form FreeNAS to Pfsense or recompile with this kernel?
In pfSense most drivers are built into the kernel. If FreeNAS has chosen to do likewise there probably won't be anything useful you can copy. If there is a if_re.ko you can copy it might not even load with the pfSense kernel and even if it does it may cause havoc if the FreeNAS derived driver doesn't have the same idea as the pfSense kernel about the layout of shared data structures.
OK, suppose it doesn't work and you decide to rebuild pfSense with your own device driver. Where will you get the device driver that fixes the problem? Do you have the necessary skills and experience to backport a "more modern" driver from a later version of FreeBSD to FreeBSD 8.1? If not, are you prepared to put in many hours to acquire those skills? Are you expecting to get lots of "free" help? How many hours are you prepared to spend to says yourself the $10 to $70 a new NIC is likely to cost?
-
Thanks wallabybob
In my plan I expectation to have 4 physics interface for Network card ( 1 Onboard and 3 PCIs) but now current version only recognized 3 PCIs NIC, so now quick solution is change to other board and waiting for next pfsense snaphots with hope.
One more time thanks alot for your help.
-
@onhel:
Strange, my NC9C has RTL8111E PCIe and both onboard NIC's are detected, re0 re1.
onhel: Did you manage to use the NC9C with pfSense 2.0 working with the Re0 and Re1 ? (8111E)
(i know that these where PCIe board with chip on it)I'm planning of using a Shuttle XG41 with "Intel G41 Express+ ICH7 Chipset" and it has 2
Realtek 8111E ports on the board and get a bit scared that I will end up with useless unit.
I do not have any space to fit any additional NIC but must rely on the ones on the motherboard.Anyone else who have tested motherboards with Realtek 8111E network chipset and PF2.0 ?
Btw. Found this on BSD forum.
http://lists.freebsd.org/pipermail/freebsd-stable/2011-June/062886.html -
Btw. Found this on BSD forum.
http://lists.freebsd.org/pipermail/freebsd-stable/2011-June/062886.htmlThat forum item suggests that, at worst, to run pfSense on your preferred motherboard it will be necessary to backport the current stable driver to FreeBSD 8.1. See my previous post for discussion of that challenge.
There are other mainboards with two better supported (e.g. Intel) NICs.
-
onhel: Did you manage to use the NC9C with pfSense 2.0 working with the Re0 and Re1 ? (8111E)
(i know that these where PCIe board with chip on it)Using 2.0 Release, and my Jetway's NC9C-550 onboard NICs have always worked. I cant speak for other boards but judging from other users I've heard on this forum, the NC9C-550's 8111E works just fine with pfSense.
-
wallabybob:
Thanks for the comment!The reason why I wanted the Shuttle XG41 was that it was a ready made and tested HW solution
(MB, CPU, Cooling, Memory, good case …) as I am NOT looking for a Atom based MB. I wanted a
minimum Core 2 Duo CPU to get some decent power under the hood to handle both 100Mbit
WAN connection and one or two IPSec with decent speed.The normal CPU score for most Atom based CPUs is between 300-700 and the box (CPU) I am looking at
has a score on about 3600. (Core 2 Quad Q8400) And that CPU is on the "verified" list on Shuttles
homepage for that case.I have been looking at few different solutions (including a MB with Intel chipset) but it all ends up
with a risky situation that all parts, when put together, maybe doesn't work well. And then I have
spent a lot of money for nothing. The biggest concern is heat. Getting a good Mini-ITX motherboard,
CPU, Small formfactor case and enough cooling that will fit inside the case.And If I look at ready-made appliances with aprox. the same spec it costs 2-3 times the amount of money.
Do you know in what timeframe that 8.2 will be included ? (1, 3, 6, 12 months ?) just a rough estimate.
I'm currently running the pfSense as a secondary solution right now in a VMWare for testing
but would like to make it primary but would rather wait for pfSense to support the XG41 (8111E)
with BSD 8.2 than to look for another HW solution. So it depends on how long that wait would be.onhel:
Thanks for the info. -
Do you know in what timeframe that 8.2 will be included ? (1, 3, 6, 12 months ?) just a rough estimate.
When pressed for release dates the pfSense developers consistently say "When it is ready." Is that estimate rough enough? :) The only discussion about next version of FreeBSD in pfSense I have seen suggests the jump will be to FreeBSD 9.x rather than FreeBSD 8.x
If your VMWare solution works well enough I suggest you stick with that. If you really want to run without VMWare there could still be other options. I don't know the details of the XG41 but presume since you mention mini-ITX it has a mini-ITX board with an expansion slot. (But maybe the box doesn't provide for use of the expansion slot.) Is there an expansion slot you can use?
-
Do you know in what timeframe that 8.2 will be included ? (1, 3, 6, 12 months ?) just a rough estimate.
When pressed for release dates the pfSense developers consistently say "When it is ready." Is that estimate rough enough? :) The only discussion about next version of FreeBSD in pfSense I have seen suggests the jump will be to FreeBSD 9.x rather than FreeBSD 8.x
If your VMWare solution works well enough I suggest you stick with that. If you really want to run without VMWare there could still be other options. I don't know the details of the XG41 but presume since you mention mini-ITX it has a mini-ITX board with an expansion slot. (But maybe the box doesn't provide for use of the expansion slot.) Is there an expansion slot you can use?
The board does have one PCIe but the case doesn't so that's a dead end. :-/
I may start look around for other options as well. Found a few boards that looks OK
with Intel LAN chipset like the MSI IM-Q35 or the new MSI IM-QM67.
Or Supermicros X9SCV-Q or X9SCV-QV4. (based on the QM67 chipset)The size of the case that I'm looking at is aprox like this:
http://www.e-itx.com/mini-box-m350.html
The main concern will be the heat and what cooling to use.
Time will tell.Found some recommendations about cooling:
http://www.cooljag.com/INTEL/Socket%20G1_PGA989/JACDD01C-1.html/Dan