linecontrol-users Mailing List for LineControl
Brought to you by:
sfuchs
Menu
▾
▴
linecontrol-users — LineControl user support
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
|---|
|
From: S. F. <lin...@sr...> - 2004-10-17 13:10:29
|
Hello, > sorry for the long answering time, I had a lot to do in tehe last > few days... I've been in the swiss-alps... away from any location where you have broadband access (or even telephone lines) ;). > I still have problems with the WLC2 now. > On 2 of 3 computers in my network, it works just fine. > > But on ONE particular computer, the one i work with the most, it > always connects, but most of the time it still shows > "unknown/invalid" in the status bar. doesn't matter which of the > user/password combinations i use (also those the other computers use > (on whose it works). > > In the /var/log/syslog there appear - quite normal - this line: > > Oct 15 17:53:25 localhost linesrv[1147]: 192.168.0.12:1179 > registered > > still i cant get to go in online mode or see the list of avaliable > connections... > > its not about my computer's firewall, because i also tried it when > deactivated, and i also tried several ip-addresses. > > what could be the problem? > any idea? > > and the funny thing is: sometimes it just works from the beginning > and sometimes it doesn't work at all... :S I wrote WLC2 using RAD Components distributed with Borland C++ Builder 5.0 Standard Edition. I know WLC2 has bugs itself but it seems that we might have problems between those RAD components and Windows too. As I'm not a Windows guru at all I can't help anyone having such problems. On my system it worked. If it doesn't work on your system and you know a bit C++ and have a C++ Builder at your hand, then please have a look at the source code yourself. Get it on http://linecontrol.srf.ch/ --> Download Greetings S. Fuchs |
|
From: S. F. <lin...@sr...> - 2004-10-11 11:23:13
|
Hallo Michael, Ist schick gleich ein Cc an die neue linecontrol-user Mailingliste damit das Zeug dort im Archiv ist. > Da ich einen ADSL Anschluss mit 5GB/Monat Limit habe aktiviere ich > ihn nur wenn ich ihn brauche. Dazu muss ich mich momentan immer per > ssh in my gateway einloggen. Ich w=FCrde nun gerne linesrv verwenden. .o0( "ACCEPT_KEYWORDS=3D'~x86' emerge =3Dnet-misc/linesrv-2.1.20" ) > Ich habe gelesen dass linesrv ADSL noch nicht unterst=FCtzt. Ist das=20 > noch aktuell ? Kann ich irgendwie helfen um das zu realisieren ? Ich glaube ADSL braucht gar keinen speziellen Support. Linesrv unterst=FCtzt beliebige net devs, die in /proc/net/dev (ethX, pppX, ...) erscheinen sowie gewisse ISDN spezialit=E4ten. Falls kein Device in /proc/net/dev mit der gesteuerten Verbindung in direktem Zusammenhang steht, so kann man auf "con_type file" umsteigen und den Verbindungs-Zustand =FCber eine Datei simulieren (throughput funktioniert dann nicht). Zum "W=E4hlen"/"Aufh=E4ngen" (im Falle von ADSL eben einfach Verbindungsauf-/-abbau) verwendet linesrv beliebige shell scripts... die m=FCssen einfach entsprechend geschrieben werden. Aber f=FCr die ist ohnehin jeder User selbst zust=E4ndig. Es sollte Dir also ohne weitere Umst=E4nde m=F6glich sein, irgendwas brauchbares zu bauen. Gib Bescheid, falls Du auf Probleme st=F6sst. Btw: wo steht, dass ADSL nicht unterst=FCtzt wird? Aus meiner Sicht kann linesrv mit jeder Verbindung umgehen, die f=FCr up- und downstream das gleiche device verwendet. Hat man f=FCr downstream eine Sat-Sch=FCssel und upstream ein modem, dann muss man etwas ausgefeilte Shellscripts schreiben und ein paar Restriktionen in Kauf nehmen, aber funktionieren sollte theoretisch auch sowas. ;) Gruesse Stefan Fuchs -- http://srf.ch/ |
|
From: S. F. <lin...@sr...> - 2004-10-07 16:23:26
|
Hello, > > linesrv can use libmysqlclient and libpam, so in "debian > > testing" for example you need the following packages: > > - libmysqlclient12 > > - libmysqlclient-dev > > - libpam0g > > - libpam0g-dev > > installed these packages just as you said: now ./configure states > this: > > ----------------- > shutdown support enabled > using pam for authentication > using MySQL backend for supplementary logging > ----------------- > Don't do 'make install'! > It has been generated but doesn't work as you would expect. > Read ./server/INSTALL instead. > Now go on with 'make' to compile linesrv and its tools... > > ok that looked quite nice... next step: make: and now there is > something wrong... Fine... first part succeeded. We'll try to use PAM for authentication and use mysql for logging. > mysql_backend.c: In function `sqlbe_connect': > mysql_backend.c:85: warning: implicit declaration of function > `mysql_connect' source='isdn_callerslog.c' > object='isdn_callerslog.o' libtool=no \ > depfile='.deps/isdn_callerslog.Po' > tmpdepfile='.deps/isdn_callerslog.TPo' \ depmode=gcc3 /bin/sh > ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -Wall -O2 -c > `test -f'isdn_callerslog.c' || echo './'`isdn_callerslog.c > gcc -g -Wall -O2 -lpam -lmysqlclient -o linesrv cfg.o client.o > cmd.o cmd_lcp3.o con.o debug.o execute.o external.o html_status.o > iface.o init.o ipvalidator.o isdn_watcher.o lcp3_supp.o lines.o > linesrv.o lists.o netinput.o pinger.o proc.o proc_lcp3.o proc_supp.o > times.o user_pam.o user.o user_noauth.o lcp3.o syslog_call_from.o > mysql_backend.o isdn_callerslog.o > mysql_backend.o(.text+0x1ab): In function `sqlbe_connect': > /var/lib/linesrv/server/mysql_backend.c:85: undefined reference to > `mysql_connect' > collect2: ld returned 1 exit status > make[2]: *** [linesrv] Error 1 > make[2]: Leaving directory `/var/lib/linesrv/server' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/var/lib/linesrv' > make: *** [all] Error 2 > > couldnt get the programme compiled now... :( what did i do wrong > this time? This time it seems that linesrv has a problem with your mysql.h it found. Your libmysqlclient version doesn't support the old-fashioned functions any more or they were not compiled in when your binary got created... Edit mysql_backend.c in some editor (no windows editor!! It will destroy it). Use nano, joe, 'mc -e <file>', nedit, vim, vi, ... Goto line 89, there's already a comment about our topic above that line. Remove the // from line 89 and put the same // in front of line 90. (read: comment out line 90, uncomment line 89) Try to compile linesrv, no need to run configure again. If it works, then run it (you have already a config file). Does it crash? If it runs: lucky man... tell me. If it doesn't work: learn coding C and fix it or use "./configure --disable-mysql", sorry. > > Hope that helps you... seems you have to learn a lot... ;) > > yap that helped me a lot... depends on which way u see it ;) > > im just a spoiled debian user, who has always been using precompiled > debian versions, with an included dependencies installer... :D I've been a debian user... started with SuSE, have gone to debian as it's for free and finally stepped to Gentoo as it's the most flexible distribution I've ever seen, though you need a fairly good knowledge about the stuff in /etc/. I think an installer which cares about dependencies is a must. Otherwise you would have to spend to much time collecting stuff you don't have installed yet. Even think about upgrading the whole system... ;). Using precompiled binaries is the common case. You just have to know about that stuff with the development packages which provide you the neccessary files needed for compilation and linking of other apps. Greetings S. Fuchs |
|
From: S. F. <lin...@sr...> - 2004-10-07 13:51:30
|
Hi,
> i just executed ./config once more and i got this message:
>
> -----------------
> shutdown support enabled
> using crypt for authentication (direct file access)
> -----------------
> Don't do 'make install'!
> It has been generated but doesn't work as you would expect.
> Read ./server/INSTALL instead.
> Now go on with 'make' to compile linesrv and its tools...
>
> the weird thing is, that i just installed the libpam-pwdfile
> package. i can't think of any other package that would be providing
> the PAM acces... another weird thing are those lines:
>
> checking mysql/mysql.h usability... no
> checking mysql/mysql.h presence... no
> checking for mysql/mysql.h... no
> checking mysql/errmsg.h usability... no
> checking mysql/errmsg.h presence... no
> checking for mysql/errmsg.h... no
>
> do they mean he doesnt recognize the mysql installation on my
> computer? i've got the version 4.0.21-3 installed...
You have a partial install of it. You've probably only the binaries
neccessary to run it on your system. But not the header files to
compile applications which use mysql resp. libmysqlclient in our case.
Read on if you want mysql support. If you don't want to log to a mysql
db, then you don't need mysql. Leave it as it is in this case.
> so far for my problems...
A _complete_ install of, for example, mysql consists not only of the
usual binary packe but additionaly of the mysql-dev package, which
contains .h files and similar stuff neccessary to compile and link
applications like linesrv against mysql. So if linesrv should use
mysql on your system, then the development files are needed also, not
only the libraries and programfiles of mysql.
This is not a special problem of linesrv... you need those things
always if you want to compile programs which use certain libraries.
linesrv can use libmysqlclient and libpam, so in "debian
testing" for example you need the following packages:
- libmysqlclient12
- libmysqlclient-dev
- libpam0g
- libpam0g-dev
btw: you don't need a full mysql installation, the mysqlclient
libraries should be sufficient.
> what means crypt authentication? how should i make the
> passwordfiles?
Your passwordfile is probably /etc/shadow, as long as you aren't using
any cluster environment or other special things. 'cat /etc/shadow' or
'cat /etc/passwd' should reveal lines like
username:$1$YVtjnJW.$riTSCrO1BKKy9..MyU6v8.:12698:0:10000::::
If /etc/passwd has a line like "root:x:0:0:root:/root:/bin/bash" (the
x in the 2nd field is relevant) then your password file is
/etc/shadow, which is probably the case on your system.
crypt is part of glibc, which you probably have installed...
(no, you don't have to check that... you have it installed.)
Execute "/lib/libc.so.6", you will get something like:
sci@blue sci $ /lib/libc.so.6
GNU C Library stable release version 2.3.3, by Roland McGrath et al.
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6).
Compiled on a Linux 2.4.21 system on 2004-08-28.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
linuxthreads-0.10 by Xavier Leroy
BIND-8.2.3-T5B
libthread_db work sponsored by Alpha Processor Inc
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Report bugs using the `glibcbug' script to <bu...@gn...>.
sci@blue sci $
If you're using crypt for user authentication, then you need
the following line in your linesrv.conf:
passwd_file /etc/shadow
For user authentication using PAM you don't need this line,
comment it out (default, as in
linesrv-2.1/server/config/complete_syntax/linesrv.conf).
Hope that helps you... seems you have to learn a lot... ;)
Greetings
S. Fuchs
|