wifiadmin-users — Wifiadmin users list, support, suggestions, announcments, etc.

Re: [Wifiadmin-users] getnext() vs get_value()

[Christopher N. <ch...@ne...>]

On Thu, 2005-06-23 at 19:39 +0300, Thanos Panousis wrote:
> Yes what you say is true, and we are embarrased :). Try to use the 
> getnext() function....Thimios develloped get_value without knowing I had 
> made something similar.

Don't be embarrassed!  That's the strength of open source, other people
can catch these things.

I'll have my branch (I guess that's what it is) remove the get_value()
calls.  You guys can pick and choose the changes to merge in when you
are good and ready after travelling and school.

I now need to write some code to configure hostap settings.  I think
that will be my next set of changes, but things are starting to get busy
around here again.

Cheers,
Chris
-- 
Wireless Group,
McMaster University

finger.localdomain
13:14:11 up 3 days, 2:17, 1 user, load average: 0.00, 0.03, 0.02

Re: [Wifiadmin-users] getnext() vs get_value()

[Thanos P. <pan...@ce...>]

Yes what you say is true, and we are embarrased :). Try to use the 
getnext() function....Thimios develloped get_value without knowing I had 
made something similar.

Christopher Ness wrote:

>These two functions seem to do the same task.  But I found get_value()
>to be flaky under our php CGI interpreter.
>
>Which is suggested to be used, and why was a second function created?  I
>tried to look up the logs in CVS, but there isn't too much verbosity in
>the log of include/functions.php
>
>I'm looking to depreciate get_value() -- any problems with that?
>
>Cheers,
>Chris
>  
>

Re: [Wifiadmin-users] [PATCH] pre-populated iwsettings

[Thanos P. <pan...@ce...>]

Good work Christopher...

Unfortunately we can't offer a lot of help, since I'm studying hard to 
get my degree before the deadline of my Msc programme that starts in 
late August, and Thimios is going to be away for about 20 days or so on 
a trip..

So we can only post some opinions/help with design, as we don't have 
time for any coding. I hope our code isn't only spaghetti code.

[Wifiadmin-users] getnext() vs get_value()

[Christopher N. <ch...@ne...>]

These two functions seem to do the same task.  But I found get_value()
to be flaky under our php CGI interpreter.

Which is suggested to be used, and why was a second function created?  I
tried to look up the logs in CVS, but there isn't too much verbosity in
the log of include/functions.php

I'm looking to depreciate get_value() -- any problems with that?

Cheers,
Chris
-- 
Wireless Group,
McMaster University

finger.localdomain
11:58:16 up 3 days, 1:01, 1 user, load average: 0.41, 0.14, 0.10

[Wifiadmin-users] [PATCH] pre-populated iwsettings

[Christopher N. <ch...@ne...>]

Hi All

Here is a patch to pre-populate text boxes.  It also has the changes
from my previous patch included as well as some help documentation for
the settings in iwsettings.php

I plan to keep building my patches as whole chunks as it is very
difficult to branch the CVS import I have, develop and then try to merge
with my other changes fixing conflicts.

Please find the patch attached, it patches against CVS on sourceforge,
the CHANGELOG was v1.3

Changelog:
------------------------------------------------------------------------
r116 | nesscg | 2005-06-21 17:49:54 -0400 (Tue, 21 Jun 2005) | 14 lines

  * (/help/iwconfig.html)
    * Added help documentation in the form of the iwconfig man page
  * (/include/functions.php)
    * parse_iwconfig()
      * Added the encryption key to the parsed array
      * getnext() is a much better function than get_value()
    * str2html()
      * New function to print htmlspecial(trim($str))
  * (iwsettings.php)
    * Now fills form with the systems current values
    * Setting name is a link to the help file anchor
    * mode_options()
      * Builds the possible modes for the options array

------------------------------------------------------------------------
r117 | nesscg | 2005-06-22 09:34:46 -0400 (Wed, 22 Jun 2005) | 3 lines

Using tabs in the file header makes the display dependent on the
tabwidth of the text editor.

------------------------------------------------------------------------
r125 | nesscg | 2005-06-22 15:01:30 -0400 (Wed, 22 Jun 2005) | 24 lines

  * (include/functions.php)
    * parse_iwconfig()
      * Returning names without quotes using new function strip_quotes()
      * Returning data rate with units for input to `iwconfig`
      * Added new KVP to return array: enc = "encryption_key security_mode"
    * strip_quotes()
      * New function to remove char[0] and char[n] from a string
  * (iwsettings.php)
    * Rewritten to pre-populate the input boxes with the system settings
    * Debug command output is commented out
    * Removed italic current settings from the label text
    * get_iwconfig_params()
      * Now knows current system settings and the $POST results
      * Compares the two to decide if a change should be made
      * Added encryption key as a configuration option
      * Escaping all arguments sometimes causes a command to fail
      * Many ctype_allnum checks use punctuation causing them to fail
    * mode_options()
      * Added a '''value="String"''' to the options
  * (README)
    * Added a section about the need for --enable-ctype when building PHP
  * (iwstatus.php)
    * Fixed some comments that were tabbed.

------------------------------------------------------------------------
r126 | nesscg | 2005-06-22 15:09:03 -0400 (Wed, 22 Jun 2005) | 2 lines

Updated copy and paste error in a comment

------------------------------------------------------------------------


Cheers,
Chris
-- 
Wireless Group,
McMaster University

finger.localdomain
10:52:08 up 2 days, 23:55, 1 user, load average: 0.16, 0.41, 0.27

Re: [Wifiadmin-users] Wireless Settings UI

[Christopher N. <ch...@ne...>]

