Date: Thu, 03 Jan 2008 09:15:15 +0200
From: Jacques Goldberg <Jacques.Goldberg@xxxxxxx>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;=20
en-US; rv:1.8.0.12) Gecko/20071019 Red=20
Hat/1.5.0.12-0.5.el4 Thunderbird/1.5.0.12 Mnenhy/0.7.5.666
To: Alessandro Ricci <aricci_arch@xxxxxxxxxxx>
Cc: discuss@xxxxxxxxxxxxx
Subject: Re: Connection problem
Alessandro, just think.
Suppose you want to send me a real paper letter.
You can use your local post office or you can send a messenger on a
Vespa.
How can a computer decide which one to use?
Your Belkin router connects you to the internet.=20
Its settings are kept when you try to dial.
Before starting your analog modem, give the command
/sbin/route -n
which will show routing to 192.168.2.1 , your Belkin router.
Now start the analog modem and again /sbin/route -n
Now stop your analog modem
Now give the command /sbin/ifconfig
It will almost certainly show the Belkin interface as eth0 , possibly
eth1.
Assuming eth0 is correct, do /sbin/ifconfig eth0 down
Repeat /sbin/ifconfig to see that the eth block has disappeared
And now try to dial.
As you quoted it yourself, you only need the=20
analog modem when you have no LAN (usually no=20
ADSL, but could be an organisation internel LAN).
So for testing just disable the LAN interface.
Jacques
Alessandro Ricci wrote:
Hello there,
Further to the last comments by Marvin and=20
Antonio I checked the resolv.conf file, that looks as follows:
>>>
# generated by NetworkManager, do not edit!
search Belkin
nameserver 192.168.2.1
>>>
These are the settings of my home lan. I entered the network
manager and
setup a separate dialup network, but looks like I can't bypass
the
router settings. May this be the reason of my problems? If
positive how
can I get the 2 items to live together? In the=20
end I just want to undersatand if I can send a=20
fax while connected to the home lan
or, at
least, if I can choose which service to activate...
Thanks again,
Alessandro
WvDial<Notice>: Don't know what to do! Starting pppd
and hoping for the
best. WvDial<Notice>: Starting pppd at Sun Dec 30 13:04:14
2007
WvDial<Notice>: Pid of pppd: 6427 WvDial<*1>: Using
interface ppp0
WvDial<*1>: pppd: =C3=AF=C2=BF=C2=BD[06][08]=C3=88=E2=80=BA[06][08]=
30 13:04:19
2007 WvDial<*1>: The PPP daemon has died: Authentication
error.
WvDial<*1>: We failed to authenticate ourselves to the peer.
WvDial<*1>:
Maybe bad account or password? (exit code =3D 19) WvDial<*1>:
man pppd
explains pppd error codes in more detail. WvDial<Notice>: I
guess that's
it for now, exiting WvDial<Notice>: The PPP daemon has died.
(exit code
=3D 19) Alessandro, Marvin is correct in his=20
determination with your problem. Whenever we=20
get (exit code =3D 19), it means that we
failed to
authenticate ourselves to the the peer. Also it would help, if
you know
ahead of time what your ISP wants so that you can have it at hand,
i.e,
like nameservers in file /etc/resolv.conf, i used to get a bunch
of
problems to connect and as soon as I with the help of Jacques,
Marv and
others on the list, we managed to fix our=20
problem. As soon as you determine that the=20
settings of your wvdial.conf file are correct
with
username and password, then you can browse Jacques's post
install page
to get pointers to fix your problem=20
http://linmodems.technion.ac.il/post-install.html Also as soon as
you
know which nameservers your ISP uses, you can=20
place them into /etc/resolv.conf file: for=20
instance, I use the following:=20
[olivares@localhost ~]$ cat /etc/resolv.conf nameserver
66.201.0.203
nameserver 12.176.80.9 nameserver 168.215.176.2=20
http://www.awesomenet.net/support_serversettings.html Regards,
Antonio
On Jan 1, 2008 7:21 PM, Marvin Stodolsky
<marvin.stodolsky@xxxxxxxxx>
wrote: > Alessandro > > WvDial<*1>: Carrier
detected. Waiting for
prompt. > WvDial Modem<*1>: ** Ascend TNT Terminal Server
** > WvDial
Modem<*1>: System Password: > WvDial<*1>: Looks
like a password prompt.
> > This looks as if your LoginName was not sent, so the
following >
password would not be adequate. Make sure your LoginName is in
the >
setup script > we recommend working directly with wvdial,
rather than
front ends to wvdial. > Below is a typical /etc/wvdial.conf
MarvS >
> > [Dialer Defaults] > Init1 =3D ATZ > Init2 =3D ATQ0 V1
E1 S0=3D0 &C1 &D2
+FCLASS=3D0 > Modem Type =3D Analog Modem > Baud =3D 460800 >
New PPPD =3D yes >
Modem =3D /dev/modem > ISDN =3D 0 > Phone =3D 8283180110 >
Password =3D
LoginPassWord > Username =3D LoginName@xxxxxxxxxxxxxxxx > >
On
Jan 1, 2008 4:44 PM, Alessandro <aricci@xxxxxxx> wrote: >
Hello
everybody and thank you for your help. > > > > I
followed the given
instruction. Now the modem is recognized for sure. > > When
I try
dialling out everything is working, the number is dialled and >
the
carrier is there. Anyway looks like I can't complete the
procedure > >
and in the end I can't get the connection. Here below the
output of > >
WvDial from terminal and the log of GnomePPP, maybe you can help
me and
> > suggest what to check. > > > > Thanks again
for your help and happy
new year. > > > > Alessandro > > > >
(WVDIAL OUTPUT) > > WvDial<*1>:
WvDial: Internet dialer version 1.56 > > WvDial<*1>:
Initializing modem.
> > WvDial<*1>: Sending: ATZ > > WvDial
Modem<*1>: ATZ > > WvDial
Modem<*1>: OK > > WvDial<*1>: Sending: ATQ0 V1
E1 S0=3D0 &C1 &D2 +FCLASS=3D0
> > WvDial Modem<*1>: ATQ0 V1 E1 S0=3D0 &C1 &D2
+FCLASS=3D0 > > WvDial
Modem<*1>: OK > > WvDial<*1>: Modem initialized.
WvDial<*1>:
Sending: ATDT<7020001033> > > WvDial<*1>:
Waiting for carrier. > >
WvDial Modem<*1>: ATDT<7020001033> > > WvDial
Modem<*1>: CONNECT 460800
> > WvDial<*1>: Carrier detected. Waiting for
prompt. > > WvDial
Modem<*1>: ** Ascend TNT Terminal Server ** > > WvDial
Modem<*1>: System
Password: > > WvDial<*1>: Looks like a password
prompt. > > WvDial<*1>:
Sending: (password) > > WvDial Modem<*1>: System
Password: > >
WvDial<*1>: Looks like a password prompt. > >
WvDial<*1>: Sending:
(password) > > WvDial Modem<*1>: System Password: >
WvDial<*1>: Looks
like a password prompt. > > WvDial<*1>: Sending:
(password) > >
WvDial<Err>: Connected, but carrier signal lost!
Retrying... > >
WvDial<*1>: Sending: ATDT<7020001033> > >
WvDial<*1>: Waiting for
carrier. > > WvDial Modem<*1>: ATDT<7020001033>
WvDial Modem<*1>:
CONNECT 460800 > > WvDial<*1>: Carrier detected.
Waiting for prompt. >
> WvDial Modem<*1>: ** Ascend TNT Terminal Server **
WvDial
Modem<*1>: System Password: > > WvDial<*1>:
Looks like a password
prompt. > > WvDial<*1>: Sending: (password) > >
WvDial Modem<*1>: System
Password: > > WvDial<*1>: Looks like a password
prompt. > > WvDial<*1>:
Sending: (password) > > WvDial<Notice>: Don't know
what to do! Starting
pppd and hoping for the > > best. > >
WvDial<Notice>: Starting pppd at
Sun Dec 30 13:04:14 2007 > > WvDial<Notice>: Pid of
pppd: 6427 > >
WvDial<*1>: Using interface ppp0 > > WvDial<*1>:
pppd:
=C3=AF=C2=BF=C2=BD[06][08]=C3=88=E2=80=BA[06][08] > > WvDial<*1>:
=C3=AF=C2=BF=C2=BD[06][08]=C3=88=E2=80=BA[06][08] > >
WvDial<*1>: Disconnecting at Sun Dec 30 13:04:19 2007 >
WvDial<*1>:
The PPP daemon has died: Authentication error. > >
WvDial<*1>: We failed
to authenticate ourselves to the peer. > > WvDial<*1>:
Maybe bad account
or password? (exit code =3D 19) > > WvDial<*1>: man pppd
explains pppd
error codes in more detail. > > WvDial<Notice>: I
guess that's it for
now, exiting > > WvDial<Notice>: The PPP daemon has
died. (exit code =3D
19) > > > > > > (GNOMEPPP LOG) > >
/home/alessandro/.wvdial.conf<Warn>:
Ignoring malformed input line: ";Do > > NOT edit this
file by hand!" > >
WvDial<*1>: WvDial: Internet dialer version 1.56 > >
WvDial<*1>:
Initializing modem. > > WvDial<*1>: Sending: ATX3 >
WvDial Modem<*1>:
ATX3 > > WvDial Modem<*1>: OK > >
WvDial<*1>: Sending: ATQ0 V1 E1 S0=3D0
&C1 &D2 +FCLASS=3D0 > > WvDial Modem<*1>: ATQ0
V1 E1 S0=3D0 &C1 &D2
+FCLASS=3D0 > > WvDial Modem<*1>: OK > >
WvDial<*1>: Modem initialized. >
> WvDial<*1>: Sending: ATM1L1DT7020001033 > >
WvDial<*1>: Waiting for
carrier. > > WvDial Modem<*1>: ATM1L1DT7020001033 >
WvDial Modem<*1>:
CONNECT 460800 > > WvDial<*1>: Carrier detected.
Waiting for prompt. >
> WvDial Modem<*1>: ** Ascend TNT Terminal Server **
WvDial
Modem<*1>: System Password: > > WvDial<*1>:
Looks like a password
prompt. > > WvDial<*1>: Sending: (password) > >
WvDial Modem<*1>: System
Password: > > WvDial<*1>: Looks like a password
prompt. > > WvDial<*1>:
Sending: (password) > > WvDial Modem<*1>: System
Password: > >
WvDial<*1>: Looks like a password prompt. > >
WvDial<*1>: Sending:
(password) > > WvDial<Err>: Connected, but carrier
signal lost! > >
WvDial<*1>: Disconnecting at Sun Dec 30 13:23:02 2007 >
> On Fri, 2007-12-28 at 19:28 -0500, Marvin Stodolsky wrote:
Alessandro, > > > > > > For candidate modem in
PCI bus: 00:1b.0 > >
> Class 0403: 8086:284b Audio device: Intel Corporation
82801H > >
> Primary PCI_id 8086:284b > > > Subsystem
PCI_id 104d:9005
> > > has from=20
/proc/asound/card0/codec#1 > > >=20
-------------------------------------------------------- >
Codec:
Conexant ID 2c06 > > > Address: 1 > > > Vendor
Id: 0x14f12c06 > > >
----------- > > > in the 104d:9005 Susbsystem. > >
So > > > For
owners of a Dell PCs with Conexant HSF modems, a driver source
package with full speed enabled is available, but requires driver
compiling. But the Dell package may not yet be competent beyond
2.6.1 >
> > kernels > > > > > > ALternatively
From > >
http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
> download
> with 2.6.22_14_generic equivalent
to > > >
2.6.22-14-generic, your kernel version. > > > Under
Linux unpack with:
> > > $ unzip hsfmodem*.zip > > > Then
install with: > > > $ sudo
dpkg -i hsfmodem*.deb > > > Subsequently, the modem
should be found
with > > > $ sudo wvdialconf /etc/wvdial.conf > >
Edit in your
personal information with: > > > $ sudo gedit
/etc/wvdial.conf > > >
and try dialing out with: > > > $ sudo wvdial. > >
See Testing.txt
for details. > > > > > > MarvS > > >
On Dec 28, 2007 3:57 PM,
Alessandro <aricci@xxxxxxx> wrote: > > > > Hello
everybody, > > > > > >
> > Any chance to use this modem with Ubuntu? Right now I
connect to
the > > > > internet through a home LAN router.
That's OK for the DSL
but > > doesn't > > > > apply when I need an
analogic line (travelling,
fax sending...). > > > > > > > > Thanks
for your help, > > > > > > > >
Alessandro > > > > > > > > >
