2007/9/20, Tuomas Jouhten <[EMAIL PROTECTED]>:
>
> I'm quite green with debian and with linux, so that workaround was found
> simply
> by an accident..
>
> The problem was evident right after Etch installation (netinst dvd-image).
> Network manager (an icon the side panel) notified that there was
Hi,
Problems with internet connection. Neither browsers nor apt cannot access
internet right after booting up to X. After booting up there's two
pppd-processes, which need to be killed, and then only after running
"pon dsl-provider" (prints "Plugin rp-pppoe.so loaded")
internet connection works.
thanks for your help.
Somehow the 2.4.7 kernel uses /dev/ttyS4 to connect to the modem instead
of /dev/ttyS3 which is used by the 2.4.2 kernel.
Well I changed everything to point to /dev/ttyS4 and everything is
working now, again. :-)
Can anybody tell me why I have to use /dev/ttyS4 now inst
On Sunday Sep 09 18:35 Philipp Bliedung wrote:
> ** It doesn't seem like the IRQ is already used, right?
Yes! And if i make cat /proc/interrupts, i see there i no interrupt
used on my system for ppp. Your strange error messages i never had.
But i had some trouble too while compiling a 2.4.x kern
Hi,
I just compiled 2.4.7 and everything seems to work just fine - like
sound, nfs, usb, etc.
But I can't get ppp to work. Everytime I use 'pon' to connect to the
internet I get this:
Sep 9 14:22:32 laptop pppd[535]: pppd 2.4.1 started by root, uid 0
Sep 9 14:22:33 laptop chat[536]: Ca
Eric writes:
> I am running Debian 2.2, and this was working fine but stopped working
> for some reason. I am pretty sure it was working after i upgraded my
> kernel to 2.4.8.
Did you upgrade the ppp package? If not, do so. 2.4 kernels require 2.4
versions of ppp.
--
John Hasler
[EMAIL PROTECTE
Ok, when I do a 'pon', my modem dials and connects,
but as soon as it connects it disconnects. I did a 'plog' to check and see if
taht would tell me what the problem was. 'Plog' is giving me this:
asphault pppd[747]: Serial connection
established
asphault pppd[747]: Couldn't attach tty to p
Thanks for the reply John. Below are details from my log files.
pointers to what I should be reading or exploring further are most
welcome.
> Graham Williams wrote to debian-user on 22 Nov 1999 08:02:22 +1100:
Graham> I just used "apt-get dist-upgrade" to move from a slink to
Graham>
Graham writes:
> Issuing "pon" or pppd directly,...
What do you mean by "pppd directly"?
> I get (in the plog file)
> chat[...]: Can't get terminal parameters: Input/output error.
Please post the complete set of messages.
> I believe pppd is working okay, since if I mimic the modem on my
I just used "apt-get dist-upgrade" to move from a slink to a potato
distribution on my Laptop (Dell Latitude CPi D300Xt). Had a minor
problem with configuring some packages because of perl. I manually
"dpkg --install perl*" and then got apt-get going again. Almost
succeeded, failing in the end on
It sounds like you might possibly have a win modem which won't work with Linux.
I had
one of those myself (LT Win Modem). You can check out the modem HOWTO for more
info,
http://metalab.unc.edu/mdw/HOWTO/Modem-HOWTO.html
There is also a link there to a list of compatible and not so compatible
Hi,
I finally got PPP to work on prodigy, however, it only work at my
workplace. Apparently the modem I have at home doesn't work. Does anyone
know what the problem could be? Do you think that V.90 modem could cause
LCP packet to be sent in error?
Thanks,
Shawn
Torsten,
> This looks REALLY weird! Either your modem is broken or your server does not
> answer in a reasonable time. Suggestion: Try to connect without ppp using e.g.
> minicom. Report if this works and try binary file transfers using rz/sz.
It was my PAM server which wasn't answering i
On Sun, Dec 06, 1998 at 06:09:52PM +, Pere Camps wrote:
> Hi!
Hello Pere,
Hmm, nobody replied so I will make a try. Forgive me if my answer is wrong but
I am really tired (3:45 am here :)
> I used to have a very stable configuration for a PPP connection
> between two debian machines w
Hi!
I used to have a very stable configuration for a PPP connection
between two debian machines which suddenly has gone away. I'll explain
myself.
I have a machine with a 56k modem that acts as a server. I had
mgetty with autoppp enabled and pppd with "auth" and "login". The serve
>> "JE" == Joe Emenaker <[EMAIL PROTECTED]> writes:
JE> However, when I try using the ISDN through the Linux box, it fails.
JE> The ISDN TA (modem) is a 3COM ImpactIQ external.
More infos would have been more useful.
With the modem, you connect and use PAP for authenticating?
Then most likely
I've got a little linux box configured as a dial-on-demand masquerading
router for the other machines in my house. It works great. when using a
normal modem.
I got ISDN, and I've been able to use it without any problems when I use it
directly from my Windows98 machine.
However, when I try usi
Hello,
Thanks for replying. I simply trying do not spam this
list by long messages. Ok, the problem is that after upgrading to hamm on
client michine I am unable to establish reliable ppp link with server
which is running BO. At the same time everything is fine when I use
ppp wrom w95 which is co-e
What exactly is your problem ?
On 21-Oct-98 Eugene Sevinian wrote:
> Hi All,
> Up to now I did not solved this damned problem. :
> Does it worse to upgrade ppp to slink or ... downgrade it to BO (if it is
> possible)? Any idea?
>
> Thanks,
>
> Eugene Sevinian
>
> --
Hi All,
Up to now I did not solved this damned problem. :
Does it worse to upgrade ppp to slink or ... downgrade it to BO (if it is
possible)? Any idea?
Thanks,
Eugene Sevinian
CRD, YerPhI, 375036, Armenia
URL: http://crdlx5.yerphi.am/
Phone: 374-2-344873
On 19 Oct 1998 [EMAIL PROTECTED] wrote:
> > No, this didn't help. Any other idea?
>
> No, but if you send me a copy of the log you get with those options
> commented out I'll try to generate some.
I am ready to provide any info concerning this PPP.
Here is log from client side after disabl
> No, this didn't help. Any other idea?
No, but if you send me a copy of the log you get with those options
commented out I'll try to generate some.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
On 19 Oct 1998 [EMAIL PROTECTED] wrote:
> Eugene Sevinian writes:
> > /etc/ppp/options:
>
> > asyncmap 0
> > auth
> > crtscts
> > lock
> > modem
> > proxyarp
> > lcp-echo-interval 30
> > lcp-echo-failure 4
> > noipx
>
> Try commenting out lcp-echo-interval and lcp-echo-failure. If that helps,
>
Eugene Sevinian writes:
> /etc/ppp/options:
> asyncmap 0
> auth
> crtscts
> lock
> modem
> proxyarp
> lcp-echo-interval 30
> lcp-echo-failure 4
> noipx
Try commenting out lcp-echo-interval and lcp-echo-failure. If that helps,
puth them back in and experiment with different values for
lcp-echo-fa
On Sun, 11 Oct 1998, Jim Foltz wrote:
> You need to give more information about your connection to get a more
> precise reply. Try including log files, /var/log/ppp.log and use the debug
> option in the /etc/ppp/peers/provider file.
>
Hello,
Below I had tried to supply all information which mig
On Sun, 11 Oct 1998, Jim Foltz wrote:
> You need to give more information about your connection to get a more
> precise reply. Try including log files, /var/log/ppp.log and use the debug
> option in the /etc/ppp/peers/provider file.
>
Hello,
Below I had tried to supply all information which migh
Hello,
I think there was an issue with the noauth option in the
/etc/ppp/peers/provider file. It was not needed in bo, but is needed in
hamm. I think also the name option is now a priveledged option, and user is
the correct option. Check these 2 items.
You need to give more information about your
Hi all,
recently I have upgrated to hamm on my home computer
which is running also w95. After that I have got broken ppp from linux
side while everything is ok from w95 :(((. Therer where no such problems
with bo. Speaking more definitly .. it looks like connection hang very
soon at the beginnig o
>Mike Patterson writes:
>> He dials in, and pap is authenticated. Great! First problem, though, is that
>> no entries get created via route and ifconfig, so he gets stuck.
>
>You need to give pppd local and remote ip numbers, like this:
>192.168.0.1:192.168.0.23
I did that in my last attempt. I
Mike Patterson writes:
> He dials in, and pap is authenticated. Great! First problem, though, is that
> no entries get created via route and ifconfig, so he gets stuck.
You need to give pppd local and remote ip numbers, like this:
192.168.0.1:192.168.0.23
> So I manually put entires in right aft
I'm running a PPP server on my debian 1.3 box for one of my friends on a win95
machine to connect to.
He dials in, and pap is authenticated. Great! First problem, though, is that
no entries get created via route and ifconfig, so he gets stuck.
So I manually put entires in right after he logs
Sorry about the delay in responding James, we had a 'significant'
storm roll through yesterday...
I don't know the mechanism for how the authentication actually
takes place for PAP but it looks to me as though you are either
asking for or giving the 'null string' as a password for any
user at .
T
If you've already received a response, forgive me--I only receive the
digest version of the mailing list.
> On 6/5/98 1:18 AM Bill Leach wrote:
> My question would be, if Mr. Whitwell's machine is using PAP, are the
> entries in the ppp/pap-secrets file correct? AFAIK for the PAP
> authenticat
On 6/5/98 1:18 AM Bill Leach wrote:
>My question would be, if Mr. Whitwell's machine is using PAP, are the
>entries in the ppp/pap-secrets file correct? AFAIK for the PAP
>authentication to work (I don't use PAP but have used CHAP), the
>Username, password, and IP address (or address range) have t
> "JW" == James Whitwell <[EMAIL PROTECTED]> writes:
JW> discussed before. I'm using ppp-2.3.3-5 and mgetty-1.1.14-1 to run a
JW> one-modem dialup. Everything works just fine until pppd goes to verify
JW> the username/password, which always fails with "PAP authentication
JW> failure for "
Well Art don't feel too silly, what you said is essentially correct (except
for the chatscript stuff of course).
The ppp protocol does not itself have a 'host/user' concept, it is a peer to
peer protocol. In practice there typically are differences when PAP or CHAP
are involved but again the diff
Subject:
>
> > I've only just joined this list, so I don't know if this has been
> > discussed before. I'm using ppp-2.3.3-5 and mgetty-1.1.14-1 to run a
> > one-modem dialup. Everything works just fine until pppd goes to verify
> > the username/password, which always fails with "PAP authent
Mr. Whitwell just informed me that he is looking for an
answer from the *host* point of view, so one of you old-timers
will need to help him with it...sorry, I should have noticed
the "mgetty" reference. Sheesh, do I feel embarrassed! <:-)
> /silly/Art
>
> Dear All,
>
> I've only just j
Oops...forgot to change some configs. to show my new
e-mail address. I also left out something in the reply,
below! Read on.
> >
> > Dear All,
> >
> > I've only just joined this list, so I don't know if this has been
> > discussed before. I'm using ppp-2.3.3-5 and mgetty-1.1.14-1 to run
>
> Dear All,
>
> I've only just joined this list, so I don't know if this has been
> discussed before. I'm using ppp-2.3.3-5 and mgetty-1.1.14-1 to run a
> one-modem dialup. Everything works just fine until pppd goes to verify
> the username/password, which always fails with "PAP authentica
Dear All,
I've only just joined this list, so I don't know if this has been
discussed before. I'm using ppp-2.3.3-5 and mgetty-1.1.14-1 to run a
one-modem dialup. Everything works just fine until pppd goes to verify
the username/password, which always fails with "PAP authentication
failure
On 02-Sep-97 Magossa'nyi A'rpa'd wrote:
>On Tue, 2 Sep 1997, Paul Rightley wrote:
>
> [Snipped]
>
>[It is an item in the Hungarian linux lists' FAQ, so please learn
>Hungarian :)]
>It seems that the problem is really with the IDE driver disabling interrupts
>while handling the hard drive. You have
On Tue, 2 Sep 1997, Paul Rightley wrote:
> Over the weekend I tried out a new external 33.6 modem (as an upgrade to my
> old
> 14.4 internal). It didn't take me long, before I had it working with my
> Debian
> 1.3.1 box - thanks Debian. The one major problem is that - when I down/up
> load
>
Over the weekend I tried out a new external 33.6 modem (as an upgrade to my old
14.4 internal). It didn't take me long, before I had it working with my Debian
1.3.1 box - thanks Debian. The one major problem is that - when I down/up load
relatively large things (like most web pages) - the modem e
44 matches
Mail list logo
