Topic: Revisited (ISDN how-to for 4.1.1:here is it!) - A Query

[Kees Blokland]

Now we are talking sense!

I guess we have to go back to basics: I tried with rh7 over the weekend. The answers are as you might expect. RH using the modem emulation: no response
, using ipppd no problem.

So, the only proper way forward seems to be ipppd support.

kees

[Kees Blokland]

...Just got my copy of Linuxformat through the door today.
They featured another firewall thingy on their coverdisk.
I put a obsolete 170mb drive in my (soon to be_ e-smithbox) box, loaded the software ( http://www.smoothwall.org ) and indeed had a running isdn firewall in no time at all, which proves that my hardware is ok (y'never know.)

..this also means I can rebuild my original router to use a 486 instead of a 'precious' 166mhz cpu/ pci-motherboard


again, these guys are using ipppd. I'm going to try to dissect it a bit more.

have fun

kees

[Charlie Brady]

Kees Blokland wrote:
 
> again, these guys [Smoothwall] are using ipppd. I'm going to
> try to dissect it a bit more.

Let me know if you can find the source code anywhere. I can't, which is pretty unusual for GPL software!

Charlie

[Kees Blokland]

You are right Charlie, no 'real' source available. It looks like they are thinking more about a commercial way of doing business, although their iso image is freely distributable. ( my impression after looking at the site for 15 mins. If I'm wrong : apologies to the smoothwall-team

But, the main point for the exercise was to see if it works & how.

One gripe seems to be that it does not do dial on demand. ( rather important, I guess)

kees

[Klaus J. Mueller]

Hi there,

more news on this one (good news, that is):

the problem is somewhere else; all of the providers I could not
dial into do not support the X75 protocol - they require HDLC.
Using the modem emulation you start off with X75 as default.
I found out how to use HDLC in modem emulation mode:
"ATS14=3"

So, the ModemInit string should look like this:
AT&ES14=3

I've tested this with all of the listed providers. All that did not work
before, do work now (at least I got a "CONNECT" message).
I have tested the whole thing with T-Online and that worked,
so I think the others should be ok as well.

I still think ipppd is the better path to travel on. Problems like
this are easier to solve and some features (multilink) can only
be used with ipppd.

But this should at least allow more people to dial into their
favourite provider using their favourite linux distro

Regards, K.

[Ian Martin]

Thanks Klaus,

I have already tried this, thanks to a reply from the ISDN4LINUX Forum and it didn't work, athough I'm pretty sure I didn't add it on to the end of MSN command! I will give it a try again later today, if I can get five minutes to spare.

Cheers Ian

[Ian Martin]

Hi All,

The S14=3 addition to the string has certainly advanced things this end a little further, but I am still not quite there, can you clever lot cast your eye over this message log and see if you can spot the problem for me please - these modem type message are just to cryptic for me to understand!

I cannot see where my password is passed to the ISP in there, maybe that's the problem.

Many thanks for your continued help in this matter

Ian


Apr 26 14:52:07 e-smith chat[1225]: abort on (Login incorrect)
Apr 26 14:52:07 e-smith chat[1225]: report (CONNECT)
Apr 26 14:52:07 e-smith chat[1225]: send (ATZ&E0S14=3^M)
Apr 26 14:52:07 e-smith chat[1225]: expect (OK)
Apr 26 14:52:07 e-smith chat[1225]: ATZ&E0S14=3^M^M
Apr 26 14:52:07 e-smith chat[1225]: OK
Apr 26 14:52:07 e-smith chat[1225]:  -- got it
Apr 26 14:52:07 e-smith chat[1225]: send (AT^M)
Apr 26 14:52:07 e-smith chat[1225]: expect (OK)
Apr 26 14:52:07 e-smith chat[1225]: ^M
Apr 26 14:52:07 e-smith chat[1225]: AT^M^M
Apr 26 14:52:07 e-smith chat[1225]: OK
Apr 26 14:52:07 e-smith chat[1225]:  -- got it
Apr 26 14:52:07 e-smith chat[1225]: send (ATDT08089933001^M)
Apr 26 14:52:08 e-smith chat[1225]: expect (CONNECT)
Apr 26 14:52:08 e-smith chat[1225]: ^M
Apr 26 14:52:09 e-smith chat[1225]: ATDT08089933001^M^M
Apr 26 14:52:09 e-smith chat[1225]: CONNECT
Apr 26 14:52:09 e-smith chat[1225]:  -- got it
Apr 26 14:52:09 e-smith diald[545]: connector: chat:  Apr 26 14:52:09
CONNECT 64000/HDLC
Apr 26 14:52:09 e-smith diald[545]: Connected to site 0.0.0.0
Apr 26 14:52:09 e-smith diald[545]: Running pppd (pid = 1226).
Apr 26 14:52:09 e-smith diald[1226]: Running pppd:
/usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1500 name
username noauth noipdefault ipparam diald
Apr 26 14:52:09 e-smith pppd[1226]: pppd 2.4.0 started by root, uid 0
Apr 26 14:52:09 e-smith pppd[1226]: Using interface ppp0
Apr 26 14:52:09 e-smith pppd[1226]: Connect: ppp0 <--> /dev/ttyI0
Apr 26 14:52:39 e-smith pppd[1226]: LCP: timeout sending Config-Requests
Apr 26 14:52:39 e-smith pppd[1226]: Connection terminated.
Apr 26 14:52:39 e-smith pppd[1226]: Exit.
Apr 26 14:52:39 e-smith diald[545]: start sl0: SIOCSIFMTU: Invalid argument
Apr 26 14:52:39 e-smith diald[545]: stop ppp0: RTNETLINK answers: No such
process
Apr 26 14:52:39 e-smith diald[545]: stop ppp0: SIOCSIFFLAGS: No such device
or address
Apr 26 14:52:40 e-smith diald[545]: Delaying 10 seconds before clear to
dial.

[Charlie Brady]

Ian Martin wrote:

> I cannot see where my password is passed to the ISP in there,
> maybe that's the problem.

Nearly all ISP's support authentication inside the PPP session using PAP or CHAP. The days of logging in and then starting PPP using a chat script are almost over.


> Apr 26 14:52:09 e-smith diald[545]: Running pppd (pid = 1226).
> Apr 26 14:52:09 e-smith diald[1226]: Running pppd:
> /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500
> mru 1500 name
> username noauth noipdefault ipparam diald
> Apr 26 14:52:09 e-smith pppd[1226]: pppd 2.4.0 started by
> root, uid 0
> Apr 26 14:52:09 e-smith pppd[1226]: Using interface ppp0
> Apr 26 14:52:09 e-smith pppd[1226]: Connect: ppp0 <-->
> /dev/ttyI0
> Apr 26 14:52:39 e-smith pppd[1226]: LCP: timeout sending
> Config-Requests
> Apr 26 14:52:39 e-smith pppd[1226]: Connection terminated.
> Apr 26 14:52:39 e-smith pppd[1226]: Exit.

This usually means that no data is coming over the link from your ISP, for whatever reason.

Charlie

[Robert Heaton]

Hi All!

I've arrived at exactly the same place as Ian Martin has, and i'm using the same isdn card, Internal BT speedway card (AVM Fritz! PCI) anyone got anymore ideas???

[Eric Siemens]

Hi guys
very interested i followed your posts.
may one of urs could help me at my problem:
i followed the steps in k-ms HOWTO but got the wrong results )up to "depmod" there were no errors but at "modprobe hisax" there were the following:

[root@guard de]# modprobe hisax type=27 protocol=2
/lib/modules/2.2.16-22smp/misc/hisax.o: init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters
/lib/modules/2.2.16-22smp/misc/hisax.o: insmod
/lib/modules/2.2.16-22smp/misc/hisax.o failed
/lib/modules/2.2.16-22smp/misc/hisax.o: insmod hisax failed


then i tried "insmod" with these results:

[root@guard de]# insmod hisax type=27 protocol=2
Using /lib/modules/2.2.16-22smp/misc/hisax.o
/lib/modules/2.2.16-22smp/misc/hisax.o: unresolved symbol
register_isdn_Rsmp9fc70046



may anyone help me ?

regards

eric

[Kees Blokland]

Guys, I love to get to the bottom of this, but right a this moment I do have a few more urgent problems to take care of, that require my total attention:

Hopefully in a week or 2 I'll come back and continue..

kees

[Sebastian Slota]

Hallo!

I use a SUSE as server till now, and tried to install e-smith last days...
My problem is AVM Fritz PCI, so i tried your how-to.
It didn't work!!!
My problem is to change the /sbin/e-smith/console file!
after editing it is impossible to login as admin and change the configuration!!! after a while, i got a message about an error in line 1534 os so, and a new login! ( the app crashed !!!)
I used COM 4 to set the ISDN device as ttyI0, and really changed only these two lines!

Does anyone has an idea????

[Sebastian Slota]

Hallo!

I use a SUSE as server till now, and tried to install e-smith last days...
My problem is AVM Fritz PCI, so i tried your how-to.
It didn't work!!!
My problem is to change the /sbin/e-smith/console file!
after editing it is impossible to login as admin and change the configuration!!! after a while, i got a message about an error in line 1534 os so, and a new login! ( the app crashed !!!)
I used COM 4 to set the ISDN device as ttyI0, and really changed only these two lines!

Does anyone has an idea????

[Klaus J. Mueller]

Hi Sebastian,

try the latest version of my howto. It does not require you to modify the
console program (suggestion from Charlie Brady) - it gets along without.
These modifications used to be a very critical part in the howto as -
just like in your case - the slightest undesired modification might
cause the program to stop working.

Suggestion:
- if you have a copy of the original console program: restore that, follow
  the current version of my howto
- if you don't have one:
  - resinstall e-smith and follow the current version of my howto
  - write "I will always make backup copies before I modify files!" 100 times

Regards, K.

Sebastian Slota wrote:
>
> Hallo!
>
> I use a SUSE as server till now, and tried to install e-smith
> last days...
> My problem is AVM Fritz PCI, so i tried your how-to.
> It didn't work!!!
> My problem is to change the /sbin/e-smith/console file!
> after editing it is impossible to login as admin and change
> the configuration!!! after a while, i got a message about an
> error in line 1534 os so, and a new login! ( the app crashed
> !!!)
> I used COM 4 to set the ISDN device as ttyI0, and really
> changed only these two lines!
>
> Does anyone has an idea????