Re: Problems with PPP on boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi In your case, is Bind being started by an init script in /etc/init.d/? If so, perhaps you could add a new init script that brings up the PPPoE connection. Then, using update-rc.d, add the symbolic links to your script with a number that causes your PPPoE init script to be run before the Bind init script and any others that require the PPPoE link. I haven't modified any of the relevant init scripts. As far as I know the ppp daemon is started from /etc/rcS.d/S40networking (it contains command 'ifup -a' which should bring up all network interfaces, including ppp0) Other daemons (bind, ntp, ...) are started from scripts that are linked to /etc/rc2.d (S19bind, S23ntp-server, etc.). The manuals you pointed me to say that /etc/rcS.d scripts are ran before any of the /etc/rc2.d scripts. I think the problem is that S40networking runs 'ifup -a' which in turn runs pppd. pppd forks and returns immediately, which means that other boot scripts are started while the ppp is making connection in the background. Best regards Tomaz Solc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEoPsfsAlAlRhL9q8RAr2nAJwIQeaZa+qOVYrpUbwVuIg6NhjRrwCcDKr0 HjdK+n1LlYC4nKiTFLizhKE= =9Zj5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems with PPP on boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone I have a server running Sarge that is connected to the internet through PPPoE (I have a DSL line). I'm running several services, including DNS (bind 8.4.6-1) and ntpd. When machine boots, it seems that sometimes daemons will start before pppd manages to establish a connection. For some services like Apache this presents no problem. But Bind and NTP will not listen for connections coming from the internet, because the ppp0 network device didn't exist when they were starting. This is quite a problem, because the machine is crippled after a reboot until I manually restart Bind and NTP. I have my PPP connection configured in /etc/network/interfaces like this: auto ppp0 iface ppp0 inet ppp pre-up ifconfig eth1 up post-up waitfor ppp0 30 post-down ifconfig eth1 down provider dsl-provider-2.4 waitfor is a script that waits for ppp0 device to become available. This was one of my failed attempts to try to halt the boot process until the internet connection is established. I've also tried to add scripts to /etc/ppp/ip-up.d that would restart Bind automatically after successful connection, but this only partially worked (my explanation is that sometimes bind haven't finished starting when the script in /etc/ppp/ip-up.d tries to restart it) Has anyone else had a problem like this? How can I force the boot process to stop until ppp0 becomes available? I'm also interested in why my post-up script in /etc/network/interfaces isn't working. It seems to be working correctly when I bring the ppp0 interface up manually with ifup ppp0. Are these scripts started asynchronously on boot? Thanks in advance Tomaz Solc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFEoA29sAlAlRhL9q8RAt7aAJdgEu6Yw3jnlLCqvUwqXqZVqbH7AKCRddvo xn54xVX3JWQoLPPNEuSndQ== =2nRM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with PPP on boot
On Mon, Jun 26, 2006 at 06:39:25PM +0200, Tomaz Solc wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone I have a server running Sarge that is connected to the internet through PPPoE (I have a DSL line). I'm running several services, including DNS (bind 8.4.6-1) and ntpd. When machine boots, it seems that sometimes daemons will start before pppd manages to establish a connection. For some services like Apache this presents no problem. But Bind and NTP will not listen for connections coming from the internet, because the ppp0 network device didn't exist when they were starting. This is quite a problem, because the machine is crippled after a reboot until I manually restart Bind and NTP. I have my PPP connection configured in /etc/network/interfaces like this: auto ppp0 iface ppp0 inet ppp pre-up ifconfig eth1 up post-up waitfor ppp0 30 post-down ifconfig eth1 down provider dsl-provider-2.4 waitfor is a script that waits for ppp0 device to become available. This was one of my failed attempts to try to halt the boot process until the internet connection is established. My understanding is that the init scripts (in /etc/init.d/) are run in sequence and that the two-digit number in the names of the symbolic links in /etc/rc1.d/, /etc/rc2.d/, etc determines the order in which the scripts in /etc/init.d/ are run. For example, S13gdm would be started before S14ppp. Take a look at these: http://www.debian.org/doc/manuals/reference/ch-system.en.html#s-boot http://www.debian.org/doc/debian-policy/ch-opersys#s-sysvinit http://www.debian.org/doc/debian-policy/ch-opersys#s-/etc/init.d And, by the way, using Debian tools such as update-rc.d will help you manage those symbolic links. I use RoaringPenguin PPPoE, so I have my own init script (one I wrote; OK, I copied another script in /etc/init./ and made minor modifications), which brings up the PPPoE link and starts my firewall script. In your case, is Bind being started by an init script in /etc/init.d/? If so, perhaps you could add a new init script that brings up the PPPoE connection. Then, using update-rc.d, add the symbolic links to your script with a number that causes your PPPoE init script to be run before the Bind init script and any others that require the PPPoE link. Did I understand your problem correctly? Dave [snip] -- Dave Kuhlman http://www.rexx.com/~dkuhlman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems with PPP under Linux 2.4.19
Hi fellow debian users. I recently compiled Linux 2.4.19 on my linux workstation. But when I try to connect to my ISP i encounter problems. It dials up as it should but just when it *should* exchangelogin information, passwords and such it just zaps. It works perfectly in linux 2.2.19. If anyone know what to do, please answer. I dont have any logs from my system available at the time I'm writing this message. I'm sorry but hopefully someone might know something that might help me. Thanks.Gratis e-mail resten av livet på: www.yahoo.se/mail Busenkelt!
Re: Problems with PPP under Linux 2.4.19
Juston Girogm writes: I recently compiled Linux 2.4.19 on my linux workstation. Did you also upgrade ppp? -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with PPP under Linux 2.4.19
In linux.debian.user, you wrote: --0-1690367834-1034174371=:44987 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi fellow debian users. I recently compiled Linux 2.4.19 on my linux workstation. But when I try to connect to my ISP i encounter problems. It dials up as it should but just when it *should* exchange login information, passwords and such it just zaps. It works perfectly in linux 2.2.19. If anyone know what to do, please answer. I dont have any logs from my system available at the time I'm writing this message. I'm sorry but hopefully someone might know something that might help me. Thanks. A common problem is to forget to include PPP in the new kernel. It is not in by default. -- Anita GnuPG key: 1024D/9EDAC910 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: changed to 2.4.16 - problems with PPP and USB
Dan Kortschak, 2002-Feb-11 12:55 +1030: PPP: I have no idea what to do here - is there something that 2.4.x does differently with the serial connection for PPP? If you compiled the kernel yourself, CONFIG_PPP_ASYNC=y/m This setting may be listed in Character Devices, I'm not sure. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
changed to 2.4.16 - problems with PPP and USB
Hi All, I've just shifted my potato install to 2.4.16 and am having problems getting PPP or USB storage to work. The modules loaded are the same (as far as it goes) as I have with 2.2.19. I've looked around as much as I can to find what might be causing the problem, to no avail. The relevant details (I hope) are below (roughly split according to either PPP or USB problem). PPP: I have no idea what to do here - is there something that 2.4.x does differently with the serial connection for PPP? USB: The appropriate USB modules are loaded and the /proc/bus/usb has the right details for drivers and devices, but it still doesn't seem to recognise /dev/sda4 as a block device (according to the documentation I've looked at and the fuzzy memories I have when I used to run the 2.3 USB backport this should work). thanks for any help Dan Kortschak # lsmod Module Size Used byTainted: P ppp_deflate44840 0 (unused) ppp_generic24328 0 [ppp_deflate] slhc4992 0 [ppp_generic] ipx21772 0 appletalk 25268 0 usb-storage47720 0 binfmt_misc 8004 1 vfat 11984 0 smbfs 40704 0 (unused) nfsd 77808 0 (unused) lockd 54760 0 [nfsd] sunrpc 71876 0 [nfsd lockd] msdos 6384 0 (unused) fat35852 0 [vfat msdos] # wvdial -- WvDial: Internet dialer version 1.41 -- Cannot open /dev/ttyS0: Input/output error # ll /dev/ttyS0 crw-r-1 root dialout4, 64 Feb 10 10:47 /dev/ttyS0 # cat /proc/bus/usb/devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc=247/900 us (27%), #Int= 3, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB OHCI Root Hub S: SerialNumber=c7813000 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=059b ProdID=0001 Rev= 1.00 S: Manufacturer=Iomega S: Product=USB Zip 100 S: SerialNumber=00F4E9C6 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl= 32ms T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 4 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0409 ProdID=55ab Rev= 1.00 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms T: Bus=01 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=05ac ProdID=0201 Rev= 1.01 S: Manufacturer=Alps Electric?M2452 S: Product=M2452 C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=keyboard E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl= 10ms T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=02 Dev#= 5 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=046d ProdID=c001 Rev= 4.00 S: Manufacturer=Logitech S: Product=USB Mouse C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 50mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usb_mouse E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl= 10ms # cat /proc/bus/usb/drivers usbdevfs hub usb_mouse keyboard usb-storage # mount -t vfat /dev/sda4 /zip mount: /dev/sda4 is not a valid block device # dpkg -l ppp modutils kernel-image-2.4.16-newpmac Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii ppp2.4.1.uus-1Point-to-Point Protocol (PPP) daemon. ii modutils 2.4.11-1 Linux module utilities. ii kernel-image-2 2.4.16-1.1 Linux kernel binary image for new Power Maci -- _ .`.`o o| ,\__ `./`r Dan Kortschak mailto:[EMAIL PROTECTED] \/\_O O |`...'.\ Before you criticise a man, try to walk a mile in his` :\ shoes. Then, if he doesn't like what you have to say, : \ you'll be a mile away, and you'll have his shoes. : \ By replying to this email you implicitly accept that your response may
Problems with ppp after upgrade to kernel 2.4.X
Hi everybody! This weekend I upgraded my server from potato to woody. Everything worked fine. Then I upgraded my kernel from 2.2.14 to 2.4.13. And after that I run into great problems with my ppp link. In the syslog I get sometimes VJ decompression error and when I watch a the interface with ifconfig ppp0 I get somethin like this ppp0 RX packets:29 errors:16 dropped:0 overruns:0 frame:0 TX packets:43 errors:0 dropped:0 overruns:0 carrier:0 At last the half of the received packets have an error. Sometimes I get a realy fine connection with no errors, but most connections are bad. And when I switch back to the 2.2.14 kernel all runs fine again!?!?! I tried other 2.4 kernels (2.4.0 and 2.4.1) and got the same problems. Additional I have a hylafax server running on this modem, but it doesn't make a difference if the server is running or not. I can submit and receive faxes without any problem, so it seems, that the modem and the serial connection to the modem are ok. Could this be an incompatibility between some of my isp dial in servers and the 2.4 kernel? Here my hard and software configuration: IBM thinkpad 380E Elsa microlink office modem german t-online isp kernel 2.4.13 pppd 2.4.1.uus hylafax 4.1beta2 Thanks in advance for your help!! mfg Markus Braun -- Linux is like a Wigwam. No Windows, no Gates, and an Apache inside. - Markus Braunfon fax: 07453/930851 Gartenstrasse 6 \|/email: [EMAIL PROTECTED] 72227 Egenhausen(o o) homepage: www.krawel.de -oOo-(_)-oOo- GnuPG Key: 0x1A5A7357 / C1CE DC19 B189 1712 419C 3944 6FA4 8F01 1A5A 7357
Problems with PPP
When I connect to the Internet, 'xconsole' shows the following: 'ppp-compress-1' unable to locate module I'm using Kernel 2.2.5, and I compiled PPP support as a module. Is this correct? If not, how can I to workaround this? Please, reply to: [EMAIL PROTECTED] Thanks.
Re: Problems with PPP
On Sun, Apr 30, 2000 at 02:23:39PM +0200, José María Pongilioni López wrote: When I connect to the Internet, 'xconsole' shows the following: 'ppp-compress-1' unable to locate module I'm using Kernel 2.2.5, and I compiled PPP support as a module. Is this correct? If not, how can I to workaround this? Please, reply to: [EMAIL PROTECTED] I have the following in /etc/modutils/aliases (2.2.14 kernel) alias char-major-108 ppp alias ppp-compress-21 bsd_comp alias ppp-compress-24 ppp_deflate alias ppp-compress-26 ppp_deflate Don't know about ppp-compress-1. Hardware compression is usually better anyway. If you modify /etc/modutils/aliases, remember to run update-modules. -- ¶ One·should·only·use·the·ASCII·characterset·when·compos » ing·email·messages.
Re: problems with ppp (think it's the modem)
On Sat, 22 Jan 2000, you wrote: On Fri, Jan 21, 2000 at 08:01:18PM +0100, mek wrote: dear debbie's, since yesterday i have problems setting up my internet-connection. did with pppconfig, did everything as written in my book, but it didnt work at all. now today i saw when i do tail -f /var/log/messages: : abort on (VOICE) : abort on (NO DIALTONE) : abort on (NO ANSWER) : send (ATZ^M) : expect (OK) : ^M : NO CARRIER : -- failed : Failed (NO CARRIER) : Exit Try minicom -s. This will set up the modem parameters, etc. You should be able to dial to you ISP (use ATDT 1234567 to actually dial the phone) and it will show you a screen asking for your ID and password. Then it will spew jibberish. If you can get that far you are doing well. mmm thanx! in the meanwhile i was messing around in /etc/chatscripts/provider by editing some lines and it helped, but now i do not see any progress anymore. de chatscript says: ABORT BUSY ABORT VOICE ABORT NO DIALTONE ABORT NO ANSWERE ATZ OK ATDT4 what gives me in /var/log/messages: NO CARRIER^M ^M ATZ^M OK -- got it send (ATDt4^M) Serial connection established. Using interface ppp0 Connect: ppp0 -- /dev/ttyS0 Remote message local IP adres xxx.xx.xx.x remote IP adres xxx.xx.xx.xxx and here it remains:-( Also try http://www.grapevine.net/~gromitkc/winmodem.html and make sure you modem is on the good list. forunately not;-) it's a cablemodem and it worked well under redhat mek
problems with ppp (think it's the modem)
dear debbie's, since yesterday i have problems setting up my internet-connection. did with pppconfig, did everything as written in my book, but it didnt work at all. now today i saw when i do tail -f /var/log/messages: : abort on (VOICE) : abort on (NO DIALTONE) : abort on (NO ANSWER) : send (ATZ^M) : expect (OK) : ^M : NO CARRIER : -- failed : Failed (NO CARRIER) : Exit this seemed to me that the modem is not working, but on the other machine (this one where i am writing this) which runs redhat it works fine (at least if u can read this mail:-) so i looked around in the howto's but didnt find anything useful specific about modem-problems. even not by searching on altavista.com (where many debian items are listed) my question is if someone would know any solution for this. oh yes, since my casema.net account has some mailproblems till late in the night, i would appreciate if u would reply to this antenna.nl address. thanx in advance mek
Re: Strange network problems on ppp interface
On Tue, Nov 02, 1999 at 04:18:31PM -0800, [EMAIL PROTECTED] wrote: Hm! I reported almost the exact same problem right about the time when kernel 2.2.0 came out. At that time I was running 2.0.36+kerneli and had updated to 2.2.0, and didn't know a thing until our cable modem went out and I needed to use the Ricochet. I'm almost certain it's a kernel issue, because the same system worked fine with a Creative external modem on the same serial port. I've been using kernel 2.2.12 or 2.2.13 since I got the modem, so I'm fairly sure that the kernel isn't the problem here. But you do give interesting information, that it seems to be specifically related to Ricochet's network. I'll browse their web page. Thanks! --Dylan Thurston
Re: Strange network problems on ppp interface
On Tue, 2 Nov 1999, Dylan Thurston wrote: On Tue, Nov 02, 1999 at 04:18:31PM -0800, [EMAIL PROTECTED] wrote: Hm! I reported almost the exact same problem right about the time when kernel 2.2.0 came out. At that time I was running 2.0.36+kerneli and had updated to 2.2.0, and didn't know a thing until our cable modem went out and I needed to use the Ricochet. I'm almost certain it's a kernel issue, because the same system worked fine with a Creative external modem on the same serial port. I've been using kernel 2.2.12 or 2.2.13 since I got the modem, so I'm fairly sure that the kernel isn't the problem here. But you do give interesting information, that it seems to be specifically related to Ricochet's network. I'll browse their web page. H. Maybe whatever it was got fixed in the more recent kernels, if it was actually a kernel problem. I was running stock Debian 2.1 (I don't think I have my disc any longer) with a kernel built from kernel.org Were you running a stock slink without any of the unofficial updates before you upgraded to potato? -- Ferret no baka
Re: Strange network problems on ppp interface
On Tue, Nov 02, 1999 at 07:29:44PM -0800, [EMAIL PROTECTED] wrote: H. Maybe whatever it was got fixed in the more recent kernels, if it was actually a kernel problem. I was running stock Debian 2.1 (I don't think I have my disc any longer) with a kernel built from kernel.org Were you running a stock slink without any of the unofficial updates before you upgraded to potato? The update was basically from potato, version 25 October, to potato, version 30 October, if I have my chronology straight. Another update: ppp (still) works fine over my combo ethernet/modem PCMCIA card. The problem seems to be Ricochet-specific. --Dylan Thurston
Re: Strange network problems on ppp interface
The only other thing I can think of checking is your radio's firmware. Not having access to a Ricochet network right now I can't do any testing. On Tue, 2 Nov 1999, Dylan Thurston wrote: On Tue, Nov 02, 1999 at 07:29:44PM -0800, [EMAIL PROTECTED] wrote: H. Maybe whatever it was got fixed in the more recent kernels, if it was actually a kernel problem. I was running stock Debian 2.1 (I don't think I have my disc any longer) with a kernel built from kernel.org Were you running a stock slink without any of the unofficial updates before you upgraded to potato? The update was basically from potato, version 25 October, to potato, version 30 October, if I have my chronology straight. Another update: ppp (still) works fine over my combo ethernet/modem PCMCIA card. The problem seems to be Ricochet-specific.
Strange network problems on ppp interface
As of yesterday, I've been having some strange problems connecting through my Ricochet modem. I'm able to connect and ping places just fine; however, all useful connections (e.g., telnet, ftp, or http) fail: with telnet, for instance, I get the standard connect messages Trying 128.32.183.1... Connected to bosco.berkeley.edu. Escape character is '^]'. but then no welcome message. There's a tcpdump of such an attempt after my signature. I'd suspect a packet filtering problem, but I'm able to connect using my EtherNet card with no problem. The only change in my configuration that seems like it might be relevant is that I had just upgraded to the latest potato, after 5 days. The only packages upgraded that seem like they could possibly be relevant are hostname and libc6. Anyone have any ideas what could cause this kind of problem? Any help is greatly appreciated. Thanks, Dylan Thurston tcpdump follows: 13:18:58.493742 204.179.128.200.1102 207.69.194.216.ftp: FP 891443817:891443823(6) ack 890014480 win 16060 nop,nop,timestamp 1471784 933090531 (DF) 13:19:13.180204 204.179.128.200.1039 128.32.136.9.domain: 61999+ A? bosco.berkeley.edu. (36) 13:19:14.523709 128.32.136.9.domain 204.179.128.200.1039: 61999* 1/4/7 (260) 13:19:14.527411 204.179.128.200.1103 128.32.183.1.telnet: S 985306204:985306204(0) win 16060 mss 1460,sackOK,timestamp 1473387 0,nop,wscale 0 (DF) [tos 0x10] 13:19:14.873703 128.32.183.1.telnet 204.179.128.200.1103: S 3402697896:3402697896(0) ack 985306205 win 17520 mss 1460 (DF) 13:19:14.873862 204.179.128.200.1103 128.32.183.1.telnet: . ack 1 win 16060 (DF) [tos 0x10] 13:19:14.918216 204.179.128.200.1103 128.32.183.1.telnet: P 1:28(27) ack 1 win 16060 (DF) [tos 0x10] 13:19:17.913712 204.179.128.200.1103 128.32.183.1.telnet: P 1:28(27) ack 1 win 16060 (DF) [tos 0x10] 13:19:22.493719 204.179.128.200.1102 207.69.194.216.ftp: FP 0:6(6) ack 1 win 16060 nop,nop,timestamp 1474184 933090531 (DF) 13:19:23.913708 204.179.128.200.1103 128.32.183.1.telnet: P 1:28(27) ack 1 win 16060 (DF) [tos 0x10] 10 packets received by filter 0 packets dropped by kernel
Re: Problems with ppp server
On 16 Dec, Joe Emenaker wrote: My only suggestion would be to try it without the asyncmap option (which should cause ppp to use the desperate asyncmap of 0x... which you could also try explicitly). If that works, start trying turning off a bunch of the bits in the asyncmap to see of the problem returns. Eventually, you may boil it down to the one or two characters than need to be escaped. - Joe Thank You. That was the trick. Commenting out the asyncmap 0 option worked. I should have realized something was amiss earlier. I am using a digital TAU modem on the server side. It must need some characters to be escaped. I will now try determining which. Gopal. -- Gopal Narayanan Ph #: (413) 545 0925 Five College Radio Astronomy Observatory Fax#: (413) 545 4223 University of Massachusetts e-mail: [EMAIL PROTECTED] Amherst MA 01003 ---
Problems with ppp server
Hello, I am at wit's end with this problem. I am trying to set up a PPP server at work. It is a Debian machine running hamm with ppp version 2.3.5-2. Same setup at my home-machine as well. I am setting this up in the server with mgetty and AutoPPP. Autoppp works and I get a succesful PAP login. After that though, the home-client machine and the work-server don't seem to communicate the local and remote addresses properly - resulting in the home machine giving up saying that it Could not determine local IP address and hangs up ppp with No network protocols running At home, I used pppconfig to setup the connection script. Note that the home PPP setup and pppconfig scripts work for another ISP, the official campus PPP connection that uses PAP. So I suspect that the problem is not in my home machine. I am able to use minicom and get connected to the debian work server. But since the home client is not able to get its local IP address from the server, the ppp connection fails. I am enclosing relevant segments of syslog and my options files below for both the client and server. For security purposes, usernames, passwords, client and server names have been edited and made generic. I would appreciate any help in this regard. I apologize for the length of this message. Gopal. home client machine syslog- Dec 16 08:47:44 home-client pppd[30193]: pppd 2.3.5 started by root, uid 0 Dec 16 08:47:45 home-client chat[30194]: abort on (BUSY) Dec 16 08:47:45 home-client chat[30194]: abort on (NO CARRIER) Dec 16 08:47:45 home-client chat[30194]: abort on (VOICE) Dec 16 08:47:45 home-client chat[30194]: abort on (NO DIALTONE) Dec 16 08:47:45 home-client chat[30194]: abort on (NO ANSWER) Dec 16 08:47:45 home-client chat[30194]: send (ATZ^M) Dec 16 08:47:45 home-client chat[30194]: expect (OK) Dec 16 08:47:46 home-client chat[30194]: ATZ^M^M Dec 16 08:47:46 home-client chat[30194]: OK Dec 16 08:47:46 home-client chat[30194]: -- got it Dec 16 08:47:46 home-client chat[30194]: send (ATDT5551212^M) Dec 16 08:47:46 home-client chat[30194]: expect (CONNECT) Dec 16 08:47:46 home-client chat[30194]: ^M Dec 16 08:48:07 home-client chat[30194]: ATDT5551212^M^M Dec 16 08:48:07 home-client chat[30194]: CONNECT Dec 16 08:48:07 home-client chat[30194]: -- got it Dec 16 08:48:07 home-client chat[30194]: send (\d) Dec 16 08:48:08 home-client pppd[30193]: Serial connection established. Dec 16 08:48:09 home-client pppd[30193]: Using interface ppp0 Dec 16 08:48:09 home-client pppd[30193]: Connect: ppp0 -- /dev/ttyS1 Dec 16 08:48:09 home-client pppd[30193]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access Dec 16 08:48:09 home-client pppd[30193]: sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0xfebf pcomp accomp] Dec 16 08:48:12 home-client pppd[30193]: sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0xfebf pcomp accomp] Dec 16 08:48:12 home-client pppd[30193]: rcvd [LCP ConfReq id=0x1 asyncmap 0x0 auth pap magic 0xcffd pcomp accomp] Dec 16 08:48:12 home-client pppd[30193]: sent [LCP ConfAck id=0x1 asyncmap 0x0 auth pap magic 0xcffd pcomp accomp] Dec 16 08:48:12 home-client pppd[30193]: rcvd [LCP ConfAck id=0x1 asyncmap 0x0 magic 0xfebf pcomp accomp] Dec 16 08:48:12 home-client pppd[30193]: sent [LCP EchoReq id=0x0 magic=0xfebf] Dec 16 08:48:12 home-client pppd[30193]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access Dec 16 08:48:12 home-client pppd[30193]: sent [PAP AuthReq id=0x1 user=myname password=mypassword] Dec 16 08:48:12 home-client pppd[30193]: rcvd [LCP EchoReq id=0x0 magic=0xcffd] Dec 16 08:48:12 home-client pppd[30193]: sent [LCP EchoRep id=0x0 magic=0xfebf] Dec 16 08:48:12 home-client pppd[30193]: rcvd [LCP EchoRep id=0x0 magic=0xcffd] Dec 16 08:48:13 home-client pppd[30193]: rcvd [PAP AuthAck id=0x1 Login ok] Dec 16 08:48:13 home-client pppd[30193]: Remote message: Login ok Dec 16 08:48:13 home-client pppd[30193]: sent [IPCP ConfReq id=0x1 addr 0.0.0.0 compress VJ 0f 01] Dec 16 08:48:13 home-client pppd[30193]: rcvd [IPCP ConfReq id=0x1 addr 192.168.1.54 compress VJ 0f 01] Dec 16 08:48:13 home-client pppd[30193]: sent [IPCP ConfAck id=0x1 addr 192.168.1.54 compress VJ 0f 01] Dec 16 08:48:16 home-client pppd[30193]: sent [IPCP ConfReq id=0x1 addr 0.0.0.0 compress VJ 0f 01] Dec 16 08:48:16 home-client pppd[30193]: rcvd [IPCP ConfReq id=0x1 addr 192.168.1.54 compress VJ 0f 01] Dec 16 08:48:16 home-client pppd[30193]: sent [IPCP ConfAck id=0x1 addr 192.168.1.54 compress VJ 0f 01] Dec 16 08:48:19 home-client pppd[30193]: sent [IPCP ConfReq id=0x1 addr 0.0.0.0 compress VJ 0f 01] Dec 16 08:48:19 home-client pppd[30193]: rcvd [IPCP ConfReq id=0x1 addr 192.168.1.54 compress VJ 0f 01] Dec 16 08:48:19 home-client pppd[30193]: sent [IPCP ConfAck id=0x1 addr 192.168.1.54 compress VJ 0f 01] Dec 16 08:48:22 home-client pppd[30193]: sent [IPCP ConfReq id=0x1 addr 0.0.0.0 compress VJ 0f 01] Dec
Re: Problems with ppp server
Autoppp works and I get a succesful PAP login. After that though, the home-client machine and the work-server don't seem to communicate the local and remote addresses properly - resulting in the home machine giving up saying that it Could not determine local IP address and hangs up ppp with No network protocols running Your ppp server needs to know what IP address it can give out to your machine. However, it looks like you might already be doing this. I did notice something a little odd, though... Your home machine, not having an IP address, asks the work-server if it can use 0.0.0.0... [HOME] sent [IPCP ConfReq id=0x1 addr 0.0.0.0 compress VJ 0f 01] Your work machine knows that this is silly and it sends back a ConfNak (to request number id=1), telling your home machine that using that address is absolutely out of the question. However, the nice thing it does is that is says (to your home machine) Psstt... ask me if you can use 192.168.1.3... [WORK] sent [IPCP ConfNak id=0x1 addr 192.168.1.3] However, the strange thing is that your home machine never shows reception of this in the logs. It just keeps asking for 0.0.0.0 and your work-server keeps trying to issue it an IP. Another thing that's wierd, is that the home machine is acknowledging the work-server's IP address, and the work server is SEEING those acknowledgements... [WORK] rcvd [IPCP ConfAck id=0x1 addr 192.168.1.54 compress VJ 0f 01] but it keeps asking for it. Strange, indeed. My only suggestion would be to try it without the asyncmap option (which should cause ppp to use the desperate asyncmap of 0x... which you could also try explicitly). If that works, start trying turning off a bunch of the bits in the asyncmap to see of the problem returns. Eventually, you may boil it down to the one or two characters than need to be escaped. - Joe
problems with PPP Debian 2.0 beta
I recently upgraded my 'base' system to 2.0 beta, and also installed PPP 2.3.5-2. However, when I did this, ppp stopped working. It will dial, and it fails with the message peer refused to authenicate. Obviously this didn't happen before... I've checked pap-secrets and that looks the same.. in fact everything looks the same that it did before. Any ideas? Thanks, Chris please cc me by email -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: problems with PPP Debian 2.0 beta
auth is selected in /ppp/options now. It wasnt before. I had to put noauth in /ect/ppp/peers/provider to override it and get a connection. Mike On Tue, Jul 14, 1998 at 09:28:53PM -0500, Chris R. Martin wrote: I recently upgraded my 'base' system to 2.0 beta, and also installed PPP 2.3.5-2. However, when I did this, ppp stopped working. It will dial, and it fails with the message peer refused to authenicate. Obviously this didn't happen before... I've checked pap-secrets and that looks the same.. in fact everything looks the same that it did before. Any ideas? Thanks, Chris please cc me by email -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Problems w/ppp dialup and sending mail: SOLVED!
On Sun, 22 Feb 1998 [EMAIL PROTECTED] wrote: Until recently, that is, when my ISP (campus.mci.net) began bouncing outgoing mail that has an unrecognized domain of origin. [snip] They are trying to look up frodo.cs.wcu.edu as a domain, and failing. Try setting visible_name to their domain: visible_name=cs.wcu.edu Smail will stick your login name in front of this and use it in the SMTP transaction. It won't end up in your headers, but it might suffice to fool your isp. Worked for me when mine did the same thing last year (that is, upgraded sendmail). -- John Hasler John, Bingo! That single change Works like a charm. In .pinerc I set visible_name=cs.wcu.edu, which actually generates an address of a real account, as I have an a login there. The combination creates a name that resolves, and campus.mci takes it. Is it significant to the success of this that the login generated by my longin name here and the domain at wcu is a legitimate account? Many thanks also to Daniel Gross and James Thomas who replied to this question. --David [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. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problems w/ppp dialup and sending mail
On Sun, 22 Feb 1998, DAVID B. TEAGUE wrote:
I installed Debian 1.1 and for a year things worked quite well. I could
send mail, receive mail via popmail, and use ppp for web access, fpt and
telnet. Except for some problems getting logged in last Christmas, which
seem to have been resolved all has been well.
Until recently, that is, when my ISP (campus.mci.net) began bouncing
outgoing mail that has an unrecognized domain of origin.
How in the blazes do i get a valid 'domain' I am assigned an ip number
each time I log in?
Try the following:
/etc/smail/routers
smart_host:
driver=smarthost, transport=smtp-rewrite;
path=mail.bingo.baynet.de
--
/etc/smail/transports-
[... other transports ...]
smtp-remap:
driver=tcpsmtp, max_addrs=100, -max_chars, inet,
remove_header=From,
insert_header=From:
${lookup:from:lsearch{maps/[EMAIL PROTECTED] ($from:$fullname)}},
remove_header=Message-ID,
insert_header=Message-ID: [EMAIL PROTECTED],
insert_header=Sender:
${lookup:from:lsearch{maps/[EMAIL PROTECTED] ($from:$fullname)}};
use_bind, defer_no_connect, -local_mx_okay, defnames
--
/etc/smail/maps/from--
root[EMAIL PROTECTED] (root)
YOURLOCALUSER [EMAIL PROTECTED] (YOURNAME)
--
Hope this helps.
Bye
Daniel
--
Daniel Gross eMail: [EMAIL PROTECTED]
Hollarstrasse 2 [EMAIL PROTECTED]
D-85053 Ingolstadt, Germany
--
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization?
Gandhi: I think it would be a good idea.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Problems w/ppp dialup Kerberos
Greetings all, OK, the ongoing saga of my ppp dialup continues. pon now attempts the connection(my modem is now recognized!). It dials and then thats it. We use Kerberos Authen so i do not know if this is causing the problem. The logs show that after the handshake the host(my school) asks for 4 returns for interactive mode which i'm familiar with from dialing in with ckermit(a dummy term). Should ppp take care of that? Any help is greatly appreciated, we're almost therethanks to you guys/gals! Regards, jd? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problems w/ppp dialup Kerberos
Jesus Duran [EMAIL PROTECTED] writes: problem. The logs show that after the handshake the host(my school) asks for 4 returns for interactive mode which i'm familiar with from dialing in with ckermit(a dummy term). Should ppp take care of that? Any help is I believe editing /etc/ppp.chatscript to reflect the dialog you do in ckermit will do the thing. Otherwise post the relevant part of /var/log/ppp.log after adding debug to /etc/ppp.options_out Ciao, Martin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Problems w/ppp dialup and sending mail
Hi Guys I installed Debian 1.1 and for a year things worked quite well. I could send mail, receive mail via popmail, and use ppp for web access, fpt and telnet. Except for some problems getting logged in last Christmas, which seem to have been resolved all has been well. Until recently, that is, when my ISP (campus.mci.net) began bouncing outgoing mail that has an unrecognized domain of origin. How in the blazes do i get a valid 'domain' I am assigned an ip number each time I log in? I include typical mail message and error that I get when attempting to send from home: From [EMAIL PROTECTED] Sun Feb 22 15:22:30 1998 Date: Sat, 21 Feb 98 15:23 EST From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: mail failed, returning to sender |- Failed addresses follow: -| [EMAIL PROTECTED] ... transport smtp: 551 Unrecognized domain 'frodo.cs.wcu.edu' |- Message text follows: | Received: by frodo.cs.wcu.edu id m0y1E3q-000hZ9C (Debian /\oo/\ Smail3.1.29.1 #29.37); Sat, 7 Feb 98 12:29 EST Message-Id: [EMAIL PROTECTED] From: dbt (David B. Teague) Subject: Ch5,6,7 notes To: [EMAIL PROTECTED] Date: Sat, 7 Feb 1998 12:29:02 -0500 (EST) X-Mailer: ELM [version 2.4 PL25 PGP2] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 10874 I include exerpts (I hope appropriate exerpts, I hope you will tell me if you need more): hosts: 127.0.0.1 localhost 152.30.5.51 frodo.cs.wcu.edufrodo The 152.30.5.51 is bogus at home, as is the cs.wcu.edu. It is set this way so I can take the machine to work to connect to the net for serious upgrades. 33K is to durned slow. Any of this except 'frodo' is mutable. 'frodo' is my machine's name, I'd very much like to keep that. /etc/smail/config # This is the main Smail configuration file. visible_name=frodo.cs.wcu.edu -domains hostnames=frodo.cs.wcu.edu:frodo:frodo.cs The rest of the conf file is 'out of the box'. I tried changing the host name, the mailer still picks up the visible name here or some other place, and mci bounces the mail. For example hostnames=wcu.campus.mci.net gets me nothing. I tried several variations on settings of hosts and host naes in config files, but I do not seem to be able to get mci to allow me to send mail with any domain name I can guess. I have appended the headers from an earlier successful mail message sent from home to a machine at work in hope that some knowledgable person can see what this ISP requires. Help, please! --David ([EMAIL PROTECTED], [EMAIL PROTECTED]) Appendix: Full headers from an ealier message successfully sent 2 Dec 1997: Received: from aus-e.mp.campus.mci.net (aus-e.mp.campus.mci.net [208.140.84.25]) by elentari.cs.wcu.edu (8.8.5/8.8.5) with ESMTP id LAA23910 for [EMAIL PROTECTED]; Tue, 2 Dec 1997 11:32:05 -0500 Received: from frodo.cs.wcu.edu ([EMAIL PROTECTED] [208.140.81.233]) by aus-e.mp.campus.mci.net (8.8.8/8.8.8) with SMTP id LAA11107; Tue, 2 Dec 1997 11:23:57 -0500 (EST) Received: by frodo.cs.wcu.edu id m0xcv26-000hZ9C (Debian /\oo/\ Smail3.1.29.1 #29.37); Tue, 2 Dec 97 11:18 EST Message-Id: [EMAIL PROTECTED] From: [EMAIL PROTECTED] (David B. Teague) Subject: Exercises on subsitution and Translation To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Tue, 2 Dec 1997 11:18:46 -0500 (EST) X-Mailer: ELM [version 2.4 PL25 PGP2] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problems w/ppp dialup and sending mail
On Sun, 22 Feb 1998 16:04:21 EST, DAVID B. TEAGUE wrote: Hi Guys I installed Debian 1.1 and for a year things worked quite well. I could send mail, receive mail via popmail, and use ppp for web access, fpt and telnet. Except for some problems getting logged in last Christmas, which seem to have been resolved all has been well. Until recently, that is, when my ISP (campus.mci.net) began bouncing outgoing mail that has an unrecognized domain of origin. How in the blazes do i get a valid 'domain' I am assigned an ip number each time I log in? If I understand what you're asking and know what I'm talking about, you need to rewrite the Sender: line in your email header; i.e.: the Sender: line should correspond to your actual (isp) email address. (As to why it matters if the domain in your Sender: line is resolvable by the DNS, I have no idea, and I'd also like to know.) There are varying ways to do this, depending on, among other things, your email client. I see you'll be using elm, which I don't currently have installed, however I believe I've heard people discuss on this that elm has a built-in facility to rewrite the Sender: line. Perhaps you can do some research, or maybe an elm user will tell you. Some email clients pass along outgoing delivery service to the MTA (smail), and others do not. If elm does not, then elm will be the only place you can rewrite your Sender: line, however if elm passes along outgoing mail deliver to your MTA, then you may be able to rewrite the sender line by configuring your MTA. By configuring your MTA to rewrite your email header, all email clients which use the MTA for outgoing mail delivery will be properly configured, but it may require more effort to set up, and as has proven for, to maintain. Other ways to rewrite email headers also exist, but these seem to be the most common. -- David Stern -- http://weber.u.washington.edu/~kotsya [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
