Dlink DGE-530T not detected



  • Hello I am having trouble installing my Dlink DGE-530T card in my new pfsense 2.0 box. The card is not detected on installation I see that others have this card installed, please help.
    Thank you



  • I have this card too
    no problem
    please show "dmesg" command

    this my dmesg about this card

    skc0: <d-link dge-530t="" gigabit="" ethernet="">port 0x1000-0x10ff mem 0xf0100000-0xf0103fff irq 21 at device 0.0 on pci5
    skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9)
    sk0: <marvell semiconductor,="" inc.="" yukon="">on skc0
    miibus1: <mii bus="">on sk0
    e1000phy0: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus1
    e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto</marvell></mii></marvell></d-link>


  • Netgate Administrator

    Unfortunately many large companies often change the chipset they use in their network cards without changing the model number.
    Some breif Googling on this shows at least two revisions of this card:
    A1 uses Marvell 88E8003 chipset
    B1 uses Marvell 88E8001 chipset

    Both those should be supported by the sk or msk drivers so perhaps your card is a different chipset.

    Steve



  • @seasnipe:

    Hello I am having trouble installing my Dlink DGE-530T card in my new pfsense 2.0 box. The card is not detected on installation I see that others have this card installed, please help.

    There is a variety of possible causes:

    1. Card might be "undetected" because it is not electrically connected to the computer because it is not correctly seated in the slot.
    2. Card might be "undetected" because it uses a chipset not recognised by any driver.
    3. Card might be "undetected" because a driver that recognised it encountered an error when attempting to initialise it.
    4. Card might be "undetected" because a driver recognised it and took ownership of it but it hasn't been added to the set of interfaces pfSense uses.

    Therefore it would help if you described what led you to determine it was "undetected" and provided the full output of the pfSense shell command dmesg.



  • I'm having the same problem, so here is the output from dmesg

    $ dmesg
    Copyright (c) 1992-2010 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    	The Regents of the University of California. All rights reserved.
    FreeBSD is a registered trademark of The FreeBSD Foundation.
    FreeBSD 8.1-RELEASE-p4 #0: Tue Sep 13 16:58:57 EDT 2011
        root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 i386
    Timecounter "i8254" frequency 1193182 Hz quality 0
    CPU: Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz (2925.99-MHz 686-class CPU)
      Origin = "GenuineIntel"  Id = 0x1067a  Family = 6  Model = 17  Stepping = 10
      Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x408e3bd <sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave>AMD Features=0x20100000 <nx,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant
    real memory  = 4294967296 (4096 MB)
    avail memory = 3126243328 (2981 MB)
    ACPI APIC Table: <dell  b9k =""  ="">
    FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
    FreeBSD/SMP: 1 package(s) x 2 core(s)
     cpu0 (BSP): APIC ID:  0
     cpu1 (AP): APIC ID:  1
    ioapic0: Changing APIC ID to 8
    ioapic0 <version 2.0=""> irqs 0-23 on motherboard
    lapic0: Forcing LINT1 to edge trigger
    netisr_init: forcing maxthreads to 1 and bindthreads to 0 for device polling
    wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
    wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (wpi_fw, 0xc0988330, 0) error 1
    ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0789370, 0) error 1
    ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc0789410, 0) error 1
    ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc07894b0, 0) error 1
    wlan: mac acl policy registered
    kbd1 at kbdmux0
    cryptosoft0: <software crypto=""> on motherboard
    padlock0: No ACE support.
    acpi0: <dell b9k =""  =""> on motherboard
    acpi0: [ITHREAD]
    acpi0: Power Button (fixed)
    Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
    acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
    cpu0: <acpi cpu=""> on acpi0
    cpu1: <acpi cpu=""> on acpi0
    acpi_hpet0: <high precision="" event="" timer=""> iomem 0xfed00000-0xfed003ff on acpi0
    Timecounter "HPET" frequency 14318180 Hz quality 900
    acpi_button0: <power button=""> on acpi0
    acpi_button0: enable wake failed
    pcib0: <acpi host-pci="" bridge=""> port 0xcf8-0xcff on acpi0
    pci0: <acpi pci="" bus=""> on pcib0
    pcib1: <acpi pci-pci="" bridge=""> irq 16 at device 1.0 on pci0
    pci1: <acpi pci="" bus=""> on pcib1
    vgapci0: <vga-compatible display=""> port 0xecd8-0xecdf mem 0xdfe00000-0xdfe7ffff,0xc0000000-0xcfffffff,0xdff00000-0xdfffffff irq 16 at device 2.0 on pci0
    agp0: <intel g33="" svga="" controller=""> on vgapci0
    agp0: detected 7164k stolen memory
    agp0: aperture size is 256M
    vgapci1: <vga-compatible display=""> mem 0xdfe80000-0xdfefffff at device 2.1 on pci0
    pci0: <multimedia, hda=""> at device 27.0 (no driver attached)
    pcib2: <acpi pci-pci="" bridge=""> irq 16 at device 28.0 on pci0
    pci2: <acpi pci="" bus=""> on pcib2
    bge0: <broadcom netlink="" gigabit="" ethernet="" controller =""  ="" ,="" asic="" rev.="" 0x5784100=""> mem 0xdfbf0000-0xdfbfffff irq 16 at device 0.0 on pci2
    miibus0: <mii bus=""> on bge0
    brgphy0: <bcm5784 10="" 100="" 1000basetx="" phy=""> PHY 1 on miibus0
    brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
    bge0: [FILTER]
    uhci0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a=""> port 0xff80-0xff9f irq 21 at device 29.0 on pci0
    uhci0: [ITHREAD]
    usbus0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a=""> on uhci0
    uhci1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b=""> port 0xff60-0xff7f irq 22 at device 29.1 on pci0
    uhci1: [ITHREAD]
    usbus1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b=""> on uhci1
    uhci2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c=""> port 0xff40-0xff5f irq 18 at device 29.2 on pci0
    uhci2: [ITHREAD]
    usbus2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c=""> on uhci2
    uhci3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d=""> port 0xff20-0xff3f irq 23 at device 29.3 on pci0
    uhci3: [ITHREAD]
    usbus3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d=""> on uhci3
    ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller=""> mem 0xff980800-0xff980bff irq 21 at device 29.7 on pci0
    ehci0: [ITHREAD]
    usbus4: EHCI version 1.0
    usbus4: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller=""> on ehci0
    pcib3: <acpi pci-pci="" bridge=""> at device 30.0 on pci0
    pci3: <acpi pci="" bus=""> on pcib3
    isab0: <pci-isa bridge=""> at device 31.0 on pci0
    isa0: <isa bus=""> on isab0
    atapci0: <intel ich7="" udma100="" controller=""> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 16 at device 31.1 on pci0
    ata0: <ata 0="" channel=""> on atapci0
    ata0: [ITHREAD]
    atapci1: <intel ich7="" sata300="" controller=""> port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf irq 20 at device 31.2 on pci0
    atapci1: [ITHREAD]
    ata2: <ata 0="" channel=""> on atapci1
    ata2: [ITHREAD]
    ata3: <ata 1="" channel=""> on atapci1
    ata3: [ITHREAD]
    pci0: <serial bus,="" smbus=""> at device 31.3 (no driver attached)
    atrtc0: <at realtime="" clock=""> port 0x70-0x7f irq 8 on acpi0
    ppc0: <parallel port=""> port 0x378-0x37f,0x778-0x77f irq 7 on acpi0
    ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
    ppc0: FIFO with 16/16/8 bytes threshold
    ppc0: [ITHREAD]
    ppbus0: <parallel port="" bus=""> on ppc0
    plip0: <plip network="" interface=""> on ppbus0
    plip0: [ITHREAD]
    lpt0: <printer> on ppbus0
    lpt0: [ITHREAD]
    lpt0: Interrupt-driven port
    ppi0: <parallel i="" o=""> on ppbus0
    uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
    uart0: [FILTER]
    pmtimer0 on isa0
    orm0: <isa option="" roms=""> at iomem 0xc0000-0xcb7ff,0xcb800-0xcd7ff,0xcd800-0xcffff pnpid ORM0000 on isa0
    sc0: <system console=""> at flags 0x100 on isa0
    sc0: VGA <16 virtual consoles, flags=0x300>
    vga0: <generic isa="" vga=""> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    atkbdc0: <keyboard controller="" (i8042)=""> at port 0x60,0x64 on isa0
    atkbd0: <at keyboard=""> irq 1 on atkbdc0
    kbd0 at atkbd0
    atkbd0: [GIANT-LOCKED]
    atkbd0: [ITHREAD]
    est0: <enhanced speedstep="" frequency="" control=""> on cpu0
    est: CPU supports Enhanced Speedstep, but is not recognized.
    est: cpu_vendor GenuineIntel, msr 6160b2506000b25
    device_attach: est0 attach returned 6
    p4tcc0: <cpu frequency="" thermal="" control=""> on cpu0
    est1: <enhanced speedstep="" frequency="" control=""> on cpu1
    est: CPU supports Enhanced Speedstep, but is not recognized.
    est: cpu_vendor GenuineIntel, msr 6160b2506000b25
    device_attach: est1 attach returned 6
    p4tcc1: <cpu frequency="" thermal="" control=""> on cpu1
    Timecounters tick every 1.000 msec
    IPsec: Initialized Security Association Processing.
    usbus0: 12Mbps Full Speed USB v1.0
    usbus1: 12Mbps Full Speed USB v1.0
    usbus2: 12Mbps Full Speed USB v1.0
    usbus3: 12Mbps Full Speed USB v1.0
    usbus4: 480Mbps High Speed USB v2.0
    ad4: 76319MB <seagate st380817as="" 3.42=""> at ata2-master UDMA100 SATA
    ugen0.1: <intel> at usbus0
    uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus0
    ugen1.1: <intel> at usbus1
    uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus1
    ugen2.1: <intel> at usbus2
    uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus2
    ugen3.1: <intel> at usbus3
    uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus3
    ugen4.1: <intel> at usbus4
    uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus4
    uhub0: 2 ports with 2 removable, self powered
    uhub1: 2 ports with 2 removable, self powered
    uhub2: 2 ports with 2 removable, self powered
    uhub3: 2 ports with 2 removable, self powered
    acd0: DVDROM <optiarc dvd-rom="" ddu1681s="" 102a=""> at ata3-master UDMA100 SATA
    lapic1: Forcing LINT1 to edge trigger
    SMP: AP CPU #1 Launched!
    Root mount waiting for: usbus4
    uhub4: 8 ports with 8 removable, self powered
    Trying to mount root from ufs:/dev/ad4s1a
    WARNING: / was not properly dismounted
    WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck
    ugen2.2: <vendor 0x0461=""> at usbus2
    ums0: <vendor 0="" 2="" 0x0461="" usb="" optical="" mouse,="" class="" 0,="" rev="" 2.00="" 2.00,="" addr=""> on usbus2
    ums0: 3 buttons and [XYZ] coordinates ID=0
    ugen2.3: <lite-on technology="" corp.=""> at usbus2
    ukbd0: <lite-on 0="" 3="" technology="" corp.="" usb="" multimedia="" keyboard,="" class="" 0,="" rev="" 1.10="" 1.18,="" addr=""> on usbus2
    kbd2 at ukbd0
    uhid0: <lite-on 0="" 3="" technology="" corp.="" usb="" multimedia="" keyboard,="" class="" 0,="" rev="" 1.10="" 1.18,="" addr=""> on usbus2
    pflog0: promiscuous mode enabled
    bge0: link state changed to UP</lite-on></lite-on></lite-on></vendor></vendor></optiarc></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></seagate></cpu></enhanced></cpu></enhanced></at></keyboard></generic></system></isa></parallel></printer></plip></parallel></parallel></at></serial></ata></ata></intel></ata></intel></isa></pci-isa></acpi></acpi></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></bcm5784></mii></broadcom></acpi></acpi></multimedia,></vga-compatible></intel></vga-compatible></acpi></acpi></acpi></acpi></power></high></acpi></acpi></dell></software></version></dell ></lahf></nx,lm></sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>
    

    Any ideas on getting this working?


  • Netgate Administrator

    First thing I'd do is check the card to see which chip it's actually using. As I said above there are a number of revisions of that card.

    Steve



  • I'll check the card tomorrow to see if there is any thing on it that would note the revision.



  • @evolvd:

    I'm having the same problem, so here is the output from dmesg

    There is no sign of your card being visible on the bus. I expect it is either dead or not correctly seated in the slot.

    Here are the PCI devices detected but not claimed by a driver:

    pci0: <multimedia, hda="">at device 27.0 (no driver attached)
    pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)</serial></multimedia,> 
    

    I would expect to see something like```
    pci#: <network, ethernet=""> at device #.# (no driver attached)</network,>

    
    @evolvd:
    
    > Any ideas on getting this working?
    
    As a further check you could post the output of the pfSense shell command _pciconf -l -v_
    
    I suggest you ensure the card is correctly seated in the slot. Is the card visible under (say) an up to date version of Linux?


  • Thanks for looking through the dmesg output I posted. I see the NIC card in the BIOS and when I plug in a ethernet cable the light go active on the card. I'm downloading the latest version of Ubuntu to see if that recognizes my card.



  • Yeah, Ubuntu was able to see the card.


  • Netgate Administrator

    Hmm,
    Try Wallabybob's suggestion above, run:

    
    pciconf -l -v
    
    

    The card should show up there as a pci device.
    Did you find out which chip is on the card? The revision number is not important other than to allow us to look up compatibility.

    Steve


  • Netgate Administrator

    Out of curiosity I googled some more and found:

    DGE-530T revision C1 (Realtek RTL8169 based, PCI ID 1186:4302)

    So it seems that D-link may (if the above report is accurate) have changed to a completely different chipset whilst keeping the same model number. Nice!

    This may be supported by the re(4) driver but possibly not the FreeBSD 8.1 release.

    Non of this explains why it doesn't appear as an unknown device in the boot log though.

    Steve

    Edit: Yes, support for the rev C1 card was only added to the re driver in Aug 2011. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=159116



  • I installed 2.1 just to see if it would make a difference (no luck) here is the output for pciconf -l -v

    $ pciconf -l -v
    hostb0@pci0:0:0:0:	class=0x060000 card=0x02941028 chip=0x29c08086 rev=0x0a hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    pcib1@pci0:0:1:0:	class=0x060400 card=0x02941028 chip=0x29c18086 rev=0x0a hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    vgapci0@pci0:0:2:0:	class=0x030000 card=0x02941028 chip=0x29c28086 rev=0x0a hdr=0x00
        class      = display
        subclass   = VGA
    vgapci1@pci0:0:2:1:	class=0x038000 card=0x02941028 chip=0x29c38086 rev=0x0a hdr=0x00
        class      = display
    none0@pci0:0:27:0:	class=0x040300 card=0x02941028 chip=0x27d88086 rev=0x01 hdr=0x00
        class      = multimedia
        subclass   = HDA
    pcib2@pci0:0:28:0:	class=0x060400 card=0x02941028 chip=0x27d08086 rev=0x01 hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    uhci0@pci0:0:29:0:	class=0x0c0300 card=0x02941028 chip=0x27c88086 rev=0x01 hdr=0x00
        class      = serial bus
        subclass   = USB
    uhci1@pci0:0:29:1:	class=0x0c0300 card=0x02941028 chip=0x27c98086 rev=0x01 hdr=0x00
        class      = serial bus
        subclass   = USB
    uhci2@pci0:0:29:2:	class=0x0c0300 card=0x02941028 chip=0x27ca8086 rev=0x01 hdr=0x00
        class      = serial bus
        subclass   = USB
    uhci3@pci0:0:29:3:	class=0x0c0300 card=0x02941028 chip=0x27cb8086 rev=0x01 hdr=0x00
        class      = serial bus
        subclass   = USB
    ehci0@pci0:0:29:7:	class=0x0c0320 card=0x02941028 chip=0x27cc8086 rev=0x01 hdr=0x00
        class      = serial bus
        subclass   = USB
    pcib3@pci0:0:30:0:	class=0x060401 card=0x02941028 chip=0x244e8086 rev=0xe1 hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    isab0@pci0:0:31:0:	class=0x060100 card=0x00000000 chip=0x27b88086 rev=0x01 hdr=0x00
        class      = bridge
        subclass   = PCI-ISA
    atapci0@pci0:0:31:1:	class=0x01018a card=0x02941028 chip=0x27df8086 rev=0x01 hdr=0x00
        class      = mass storage
        subclass   = ATA
    atapci1@pci0:0:31:2:	class=0x01018f card=0x02941028 chip=0x27c08086 rev=0x01 hdr=0x00
        class      = mass storage
        subclass   = ATA
    none1@pci0:0:31:3:	class=0x0c0500 card=0x02941028 chip=0x27da8086 rev=0x01 hdr=0x00
        class      = serial bus
        subclass   = SMBus
    bge0@pci0:2:0:0:	class=0x020000 card=0x02941028 chip=0x169814e4 rev=0x10 hdr=0x00
        class      = network
        subclass   = ethernet
    none2@pci0:3:0:0:	class=0x020000 card=0x43021186 chip=0x43021186 rev=0x10 hdr=0x00
        class      = network
        subclass   = ethernet
    

    I'm going to be ordering another card today but maybe this will help someone else.


  • Netgate Administrator

    Well at least it showed up!

    none2@pci0:3:0:0: class=0x020000 card=0x43021186 chip=0x43021186 rev=0x10 hdr=0x00
        class      = network
        subclass  = ethernet

    As you can see this is indeed the rev C1 hardware with the Realtek chip (device ID:4302).
    The only build of 2.1 currently available (unless I missed some announcement) is still built on FreeBSD 8.1. 2.1 will be built on FreeBSD 9.X in future and this should include support for your card.

    Steve



  • ha yeah I'm glad I could see the problem. I'm ordering another card right now so I will just use this card for something else. I have a question about the card I was going to get. I made another thread about it. http://forum.pfsense.org/index.php/topic,43616.0.html



  • fyi, those cards WILL fail randomly causing connectivity loss.  :(

    i learned this the hard way. you are much better off with an intel base card. like the intel pro-1000 mt (either desktop/or server models) …i have found the server models of the pro-1000 to be extremely solid.

    the dlink (especially the rev. b's) on the other hand...they would just puke randomly and you would have to restart the whole firewall to bring them back to life.

    you can find the pro-1000's on ebay for pretty cheap. i am running four in the PCI slots and have yet to have a single problem once i put the firewall back into production. my throughput is between 20mbps to 300mbps, and they handle it without breaking a sweat.

    just an FYI is all.  :D



  • What I find about of pfsense is that the hardware is really important. This is not highlighted enough on their website.
    When somebody is considering pfsense, it is important to consider the hardware.

    Coming from a Microsoft background, you don't think hardware compatibility problem immediately when you setup your freeBsd box, but you should, especially with a pfsense box since it doesn't uses the last updated distro of freeBSD.

    So when you buy brand new NIC, because pfsense is not the most recent distro it is quite possible your new hardware driver will not be available in the pfsense distro.

    I'm just saying this from experience, as I figure that the hardware was really important after buying it, and starting to setup my pfsense. Then when it didn't work I start reading more about pfsense, and realize all the above explanation.

    I think pfsense website should find a way to make it stand out on their home page.

    Something like: "BEFORE YOU START BUYING PARTS FOR SETTING UP PFSENSE, MAKE SURE THE HARDWARE YOU WANT TO BUY IS COMPATIBLE WITH PFSENSE DISTRO"

    Doing this type of warning will avoid a lot of headach, and maybe having the list of compatible hard drive easy to find :)



  • 100% correct. even though the dlink NIC will work, but you will have issues with them. drop connections, packet mangling, etc.

    i learned this the hard way as well, but once spending time in the forums and reading the vast amount of information within…i have a very good understanding of the overall product and the in's/out's of pfsense.  ...however, being a microsoft guy for the past 15+ years...it did take me a little longer than it should have.  ;D

    @pat1974:

    What I find about of pfsense is that the hardware is really important. This is not highlighted enough on their website.
    When somebody is considering pfsense, it is important to consider the hardware.

    Coming from a Microsoft background, you don't think hardware compatibility problem immediately when you setup your freeBsd box, but you should, especially with a pfsense box since it doesn't uses the last updated distro of freeBSD.

    So when you buy brand new NIC, because pfsense is not the most recent distro it is quite possible your new hardware driver will not be available in the pfsense distro.

    I'm just saying this from experience, as I figure that the hardware was really important after buying it, and starting to setup my pfsense. Then when it didn't work I start reading more about pfsense, and realize all the above explanation.

    I think pfsense website should find a way to make it stand out on their home page.

    Something like: "BEFORE YOU START BUYING PARTS FOR SETTING UP PFSENSE, MAKE SURE THE HARDWARE YOU WANT TO BUY IS COMPATIBLE WITH PFSENSE DISTRO"

    Doing this type of warning will avoid a lot of headach, and maybe having the list of compatible hard drive easy to find :)


Log in to reply