-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I know this would be better posted in suse-isdn, but I don't speak German... I'm using SuSE 8.0 pro on a K6 with the latest i4l updates (2002.7.31-0). My ISDN card is an ISA model (yeah, sorry), Gazel 753. The problem is the following: I have only one provider, configured through YaST2. I checked the "Automatic connection" option (loose translation, I'm using french version. It is for "dial-on-demand".) The SMPPPD server is up and running. The connection is etablished correctly if I use KInternet (i.e. manually), but the automatic part doesn't work. Is there a known bug with automatic ISDN connection? Or a trick? It did work OK with SuSE 7.3. Regards, - -- Thibaut Cousin email : cousin@in2p3.fr web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9mckuv1vqsTa1E4oRApcZAJ9HtSnmJ3P4Eux1uMzmcyQt8oNp+ACeOmyz 0KqsCn6lTrqfonu/IVJiYzk= =G6Ua -----END PGP SIGNATURE-----
On Tue, 2002-10-01 at 18:11, Thibaut Cousin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I know this would be better posted in suse-isdn, but I don't speak German... I'm using SuSE 8.0 pro on a K6 with the latest i4l updates (2002.7.31-0). My ISDN card is an ISA model (yeah, sorry), Gazel 753.
The problem is the following: I have only one provider, configured through YaST2. I checked the "Automatic connection" option (loose translation, I'm using french version. It is for "dial-on-demand".) The SMPPPD server is up and running. The connection is etablished correctly if I use KInternet (i.e. manually), but the automatic part doesn't work. Is there a known bug with automatic ISDN connection? Or a trick? It did work OK with SuSE 7.3.
Regards,
Thibaut Cousin
Bonsoir Thibaut, First, I do know some French, but this is an English list, so ... Second, the Germans (normally, at lest they are supposed to) know English (or they are that damn stoopid that they won't be able to answer your question ... *haha*), so if you don't get a good answer here, then try the SuSE-ISDN list in English ... The problem should not be with the ISA card. I have got two boxen in my two residences, both run SuSE 8.0, both run ISDN, both run Fritz!Card, just that one box has got the Fritz PCI card, the other box has got a Fritz ISA PnP card (1). OK, so far, this is just one little hint that ISA don't hurt - at least it shouldn't *haha* OK, so now let's finally go to work! Obviously YaST2 doesn't do its job correctly. This is not nice, but we can get around this. Check /etc/sysconfig/isdn/; since you only got one provider, you should have only two files in there: cfg-contr0 # that's for the card cfg-net0 # that's for the connection / provider. Edit the latter as root. Especially check this line: DIALMODE="manual" Or whatever is in there. Overwrite it with "automatic", save the file and restart ISDN, I don't remember the command right now. A reboot is overkill, but it will definitely restart ISDN:-) See what will happen then. Salut! Wolfi ============================================= mailto:wolfi_z@gmx.net (1) the reason is, I got the ISA card for 15.-Euro, used, so that's a cool price, and I could avoid buying a new card. And I do have two ISA slots in one of my boxen (the older one. The newer one has got no more ISA)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mardi 1 Octobre 2002 20:48, wolfi a écrit :
I know this would be better posted in suse-isdn, but I don't speak German... I'm using SuSE 8.0 pro on a K6 with the latest i4l updates (2002.7.31-0). My ISDN card is an ISA model (yeah, sorry), Gazel 753.
The problem is the following: I have only one provider, configured through YaST2. I checked the "Automatic connection" option (loose translation, I'm using french version. It is for "dial-on-demand".) The SMPPPD server is up and running. The connection is etablished correctly if I use KInternet (i.e. manually), but the automatic part doesn't work. Is there a known bug with automatic ISDN connection? Or a trick? It did work OK with SuSE 7.3.
First, I do know some French, but this is an English list, so ... Second, the Germans (normally, at lest they are supposed to) know English (or they are that damn stoopid that they won't be able to answer your question ... *haha*), so if you don't get a good answer here, then try the SuSE-ISDN list in English ... The problem should not be with the ISA card. I have got two boxen in my two residences, both run SuSE 8.0, both run ISDN, both run Fritz!Card, just that one box has got the Fritz PCI card, the other box has got a Fritz ISA PnP card (1). OK, so far, this is just one little hint that ISA don't hurt - at least it shouldn't *haha*
OK, so now let's finally go to work! Obviously YaST2 doesn't do its job correctly. This is not nice, but we can get around this. Check /etc/sysconfig/isdn/; since you only got one provider, you should have only two files in there:
cfg-contr0 # that's for the card cfg-net0 # that's for the connection / provider.
Edit the latter as root. Especially check this line:
DIALMODE="manual"
Or whatever is in there. Overwrite it with "automatic", save the file and restart ISDN, I don't remember the command right now. A reboot is overkill, but it will definitely restart ISDN:-) See what will happen then.
Thanks for the answer! I tried that yesterday, to no avail. The DIALMODE variable was "auto", I changed it to "automatic" just in case, but it didn't correct the problem. Of course I restarted everything before testing the change. What can I investigate next? Any idea? - -- Thibaut Cousin email : cousin@in2p3.fr web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9nApIv1vqsTa1E4oRAu3kAJ9nnjyAqiWUI/4sqbLPIRrtuxgylgCg1Yxv ine/amS06oPPqRXdwPUavVo= =M3Q8 -----END PGP SIGNATURE-----
On Thu, 2002-10-03 at 11:13, Thibaut Cousin wrote: (...)
Thanks for the answer! I tried that yesterday, to no avail. The DIALMODE variable was "auto", I changed it to "automatic" just in case, but it didn't correct the problem. (..)
OK, 'automatic' was just a guess, I don't use it that way, so maybe I was wrong there and it should be 'auto'. I use 'manual'. Anyway, this was not the cause.
What can I investigate next? Any idea?
Can you check 'dial on demand' in YaST2 ?? This is possible in SuSE 8.1, which I am running since yesterday. Wolfi ============================================= mailto:wolfi_z@gmx.net
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Jeudi 3 Octobre 2002 11:59, wolfi a écrit :
Thanks for the answer! I tried that yesterday, to no avail. The DIALMODE variable was "auto", I changed it to "automatic" just in case, but it didn't correct the problem. (..)
OK, 'automatic' was just a guess, I don't use it that way, so maybe I was wrong there and it should be 'auto'. I use 'manual'. Anyway, this was not the cause.
What can I investigate next? Any idea?
Can you check 'dial on demand' in YaST2 ?? This is possible in SuSE 8.1, which I am running since yesterday.
Yes, I did check this option. I'm using SuSE 8.0, but I should receive 8.1 very soon :)) Does anyone know anything else I could check? A log I could look at? A test I could run? Could SMPPPD prevent the automatic dialing from working? - -- Thibaut Cousin email : cousin@in2p3.fr web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9nDdbv1vqsTa1E4oRAhomAJkBulfwJ9NgbJvL9apFsfUUmwAFNQCgyEl9 NW1FC2c2OuKeD07os/vMt1w= =N4ly -----END PGP SIGNATURE-----
participants (2)
-
Thibaut Cousin
-
wolfi