Topic: isdn

[NeL]

Hello,
 
I would like to know why with e-smith 4.1.2 i can't use eicon diva pci isdn card and with sme5.1.2 it work fine... Did someone can explain to me what's wrong with 4.1.2 and fine with 5.1.2? I have alway the same message on 4.1.2: sl0: SIOSIFMTU: invalid argument ...where can i change it? I would like to understand before passing on 5.1.2 ;o)
Thanks.
NeL

[Filippo Carletti]

First, 4.1.2 and 5.1.2 have totally different approaches to isdn, 4 uses async ppp (ttyIn), dealing with isdn card as a serial modem, while 5 has sync ppp (ippp).

Second, 4 and 5 uses different kernel versions and your card is probably unsupported as of version 4.

How have you configured your card on e-smith 4.1.2 ?

[Hsing-Foo]

Hi,

V 4.1.2 does NOT support passive ISDN cards natively as does 5.1.2 (experimental).

You have to make changes to the system itself.

Take a look here:

http://internet-sicherheit.net/isdn4es-howto.html

Regards,
RequestedDeletion

[NeL]

Before posting here i read this help but i currently have a MTU error message...then i try to change it but i have alway the same message??
My card is eicon diva pci : type=11 protocol=2. I feel as if this hardware is compatible ( i have no error message and when i look at dmesg i have my card ;o)

But i can't have connection. I don't know what MTU i should use to make it work fine?
If someone can help me or tell me if someone use this hardware with more succès than me ...
NeL

[guestHH]

Hi,

EICON DIVA PC should work fine (i use it now and then.. )

Try MTU 1500, MRU 1524

Regards,
guestHH

[Charlie Brady]

NeL wrote:

> I would like to know why with e-smith 4.1.2 i can't use eicon
> diva pci isdn card and with sme5.1.2 it work fine...

Many hours of work by a number of people.

Charlie

[NeL]

That's fine but i follow exactly the help documentation but ... no succès.
Could you explain what you do to have a working isdn solution? ( starting with a fresh e-smith 4.1.2, what package  you update, what package you add and what are the step of the installation of isdn solution ...) This solution work one time on my server but after a lot of tests. I can't have a working solution since a long time. Sometime i can ping external machine, but just sometime.
If you have a documentation .. mail it to me ;o)
Thanks.
NeL

[Filippo Carletti]

ISDN on e-smith 4.1.2.

 - /etc/modules.conf: options hisax type=nn protocol=2 (alias char-major-43 hisax)

 - /sbin/e-smith/config set ModemInit "&E123456S14=3" (where 123456 is your MSN)

 - /sbin/e-smith/config set DialupModemDevice /dev/ttyI0

[NeL]

on a fresh install..ok but it's not ok May be in france it doesn't work like that ...
I make a new install and i will try again...with all your help message.

NeL

[NeL]

After a lot of test i try again but i have a recurent message: sl0: SIOCSIFMTU: invalid argument ??? What is the normal MTU for a isdn connection? I try with MTU 1500 and MRU 1524.. i don't know where i can found this info..if someone know this problem i would like to have infos...
Thanks.
NeL
PS: is it possible to adapt the 5.1.2 approaches to isdn on 4.1.2 ?

[Filippo Carletti]

> PS: is it possible to adapt the 5.1.2 approaches to isdn on
> 4.1.2 ?

I strongly advise against it.
4.1.2 had  kernel 2.2.16 containing an older isdn4k.
SME 5 uses the same approach of 4.1.2, but has 2.2.19.
SME 5.1.2 uses the new approach (but can use the old) and also has 2.2.19.

[NeL]

I don't understand why it doesn't work on my server...
I would like to find someone which have a working solution..then i would like to know what exactly to do to have a working solution...with a 4.1.2 fresh install and a eicon diva pci card ;o)

NeL

[guestHH]

Hi NeL,

Filippo gave you the solution in his posts.

That's all there is concerning ISDN. Maybe a closer study of your logfiles and deamon outputs can give you more info

Maybe 'playing' with /etc/sysconfig/network-scripts/chat-ppp0 can help you.
(first make a copy of it and better yet make a custom template)

Once I had to add L0M0 at the reset command to make it work.

And maybe it's a good idea to try different ISDN providers, to eliminate the error is on your side or not....

Regards,
guestHH

[NeL]

Here is what i have in /var/log/message when i try my isdn connection: if someone can help me ;o)

