I ran into strange problems accessing a shared Novell Netware (5.0) folder. Everytime the folder was attempted to be accessed from multiple machines the window would freeze and if you waited long enough, there would be an error message along the lines of “Netware Alert Message”… NIOS.NLM
Call to NIOS page unlock by module unknown failed Address 0x05650016, length 0x00700465 and then according to what I was told, ctrl-enter was instructed to clear the message and the machine rebooted.
The last time I used openvpn, it was version 1.x and only supported a single connection per running process. So, if you had a server that you wanted to support multiple clients connecting, you had to… have multiple ports open to the outside world (unless you did something VERY fancy), and had to have as many openvpn processes open and listening for connections, as you had clients you expected to connect. It wasn’t a pretty setup unless you had a small number (1-5) that you expected to connect. Fortunately that has changed with the 2.0 series of openvpn and it’s really matured as a vpn solution.
I had hoped to do an article on metasploit in the not too distant future, but not as early as tonight…. However, I’ve made a couple of references to it in previous posts which, well, it would be nice if I’d already given a bit of information about metasploit in general. For starters, metasploit is considered a “framework” for exploit modules and payload modules. Much like real weapons, knives, guns…. there are good uses and there are bad uses. It can be used by a network/security auditor to check for vulnerable systems. It could also be used by a cracker to exploit systems remotely. There’s a fine line.
So, according to D-Link there is a short list of access points that the DWL-800AP+ will repeat for. They are all d-link branded access points. It seems that there have been firmware updates to improve the compatibility with more models (of d-link access points.) Some of the incompatibilities have been with WEP encryption from what I’ve read.
Ok, so here’s the synopsis… I’ve spent the last few articles setting up a D-link DWL-800AP+ as a repeater for a linksys WAP11 (v. 1.1) As of the end of the last entry I had a bit of a problem with WEP but that seems to have been resolved now and here I am to fill you in on what went wrong. It was really a simple mistake. When I copied and pasted over from the linksys….
So, I set a WEP key on the linksys (WAP11 v. 1.1) and it promptly disappeared… it stopped responding (over the WIRED network) to my wap11gui admin tool. I quickly realized that part of the problem is from having two network cards attached (both in the 192.168.0 range)… disconnect the usb card and reconnect. Then I use the “security” tab to enable WEP (128-bit)
Ok, so now I had to add the new D-Link’s MAC address to the list of authorized MAC’s in the Linksys WAP11 (v. 1.1) For this, I call on wap11gui. Used to (since I use linux), I would have to suffer through a Windows boot on the laptop and balance the laptop on the edge of the bed and connect through usb to the linksys… now I can just administer it from my desk. Nice… Anyway, I log into that and Visit the “security” tab and “Authorized Mac”, and add the d-Link DWL-800AP+ to the list.
So, now that I was “in” the DWL-800AP+ it was time to see if I could set it up as a repeater. I visited the “wireless” tab of the web based configuration and chose Repeater mode instead of AP mode and saw that I would need the Mac address of the access point that I wanted to “repeat” signal from. In this case it’s the old Linksys WAP11 v. 1.1 So, I opened up a console and (as root) did an arpping 192.168.0.250 (the ip address of my Linksys AP). Got the reply back and typed it in.
For starters, I hooked the D-link DWL-800AP+ up and connected it through a crossover cable to my usb network card. That way I could access it exclusively on one adapter and look online for information with the other adapter, which came in quite handy. The first thing I found was that by default the dwl-800ap+ was configured to use 192.168.0.30 as it’s IP address. This one was not configured with the default settings. (Used / via ebay….) So, I did an nmap -sT 192.168.0.* -e eth1 which scanned the whole 192.168.0. list of addresses using my eth1 adapter (as opposed to the default adapter eth0)
I’ve got a single access point for my wireless network layer at the house and unfortunately have at least one real “dead spot” in the house. As luck would have it that dead spot is at the couch… so for some time I’ve looked at ways to extend the wireless network range or other ways. One such possibility of course, is a repeater. These days, most wireless repeaters I see either only work with their brand access point. (So a linksys repeater would only work with certain models of linksys access point…) Or… the repeater would only repeat 802.11g *(the newer wireless) traffic. Given that everything I’ve got is still 802.11b I didn’t really want to do a new round of hardware for ALL the wireless devices (the access point still works….) So… looking for a repeater I went.