On Tue, 2005-06-21 at 10:01 +0300, Thanos Panousis wrote:
> The thing is that if you pre-populate the text-boxes, which looks nicer 
> indeeed, you have no way of knowing which textbox was altered by the 
> user. So in iwsettings, where I must parse the textboxes to issue a 
> `iwconfig bla blah`, I want to shorten the last command to just the 
> needed directives, since prism drivers tend to be a little buggy with 
> too many iwconfig arguements.
> 
> I'm sure there is a way to actually post only the user-changed 
> values(JS?), but I didn't decide to use one.

Why not get the data again using `get_wireless_status()` before building
the iwconfig argument list.  Now you know the current state of the
system and have the values entered by the user in the form.
 
Then compare what the system settings are to the user input fields
building an argument list for only the ones that changed?

Cheers,
Chris
-- 
Wireless Group,
McMaster University

finger.localdomain
11:16:57 up 1 day, 20 min, 1 user, load average: 0.01, 0.01, 0.00

[Wifiadmin-users] [PATCH] : Little things

[Christopher N. <ch...@ne...>]

Hi guys,

Here is the work I did yesterday it has some simple little changes and a
few new functions in it.

You probably want to remove the iwsettings.php changes in r108 as it
forces the site survey link.  That is the only thing that is particular
to our installation.

Patch file is attached.  

I'm not sure about my changes to `get_value()` as PHP and myself are
just getting acquainted again.  The function is a little flaky on our
PHP 5.0.4 CGI interpreter.  Sometimes no values are returned for a site
scan when I know `iwlist` is returning values for all cells.  

I'm not sure if the test is done on the value assignment or the outcome
of strstr() in the if statement.

Here is the change log:

[nesscg@finger wifiadmin-branch]$ svn log -rHEAD:103
------------------------------------------------------------------------
r112 | nesscg | 2005-06-21 13:09:48 -0400 (Tue, 21 Jun 2005) | 4 lines

 /iwstatus.php
  - When the logs variable is set adjusted the text and link to
    allow hiding of the log messages.

------------------------------------------------------------------------
r108 | nesscg | 2005-06-20 18:17:48 -0400 (Mon, 20 Jun 2005) | 17 lines

 include/
   (footer.php): Updated a spelling mistake
   (functions.php)
     get_value(): Test if the string was found before scanning
     get_scan_results():
       - Test if a frequency was found before trying to convert it to a channel.
       - Update string search to use equal signs (probably a HostAP change).
     get_hostap_stats():
       - Wrote a new function to get data from the wif's statistics file
     hostap_stat_short2human():
       - Parses an array to make keys more human readable from the HostAP shortform.
 (iwsettings.php):
   - Force Site Survey link to always be printed.
   - For scanning to work the HostAP driver needs these values:
         iwpriv wlan0 other_ap_policy 3
         iwpriv wlan0 ap_scan 1

------------------------------------------------------------------------
r103 | nesscg | 2005-06-20 12:32:31 -0400 (Mon, 20 Jun 2005) | 7 lines

The log link was ignoring the fact that HostAP has two devices and a
lot of the `dmesg` logging takes place as wifi*.

Made the grep command aware of the fact that it should be looking for
both:
  ''"wlan\|wifi"''

------------------------------------------------------------------------


-- 
Wireless Group,
McMaster University

finger.localdomain
13:11:57 up 1 day, 2:15, 1 user, load average: 0.12, 0.07, 0.01

Re: [Wifiadmin-users] Wireless Settings UI

[Thanos P. <pan...@ce...>]

Yes, thimios likes the second option because he implemented that one :).

The thing is that if you pre-populate the text-boxes, which looks nicer 
indeeed, you have no way of knowing which textbox was altered by the 
user. So in iwsettings, where I must parse the textboxes to issue a 
`iwconfig bla blah`, I want to shorten the last command to just the 
needed directives, since prism drivers tend to be a little buggy with 
too many iwconfig arguements.

I'm sure there is a way to actually post only the user-changed 
values(JS?), but I didn't decide to use one.

Thimios Dimopulos wrote:

>I also think the second option looks better.
>
>On Tuesday 21 June 2005 00:51, Christopher Ness wrote:
>  
>
>>Which is the prefered UI for editing settings in a text box form?
>>
>>The method used by iwsettings.php where the current value is printed
>>beside the header and the text box is left blank
>>
>> - or -
>>
>>The method used by ifsettings.php where the current value is
>>pre-populated into the text box for the user.  I think I'd be leaning to
>>this method myself.
>>
>>Cheers,
>>Chris
>>    
>>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>Wifiadmin-users mailing list
>Wif...@li...
>https://lists.sourceforge.net/lists/listinfo/wifiadmin-users
>
>
>  
>

Re: [Wifiadmin-users] Wireless Settings UI

[Thimios D. <dim...@ce...>]

I also think the second option looks better.

On Tuesday 21 June 2005 00:51, Christopher Ness wrote:
> Which is the prefered UI for editing settings in a text box form?
>
> The method used by iwsettings.php where the current value is printed
> beside the header and the text box is left blank
>
>  - or -
>
> The method used by ifsettings.php where the current value is
> pre-populated into the text box for the user.  I think I'd be leaning to
> this method myself.
>
> Cheers,
> Chris

[Wifiadmin-users] Wireless Settings UI

[Christopher N. <ch...@ne...>]

Which is the prefered UI for editing settings in a text box form?

The method used by iwsettings.php where the current value is printed
beside the header and the text box is left blank

 - or -

The method used by ifsettings.php where the current value is
pre-populated into the text box for the user.  I think I'd be leaning to
this method myself.

Cheers,
Chris
-- 
Wireless Group,
McMaster University