Feb 11 16:36:15 e-smith diald[684]: Delaying 10 seconds before clear to dial.
Feb 11 16:36:26 e-smith diald[684]: Calling site 192.168.254.254
Feb 11 16:36:28 e-smith chat[1737]: abort on (BUSY)
Feb 11 16:36:28 e-smith chat[1737]: abort on (ERROR)
Feb 11 16:36:28 e-smith chat[1737]: abort on (NO CARRIER)
Feb 11 16:36:28 e-smith chat[1737]: abort on (NO DIALTONE)
Feb 11 16:36:28 e-smith chat[1737]: abort on (Invalid Login)
Feb 11 16:36:28 e-smith chat[1737]: abort on (Login incorrect)
Feb 11 16:36:28 e-smith chat[1737]: report (CONNECT)
Feb 11 16:36:28 e-smith chat[1737]: send (ATZ^M)
Feb 11 16:36:28 e-smith chat[1737]: expect (OK)
Feb 11 16:36:28 e-smith chat[1737]: ATZ^M^M
Feb 11 16:36:28 e-smith chat[1737]: OK
Feb 11 16:36:28 e-smith chat[1737]:  -- got it
Feb 11 16:36:28 e-smith chat[1737]: send (ATL0M0^M)
Feb 11 16:36:28 e-smith chat[1737]: expect (OK)
Feb 11 16:36:28 e-smith chat[1737]: ^M
Feb 11 16:36:28 e-smith chat[1737]: ATL0M0^M^M
Feb 11 16:36:28 e-smith chat[1737]: OK
Feb 11 16:36:28 e-smith chat[1737]:  -- got it
Feb 11 16:36:28 e-smith chat[1737]: send (ATS14=3&E0223350536&B512^M)
Feb 11 16:36:28 e-smith chat[1737]: expect (OK)
Feb 11 16:36:28 e-smith chat[1737]: ^M
Feb 11 16:36:28 e-smith chat[1737]: ATS14=3&E0223350536&B512^M^M
Feb 11 16:36:28 e-smith chat[1737]: OK
Feb 11 16:36:28 e-smith chat[1737]:  -- got it
Feb 11 16:36:28 e-smith chat[1737]: send (ATDT0860922000^M)
Feb 11 16:36:29 e-smith chat[1737]: expect (CONNECT)
Feb 11 16:36:29 e-smith chat[1737]: ^M
Feb 11 16:36:30 e-smith chat[1737]: ATDT0860922000^M^M
Feb 11 16:36:30 e-smith chat[1737]: CONNECT
Feb 11 16:36:30 e-smith chat[1737]:  -- got it
Feb 11 16:36:30 e-smith diald[684]: connector: chat:  Feb 11 16:36:30 CONNECT 64000/HDLC
Feb 11 16:36:30 e-smith diald[684]: Connected to site 192.168.254.254
Feb 11 16:36:30 e-smith diald[1738]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1500 name eric.lenezet sync noauth noipdefault ipparam diald
Feb 11 16:36:30 e-smith pppd[1738]: pppd 2.4.0 started by root, uid 0
Feb 11 16:36:30 e-smith diald[684]: Running pppd (pid = 1738).
Feb 11 16:36:30 e-smith pppd[1738]: Using interface ppp0
Feb 11 16:36:30 e-smith pppd[1738]: Connect: ppp0 <--> /dev/ttyI0
Feb 11 16:36:58 e-smith pppd[1738]: Hangup (SIGHUP)
Feb 11 16:36:58 e-smith pppd[1738]: Modem hangup
Feb 11 16:36:58 e-smith pppd[1738]: Connection terminated.
Feb 11 16:36:58 e-smith pppd[1738]: Exit.
Feb 11 16:36:58 e-smith diald[684]: start sl0: SIOCSIFMTU: Invalid argument
Feb 11 16:36:58 e-smith diald[684]: stop ppp0: RTNETLINK answers: No such process
Feb 11 16:36:59 e-smith kernel: ppp: ppp0 not active
Feb 11 16:36:59 e-smith diald[684]: stop ppp0: SIOCSIFFLAGS: No such device or address
Feb 11 16:36:59 e-smith diald[684]: Disconnected. Call duration 29 seconds.
Feb 11 16:36:59 e-smith diald[684]: IP transmitted 0 bytes and received 0 bytes.
Feb 11 16:37:00 e-smith diald[684]: Delaying 10 seconds before clear to dial.
NeL

[Filippo Carletti]

Add debug to /etc/ppp/options (temporarly).
Better not to post real phone numbers.
Then, also, try to remove sync option to pppd (/etc/diald.conf).