I could very, very easily be mistaken; but I think a standalone build of broadcom-sta will, and should
always fail. It's built at the same time the kernel is, and the kernel-specific package of broadcom-sta needs to be used.
I see there's been work on this since the thread was started. A newer kernel has been rebuilt with broadcom-sta and similar packages having the kernel's version added to their name, rather than to their version. Me, I don't know if that's what will be set in stone for the future.
Please try this for now:
-- or --http://vectorlinux.osuosl.org/VL64-7.1/extra/n/broadcom-sta-220.127.116.11_3.18.14-x86_64-1vl71.txz
depending on your processor.
Put the download somewhere that it can be accessed by, or copied to, your VL installation. I assume you're not downloading within VL when your connection doesn't work.
Boot VL and
upgradepkg --install-new /path/to/broadcom-sta-18.104.22.168_3.18.14-x86-1vl71.txz
Ideally, the last line is unneccesary because the package's doinst should handle it, and wl.ko doesn't have dependencies anyway. Running it doesn't hurt anything, and is the "belt and suspenders" approach.
If this works, add 'broadcom-sta' to the EXCLUDE= line near the top of /etc/slapt-get/slapt-getrc. Just tack on ',broadcom-sta' at the end of the line. That way the wrong broadcom-sta package won't be pulled next time you do --upgrade. If there is an actual upgrade to broadcom-sta for this kernel (doubtful), you can use the same 'upgradepkg' line to install that.
I have an ulterior motive here. I don't have a wifi device to test this with, and wish to know whether this works for various reasons. Feedback very much appreciated.