Re: 2.4.9 ppp woes
Matt Chatterley wrote: However, when I run PPPD (I've applied the PPPoATM patches, and compiled = a patched version of PPPD 2.4.0), it complains that PPP_GENERIC is not = installed in my kernel. It is. I've selected, infact, every single PPP = option (as a test), and have tried both with them as modules (and then = physically loaded them by hand), and directly in the kernel. PPPD 2.4.0 has some bugs. Try using 2.4.1 or higher. Maybe it might help. Paolo Falcone __ www.edsamail.com
2.4.9 ppp woes
Hi all, I've just installed Woody on Linux box which I've been meaning to reinstall for ages (I used Debian 1.3.1 and 2.0 some time ago, but had been using RH6 until now); this reinstall coincided with the installation of ADSL in my flat -- the new box is intended to handle that connection, provide a few services, and be a samba logon server for my home LAN. After problems with kernel 2.4.8 (failing to recognize an IDE drive), I installed 2.4.9 from source. However, when I run PPPD (I've applied the PPPoATM patches, and compiled a patched version of PPPD 2.4.0), it complains that PPP_GENERIC is not installed in my kernel. It is. I've selected, infact, every single PPP option (as a test), and have tried both with them as modules (and then physically loaded them by hand), and directly in the kernel. Has anyone else had problems with PPP under 2.4.9, or with the PPPoATM patch(es), or does anyone have any suggestions? I've run out of ideas. Danke, Matt.
Re: PPP woes (again)
John Hasler wrote: Paul writes: The pon command works much better but seems to disconnect if left alone too long, though it`s fine as long as information is being transferred constantly. Either your ISP is dropping your connection when it is idle too long, or you have somehow given ppp an 'idle xxx' option. The first is the most likely. Post your /etc/ppp/options file. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI Here it is. I still find it curious however that I if this is an ISP problem and I need to ping every so often that a week or so ago I had Wvdial working fine without doing so.# /etc/ppp/options # # $Id: options,v 1.4 1996/05/01 18:57:04 alvar Exp $ # # Originally created by Jim Knoble [EMAIL PROTECTED] # Modified for Debian by alvar Bray [EMAIL PROTECTED] # Modified for PPP Server setup by Christoph Lameter [EMAIL PROTECTED] # # Use the command egrep -v '#|^ *$' /etc/ppp/options to quickly see what # options are active in this file. # Specify which DNS Servers the incoming Win95 or WinNT Connection should use # Two Servers can be remotely configured # ms-dns 192.168.1.1 # ms-dns 192.168.1.2 # Specify which WINS Servers the incoming connection Win95 or WinNT should use # ms-wins 192.168.1.50 # ms-wins 192.168.1.51 # Run the executable or shell command specified after pppd has # terminated the link. This script could, for example, issue commands # to the modem to cause it to hang up if hardware modem control signals # were not available. #disconnect chat -- \d+++\d\c OK ath0 OK # async character map -- 32-bit hex; each bit is a character # that needs to be escaped for pppd to receive it. 0x0001 # represents '\x01', and 0x8000 represents '\x1f'. asyncmap 0 # Require the peer to authenticate itself before allowing network # packets to be sent or received. # Please do not disable this setting. It is expected to be standard in # future releases of pppd. Use the call option (see manpage) to disable # authentication for specific peers. auth # Use hardware flow control (i.e. RTS/CTS) to control the flow of data # on the serial port. crtscts # Use software flow control (i.e. XON/XOFF) to control the flow of data # on the serial port. #xonxoff # Specifies that certain characters should be escaped on transmission # (regardless of whether the peer requests them to be escaped with its # async control character map). The characters to be escaped are # specified as a list of hex numbers separated by commas. Note that # almost any character can be specified for the escape option, unlike # the asyncmap option which only allows control characters to be # specified. The characters which may not be escaped are those with hex # values 0x20 - 0x3f or 0x5e. #escape 11,13,ff # Don't use the modem control lines. #local # Specifies that pppd should use a UUCP-style lock on the serial device # to ensure exclusive access to the device. lock # Use the modem control lines. On Ultrix, this option implies hardware # flow control, as for the crtscts option. (This option is not fully # implemented.) modem # Set the MRU [Maximum Receive Unit] value to n for negotiation. pppd # will ask the peer to send packets of no more than n bytes. The # minimum MRU value is 128. The default MRU value is 1500. A value of # 296 is recommended for slow links (40 bytes for TCP/IP header + 256 # bytes of data). mru 552 # Set the interface netmask to n, a 32 bit netmask in decimal dot # notation (e.g. 255.255.255.0). #netmask 255.255.255.0 # Disables the default behaviour when no local IP address is specified, # which is to determine (if possible) the local IP address from the # hostname. With this option, the peer will have to supply the local IP # address during IPCP negotiation (unless it specified explicitly on the # command line or in an options file). noipdefault # Enables the passive option in the LCP. With this option, pppd will # attempt to initiate a connection; if no reply is received from the # peer, pppd will then just wait passively for a valid LCP packet from # the peer (instead of exiting, as it does without this option). passive # With this option, pppd will not transmit LCP packets to initiate a # connection until a valid LCP packet is received from the peer (as for # the passive option with old versions of pppd). #silent # Don't request or allow negotiation of any options for LCP and IPCP # (use default values). #-all # Disable Address/Control compression negotiation (use default, i.e. # address/control field disabled). #-ac # Disable asyncmap negotiation (use the default asyncmap, i.e. escape # all control characters). #-am # Don't fork to become a background process (otherwise pppd will do so # if a serial device is specified). #-detach # Disable IP address negotiation (with this option, the remote IP # address must be specified with an option on the command line or in an # options file). #-ip # Disable magic number negotiation.
Re: PPP woes (again)
Paul writes: Here it is. Looks normal, except for 'passive' being enabled (that doesn't account for your problem). I still find it curious however that I if this is an ISP problem and I need to ping every so often that a week or so ago I had Wvdial working fine without doing so. ISP's do change policies. -- John HaslerThis posting is in the public domain. [EMAIL PROTECTED]Do with it what you will. Dancing Horse Hill Make money from it if you can; I don't mind. Elmwood, Wisconsin Do not send email advertisements to this address.
PPP woes (again)
After re-installing I find that when I use Wvdial to connect to my ISP it connects fine but then disconnects again after a minute or two with something like ppp daemon has died. Error code =1. The pon command works much better but seems to disconnect if left alone too long, though it`s fine as long as information is being transferred constantly. PPP is a loadable module, would compiling it into the kernel help? Any Ideas? Paul
Re: PPP woes (again)
Paul writes: The pon command works much better but seems to disconnect if left alone too long, though it`s fine as long as information is being transferred constantly. Either your ISP is dropping your connection when it is idle too long, or you have somehow given ppp an 'idle xxx' option. The first is the most likely. Post your /etc/ppp/options file. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: PPP woes
On Mon, 17 May 1999, R.Feenstra wrote: Sorry for jumping right in but you seem eager to help :) Where exactly can i find the option for turning ppp on in the kernel using make menuconfig ? I've looked till my head hurts but am not able to find it ! I'm using kernel-source-2.2.1 is that the problem ? Any help would be greatly apreciated ... Rene Perhaps too eager. Do feel free to ask, but sometimes I speak too soon ;) I copy to the list so any foolish things I say can be corrected by some of the good folk out there. This time I have just compiled my own kernel for a newly installed 2.0 system and for my 2.1 sytem, these run so _perhaps_ I can talk a little about kernel compiling. You enable ppp in the kernel in the configuration. Of course you must have tcp/ip enabled as well, and your ppp packages installed as well. To compile a kernel, I recommend that you do it the Debian way, with the kernel package. There many things are automated. From the README file that appears on my system as /usr/doc/kernel-package/README For the Brave and the impatient: [to compile the kernel] 1% cd kernel source tree 2% make config # or make menuconfig or make xconfig and configure 3% make-kpkg clean 4% make-kpkg --rootcmd fakeroot --revision=custom.1.0 kernel_image 5% dpkg -i ../kernel-image-X.XXX_1.0_arch.deb 6% shutdown -r now # If and only if LILO worked or you have a means of # booting the new kernel. YOU HAVE BEEN WARNED!! In the variant of make config that you use, you set the various options (CPU, file systems supported, CDROM, SCSI, low level drivers for boards, ppp, tcp/ip, and so on.) You need to get and install the .deb kernel-package, and the kernel source package for kernel 2.0.36, as well as bin86. I will say that the command in 4% did not work for me. I did this instead: 4% make-kpkg --revision=custom.1.0 kernel_image The reason for the custom.1.0 is so you can identify just compiled kernel .deb. You will, of course need to read the README and all the doc files BEFORE trying things. If you are running slink (2.1) or earlier, 2.0.36 is a good solid kernel. If you are running something later, and you are a beginner, don't, slink (2.1) is the latest stable version of Debian. You don't want to run unstable versions. Heck! I DON'T want to urn unstable versions. If I can help you further, feel free to ask. Only, understand that while I know some things, and am willing to share, there are many things I'll have to ask about on the mailing list, even as we discuss your problems. --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (Hope this qualifies:)
Re: PPP woes
JH == John Hasler [EMAIL PROTECTED] writes: JH David Teague writes: ppp has not been in default kernels I use. JH Only if you did not select it as a module when you installed. And even than, I believe all modules are installed, you just select which modules should be loaded by default. You can still select a module with modconf. Or uncomment auto in /etc/modules. BTW: the message kernel lacks ppp support could also mean the original poster used a wrong device name like /dev/ttys1 instead of /dev/ttyS1. Ciao, Martin
Re: PPP woes
William R Pentney writes: I have not yet recompiled my Debian kernel. (no lectures, please ...) No lectures. If the default kernel works for you, use it. Is PPP built into the default kernel? Yes, though pppd may try to tell you otherwise. I am having problems getting chat to speak to my modem. Chat knows nothing about modems. It just talks to its standard input and standard output. When pppd runs chat it connects chat to the modem. Any ideas? Run pppconfig and then use pon to start ppp and poff to stop it. If pppconfig doesn't do the job email me. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: PPP woes
On Fri, 14 May 1999, William R Pentney wrote: A couple of questions. 1) I have not yet recompiled my Debian kernel. (no lectures, please ...) Is PPP built into the default kernel? 2) I am having problems getting chat to speak to my modem. It simply isn't recognizing it. Is there some configuration I must perform before chat will work? Any ideas? Bill ppp has not been in default kernels I use. You will need to recompile a kernel to get ppp either as a module or built into the kernel. I recommend building it in, but many do not agree. No big thing, I think. I seem to recall that nothing about ppp works until you have kernel support. Try that then see if things will work for you. I got mine working with difficutly in 0.93 and 1.1, but 2.0 was much easier. It won't be difficult for you. Ping the list back if you continue to have problems once you recompile the kernel. I will try to help you, as many have helped me. BTW -- You will find the kernel package easier than bare-handed kernel recompile. Besides, I am under the impression that there are some things in the kernel how-to that aren't quite correct. Will someone else please remark on kernel compiles? --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (Hope this qualifies:)
Re: PPP woes
David Teague writes: ppp has not been in default kernels I use. Only if you did not select it as a module when you installed. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
PPP woes
A couple of questions. 1) I have not yet recompiled my Debian kernel. (no lectures, please ...) Is PPP built into the default kernel? 2) I am having problems getting chat to speak to my modem. It simply isn't recognizing it. Is there some configuration I must perform before chat will work? Any ideas? - thanks, Bill
