RE: [leaf-user] Testing dial-up modem
Please reply to the list; you'll get more useful responses. Have you followed the procedures in http://leaf.sourceforge.net/devel/jnilo/bumodem.html? -Richard On Tue, 2003-02-18 at 18:27, Greg Playle wrote: > I checked the logs; it showed only that the chat script was failing. > I inserted SAY messages to do println debugging in the chat scripts; the > scripts either never quite communicate with the modem, or fail at the dial > command. > syslog does show some info, but didn't show details. I'll try setting the > options for logging and see what I get. > > -Original Message- > From: Richard Doyle [SMTP:[EMAIL PROTECTED]] > Sent: Monday, 17 February, 2003 22:18 > To: [EMAIL PROTECTED] > Cc: '[EMAIL PROTECTED]' > Subject: Re: [leaf-user] Testing dial-up modem > > Check your logs. pppd should let daemon.info know when the serial > connection is established. Should also show up in syslog, if memory > serves. You can set logging level in /etc/ppp/options. > > -Ricahrd > > On Mon, 2003-02-17 at 13:18, Greg Playle wrote: > > I'm new to LEAF, using Bering 1.1, and attempting to set it up for a > serial > > modem (exterior), with two ethernet interfaces. > > > > I've got a booting distro, but there seems to be problems talking to the > > modem. While I learn about PPP, can someone point me to a way to verify > > the serial interface is actually detected, and is in fact talking to the > > modem? > > > > Thank you > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > > > leaf-user mailing list: [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/leaf-user > > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html > > > -- > Richard Doyle <[EMAIL PROTECTED]> > -- Richard Doyle <[EMAIL PROTECTED]> --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
RE: [leaf-user] Testing dial-up modem
Richard: Thank you for the reply. Yes, I followed those procedures. I've set the system-wide options for ppp to debug, which was helpful. The /var/log/messages now has the chat scripts results in it. The ABORT commands appear to be sent, and the ATZ^M, but the chat script gives an "expect (OK)", then an alarm and a failed, with no further indication of what failed. For some reason, the SAY messages didn't show up either, so I removed them. There does not appear to be anything in syslog or ppp.log that adds any information; ppp.log indicates the same process. I never hear any dialing, and I see no change in the status lights on the modem. ifup shows ppp0 present. Are there other things I should try for debug? Richard sent: Have you followed the procedures in http://leaf.sourceforge.net/devel/jnilo/bumodem.html? -Richard --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
RE: [leaf-user] Testing dial-up modem
Post a log segment showing a complete sequence of chat and pppd entries. In general it is helpful to post unedited logs (but replace passwords with x's). The summary you provided doesn't provide any evidence that your system is communicating with your modem. The unsummarized log may give us a clue. My home network has two internal subnets and a dial-up connection to the Internet (currently via an internal modem, but in the past an external one), so your intended configuration is quite feasible. Your problem is probably not LEAF-specific--you might get more help by looking in the ppp howto (https://secure.linuxports.com/howto/ppp/), which is a bit old, and the linux-ppp mailing list (http://vger.kernel.org/majordomo-info.html). -Richard On Tue, 2003-02-18 at 20:06, Greg Playle wrote: > Richard: > Thank you for the reply. Yes, I followed those procedures. > > I've set the system-wide options for ppp to debug, which was helpful. > The /var/log/messages now has the chat scripts results in it. > The ABORT commands appear to be sent, and the ATZ^M, but the chat script > gives an "expect (OK)", then an alarm and a failed, with no further > indication of what failed. > For some reason, the SAY messages didn't show up either, so I removed > them. > There does not appear to be anything in syslog or ppp.log that adds any > information; ppp.log indicates the same process. > > I never hear any dialing, and I see no change in the status lights on the > modem. > > ifup shows ppp0 present. > > Are there other things I should try for debug? > > Richard sent: > > Have you followed the procedures in > http://leaf.sourceforge.net/devel/jnilo/bumodem.html? > > -Richard > > > > --- > This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. > The most comprehensive and flexible code editor you can use. > Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. > www.slickedit.com/sourceforge > > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html > -- Richard Doyle <[EMAIL PROTECTED]> --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] Testing dial-up modem
On Wed, 2003-02-26 at 19:18, Greg Playle wrote: > On 19 Feb 2003 13:11:07 -0800, Richard Doyle wrote in reply: > > --- snip --- > Post a log segment showing a complete sequence of chat and pppd entries. > In general it is helpful to post unedited logs (but replace passwords > with x's). > > The summary you provided doesn't provide any evidence that your system > is communicating with your modem. The unsummarized log may give us a > clue. > > My home network has two internal subnets and a dial-up connection to the > Internet (currently via an internal modem, but in the past an external > one), so your intended configuration is quite feasible. Your problem is > probably not LEAF-specific--you might get more help by looking in the > ppp howto (https://secure.linuxports.com/howto/ppp/), which is a bit > old, and the linux-ppp mailing list > (http://vger.kernel.org/majordomo-info.html). > > -Richard > > > - end snip -- > > Richard: > I had no fear that what I wanted was achievable; I seem to have done > something incorrectly in setting it up. > > I've pulled various logs and configuration files and will post them below. > Advice and comment is quite welcome. > > The machine is an older P75, no hard drive, two 3C905B NICs, and an > external Zoltrix 56k modem. What I am trying to set up is a dual-homed > firewall, dial-up service, and an internal "store and forward" server in > the DMZ, to capture, filter, and hold e-mail and such until I can join the > net and pull them. Getting Bering working is the first step in this. > > On to the logs: each is identified by a line before and after. Some > lines may wrap > > snip /var/log/messages > Feb 26 19:56:48 firewall syslogd 1.3-3#31.slink1: restart. > Feb 26 19:56:48 firewall kernel: klogd 1.3-3#31.slink1, log source = > /proc/kmsg started. > Feb 26 19:56:48 firewall kernel: Loaded 21 symbols from 8 modules. > Feb 26 19:56:48 firewall kernel: BIOS-provided physical RAM map: > Feb 26 19:56:48 firewall kernel: 32MB LOWMEM available. > Feb 26 19:56:48 firewall kernel: Initializing CPU#0 > Feb 26 19:56:48 firewall kernel: Memory: 30136k/32768k available (965k > kernel code, 2244k reserved, 252k data, 64k init, 0k highmem) > Feb 26 19:56:48 firewall kernel: Dentry cache hash table entries: 4096 > (order: 3, 32768 bytes) > Feb 26 19:56:48 firewall kernel: Inode cache hash table entries: 2048 > (order: 2, 16384 bytes) > Feb 26 19:56:48 firewall kernel: Intel Pentium with F0 0F bug - workaround > enabled. > Feb 26 19:56:48 firewall kernel: Checking 'hlt' instruction... OK. > Feb 26 19:56:48 firewall kernel: PCI: PCI BIOS revision 2.10 entry at > 0xfcb71, last bus=0 > Feb 26 19:56:48 firewall kernel: PCI: Using configuration type 1 > Feb 26 19:56:48 firewall kernel: PCI: Probing PCI hardware > Feb 26 19:56:48 firewall kernel: Limiting direct PCI/PCI transfers. > Feb 26 19:56:48 firewall kernel: Linux NET4.0 for Linux 2.4 > Feb 26 19:56:48 firewall kernel: Based upon Swansea University Computer > Society NET3.039 > Feb 26 19:56:48 firewall kernel: Serial driver version 5.05c (2001-07-08) > with MANY_PORTS SHARE_IRQ DETECT_IRQ SERIAL_PCI enabled > Feb 26 19:56:48 firewall kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A > Feb 26 19:56:48 firewall kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A > Feb 26 19:56:48 firewall kernel: Real Time Clock Driver v1.10e > Feb 26 19:56:48 firewall kernel: Software Watchdog Timer: 0.05, timer > margin: 60 sec > Feb 26 19:56:48 firewall kernel: Floppy drive(s): fd0 is 1.44M > Feb 26 19:56:48 firewall kernel: FDC 0 is a National Semiconductor PC87306 > Feb 26 19:56:48 firewall kernel: NET4: Linux TCP/IP 1.0 for NET4.0 > Feb 26 19:56:48 firewall kernel: IP Protocols: ICMP, UDP, TCP, IGMP > Feb 26 19:56:48 firewall kernel: IP: routing cache hash table of 512 > buckets, 4Kbytes > Feb 26 19:56:48 firewall kernel: TCP: Hash tables configured (established > 2048 bind 2048) > Feb 26 19:56:48 firewall kernel: NET4: Unix domain sockets 1.0/SMP for > Linux NET4.0. > Feb 26 19:56:48 firewall kernel: RAMDISK: Compressed image found at block 0 > Feb 26 19:56:48 firewall kernel: Freeing initrd memory: 401k freed > Feb 26 19:56:48 firewall kernel: Freeing unused kernel memory: 64k freed > Feb 26 19:56:48 firewall kernel: 3c509.c:1.19 16Oct2002 [EMAIL PROTECTED] > Feb 26 19:56:48 firewall chat[9516]: abort on (BUSY) This is oddly wrong. Your system is attempting to run chat even before the kernel loads the ppp modules, much less pppd. What does your /etc/network/interfaces file contain? Have you followed http://leaf.sourceforge.net/devel/jnilo/bumodem.html step-by-step? > Feb 26 19:56:48 firewall chat[9516]: abort on (NO CARRIER) > Feb 26 19:56:48 firewall chat[9516]: abort on (VOICE) > Feb 26 19:56:48 firewall chat[9516]: abort on (NO DIALTONE) > Feb 26 19:56:48 firewall chat[9516]: abort on (NO
Re: [leaf-user] Testing dial-up modem
On 27 Feb 2003, Richard Doyle wrote: > On Wed, 2003-02-26 at 19:18, Greg Playle wrote: > > On 19 Feb 2003 13:11:07 -0800, Richard Doyle wrote in reply: > > [funky quoting of Richard's email] > > --- snip --- > > Post a log segment showing a complete sequence of chat and pppd entries. > > In general it is helpful to post unedited logs (but replace passwords > > with x's). > > [... omitted stuff ... Greg's log output follows...] > > Feb 26 19:56:48 firewall kernel: RAMDISK: Compressed image found at block 0 > > Feb 26 19:56:48 firewall kernel: Freeing initrd memory: 401k freed > > Feb 26 19:56:48 firewall kernel: Freeing unused kernel memory: 64k freed > > Feb 26 19:56:48 firewall kernel: 3c509.c:1.19 16Oct2002 [EMAIL PROTECTED] > > Feb 26 19:56:48 firewall chat[9516]: abort on (BUSY) > This is oddly wrong. Your system is attempting to run chat even before > the kernel loads the ppp modules, much less pppd. What does your > /etc/network/interfaces file contain? Have you followed > http://leaf.sourceforge.net/devel/jnilo/bumodem.html step-by-step? Are you editing /boot/etc/modules? (you should not do that for ppp) > > Feb 26 19:56:48 firewall chat[9516]: abort on (NO CARRIER) > > Feb 26 19:56:48 firewall chat[9516]: abort on (VOICE) > > Feb 26 19:56:48 firewall chat[9516]: abort on (NO DIALTONE) > > Feb 26 19:56:48 firewall chat[9516]: abort on (NO ANSWER) > > Feb 26 19:56:48 firewall chat[9516]: send (ATZ^M) > > Feb 26 19:56:48 firewall kernel: http://www.scyld.com/network/3c509.html > > Feb 26 19:56:48 firewall kernel: CSLIP: code copyright 1989 Regents of the > > University of California > > Feb 26 19:56:48 firewall kernel: PPP generic driver version 2.4.2 > > Feb 26 19:56:49 firewall chat[9516]: expect (OK) > > Feb 26 19:56:56 firewall root: Shorewall Started > > Feb 26 19:57:34 firewall chat[9516]: alarm > > Feb 26 19:57:34 firewall chat[9516]: Failed > > > > - end snip > > > > -- snip /var/log/modules > Eh? I'll assume its /etc/modules, as the file itself states: > > > # /etc/modules: kernel modules to load at boot time. > > # > > # ISA ethernet cards > > 3c509 This module should not support the 3c905... but you are showing evidence in your logs that such support is present, without showing the "3c905" or "3c59x" modules that do support it. More evidence of mucking with /boot/etc/modules and /boot/lib/modules? Or did you abbreviate this file? What is the output of "cat /proc/interrupts"? "lsmod"? "cat /proc/pci"? Old BIOSes were particularly bizarre in their handling of PCI interrupts, and you may have a conflict between your 905 cards and the serial port (irq4). [...] --- Jeff NewmillerThe . . Go Live... DCN:<[EMAIL PROTECTED]>Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/BatteriesO.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --- --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
