Wireless network card configuation



  • Hi,

    I've just put a D-Link DWL-G520+ PCI card in my pfSense box
    however can't seem to get it configured.

    Things I already found out:

    pciconf -lv gives me:
    none1@pci0:12:0:        class=0x028000 card=0x3b041186 chip=0x9066104c rev=0x00 hdr=0x00
        vendor  = 'Texas Instruments (TI)'
        device  = 'TNETW1130(ACX111) 802.11b/g Wireless Cardbus/PCI Adapter'
        class    = network

    ifconfig tells me:
    ng0: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng1: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng2: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng3: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng4: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng5: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng6: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng7: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng8: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng9: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng10: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng11: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng12: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng13: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng14: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng15: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    ng16: flags=8890 <pointopoint,noarp,simplex,multicast>mtu 1500
    (those are entries that weren't there before the card was in my pfSense box)

    any help is welcome.

    Thanks,
    MickeyByte</pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast>



  • ng0 to ng16 are pptp interfaces (the /29 subnet for your pptp users). They don't have to do anything with the wireless card at all.

    Did you try to assign the interface? Only adding an interface to the box doesn't make it visible in the webgui. Try Interfaces>(assign) in the webgui and hit the [+] button.



  • Is that card suported?



  • If it's assignable it might work. I don't have such a card, so I don't know. All I can say is that atheros chipset based cards should be preferred to be used with pfsense as all the devs run these cards which makes support for them better of course.



  • ng0 to ng16 are pptp interfaces (the /29 subnet for your pptp users). They don't have to do anything with the wireless card at all.

    :-[ D'oh! (I'm hitting my head on the table for a few times now)
    That's the problem when you change too much at once.

    [quote]If it's assignable it might work. I don't have such a card, so I don't know. All I can say is that atheros chipset based cards should be preferred to be used with pfsense as all the devs run these cards which makes support for them better of course.
    If I try to assign an extra interface (I now have LAN: rl1 and WAN: rl0, which are 2 realtek cards), I have one extra card in the list: plip0(0)
    Guess that's not the one I need, is it?

    How can I find out if that card is atheros based, or if it isn't where to find what it is and may find drivers for it?

    Thanks!
    M.



  • plip is not a real interface and you shouldn't assign it. It's something needed behind the scenes. If the card would be atheros you would see an ath0 assignable interface. As it doesn't show up as assignable it's something we don't have a driver for. Check freebsd site for that hardware if it is supported.



  • I think that card is not natively suported (TI ACX111). Perhaps with NDISulator you can use Window$ drivers, but don't expect hostap modes.



  • Hi,

    I've also been looking around and given up hope I will get it working.
    Seems I'm having just that one card that had to use another chipset  :(

    Thanks for the support!



  • Texas instruments cards are not supported, you might however get it running with project evil aka ndisulator.
    Texas instruments think they have some magic chips that can do stuff that noone else has figured out yet, and imo. they are so wrong in protecting stuff to a degree that makes their chips pretty much unusable in any open source project.

    So stay off Texas instruments and show them that their chips suck as long as they don't provide unix/linux drivers.



  • That card seems to have some driver available, but it's not in the FreeBSD base system.  At this point, we're not going to add any drivers that aren't found in base (anything in base should work pretty well, anything not in base probably isn't there for a reason)  :)



  • Hello, BETA-1 is great so far.  ;) I have a question on making an automatic conneciton on power up.

    I'm a Robotics experimenter and utlizing 2 Wrap boards each with dual CM9 cards. The wireless parts are very stable now with the new release thanks. I have setup one card on each for Turbo mode between themselves ATH1 <-> ATH1 and each boards ATH0 to G mode for regular server / client usage at either end.

    My question is how can I automatically make the connection between my 2 wrap boards ATH1 <-> ATH1 without doing it by hand once they are both booted. Thanks in advance.

    –RW


Locked