You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(3) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Veli-Matti R. <vm...@wi...> - 2005-07-21 15:47:03
|
Hi, > I just want to know where is the initial firewall rule > in SAB Gateway that causes the redirection to the SAB > Gateway ? > > Simply put where the redirection happens in the code ? > The initial ruleset is defined in a "template" file named sth like sysconf_iptables_tpl, which is in /usr/local/wifinet/templates/ directory. after running the /usr/local/wifinet/scripts/updateconfig.pl the actual firewall rule file /etc/sysconfig/iptables is replaced by a new one that is based on the template file and the parameter values in /usr/local/wifinet/conf/nwsetup.conf. The new rules will become effective after restarting the firewall with /etc/init.d/iptables or the whole gateway with /usr/local/wifinet/scripts/restart_gateway.pl Regards, Veli-Matti -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.2/53 - Release Date: 20.7.2005 |
From: Fabian R. <rit...@us...> - 2005-07-21 14:50:31
|
On 21.07.2005, at 16:14, Aime wrote: > I just want to know where is the initial firewall rule > in SAB Gateway that causes the redirection to the SAB > Gateway ? > > Simply put where the redirection happens in the code ? It uses the Linux iptables firewall to do the redirect. The first rule in the firewall essentially says "redirect all traffic to http://authenticationserver:port/". After the user was authenticated, a new iptables rule will be inserted on top that lets the traffic of this user pass through. You can study the Perl script that manipulates the firewall settings, it is called "reinst_rules". Fabian |
From: Aime <akl...@ya...> - 2005-07-21 14:14:29
|
Hello List I just want to know where is the initial firewall rule in SAB Gateway that causes the redirection to the SAB Gateway ? Simply put where the redirection happens in the code ? Thanks in advance --Aimé __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Veli-Matti R. <vm...@wi...> - 2004-12-30 18:07:55
|
Hello, > I wold like to use your open source gateway, but I have some trouble > installing the app. I use a fresh rh 7.3 and the install script is > running fine. > > But afterwards, when I point to > > https://<my-ip>/ or http://<my-ip>/ > > I get a loop opening the same page all the time - it is not redirecting > to the login page. Note that any URL other than https://<my-ip>/nwadmin https://<my-ip>/mrtg will cause the browser to be redirected login portal, which is served from another host, SAB Server. I remember seeing the looping behaviour as well, but can't remember exactly which configuration error caused that to happen. What is the URL you see flashing on the browser when it loops? > My second problem is where to maintain the aaa server - is it also the > loop problem - can i log into radius with admin and maintain everything? SAB Gateway is intended to be hooked against a SAB Server, that provides both the portal and radius service for the gateway. The SAB Server has graphical UI for administering gateways, service locations and subsrcibers etc. > Thank you very much for any help - and most importent: Is there any > documentation for the software package? Documents about SAB gateway and its use can be found by registering at our opensource web site, http://extra.wificom.com/opensource Best regards, Veli-Matti Riepula |
From: Thai D. H. <td...@is...> - 2004-11-21 11:51:14
|
Dear List I know SAB-Gateway provide the functions below - AAA - Networking - Management I would like to ask if any one know about a free (or GNU licensed) software like SAB Server with following functions - Subscribers management - Self care Portal (Web pages) - Service creation and management - etc. I'm looking forward to hearing from List. Brgds Hoa |
From: Fabian R. <rit...@us...> - 2004-11-15 20:10:43
|
On Saturday 13 November 2004 06:40, Lawrence wrote: > I installed the wificom sab gateway but somehow no > password was set for the admin user (don't ask). > Is there a way to manually reset this password? I guess this is the password for the admin web site you are wondering about? It's a standard Apache password file. I don't remember the precise details, but an "slocate htaccess" (or was it dlocate?) should find it for you. Fabian |
From: Fabian R. <rit...@us...> - 2004-11-15 19:08:21
|
On Monday 15 November 2004 12:58, sw wrote: > I have download sab-ag-4.2.3.tar and I think it is only for Redhat?!? > > Is there anywhere a SAB Gatway for SuSE? The gateway is packaged for Red Hat Linux 7.3. I'm afraid you would have to invest a few days work if you wanted to install it on another Linux distro. Fabian |
From: sw <sw...@de...> - 2004-11-15 12:58:10
|
hi wlan-gateway-devel-list, I have download sab-ag-4.2.3.tar and I think it is only for Redhat?!? Is there anywhere a SAB Gatway for SuSE? thank you for answering Sabrina Winkelmann |
From: Lawrence <kh...@ya...> - 2004-11-13 06:40:44
|
HI, I installed the wificom sab gateway but somehow no password was set for the admin user (don't ask). Is there a way to manually reset this password? THanks, Laurie ___________________________________________________________ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com |
From: Veli-Matti R. <vm...@wi...> - 2004-07-28 12:07:00
|
> Hi, > > Sorry for my bad english. > > In the nwsetup.conf, there is parameters about PPTP VPN : > > ### PPTP in use ###################### > %pptp=on > %pptpun=public > %pptppw=private > > Theses parameters appears to be no yet used. There isn't any hook on the > template directory that match with these entries. > > This feature is an old feature disabled for security reason or it's a new > one not yet implemented ? Correct, at the moment those parameters are not actually used anywhere. The PPTP client feature on SAB Gateway has not yet been implemented. Best regards, Veli-Matti |
From: Veli-Matti R. <vm...@wi...> - 2004-07-28 11:46:03
|
Hello, > Seems that this place is the only one to get some kind of support. I'm > about to ask a very basic question that is apparently already answered in > the project page. But read it carefully anyway.... > I understand this project needs Linux Red Hat 7.3. > > I believe it is a MINIMUM system requirement. I just installed Linux Red > Hat 9 on a machine to test SAB GATEWAY. > Could it be the reason why I can't complete the bash build.sh command > properly ? Here's a transcript : I'm afraid that the RH7.3 is required, and with the predefined packages installed since the install.sh compares the RPM list of installed RPMs to an static list that comes with SAB gateway. If they don't match, then install fails. You can try to workaround this by disabling the RPM check or making it to compare to the list of RPMs that you have actually installed. Rgs, Veli-Matti |
From: <ro...@ro...> - 2004-07-27 13:00:17
|
Hi, Seems that this place is the only one to get some kind of support. I'm about to ask a very basic question that is apparently already answered in the project page. But read it carefully anyway.... I understand this project needs Linux Red Hat 7.3. I believe it is a MINIMUM system requirement. I just installed Linux Red Hat 9 on a machine to test SAB GATEWAY. Could it be the reason why I can't complete the bash build.sh command properly ? Here's a transcript : [root@localhost install]# bash build.sh This is build.sh at localhost.localdomain on mar jui 27 14:40:15 CEST 2004 /bin/rm -f *~ *.bak core /bin/rm -f wificom-ag.spec /bin/rm -f /bin/rm -f wificom-ag-4.2.3.tar.gz wificom-ag-4.2.3-*.rpm /bin/rm -f wificom-ag-conf-4.2.3.tar.gz /bin/rm -rf BUILD /bin/rm -rf wificom-ag-4.2.3 wificom-ag-root /bin/rm -rf wificom-ag-conf-4.2.3 wificom-ag-conf-root /bin/rm -f Makefile config.cache config.log config.status config.h [...] install -c -m 0644 VERSION wificom-ag-4.2.3 tar cvzf wificom-ag-4.2.3.tar.gz wificom-ag-4.2.3 wificom-ag-4.2.3/ wificom-ag-4.2.3/VERSION mkdir -p /root/wlan-gateway/install/BUILD rpm -bb wificom-ag.spec -bb: unknown option make: *** [wificom-ag] Erreur 1 build.sh: building --> wificom-ag <-- RPM FAILED. Exiting... Of course I could downgrade to Red Hat 7.3 (how sad...). But only if I'm told that this is the only way to make it work.I installed pretty much anything that needed to be installed under R.H. 9, but to no avail. If anyone has an idea/solution, I'd be glad to hear from it ! Cheers. R. |
From: Pierre-Emmanuel B. <pbr...@sa...> - 2004-07-13 11:27:46
|
Hi, Sorry for my bad english. In the nwsetup.conf, there is parameters about PPTP VPN : ### PPTP in use ###################### %pptp=on %pptpun=public %pptppw=private Theses parameters appears to be no yet used. There isn't any hook on the template directory that match with these entries. This feature is an old feature disabled for security reason or it's a new one not yet implemented ? Regards. Pierre-Emmanuel Brinette Network Engineer ________________________ SATXPRO 38, place des pavillons F-69007 Lyon France Tel: +33 (0) 4 72 80 82 35 GSM: +33 (0) 6 60 03 82 35 Fax: +33 (0) 4 78 72 83 94 http://www.satxpro.com |
From: Veli-Matti R. <vm...@wi...> - 2004-07-08 12:55:50
|
> Hi again Veli-Matti, > I have grabbed the files and mantained the directory structure but the > problem is that is still difficult for me to install the SAB Gateway > (too many RH7.3 checks!). > Do you have a running snapshot of a /usr/local/wifinet/ directory as > well as of the /var/www/ directory? > It would help a lot in order to understand how the SAB gateway is working. Hi, If you take the files from CVS, then you have a "running snapshot". also, /var/www/ only contains the files created by MRTG. the Gateway uses different directories under wifinet/ for HTML/CGI files. Rgs, Veli-Matti |
From: Veli-Matti R. <vm...@wi...> - 2004-07-07 10:58:14
|
> Hi, > it is me again, first of all thanks for your answer, > if it is all such a big work to port it to debian, I was thinking of > skipping the automatic instalation and trying to install my self the > necessary packages. > Is there any source code available to use once all the necessary > packages are in place? > It seems to me that all is based on perl scripts... which one > should I use? > > Sorry if my questions are too stupid. > Thanks in advance, > Saverio Hi Saverio, yes, the gateway consists purely of Perl and shell scripts, so there's no separate source code as such needed. Just grab the files, maintaining the directory structure, from the project CVS. Best regards, Veli-Matti |
From: Veli-Matti R. <vm...@wi...> - 2004-07-05 11:23:52
|
> Dear SAB WLAN Gateway Project Members, > I have downloaded the SAB Gateway and tried to install it, actually my > intentions are to install it on a Debian Linux OS. > I have seen that it is developed thinking of a RH 7.3 OS. > Can I ask you how to install and run it under a Debian Linux? > Hello, yes, SAB Gateway installation assumes a RH7.3 setup. Most of the RH-specific files are related to basic networking, such as setting the IP addresses etc. for which the SAB Gateway uses red-hat scripts. Look in the directory /usr/local/wifinet/templates/, there are all the template files which are used when generating new configuration files. In addition to "porting" the template files, the updateconfig.pl and cgi-bin scripts would need to be reviewed to see that they are valid for possibly changed file locations. Additionally, porting to another distribution would require to adapt the install.sh script to omit RH7.3 specific checks. As the installation handles RPMs the target host obviously needs to be able to handle RPMs (IIRC, Debian uses it's own package management tools). Overall, the tasks cumulate to quite a bit of change work, so probably we're talking of few days of effort rather than few hours. Rgs, Veli-Matti |
From: V-M R. <vm...@wi...> - 2004-06-10 12:16:43
|
This maintenance release of SAB Gateway has update script which has been modified. You can download the release from the SourceForge site: https://sourceforge.net/projects/wlan-gateway/ |
From: Fabian R. <rit...@us...> - 2004-06-02 13:44:23
|
The RPMs in the previous release had been corrupted by the SourceForge CVS. This release should install cleanly now. You can download the release from the SourceForge site: https://sourceforge.net/projects/wlan-gateway/ |
From: Fabian R. <rit...@us...> - 2004-05-18 14:44:15
|
Hello, We have released SAB Gateway 4.2 on SourceForge. Release 4.2 has two major changes: * All parameters are expected to be URL encoded. All scripts try to quote and escape special characters properly when they are passed through the shell. * We implemented the SAB Generic API. The old API still exists but has become obsolete. Fabian |
From: <far...@wi...> - 2004-05-14 08:23:35
|
From: V-M R. <vm...@wi...> - 2004-05-05 11:47:50
|
When the gateway 4.1.0 is upgraded to 4.1.2 then the sessionfiles and RADIUS records have naming issue. The template %locationcode value is used instead of NASID. Example below: faulty record --> alfa1.10.0.0.53#%locationcode-120.open-request. ok record --> ga0001.10.0.0.52#ws217-104.open-request The parameters locationcode and networkname were renamed to nasid and domainsuffix since 4.1.0. so some files must have left behind or not copied during the upgrade. --- Veli-Matti |
From: Fabian R. <rit...@us...> - 2004-03-30 12:45:39
|
Hi, I just uploaded SAB Gateway 4.1.2. The only change over release 4.1.1 is that the source and binary code distributions are now packaged with the GPL terms. Fabian |