swscanner

Network

Source (required if based on other people's work):

0
Score 78%
Description:

Simple Wireless Scanner (SWScanner) is an application for Linux environments designed for scanning, configuring, and (in general) managing wireless networks. SWScanner is also a powerfull wardriving tool, and has a high level of compatibility with NetStumbler, a similar and well-known application designed for other operating system.
Last changelog:

12 years ago


+ SWScanner 0.2.2 (16/12/2005)
- Added man page and project docbook documentation.
- Use of KDE XMLGUI architecture for designing the menu and tool bars.
- Extended use of KDE Actions.
- Re-ordering of menu and toolbars.
- New real-xml format for storing data in *.sws files. Still supporting old versions.
- New file conversion capabilities.
- New statistics section.
- New support for vendor information in the accesspoint list.
- Upgraded scanning code up to Wireless Tools v27.
- Possibility of using sounds when scanning.
- Possibility of hiding parts of main window.
- Cleaner code. More and more KDE-compliant.
- Added MIME-type support for SWScanner files.
- Cleaner .pot file.
- Solved some minor bugs with K-Menu desktop files.
- Basic although functional DCOP support.
- Other minor bugs and improvements.

+ SWScanner 0.2.0 (09/08/2005)
- Extended use of kdelibs instead of qtlibs to create a more KDE-compliant
look & feel.
- Extended code-reorganization and improvement.
- Possibility of generate a per-accesspoint signal/noise chart.
- Added a tray-icon with the most important funcions (included accespoint
management functions).
- Solved encoding problem with .desktop files.

+ SWScanner 0.1.8 (03/05/2005)
- Removed xterm from configure checks. SWScanner now allows you to choose
the x-terminal to use in the configuration dialog.
- Changed from fixed icons to icon-theme-dependent icons.
- Added an extra K-menu icon to run SWScanner as root.
- Added the file to open at start as a new command-line argument.
- Other minor bugs/changes.

+ SWScanner 0.1.7 (26/02/2005)
- Solved a bug by wich an 'error opening ~/.swscanner/swscanner.db database'
error appeared when trying to configure a new node. This was caused because
SWScanner didn't create the ~/.swscanner directory first.
- Added 'Andrés Seco Hernández' and 'Eugenio J. Sánchez' to credits as
Debian packagers.
- Other minor bugs/changes.

+ SWScanner 0.1.6 (26/01/2005)
----------------------------
- Implemented '--with-extra-libs' and '--enable-extra-debug options'
to configure script.
- Configure script now takes care of all needed libraries and binaries
(xterm)
- Added support for internationalization.
- Translated into Spanish.
- Filter by wep is now possible.
- Added a new thread that handles the scanning routine
- After make install, SWScanner icon now appears in Internet menu
- Added two command-line options:
* -i --iface pre-selects an interface
* -f --fileopen opens a file at start
- Added a command-line argument:
* --on (makes SWScanner to start scanning automatically).

+ SWScanner 0.1 --> SWScanner 0.1.5 (also a private release)
--------------------------------------------------

- A huge of minor bugs fixed
- Added compatibility with ipw2200 and ipw2100 driver
- Added compatibility with orinoco driver >= 0.15rc2
- Added extra debug information to stdout. Can be disabled using the option
--disable-debug in configure script

+ SWScanner 0.1 - First private release
-------------------------------------

CyberSpy

12 years ago

Hi, I've been trying for quite some time to compeile and install this app. But I get the same error with 0.2.2 and svn. I saw an answer on your forums, but it's not in english.

shapehandler.h:28:22: error: shapefil.h: No such file or directory
shapehandler.h:39: error: ‘SHPHandle’ does not name a type
shapehandler.h:40: error: ‘DBFHandle’ does not name a type
shapehandler.h:47: error: expected `)' before ‘sH’
make[2]: *** [main.o] Error 1
make[2]: Leaving directory `/home/cyberspy/swscanner/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/cyberspy/swscanner'
make: *** [all] Error 2
[cyberspy@goliath swscanner]$

My distro is Fedora Core 5, my DE is KDE 3.5.2 and, yes, both shapelib and shapelib-devel are both installed. Thank you in advance for any help.

Report

CyberSpy

12 years ago

I've fixed it. I had to go in to the src dir and edit an include in the shapefile.h file. An FC5 rpm is in thw works. The only issue I have now, isn't swscanner related (I don't think), when I go into KMenu and Internet, I see both SWScanner and SWSCanner - run as root. Both load, however only root can access wlan0, so if I try and scan as a normal user, I get an error. I'm thinking I need to setup a SUDO wheel, or it's related to WPA_SUPPLICANT, which I don't think is used by swscanner, but it is used by ndiswrapper and my driver, and you have to be root to use wpa_supplicant, again, I think SUDO may fix that, but either way, an i386 and x86_64 rpm are going to be built for FC5 .

Report

C

ivanfor

12 years ago

Yes, you're right. Almost every command related with network interfaces need superuser privileges. So, if you're going to scan, you need to use the SWScanner - as root link or (if you prefer), configure sudo (as I do for myself).

Report

gohanz

12 years ago

SAme problem also with 2.6.15.4

make[2]: Entering directory `/root/Desktop/swscanner/swscanner-0.2.2/src'
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/kde/include -I/usr/lib/qt/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -Wno-non-virtual-dtor -MT scanning.o -MD -MP -MF ".deps/scanning.Tpo" -c -o scanning.o scanning.cpp; \
then mv -f ".deps/scanning.Tpo" ".deps/scanning.Po"; else rm -f ".deps/scanning.Tpo"; exit 1; fi
scanning.cpp: In function `int print_scanning_info(int, char*, APList*)':
scanning.cpp:133: error: invalid conversion from `unsigned char*' to `char*'
make[2]: *** [scanning.o] Error 1
make[2]: Leaving directory `/root/Desktop/swscanner/swscanner-0.2.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/Desktop/swscanner/swscanner-0.2.2'
make: *** [all] Error 2
root@argo:~/Desktop/swscanner/swscanner-0.2.2#

Report

C

ivanfor

12 years ago

Hi.
It is fixed (among other things related to newer kernels and wireless-tools) in the svn version. Take a look at http://www.swscanner.org/en/subversion or directly download the development version at http://websvn.swscanner.org/dl.php?repname=swscanner&path=%2Ftrunk%2F&rev=0&isdir=1

Note that svn version needs wireless-tools v28 installed

If this is the only error you get, you can also change line 133 of scanning.cpp from "wrq.u.data.pointer = buffer;" to "wrq.u.data.pointer = (char *)buffer;"

Report

gohanz

12 years ago

i Have 2.6.14.4 after i will try with the 2.6.15.4.

Report

gohanz

12 years ago

With the SlackWare 10.2 i have this problem.

scanning.cpp: In function `int print_scanning_info(int, char*, APList*)':
scanning.cpp:133: error: invalid conversion from `unsigned char*' to `char*'
make[2]: *** [scanning.o] Error 1
make[2]: Leaving directory `/tmp/swscanner-0.2.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/swscanner-0.2.2'
make: *** [all] Error 2

Report

C

ivanfor

12 years ago

Strange... you're the first (AFAIK) with this problem. It seems to be a WT/kernel version related problem. Could you post wich ones are you using in order to try to reproduce the errors??

Thx.

Report

poisoned

12 years ago

Having the same problem on Slackware current:
gcc 3.4.5
glibc 2.3.6
Qt: 3.3.5
KDE: 3.5.1
linux-2.6.15.4
and using the latest svn head of madwifi:
make[2]: Entering directory `/home/poison/files/apps/swscanner-0.2.2/src'
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/kde/include -I/usr/lib/qt/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -Wno-non-virtual-dtor -MT scanning.o -MD -MP -MF ".deps/scanning.Tpo" -c -o scanning.o scanning.cpp; \
then mv -f ".deps/scanning.Tpo" ".deps/scanning.Po"; else rm -f ".deps/scanning.Tpo"; exit 1; fi
scanning.cpp: In function `int print_scanning_info(int, char*, APList*)':
scanning.cpp:133: error: invalid conversion from `unsigned char*' to `char*'
make[2]: *** [scanning.o] Error 1
make[2]: Leaving directory `/home/poison/files/apps/swscanner-0.2.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/poison/files/apps/swscanner-0.2.2'
make: *** [all] Error 2

Report

jpetso

12 years ago

KDE definitely needs applications like this one. That said, have you maybe thought of working together with the Solid team (at http://solid.kde.org), bringing in your skills and code in order to create the KDE4 networking backend?

Kévin Ottens is doing a good job, but he really needs people like you who are experienced with (wireless) networks and contribute to the common device library, making it easy for any KDE application to gather and use the data that your application can already retrieve.

Report

C

ivanfor

12 years ago

Yep. Of course i'd be proud to be able to help in KDE4 development.

The problem is that I don't really know if I will be usefull as I'm a quite newbie (1,5 years old) Linux (Debian only) user and, of course, developpr. SWScanner is my first GUI application which I mainly developed in 3 months. I'm sure lots of lines of code could be improved by experts.

Anyway, I'm a quick learner so I'd never mind to share all my knowledge and part of my free time to that interesting project.

Are you taking part of it?? What's (in your opinion) the best way to get in touch with the project? (I suppose through it's mailing list).

Thx for your comments :-)

Report

jpetso

12 years ago

> Are you taking part of it?? What's
> (in your opinion) the best way to
> get in touch with the project?

I'm not into the Solid project, but I had the opportunity to work on KDevelop4's Java support since September 05. I introduced myself over the mailing list and was lucky enough to be supported by Roberto Raggi and Adam Treat when I needed help or explanations.

IRC (#solid) is not a bad way too, if the respective people are online and get to see your request in bearable time ;-) Remember to prefix your IRC message with the name of the one that you want to talk to, so that his IRC client flashes ("jpetso: hello!").

If you want to be prepared well before approaching the developers, it's always a good idea to get the source code that you're interested in from KDE's anonymous SVN server and see what it looks like. That way, you can not only learn about the current code, but also see in which style new code (e.g. by you) should be written in.

> The problem is that I don't really
> know if I will be usefull as I'm a
> quite newbie (1,5 years old) Linux
> (Debian only) user and, of course,
> developpr. SWScanner is my first GUI
> application which I mainly developed
> in 3 months. I'm sure lots of lines
> of code could be improved by
> experts.

That's what I'm thinking all the time. In case you're not sure about your code, it's always a good idea to send the corresponding patches to the mailing list (one patch for one purpose, using svn diff) and let the more experienced developers comment on it. At least, that's what I do, and you will have to do one or two patches anyways before someone tells you to get a developer SVN account.

Also a good thing to do is checking out the documents at developer.kde.org, most notably http://developer.kde.org/documentation/other/developer-faq.html . You're getting more confident over time, believe me.

For the Solid project itself, there is a general page about getting involved with it at http://solid.kde.org/cms/1086 and a wiki page with available tasks at http://solid.kde.org/wiki/index.php/Tasks . When you feel like it, just approach Kévin Ottens (the main Solid developer) by mailing list or over IRC (where he's named ervin) and ask him for guidance.

And remember: if some remarks sound cold, they mostly do so because the developers don't take too much time to polish their phrasings, and they almost never want to critisize you personally. Quite the opposite - even if KDE as a whole is doing well, there are only one or a few developers per project who make for success or failure of it. (Unless you got some real lucky project, like Amarok.) So there's definitely the need for anyone who wants to help out.

Good luck,
Jakob

Report

12 years ago


+ SWScanner 0.2.2 (16/12/2005)
- Added man page and project docbook documentation.
- Use of KDE XMLGUI architecture for designing the menu and tool bars.
- Extended use of KDE Actions.
- Re-ordering of menu and toolbars.
- New real-xml format for storing data in *.sws files. Still supporting old versions.
- New file conversion capabilities.
- New statistics section.
- New support for vendor information in the accesspoint list.
- Upgraded scanning code up to Wireless Tools v27.
- Possibility of using sounds when scanning.
- Possibility of hiding parts of main window.
- Cleaner code. More and more KDE-compliant.
- Added MIME-type support for SWScanner files.
- Cleaner .pot file.
- Solved some minor bugs with K-Menu desktop files.
- Basic although functional DCOP support.
- Other minor bugs and improvements.

+ SWScanner 0.2.0 (09/08/2005)
- Extended use of kdelibs instead of qtlibs to create a more KDE-compliant
look & feel.
- Extended code-reorganization and improvement.
- Possibility of generate a per-accesspoint signal/noise chart.
- Added a tray-icon with the most important funcions (included accespoint
management functions).
- Solved encoding problem with .desktop files.

+ SWScanner 0.1.8 (03/05/2005)
- Removed xterm from configure checks. SWScanner now allows you to choose
the x-terminal to use in the configuration dialog.
- Changed from fixed icons to icon-theme-dependent icons.
- Added an extra K-menu icon to run SWScanner as root.
- Added the file to open at start as a new command-line argument.
- Other minor bugs/changes.

+ SWScanner 0.1.7 (26/02/2005)
- Solved a bug by wich an 'error opening ~/.swscanner/swscanner.db database'
error appeared when trying to configure a new node. This was caused because
SWScanner didn't create the ~/.swscanner directory first.
- Added 'Andrés Seco Hernández' and 'Eugenio J. Sánchez' to credits as
Debian packagers.
- Other minor bugs/changes.

+ SWScanner 0.1.6 (26/01/2005)
----------------------------
- Implemented '--with-extra-libs' and '--enable-extra-debug options'
to configure script.
- Configure script now takes care of all needed libraries and binaries
(xterm)
- Added support for internationalization.
- Translated into Spanish.
- Filter by wep is now possible.
- Added a new thread that handles the scanning routine
- After make install, SWScanner icon now appears in Internet menu
- Added two command-line options:
* -i --iface pre-selects an interface
* -f --fileopen opens a file at start
- Added a command-line argument:
* --on (makes SWScanner to start scanning automatically).

+ SWScanner 0.1 --> SWScanner 0.1.5 (also a private release)
--------------------------------------------------

- A huge of minor bugs fixed
- Added compatibility with ipw2200 and ipw2100 driver
- Added compatibility with orinoco driver >= 0.15rc2
- Added extra debug information to stdout. Can be disabled using the option
--disable-debug in configure script

+ SWScanner 0.1 - First private release
-------------------------------------

product-maker posixru Jan 25 2012

product-maker 14 66

File (click to download) Version Description Packagetype Architecture Downloads Date Filesize DL OCS-Install
Pling
Details
license
version
0.2.2
updated Feb 24 2006
added Jan 11 2006
downloads today
0
page views today 0
System Tags app software