Topic: ISDN4ES - no connection possible

[Wolfgang Vonderschmitt]

Hello,

I can't connect to my isp ( T-Online) with e-smith4.1.2 and Teles16.3
when I boot the e-smith, I can see:
loaded -->isdn4es = o.k.
also my clients have connection to e-smith, I can use the html-manager,
so far so good.
on second shell, I tried several commands with following results:

lsmod =
  hisax
  isdn ( hisax)
  slhc ( slip ppp-4mppe isdn )

tail -f /var/log/messages=
  e-smith diald(699) : delaying 10 seconds before clear to dial
  e-smith diald(699) : calling site 0.0.0.0
  e-smith chat(1472): abort on (busy)
  e-smith chat(1472): abort on (error)
  e-smith chat(1472): abort on (no carrier)
  e-smith chat(1472): abort on (no dialtone)
  e-smith chat(1472): abort on (invalid login)
  e-smith chat(1472): abort on (login incorrect)
  e-smith chat(1472): report (connect)
  e-smith chat(1472): expect (atz&86663)
  e-smith chat(1472): alarm
  e-smith chat(1472): failed
  e-smith chat(1472): connect script failed.

btw:
on the same pc I can use also fli4l ( one disc floppy linux router), that means my teles16.3 is o.k. with irq and io.
So I use the same settings with e-smith.
any help will be really appreciated

ciao wolfgang

[Kees]

Hi Wolfgang,

You could have a look at some of my work on this.

http://www.blokland.co.uk/Kees/docs/e-smith/debug-modem-howto.htm

But, before you get too exited, don't throw your fli4l away yet, unless you have some decent hardware running your e-smith box (> 300Mhz cpu)

The reason is that every time e-smith changes it's ip address on the external interface, lots of services are restarted, which takes a long time.
( something like 2-3 minutes on a 100Mhz box.)

During this time you do not have access to the net yet.

Using your fli4l ( I'm using a 486dx80) gets you online in .5 seconds, because it does not have to do all this extra stuff..

But, by all means, try it out, and let me know what your experiences are!

[Wolfgang Vonderschmitt]

> Hi Kees,
>
> > You could have a look at some of my work on this.
> >
> > http://www.blokland.co.uk/Kees/docs/e-smith/debug-modem-howto.htm
>
> I did, but without success.
> my problem is, I can't get any connection with e-smith....
> with fli4l no problems at all on the same machine
>
> > But, before you get too exited, don't throw your fli4l away yet, unless
> you
> > have some decent hardware running your e-smith box (> 300Mhz cpu)
>
> this for sure I won't
> every night before i go to sleep, I reboot with fli4l,
> so my kids can use the internet
>
> > The reason is that every time e-smith changes it's ip address on the
> > external interface, lots of services are restarted, which takes a long
> time.
> > ( something like 2-3 minutes on a 100Mhz box.)
>
> but first you need a positive connection...
>
> question-
> is there any tool to check my hardware (isdn-card)in e-smith
> modprobe hisax ... i know allready
> maybe I can make a manuall call with another programm, just to check,
> if my teles card will work properly or to check my irq for the card?
>
> Ciao  Wolfgang
>
>                   Diver does it deeper....

[Kees]

Hi Wolfgang:

In your first mail you wrote:

e-smith chat(1472): report (connect)
e-smith chat(1472): expect (atz&86663)
e-smith chat(1472): alarm
e-smith chat(1472): failed
e-smith chat(1472): connect script failed.

You are right, I did not look close enough to what you said..

You are right to question if the Teles is working, but If you are running fli4l on the same box, then I would think that the bios settings stay the same. ( this I assume from you saying you boot it every night for the kids...)

So atart again: I do not understand where the 'atz&86663' comes from.

This is wrong. It should only say 'atz'.
Have a look at the setup strings again.

/sbin/e-smith/config set ModemInit "&E123456S14=3"

86663 is your home-phone number ? only 5 digits ?

If so, it should never appear there.

kees

[Wolfgang Vonderschmitt]

Hi again,

/sbin/e-smith/config set ModemInit ????

I don't have such a string in my config, only 2 lines:

exec "/sbin/e-smith/db", "configuration", @ARGV;
die "Could not exec /sbin/e-smith/db";


ciao wolfgang

[NeL]

do you have a working solution now?
NeL