From: Frank Krauss <fmfkrauss@mindspring.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Problem with "persist" on PPP 2.4.3 under Linux Kernel 2.6.9
Date: Tue, 25 Jan 2005 18:22:57 +0000 [thread overview]
Message-ID: <05012513283100.25676@sevencardstud.cable.nu> (raw)
In-Reply-To: <05011913351800.04070@sevencardstud.cable.nu>
Hello Bhaskar,
Thank you very much for telling me where this Fix goes.
I will look into trying it out on my System.
Meanwhile, just for your information, the 2.4.1 version of PPP is working
perfect with the "persist" option.
Thanks again,
Frank
=====================================
On Sun, 23 Jan 2005, Bhaskar wrote:
> Hi,
> The patch I have added is in 2.4.0. In 2.4.3 it is in tty_disestablish_ppp.
>
> -Bhaskar
> Frank Krauss wrote:
>
> >Hello Bhaskar,
> >
> >Thank you very much for the Patch.
> >
> >I had gone back to the 2.4.0 version of PPP where the "persist" option is
> >running perfect with Kernel 2.6.9.
> >
> >When I got your Code, I did some research on it.
> >Unfortunately, there is no function called "disestablish_ppp" in
> >sys-linux.c in the PPP 2.4.3 version that I have.
> >
> >The only two functions whose names are similar to this are
> >"tty_disestablish_ppp" and "generic_disestablish_ppp".
> >
> >Would you be able to tell me where you found this Patch?
> >Would you be able to give me the actual patch file, where the line numbers are
> >mentioned?
> >
> >Thank you again very much for taking an interest in my Problem.
> >
> >Yours truly,
> >
> >Frank
> >
> >=====================================
> >
> >On Sat, 22 Jan 2005, Bhaskar wrote:
> >
> >
> >>Hi,
> >>Even I had faced this problem. I found that its because of some bug in
> >>the linux kernel itself. I don't exactly know where is the problem.
> >>But I found a small patch added to ppp code which solved the problem.
> >>If you enable "debug" option and also give the logfile, you would see
> >>one error displayed saying it could not open the channel # and the
> >>channel number changes and never connects.
> >>
> >>The patch added is
> >>
> >> if (!looped && ifunit >= 0 && ioctl(ppp_dev_fd, PPPIOCDETACH) < 0) {
> >> int flags;
> >>
> >> error("Couldn't release PPP unit: %m");
> >> close(ppp_dev_fd);
> >> ppp_dev_fd = open("/dev/ppp", O_RDWR);
> >> if (ppp_dev_fd < 0)
> >> fatal("Couldn't open /dev/ppp: %m");
> >> flags = fcntl(ppp_dev_fd, F_GETFL);
> >> if (flags = -1
> >> || fcntl(ppp_dev_fd, F_SETFL, flags | O_NONBLOCK) = -1)
> >> warn("Couldn't set /dev/ppp to nonblock: %m");
> >> }
> >>
> >>in sys-linux.c file and the function name is disestablish_ppp().
> >>
> >>This should work if you are still facing the problem.
> >>
> >>-Bhaskar
> >>Frank Krauss wrote:
> >>
> >>
> >>
> >>>Hello Ankit,
> >>>
> >>>Thank you very much for your response.
> >>>
> >>>Unfortunately, in my case, I don't believe that the method you suggested is
> >>>feasable.
> >>>
> >>>My connection supports a Web/Ftp/Game Server and thus has to be connected to
> >>>the Internet and available 24/7 so that my potential clients can see my Web
> >>>page and play the Game that I offer.
> >>>
> >>>I have been running my system using the "persist" option to keep me connected to
> >>>the Internet for over a year and its worked perfectly.
> >>>
> >>>I believe that there must be some type of Bug in the "persist" area of the Code
> >>>that is going bad.
> >>>
> >>>Thank you again for your suggestion.
> >>>
> >>>Frank
> >>>
> >>>=====================================
> >>>
> >>>On Wed, 19 Jan 2005, Desai, Ankit (Export) wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>You can try and use diald option, which will try to reconnect to the
> >>>>internet on demand/use. So, even if you are offline, and there is a demand
> >>>>for internet connection, it will try to reconnect on its own.
> >>>>
> >>>>Just make sure, you configure diald correctly, it is a little bit tricky.
> >>>>
> >>>>Regards,
> >>>>Ankit
> >>>>
> >>>>-----Original Message-----
> >>>>From: Frank Krauss [mailto:fmfkrauss@mindspring.com]
> >>>>Sent: Wednesday, January 19, 2005 1:30 PM
> >>>>To: linux-ppp@vger.kernel.org
> >>>>Subject: Problem with "persist" on PPP 2.4.3 under Linux Kernel 2.6.9
> >>>>
> >>>>
> >>>>Good day,
> >>>>
> >>>>I'm having a problem that I can't seem to find any indication of a fix on
> >>>>GOOGLE for and so I'm hoping that someone on this list can point me in
> >>>>the correct direction.
> >>>>
> >>>>I'm running Linux Kernel 2.6.9 on a Pentium 4 using the Caldera
> >>>>Distribution.
> >>>>I installed PPP 2.4.3 and have been using it successfully for a couple of
> >>>>days. My problem with it is the following:
> >>>>
> >>>>I'm running a 24/7 Server and after every 12 Hour period, my I.S.P,
> >>>>which is Mindspring/Earthlink, drops my connection.
> >>>>I have the "persist" option specified to take care of this problem and so
> >>>>PPP should re-connect successfully. This worked perfect with my previous
> >>>>system using Kernel 2.4.22 and PPP 2.4.1.
> >>>>
> >>>>Unfortunatly, the "persist" option dosn't seem to be working correctly for
> >>>>me. At the moment the line gets dropped, PPP now gives me the following
> >>>>messages in my /var/log/messages file:
> >>>> tcflush failed: Input/output error
> >>>> Modem hangup
> >>>> tcsetattr: Invalid argument (line 962)
> >>>> tcsetattr: Invalid argument (line 1001)
> >>>> Exit.
> >>>>
> >>>>This causes me to have to bring up PPP again myself rather than having
> >>>>the "persist" option work as it should.
> >>>>
> >>>>This has happened each time for the last (3) re-cycle attempts with the
> >>>>exact same messages.
> >>>>
> >>>>If anyone has knowledge of a fix to correct this problem or an option
> >>>>to use, I would be glad to try them out.
> >>>>
> >>>>My Environment is:
> >>>>Computer: Pentium-4
> >>>>Distribution: Caldera 2.3
> >>>>Kernel: 2.6.9
> >>>>GCC: 3.4.3
> >>>>GLIBC: 2.3.3
> >>>>PPP: 2.4.3
> >>>>
> >>>>Any assistance that someone could give me to solve this problem
> >>>>would be greatly appreciated.
> >>>>
> >>>>Yours truly,
> >>>>
> >>>>Frank Krauss
> >>>>
> >>>>-
> >>>>To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> >>>>the body of a message to majordomo@vger.kernel.org
> >>>>More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>>>
> >>>>
> >>>>
> >>>>
> >>>-
> >>>To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> >>>the body of a message to majordomo@vger.kernel.org
> >>>More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>>
> >>>
> >>>
> >>>
> >>>
> >>-
> >>To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> >>the body of a message to majordomo@vger.kernel.org
> >>More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>
> >>
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> >
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2005-01-25 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 18:29 Problem with "persist" on PPP 2.4.3 under Linux Kernel 2.6.9 Frank Krauss
2005-01-19 18:48 ` Desai, Ankit (Export)
2005-01-20 3:35 ` Frank Krauss
2005-01-22 13:22 ` Bhaskar
2005-01-23 20:04 ` Frank Krauss
2005-01-24 4:51 ` Bhaskar
2005-01-25 18:22 ` Frank Krauss [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05012513283100.25676@sevencardstud.cable.nu \
--to=fmfkrauss@mindspring.com \
--cc=linux-ppp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).