finger.localdomain
17:46:49 up 6:49, 1 user, load average: 0.11, 0.07, 0.02

Re: [Wifiadmin-users] wifi* displayed

[Thanos P. <pan...@ce...>]

Stop working! thimios has already posted a patch for this in the CVS! :) 
sorry, but I had forgotten all about it...

Christopher Ness wrote:
> On Fri, 2005-06-17 at 20:21 +0300, Thanos Panousis wrote:
> 
>>Yes that is the case, our variables are named in a coherent way, and 
>>that sucks. But there just a few vars there in config.php, so it fairly 
>>easy to implement a single naming convention.
> 
> 
> What format would you like to see new additions to the config file?
> 
> 
>>You are also wright with the wifi interfaces that pop up. The last 
>>version of wifiadmin was made with older versions of hostap, that did 
>>not involve showing 2 ifs per wifi card. This must be fixed of course. 
>>There is no way in the current design, to not show some ifs. All the 
>>parsing of the wireless configuration is parsed on every request. So we 
>>got to figure how to design this....
>>
>>I will post later with more ideas.
> 
> 
> Here is how I am currently looking though the code.
> 
> The pages that I see using wireless interface settings are:
> 	iwsettings.php
> 	iwstatus.php
> 	iwsecurity.php
> 	ifsettings.php - does, but separate from the above
> 
> I'm using version 0.0.4 of wifiadmin as my base, not CVS - would you
> prefer I diff against CVS?  It is easier for me to track a stable
> release instead of vendor CVS drops.
> 
> I added a check to get_wireless_status() that drops interfaces with the
> substring "wifi" in them.  It would need to be extended to look up the
> strings to exclude from the config file instead of being hard coded.
> 
> /*iwconfig output in an array with device names as keys*/
> function get_wireless_status(){
>         global $iwconfig_bin;
>         $iwconfig_output = trim(`$iwconfig_bin`);
>         $device_status_strings = explode("\n\n", $iwconfig_output);
>         foreach($device_status_strings as $device_status_string){
>                 sscanf($device_status_string,"%s ",$device);
>                 if (strstr($device_status_string, "no wireless
> extensions") !==
>                         continue;
>                 if (strstr($device, "wifi") !== false)
>                         continue;
>                 $devices_data[$device] =
> parse_iwconfig($device_status_string);
>                 $devices_data[$device]["name"] = $device;
>         }
>         return $devices_data;
> }
> 
> This covers all iw*.php pages, but not ifsettings.php which calls
> get_ethernet_status() instead which could be modified in the same way,
> therefore a function call would be nice since it's used at least twice.
> 
> Perhaps named 
>         boolean display_interface()
> 
> True would mean to display the interface, false would mean not to
> display it.
> 
> Is there a better place to put these interface checks?  No need for a
> quick reply I'm moving on to other things this afternoon.
> 
> Cheers,
> Chris

Re: [Wifiadmin-users] wifi* displayed

[Thimios D. <dim...@ce...>]

Sorry for taking so long to reply, guess i would save you some time. I have 
already fixed this fake wifi thing, take a look at 
http://wifiadmin.sourceforge.net/, it is the most recent news posted (i made 
a patch against latest version of wifiadmin). Code in the cvs has it fixed 
too.




On Friday 17 June 2005 21:00, Christopher Ness wrote:
> On Fri, 2005-06-17 at 20:21 +0300, Thanos Panousis wrote:
> > Yes that is the case, our variables are named in a coherent way, and
> > that sucks. But there just a few vars there in config.php, so it fairly
> > easy to implement a single naming convention.
>
> What format would you like to see new additions to the config file?
>
> > You are also wright with the wifi interfaces that pop up. The last
> > version of wifiadmin was made with older versions of hostap, that did
> > not involve showing 2 ifs per wifi card. This must be fixed of course.
> > There is no way in the current design, to not show some ifs. All the
> > parsing of the wireless configuration is parsed on every request. So we
> > got to figure how to design this....
> >
> > I will post later with more ideas.
>
> Here is how I am currently looking though the code.
>
> The pages that I see using wireless interface settings are:
>  iwsettings.php
>  iwstatus.php
>  iwsecurity.php
>  ifsettings.php - does, but separate from the above
>
> I'm using version 0.0.4 of wifiadmin as my base, not CVS - would you
> prefer I diff against CVS?  It is easier for me to track a stable
> release instead of vendor CVS drops.
>
> I added a check to get_wireless_status() that drops interfaces with the
> substring "wifi" in them.  It would need to be extended to look up the
> strings to exclude from the config file instead of being hard coded.
>
> /*iwconfig output in an array with device names as keys*/
> function get_wireless_status(){
>         global $iwconfig_bin;
>         $iwconfig_output = trim(`$iwconfig_bin`);
>         $device_status_strings = explode("\n\n", $iwconfig_output);
>         foreach($device_status_strings as $device_status_string){
>                 sscanf($device_status_string,"%s ",$device);
>                 if (strstr($device_status_string, "no wireless
> extensions") !==
>                         continue;
>                 if (strstr($device, "wifi") !== false)
>                         continue;
>                 $devices_data[$device] =
> parse_iwconfig($device_status_string);
>                 $devices_data[$device]["name"] = $device;
>         }
>         return $devices_data;
> }
>
> This covers all iw*.php pages, but not ifsettings.php which calls
> get_ethernet_status() instead which could be modified in the same way,
> therefore a function call would be nice since it's used at least twice.
>
> Perhaps named
>         boolean display_interface()
>
> True would mean to display the interface, false would mean not to
> display it.
>
> Is there a better place to put these interface checks?  No need for a
> quick reply I'm moving on to other things this afternoon.
>
> Cheers,
> Chris

Re: [Wifiadmin-users] wifi* displayed

[Christopher N. <ch...@ne...>]

On Fri, 2005-06-17 at 20:21 +0300, Thanos Panousis wrote:
> Yes that is the case, our variables are named in a coherent way, and 
> that sucks. But there just a few vars there in config.php, so it fairly 
> easy to implement a single naming convention.

What format would you like to see new additions to the config file?

> You are also wright with the wifi interfaces that pop up. The last 
> version of wifiadmin was made with older versions of hostap, that did 
> not involve showing 2 ifs per wifi card. This must be fixed of course. 
> There is no way in the current design, to not show some ifs. All the 
> parsing of the wireless configuration is parsed on every request. So we 
> got to figure how to design this....
> 
> I will post later with more ideas.

Here is how I am currently looking though the code.

The pages that I see using wireless interface settings are:
	iwsettings.php
	iwstatus.php
	iwsecurity.php
	ifsettings.php - does, but separate from the above

I'm using version 0.0.4 of wifiadmin as my base, not CVS - would you
prefer I diff against CVS?  It is easier for me to track a stable
release instead of vendor CVS drops.

I added a check to get_wireless_status() that drops interfaces with the
substring "wifi" in them.  It would need to be extended to look up the
strings to exclude from the config file instead of being hard coded.

/*iwconfig output in an array with device names as keys*/
function get_wireless_status(){
        global $iwconfig_bin;
        $iwconfig_output = trim(`$iwconfig_bin`);
        $device_status_strings = explode("\n\n", $iwconfig_output);
        foreach($device_status_strings as $device_status_string){
                sscanf($device_status_string,"%s ",$device);
                if (strstr($device_status_string, "no wireless
extensions") !==
                        continue;
                if (strstr($device, "wifi") !== false)
                        continue;
                $devices_data[$device] =
parse_iwconfig($device_status_string);
                $devices_data[$device]["name"] = $device;
        }
        return $devices_data;
}

This covers all iw*.php pages, but not ifsettings.php which calls
get_ethernet_status() instead which could be modified in the same way,
therefore a function call would be nice since it's used at least twice.

Perhaps named 
        boolean display_interface()

True would mean to display the interface, false would mean not to
display it.

Is there a better place to put these interface checks?  No need for a
quick reply I'm moving on to other things this afternoon.

Cheers,
Chris
-- 
Wireless Group,
McMaster University

finger.localdomain
13:24:13 up 1 day, 21:48, 2 users, load average: 0.01, 0.02, 0.00

Re: [Wifiadmin-users] wifi* displayed

[Thanos P. <pan...@ce...>]

Yes that is the case, our variables are named in a coherent way, and 
that sucks. But there just a few vars there in config.php, so it fairly 
easy to implement a single naming convention.

You are also wright with the wifi interfaces that pop up. The last 
version of wifiadmin was made with older versions of hostap, that did 
not involve showing 2 ifs per wifi card. This must be fixed of course. 
There is no way in the current design, to not show some ifs. All the 
parsing of the wireless configuration is parsed on every request. So we 
got to figure how to design this....

I will post later with more ideas.

Christopher Ness wrote:

>Is there a way to ignore the wifi* interfaces when using HostAP?  I know
>why wifiadmin displays everything in `iwconfig` but it would be nice to
>have some interfaces not be output.
>
>I took a look though the config.php file and did not see any filtering
>variables.
>
>Would this be a feature to add that other users would like to see?
>
>It's annoying how wifi0 is the default display when I really want to see
>wlan0.  ;)
>
>The config file could hold a variable like:
>
>$IGNORE_INTERFACES_REGEXP = "wifi*"
>
>What is the standard for using config variables?  Some seem to be all
>uppercase while others are lower case just like variables.
>
>Cheers,
>Chris
>  
>

[Wifiadmin-users] wifi* displayed

[Christopher N. <ch...@ne...>]

Is there a way to ignore the wifi* interfaces when using HostAP?  I know
why wifiadmin displays everything in `iwconfig` but it would be nice to
have some interfaces not be output.

I took a look though the config.php file and did not see any filtering
variables.

Would this be a feature to add that other users would like to see?

It's annoying how wifi0 is the default display when I really want to see
wlan0.  ;)

The config file could hold a variable like:

$IGNORE_INTERFACES_REGEXP = "wifi*"

What is the standard for using config variables?  Some seem to be all
uppercase while others are lower case just like variables.

Cheers,
Chris
-- 
Wireless Group,
McMaster University

finger.localdomain
12:02:54 up 1 day, 20:27, 2 users, load average: 0.12, 0.22, 0.13

Re: [Wifiadmin-users] Stripping WifiAdmin Down

[Christopher N. <ch...@ne...>]

On Thu, 2005-06-16 at 16:13 +0300, Thanos Panousis wrote:
> Kinda like using mysql in proprietory code/sites.

Excellent, I have been designing a strong interface between the two
objects so that we can use them separately.  They are command line
programs like `iwconfig` and Wifiadmin gathers the output for display.

Could McMasters Wireless Group ask for limited rights as suggested by
section 4 of the GPL to explicitly allow us to execute proprietary
programs with WifiAdmin?  This would likely make my supervisors sleep a
little better.

My understanding of the GPL is very basic, but an explicit "Yes - you
can do that." would be nice.

> May I ask what do those proprietary programmes do?

Absolutely.  The programs are currently part of some research to test
and modify a wireless mesh for dynamic configurations.  Sounds fancy,
eh?  :)  But they will likely be based on network traffic in the mesh
and a few other degrees of freedom.

Thanks for the great code base!  
I just wanted to make sure the project developers were aware what we are
working on so that if we decide to _eventually_ create a product out of
the derivative work we will still be in good standing.

Cheers,
Chris
-- 
Wireless Group,
McMaster University

finger.localdomain
11:34:48 up 19:59, 1 user, load average: 0.04, 0.01, 0.00

Re: [Wifiadmin-users] Stripping WifiAdmin Down

[Thanos P. <pan...@ce...>]

[Wifiadmin-users] Stripping WifiAdmin Down

[Christopher N. <ch...@ne...>]

Hi there.

We are looking at using wifiadmin as the basis for a wireless mesh web
configuration.

We are planning on stripping out the user configuration code and perhaps
some of the usage code.  Then we'd like to add some hooks to proprietary
programs we have written to configure the nodes of the mesh.

Is this a valid use of the GPL if we provide the source code for our
changes to wifiadmin only but keep our private programs proprietary?

Cheers,
Chris
-- 
Wireless Group,
McMaster University

finger.localdomain
15:53:43 up 18 min, 1 user, load average: 0.12, 0.36, 0.25

[Wifiadmin-users] install

[rubens.andrade - B. <rub...@bo...>]

Wifiadmin

not >>apache >>.php

HElp for install ???

Rubens Andrade

Re: [Wifiadmin-users] firewall and bridge

[Giorgio D. <gio...@gi...>]

Hello Thimios,

thanks for your answer. You are right, I already know and use Webmin on one 
of my server (which is not a wireless node) but still it lacks a module to 
administer a wireless card, pcmcia or miniPCI and a module to manage a 
bridge. As you know, better than me, a real sysadmin does not need these 
frills and drills but still there is many people who would like things a 
bit easier. Well, I dont want to re-invent the wheel and you are right to 
say that "before wifiadmin there was nothing for a hostap based access 
point doing signal/noise graphs, access list management and associated 
clients listing".
I was just asking if in your mind there are new features in the agenda or 
not. I know that it's very difficult to work on a project as hobbyst for 
free due to lack of time. I appreciate a lot your job. I will follow very 
closed this mailing list.
Cheers

Giorgio

>Hello Giorgio
>
>Thanks for praising our little project. When we started wifiadmin, we had the
>access point node in mind. There are many, and in some cases better coded,
>web interfaces for things like firewall management and even general system
>administration (check out webmin), but, to my knowledge, before wifiadmin,
>there was nothing for a hostap based access point doing signal/noise graphs,
>access list management and associated clients listing. And of course there is
>m0n0wall, which is a whole bsd distribution, and not just a web interface
>suitable for any linux distribution.
>
>Both me and Thanos haven't touched the code for quite a long time, mainly due
>to lack of time. If you or anyone else is interested in breathing some fresh
>air, even by changing the initial purpose of the project a bit, you are most
>welcomed.
>
>
>On Wednesday 25 May 2005 23:05, Gio Ducci wrote:
> > Hi to all,
> >
> > I'm new to this mailing list and I'm actually using a "pebble" like
> > distribution called "voyage" ( http://voyage.hk) based on Sarge Debian on a
> > WRAP board (www.pcengines.ch) as WIFI access point, firewall, captive
> > portal etc...as I need a web administration interface I was googling on
> > internet and I found WIFIAdmin which is very nice, congratulations for the
> > job.
> > I tried once M0N0wall (www.m0n0.ch/wall) and I'm wondering if wifiadmin
> > could in the future include some (not all ) of the features included in the
> > M0N0wall's web interface as i.e. firewall rules and bridging. As I'm not
> > very good with PHP programming unfortunately cannot help programming but I
> > read in the mailing list archives that Rob Flickenger hacked a little bit
> > the code inserting new features for the "metrix" distro. Do you think to
> > include these hacks in the next release?
> > Cheers
> >
> > Giorgio
> >
> >
> > Giorgio Ducci
> >
> > Villa 38-26, rue D. Ignatieff
> > lot. CPS-Receiving
> > 98800 Noumea
> > New Caledonia
> >
> > Tel.:+687-253084
> > GSM.:+687-782650
> >
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
> > online with coworkers and clients while avoiding the high cost of travel
> > and communications. There is no equipment to buy and you can meet as often
> > as you want. Try it
> > free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
> > _______________________________________________
> > Wifiadmin-users mailing list
> > Wif...@li...
> > https://lists.sourceforge.net/lists/listinfo/wifiadmin-users
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
>online with coworkers and clients while avoiding the high cost of travel and
>communications. There is no equipment to buy and you can meet as often as
>you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
>_______________________________________________
>Wifiadmin-users mailing list
>Wif...@li...
>https://lists.sourceforge.net/lists/listinfo/wifiadmin-users

Re: [Wifiadmin-users] firewall and bridge

[Thimios D. <dim...@ce...>]

Hello Giorgio

Thanks for praising our little project. When we started wifiadmin, we had the 
access point node in mind. There are many, and in some cases better coded, 
web interfaces for things like firewall management and even general system 
administration (check out webmin), but, to my knowledge, before wifiadmin,  
there was nothing for a hostap based access point doing signal/noise graphs, 
access list management and associated clients listing. And of course there is 
m0n0wall, which is a whole bsd distribution, and not just a web interface 
suitable for any linux distribution.

Both me and Thanos haven't touched the code for quite a long time, mainly due 
to lack of time. If you or anyone else is interested in breathing some fresh 
air, even by changing the initial purpose of the project a bit, you are most 
welcomed. 


On Wednesday 25 May 2005 23:05, Gio Ducci wrote:
> Hi to all,
>
> I'm new to this mailing list and I'm actually using a "pebble" like
> distribution called "voyage" ( http://voyage.hk) based on Sarge Debian on a
> WRAP board (www.pcengines.ch) as WIFI access point, firewall, captive
> portal etc...as I need a web administration interface I was googling on
> internet and I found WIFIAdmin which is very nice, congratulations for the
> job.
> I tried once M0N0wall (www.m0n0.ch/wall) and I'm wondering if wifiadmin
> could in the future include some (not all ) of the features included in the
> M0N0wall's web interface as i.e. firewall rules and bridging. As I'm not
> very good with PHP programming unfortunately cannot help programming but I
> read in the mailing list archives that Rob Flickenger hacked a little bit
> the code inserting new features for the "metrix" distro. Do you think to
> include these hacks in the next release?
> Cheers
>
> Giorgio
>
>
> Giorgio Ducci
>
> Villa 38-26, rue D. Ignatieff
> lot. CPS-Receiving
> 98800 Noumea
> New Caledonia
>
> Tel.:+687-253084
> GSM.:+687-782650
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
> online with coworkers and clients while avoiding the high cost of travel
> and communications. There is no equipment to buy and you can meet as often
> as you want. Try it
> free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
> _______________________________________________
> Wifiadmin-users mailing list
> Wif...@li...
> https://lists.sourceforge.net/lists/listinfo/wifiadmin-users

[Wifiadmin-users] firewall and bridge

[Gio D. <gio...@gi...>]

Hi to all,

I'm new to this mailing list and I'm actually using a "pebble" like 
distribution called "voyage" ( http://voyage.hk) based on Sarge Debian on a 
WRAP board (www.pcengines.ch) as WIFI access point, firewall, captive 
portal etc...as I need a web administration interface I was googling on 
internet and I found WIFIAdmin which is very nice, congratulations for the 
job.
I tried once M0N0wall (www.m0n0.ch/wall) and I'm wondering if wifiadmin 
could in the future include some (not all ) of the features included in the 
M0N0wall's web interface as i.e. firewall rules and bridging. As I'm not 
very good with PHP programming unfortunately cannot help programming but I 
read in the mailing list archives that Rob Flickenger hacked a little bit 
the code inserting new features for the "metrix" distro. Do you think to 
include these hacks in the next release?
Cheers

Giorgio


Giorgio Ducci

Villa 38-26, rue D. Ignatieff
lot. CPS-Receiving
98800 Noumea
New Caledonia

Tel.:+687-253084
GSM.:+687-782650  

[Wifiadmin-users] dhcp and WiCCP

[Steve W. <st...@me...>]

Hello,

can I run dhcpd on my Linux hostap+wiccpm.o AccessPoint to issue client IPs to
WiCCP slaves ?

I gave it a brief test and it didnt work immeditely so I am wondering if it is
possible.


kinds regards,
Steve

Re: [Wifiadmin-users] PHP errors in debian

[Sebastian O. <ker...@gm...>]

Now its working

thanks



Am Sonntag, den 13.03.2005, 02:42 +0200 schrieb Thimios Dimopulos:
> So, Sebastian gave me a user account to investigate this. I am posting 
> here, since more people might want to see this.
> It is most probably a problem with your sudo configuration. It seems 
> that the user www-data can't run "sudo /sbin/iwconfig"
> 
> to see if this is the case, create a file called test.php in your 
> wifiadmin directory, with the following content:
> 
> <?php
>     include( "include/functions.php");
> 
>     //this just runs iwconfig, and prints it's output, and the return code
>     print( system("sudo /sbin/iwconfig", $return_value));
>     echo("\n $return_value \n");
> 
>     //the get_wireless_status function, parses the output of iwconfig, 
> and returns it in an array
>     print_r(get_wireless_status());
> ?>
> 
> then become www-data, by running:
> 
> su - www-data
> 
> and now try to execute the above script, running
> 
> php test.php
> 
> if you don't get the correct output (which is the ouput of iwconfig, 
> followed by a 0, followed by the pretty-print of the corresponding 
> array), check your /etc/sudoers file. Mine, looks like this:
> 
> # Cmnd alias specification
> Cmnd_Alias      WIFIADMIN = /sbin/iwconfig, /sbin/ifconfig, 
> /sbin/iwlist, /sbin/iwpriv,  /sbin/route, /usr/bin/host, /usr/sbin/arp
> 
> 
> # User privilege specification
> root    ALL=(ALL) ALL
> www-data ALL=(ALL) NOPASSWD: WIFIADMIN
> 
> 
> hope this helps.
> 
> 
> Thimios Dimopulos wrote:
> 
> > There probably is a bug, concerning the way wifiadmin parses the 
> > output of your wireless tools. Could you give me a temporar user 
> > acount on your machine to check it out?
> >
> >
> >
> >
> >
> >
> > Sebastian Ortwein wrote:
> >
> >> Am Donnerstag, den 10.03.2005, 19:26 +0200 schrieb Thimios Dimopulos:
> >>  
> >>
> >>> Sebastian Ortwein wrote:
> >>>
> >>>   
> >>>
> >>>> Hey
> >>>>
> >>>> I get following errors with my Browser in wifiadmin
> >>>> in wireless status
> >>>>
> >>>> Notice: Undefined variable: current in /var/www/wifiadmin/iwstatus.php
> >>>> on line 106
> >>>>
> >>>> Notice: Undefined variable: current in /var/www/wifiadmin/iwstatus.php
> >>>> on line 330
> >>>>
> >>>> status
> >>>> This device\'s mode is not supported.
> >>>>
> >>>>
> >>>> Notice: Undefined variable: current in /var/www/wifiadmin/iwstatus.php
> >>>> on line 345
> >>>>
> >>>> ___________________________________________
> >>>>
> >>>> in wireless settings
> >>>>
> >>>> Wireless Settings
> >>>>
> >>>> Notice: Undefined variable: current in 
> >>>> /var/www/wifiadmin/iwsettings.php
> >>>> on line 200
> >>>>
> >>>> Current settings for device
> >>>> ___________________________________________
> >>>>
> >>>> I used today CVS sources and i try to get it running under debian with
> >>>> apache 1.3 and php4. I dont't know where is my problem I have 
> >>>> installed
> >>>> php4-cli but I don't know how to check it.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>     
> >>>
> >>> Please provide more details. Post the output of the following:
> >>>
> >>> iwconfig --version
> >>>   
> >>
> >>
> >> iwconfig  Wireless-Tools version 27
> >>          Compatible with Wireless Extension v11 to v17.
> >>
> >> Kernel    Currently compiled with Wireless Extension v16.
> >>
> >> eth2      Recommend Wireless Extension v16 or later,
> >>          Currently compiled with Wireless Extension v16.
> >>
> >>  
> >>
> >>> iwconfig
> >>>   
> >>
> >>
> >> lo        no wireless extensions.
> >>
> >> eth0      no wireless extensions.
> >>
> >> eth1      no wireless extensions.
> >>
> >> eth2      IEEE 802.11b/g  Mode:Managed  Frequency:2.422GHz
> >>          Access Point: 00:00:00:00:00:00   Bit Rate:0kb/s   Tx-Power=31
> >> dBm
> >>          Sensitivity=20/200
> >>          Retry min limit:8   RTS thr:2347 B   Fragment thr:2346 B
> >>          Encryption key:off
> >>          Link Quality:33  Signal level:0  Noise level:19
> >>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >>          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> >>
> >> ppp0      no wireless extensions.
> >>
> >>  
> >>
> >>> ifconfig
> >>>
> >>>   
> >>
> >> eth0      Link encap:Ethernet  HWaddr 00:50:FC:39:CD:F6
> >>          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
> >>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >>          RX packets:761544 errors:0 dropped:0 overruns:0 frame:0
> >>          TX packets:643074 errors:0 dropped:0 overruns:1 carrier:0
> >>          collisions:0 txqueuelen:1000
> >>          RX bytes:675720758 (644.4 MiB)  TX bytes:95344004 (90.9 MiB)
> >>          Interrupt:12
> >>
> >> eth1      Link encap:Ethernet  HWaddr 00:04:75:9D:5D:62
> >>          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
> >>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >>          RX packets:1910750 errors:0 dropped:0 overruns:2 frame:0
> >>          TX packets:2343936 errors:0 dropped:0 overruns:0 carrier:0
> >>          collisions:0 txqueuelen:1000
> >>          RX bytes:805944616 (768.6 MiB)  TX bytes:2692199645 (2.5 GiB)
> >>          Interrupt:10 Base address:0xb000
> >>
> >> eth2      Link encap:Ethernet  HWaddr 00:01:36:07:11:8C
> >>          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
> >>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >>          TX packets:185 errors:0 dropped:0 overruns:0 carrier:0
> >>          collisions:0 txqueuelen:1000
> >>          RX bytes:0 (0.0 b)  TX bytes:39463 (38.5 KiB)
> >>          Interrupt:12
> >>
> >> lo        Link encap:Local Loopback
> >>          inet addr:127.0.0.1  Mask:255.0.0.0
> >>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >>          RX packets:15140 errors:0 dropped:0 overruns:0 frame:0
> >>          TX packets:15140 errors:0 dropped:0 overruns:0 carrier:0
> >>          collisions:0 txqueuelen:0
> >>          RX bytes:1581832 (1.5 MiB)  TX bytes:1581832 (1.5 MiB)
> >>
> >> ppp0      Link encap:Point-to-Point Protocol
> >>          inet addr:85.74.8.70  P-t-P:62.104.190.40
> >> Mask:255.255.255.255
> >>          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1454  Metric:1
> >>          RX packets:760936 errors:0 dropped:0 overruns:0 frame:0
> >>          TX packets:642285 errors:0 dropped:0 overruns:0 carrier:0
> >>          collisions:0 txqueuelen:3
> >>          RX bytes:658830010 (628.3 MiB)  TX bytes:81125850 (77.3 MiB)
> >>
> >>
> >>
> >>  
> >>
> >>> if you are using the hostap driver, also post the output of
> >>>
> >>> ls -lhR /proc/net/hostap/
> >>>   
> >>
> >>
> >> i have no hostap driver
> >>  
> >>
> >>
> >> I hope it help. It is the first time I try a wireless connection in
> >> Linux. I will use your program for a wireless-linux-router. I use a old
> >> debian woody so it can be that same programs are outdated with your
> >> webinterface.
> >>
> >> Thanks for the help
> >>  
> >>
> >
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > Wifiadmin-users mailing list
> > Wif...@li...
> > https://lists.sourceforge.net/lists/listinfo/wifiadmin-users
> >
> >
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Wifiadmin-users mailing list
> Wif...@li...
> https://lists.sourceforge.net/lists/listinfo/wifiadmin-users
> 
-- 
Sebastian Ortwein <ker...@gm...>

Re: [Wifiadmin-users] PHP errors in debian

[Thimios D. <dim...@ce...>]

So, Sebastian gave me a user account to investigate this. I am posting 
here, since more people might want to see this.
It is most probably a problem with your sudo configuration. It seems 
that the user www-data can't run "sudo /sbin/iwconfig"

to see if this is the case, create a file called test.php in your 
wifiadmin directory, with the following content:

<?php
    include( "include/functions.php");

    //this just runs iwconfig, and prints it's output, and the return code
    print( system("sudo /sbin/iwconfig", $return_value));
    echo("\n $return_value \n");

    //the get_wireless_status function, parses the output of iwconfig, 
and returns it in an array
    print_r(get_wireless_status());
?>

then become www-data, by running:

su - www-data

and now try to execute the above script, running

php test.php

if you don't get the correct output (which is the ouput of iwconfig, 
followed by a 0, followed by the pretty-print of the corresponding 
array), check your /etc/sudoers file. Mine, looks like this:

# Cmnd alias specification
Cmnd_Alias      WIFIADMIN = /sbin/iwconfig, /sbin/ifconfig, 
/sbin/iwlist, /sbin/iwpriv,  /sbin/route, /usr/bin/host, /usr/sbin/arp


# User privilege specification
root    ALL=(ALL) ALL
www-data ALL=(ALL) NOPASSWD: WIFIADMIN


hope this helps.


Thimios Dimopulos wrote:

> There probably is a bug, concerning the way wifiadmin parses the 
> output of your wireless tools. Could you give me a temporar user 
> acount on your machine to check it out?
>
>
>
>
>
>
> Sebastian Ortwein wrote:
>
>> Am Donnerstag, den 10.03.2005, 19:26 +0200 schrieb Thimios Dimopulos:
>>  
>>
>>> Sebastian Ortwein wrote:
>>>
>>>   
>>>
>>>> Hey
>>>>
>>>> I get following errors with my Browser in wifiadmin
>>>> in wireless status
>>>>
>>>> Notice: Undefined variable: current in /var/www/wifiadmin/iwstatus.php
>>>> on line 106
>>>>
>>>> Notice: Undefined variable: current in /var/www/wifiadmin/iwstatus.php
>>>> on line 330
>>>>
>>>> status
>>>> This device\'s mode is not supported.
>>>>
>>>>
>>>> Notice: Undefined variable: current in /var/www/wifiadmin/iwstatus.php
>>>> on line 345
>>>>
>>>> ___________________________________________
>>>>
>>>> in wireless settings
>>>>
>>>> Wireless Settings
>>>>
>>>> Notice: Undefined variable: current in 
>>>> /var/www/wifiadmin/iwsettings.php
>>>> on line 200
>>>>
>>>> Current settings for device
>>>> ___________________________________________
>>>>
>>>> I used today CVS sources and i try to get it running under debian with
>>>> apache 1.3 and php4. I dont't know where is my problem I have 
>>>> installed
>>>> php4-cli but I don't know how to check it.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>     
>>>
>>> Please provide more details. Post the output of the following:
>>>
>>> iwconfig --version
>>>   
>>
>>
>> iwconfig  Wireless-Tools version 27
>>          Compatible with Wireless Extension v11 to v17.
>>
>> Kernel    Currently compiled with Wireless Extension v16.
>>
>> eth2      Recommend Wireless Extension v16 or later,
>>          Currently compiled with Wireless Extension v16.
>>
>>  
>>
>>> iwconfig
>>>   
>>
>>
>> lo        no wireless extensions.
>>
>> eth0      no wireless extensions.
>>
>> eth1      no wireless extensions.
>>
>> eth2      IEEE 802.11b/g  Mode:Managed  Frequency:2.422GHz
>>          Access Point: 00:00:00:00:00:00   Bit Rate:0kb/s   Tx-Power=31
>> dBm
>>          Sensitivity=20/200
>>          Retry min limit:8   RTS thr:2347 B   Fragment thr:2346 B
>>          Encryption key:off
>>          Link Quality:33  Signal level:0  Noise level:19
>>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>>          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>>
>> ppp0      no wireless extensions.
>>
>>  
>>
>>> ifconfig
>>>
>>>   
>>
>> eth0      Link encap:Ethernet  HWaddr 00:50:FC:39:CD:F6
>>          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:761544 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:643074 errors:0 dropped:0 overruns:1 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:675720758 (644.4 MiB)  TX bytes:95344004 (90.9 MiB)
>>          Interrupt:12
>>
>> eth1      Link encap:Ethernet  HWaddr 00:04:75:9D:5D:62
>>          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:1910750 errors:0 dropped:0 overruns:2 frame:0
>>          TX packets:2343936 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:805944616 (768.6 MiB)  TX bytes:2692199645 (2.5 GiB)
>>          Interrupt:10 Base address:0xb000
>>
>> eth2      Link encap:Ethernet  HWaddr 00:01:36:07:11:8C
>>          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:185 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:0 (0.0 b)  TX bytes:39463 (38.5 KiB)
>>          Interrupt:12
>>
>> lo        Link encap:Local Loopback
>>          inet addr:127.0.0.1  Mask:255.0.0.0
>>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>          RX packets:15140 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:15140 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:0
>>          RX bytes:1581832 (1.5 MiB)  TX bytes:1581832 (1.5 MiB)
>>
>> ppp0      Link encap:Point-to-Point Protocol
>>          inet addr:85.74.8.70  P-t-P:62.104.190.40
>> Mask:255.255.255.255
>>          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1454  Metric:1
>>          RX packets:760936 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:642285 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:3
>>          RX bytes:658830010 (628.3 MiB)  TX bytes:81125850 (77.3 MiB)
>>
>>
>>
>>  
>>
>>> if you are using the hostap driver, also post the output of
>>>
>>> ls -lhR /proc/net/hostap/
>>>   
>>
>>
>> i have no hostap driver
>>  
>>
>>
>> I hope it help. It is the first time I try a wireless connection in
>> Linux. I will use your program for a wireless-linux-router. I use a old
>> debian woody so it can be that same programs are outdated with your
>> webinterface.
>>
>> Thanks for the help
>>  
>>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Wifiadmin-users mailing list
> Wif...@li...
> https://lists.sourceforge.net/lists/listinfo/wifiadmin-users
>
>