Jump to content

d3ac0n

Members
  • Posts

    12
  • Joined

  • Last visited

d3ac0n's Achievements

New Here

New Here (1/7)

0

Reputation

  1. Just as a brief answer to this, I am using the most updated driver for this card, and it does support WEP, and did work while under Windows 2000 with WEP and WPA. Here's a bit from my dmesg output ndiswrapper: using irq 9 wlan0: ndiswrapper ethernet device xx:xx:xx:xx:xx:xx using driver net2pg54 wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP So it's not an issue of WEP function not being supported or the NIC not working. I think there is a code issue or a config issue here, I just don't know what. But thanks for the help anyways. I'll take any input I can get.
  2. ok, I understand the part about having ESSID broadcast on, although I don't understand the need for that. It's always worked without encryption with no ESSID broadcast. What I'm stuck on is what you mean by the KEY line. This is what my config file looks like. DEVICE=wlan0 BOOTPROTO=dhcp ONBOOT=yes HWADDR=<my NIC MAC> METRIC=10 MII_NOT_SUPPORTED=no WIRELESS_MODE=Managed WIRELESS_ESSID= <My essid> ENCRPTION=on WIRELESS_ENC_KEY=<my key> DHCP_HOSTNAME=SUMOMO NEEDHOSTNAME=no Now, as far as the shared/not shared, are you talking about normal WEP vs WPA? and why would there be two seperate sets of info on one line for a WEP or WPA key? could you clarify please?
  3. Well, after finally being able to get my wireless working using ndiswrapper 1.1, I decided that I didn't want to run it unprotected, so I decided that I would setup WEP on my network. I set a 13 digit WEP key on my wireless base station and saved it in. When I went to set the encryption key on Mandrake, I got some strange errors [root@SUMOMO deacon]# iwconfig wlan0 enc 1234567890123 Error for wireless request "Set Encode" (8B2A) : SET failed on device wlan0; Invalid argument. It doesn't matter WHAT I use for a WEP key or the length. I always get this error. Any ideas?
  4. Hey all. I recently had to format and reinstall my MDK installation on my laptop (due to hosing the boot sector and the partition table. Don't ask.) So I was going about getting everything set back up, and went to reinstall the wireless card using ndiswrapper 0.12, the same version I used before, using the same drivers off the same CD I used before. Really the only thing different is that this is a fresh install of MDK 10.1. I made sure to remove the old ndiswrapper 0.4 version that comes with MDK 10.1, and proceeded to install ndiswrapper 0.12. Everything went fine. I copied over the drivers into my home directory and pointed ndiswrapper to them. then after running ndiswrapper -m and modeprobe ndiswrapper I checked my dmesg and found THIS: ndiswrapper version 0.12 loaded (preempt=no,smp=no) ndiswrapper (import:235): Unknown symbol: ntoskrnl.exe:ZwOpenKey ndiswrapper (import:235): Unknown symbol: ntoskrnl.exe:ZwEnumerateKey ndiswrapper (import:235): Unknown symbol: ntoskrnl.exe:ZwClose ndiswrapper (import:235): Unknown symbol: ntoskrnl.exe:ZwQueryValueKey ndiswrapper (import:235): Unknown symbol: NDIS.SYS:NdisRegisterProtocol ndiswrapper (import:235): Unknown symbol: NDIS.SYS:NdisOpenAdapter ndiswrapper (import:235): Unknown symbol: NDIS.SYS:NdisCloseAdapter ndiswrapper (import:235): Unknown symbol: NDIS.SYS:NdisRequest ndiswrapper (import:235): Unknown symbol: NDIS.SYS:NdisDeregisterProtocol ndiswrapper (load_driver:2034): unable to prepare driver 'netcbg54' Anybody have any idea what this is about? I didn't run into this the last time around, and I'm fairly certain that it's not due to ndiswrapper being installed incorrectly. I guess I could try some other drivers, but there are not others that I know of, other than some really oddball ones pointed to in the ndiswrapper wiki list. I guess I will try those and give you guys an update, but I don't hold out much hope. If anybody comes up with any other ideas, please let me know!
  5. OK, I FINALLY figured it out! I checked my /etc/sysconfig/network file. the ONLY listing it had in there for an interface was the wlan0 which I had removed! a quick line change to make it eth0 and a reboot and VOILA! I am ON THE NET! Persistance is a beautiful thing!
  6. anybody have any idea? I even removed the Wireless bridge and connected the MDK box to the port on the Linksys Swicth that the Bridge had been using. Same issue. So it's not the Bridge thats at fault, and I'm back to square one. I REALLY REALLY don't want to have to format and start over with this machine if anyone can give me ANY clue as to how to proceed from here. HELP!!
  7. ifconfig get's me the static IP info I setup. (Can't paste in anything since I am on my WinXP box right now, using a KVM switch to swap back and forth between it and the Problem MDK box) in case it matters, here's the IP info I have IP = 10.50.2.2 SN = 255.255.255.0 DG = 10.50.2.1 no DHCP (of course) DNS = 10.50.2.4 <- my In-house Caching DNS server. 4.2.2.1 <- Backup option, incase my server goes down 4.2.2.2 <- same as above ok, I "sneakernet"-ed my resolv.conf over to the WinXP machine as a .txt. here it is search deacon local # search deacon local deacon local deacon local deacon local deacon local deacon.no-ip.com local deacon.no-ip.com deacon.no-ip.com deacon.no-ip.com local deacon.no-ip.com local deacon.no-ip.com deacon.no-ip.com deacon.no-ip.com local deacon.no-ip.com local deacon.no-ip.com deacon.no-ip.com local deacon.no-ip.com local deacon.no-ip.com local deacon.no-ip.com local nameserver 10.50.2.4 nameserver 4.2.2.1 nameserver 4.2.2.2 # nameserver 127.0.0.1 # ppp temp entry I have no idea what all that commented out stuff is for. (that whole chunk of text is commented out. The transfer to the XP machine messed up the formatting) It may have been generated when I was fighting to get my wireless card working, or during the current problems. But since it's commented out, I would imagine that it's not an issue. Hope that helps!
  8. Ok, got a strange one here. I have a network in my house, consisting of several Windows and Linux boxes. I recently gave up trying to get my Asus Wireless card to work AT ALL on an old P2 400 MGZ machine with MDK10.1 using ndiswrapper, and went back to the old Kingston NIC that was already installed and is a "Known-Good" NIC. So I strung the CAT5 cable, crimped and added the ends, tested by pinging all the other machines in my network, and surfed to my firewall's HTTP Admin interface. All successful. However, when I try to surf the web (using firefox), I get "The connection was refused When connecting to <website name>" for all websites. When I try and ping out (as root) to websites, using either URL or IP, I get: connect: network is unreachable I tried the IPv6 trick in firefox suggested by (i think) An0n, no joy. I made sure to completely uninstall ndiswrapper from my machine to ensure that there is no conflict there. I even removed the network connection for eth0 using MCC, rebooted, and created a new connection using all the correct settings. No change. At this point I'm at a bit of a loss. I have another MDK 10.1 machine (laptop) that connects WIRELESSLY just fine through the EXACT SAME network equipment with no problems at all. I'm about 2 steps from formatting the darn thing and starting over. But I thought I'd give you guys a shot at figuring it out first. Just in case it's needed, here is my network layout Cable Modem -> Smoothwall Linux Firewall -> Linksys 4 port switch -> Buffalotech wireless bridge/3 port switch-> Problem MDK box. The linksys switch has my Win2K DNS/WINS/File Server, my WinXP box, and my Wife's WinXP box off of it, in addition to the Wireless Bridge/Switch. The Buffalotech Wireless Bridge/Switch connects my MDK 10.1 Laptop wirelessly, and the MDK 10.1 Box I am having problems with via the Fast Ethernet Switch. My entire network uses a single class C subnet using all static IPs (so no DHCP issues here) So there you have it. Anybody have any suggestions? 'Cause I'm fresh out of ideas.
  9. In response to your question Leo, it happens both in the GUI AND in a terminal window. Which is really annoying when trying to type things like "urpmi" or fill out web-forms with my real name, which happens to have several m's in it! lol.
  10. Ok, this is a strange one... I have Mandrake Linux 10.1 Community installed on my IBM Thinkpad i1400 laptop on a dual-boot with WinXP. My issue is that the M key doesn't work right in Mandrake. It works normally when I boot into XP, but when I'm in Linux I can't just tap the key and get a standard lowercase 'm'. If I hold down Shift I can get a Capital 'M', if I hit Capslock and Shift I can get a lowercase 'm', but I can't just hit the key! Mandrake installed with a generic 105 keyboard layout, and thinking it was a layout issue (might still be) I changed the keyboard to the only Thinkpad entry in the Keyboards list. No change. Tried searching the net and the forums, and the answer I keep coming up with is a layout issue. But I'd really rather not just run through all the layouts until I get one that works, simply because A. that will take FOREVER and B. there is a chance that I might choose a totally incompatible layout and lose keyboard functionality altogether. (which would be a bad thing.) Has anyone else out there run into this issue yet? and can anyone else point me to a solution? Thanks in advance, D3ac0n
  11. Hmm... Looks like nobody knows. strange thing is, whenever I try to compile the 8.0 ndiswrapper from source, it errors out as if I didn't have the kernel source installed, when I do. (made a point of adding it in after the original install.) I know it's not a symlink issue, because when you do a GUI-based install of the kernel source, it automatically adds all the correct symlinks. But I keep getting this error when trying to perform a "make install" on it. make -C driver install make[1]: Entering directory '/home/deacon/ndiswrapper-0.8/driver' make -C /lib/modules/2.6.3-4mdk/build SUBDIRS=/home/deacon/ndiswrapper-0.8/drivers DRV_VERSION=0.8 modules make[2]: Entering directory '/lib/modules/2.6.3-4mdk/build' make[2]: ***No rule to make target 'modules'. Stop. make[2]: Leaving directory '/lib/modules/2.6.3-4mdk/build' make[1]: *** [default] Error 2 make[1]: Leaving Directory '/home/deacon/ndiswrapper-0.8/driver' make: *** [install] Error2 I was thinking that this might be related to the ndiswrapper 0.4 version being installed, but I'm not entirely sure. anyone have any clues?
  12. ok, not sure if this should go in the hardware or software forums, so I'll start here. Bit of a Linux n00b here, so please bear with my ignorance. I am trying to get my Buffalotech wireless card working under Mandrake 10 Now, as many here may know, this runs the MELCO Chipset, and there are no linux drivers available from Buffalotech or Melco. So, I have to resort to using Ndiswrapper. Unfortunately, the version of ndiswrapper that 10 ships with (0.4) doesn't work, and Mandrake will not allow me to install 8.0. I can install 7.5, but it does not run, just 4.0 runs. I did search the forums already, and tried some of the suggestions offered. I already ran: urpme ndiswrapper That helped remove the non-functional binary installation of 7.5 I had tried, and then when I ran it again to remove 4.0, I got: unknown package: ndiswrapper so I thought it was gone, until I ran dmesg, and saw, on the very last line: ndiswrapper version 4.0 loaded ok, what's the deal here? how do I get this 4.0 version OUT of my machine so I can install 8.0?
×
×
  • Create New...