Read though Jacque's PostInstall howto at http://linmodems.technion.ac.il On Tue, Jan 20, 2009 at 2:54 AM, D Brewer <interscientific@xxxxxxxxx> wrote:> MarvS,>> Thank you for your efforts. I have connected to these IPs before on another> Ubuntu machine (assisted by members of this list several weeks ago). I also> get the same results with this current modem/machine when I try to connect> to another ISP (a paid service). So it seems to be something about this> modem that is supposedly Linux compatible in theory, but not consistently so> in practice.>> Do you have any other ideas to try? If there aren't any other ideas, then I> might just have to give up and tell my friend the only way I can get the> machine to connect is with broadband (which I've already tried and> confirmed).>> Thank you again for all of your help!>> Devon>> --- On Mon, 1/19/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:>> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>> Subject: Re: USR 5637 USB ext modem Linux compatible but problem connecting> To: "D Brewer" <interscientific@xxxxxxxxx>> Cc: "anthony" <anthonykbrown@xxxxxxxxxxxx>, discuss@xxxxxxxxxxxxx> Date: Monday, January 19, 2009, 7:56 PM>>> -----Inline Attachment Follows----->> DB,>> Having a nation wide dialing coverage, I used a USB Conexant modem> ,attempting several different /etc/ppp/options conditions using:> [Dialer Defaults]> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0> Modem Type = Analog Modem> Phone = 12064951000> ISDN = 0> Username = guest> Init1 = ATZ> Password = password> Modem = /dev/modem> Baud = 460800> Stupid Modem = 1> #end>> While temporary CONNECTs were achieved, and even DNS assignments in> some cases, I could neither PING, browse of maintain a CONNECT.> I suggest you change to a different Internet prov ider.> We do occassionally encounter Linux hostile IPs.>> Check with you local Linux club and to determine what effective IPs are.>> MarvS>> On Mon, Jan 19, 2009 at 3:15 PM, D Brewer <interscientific@xxxxxxxxx> wrote:>> Thank you, MarvS.>>>> I had the lcp settings enabled because that's what Anthony Brown's post>> suggested to do, along with enabling the passive mode. I commented out>> the>> lcp commands, ran wvdial, and got the same essential result:>>>> $ wvdial>> --> WvDial: Internet dialer version 1.60>> --> Cannot get information for serial port.>> --> Initializing modem.>> --> Sending: ATZ>> ATZ>> OK>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>> OK>> --> Modem initialized.>> --> Sending: ATDT4951000>> --> Waiting for carrier.>> ATDT4951000>> CONNECT 48000/ARQ/V90/LAPM/V42BIS>> --> Carrier detected. Starting PPP immediately.>> --> Starting pppd at Mon Jan 19 12:06:12 2009>> --> Pid of pppd: 6144>> --> Using interface ppp0>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> local IP address 64.40.60.18>> --> pppd: ��[06][08]`�[06][08]>> --> remote IP address 64.40.40.6>> --> pppd: ��[06][08]`�[06][08]>> --> primary DNS address 64.40.40.53>> --> pppd: ��[06][08]`�[06][08]>> --> secondary DNS address 66.54.140.10>> --> pppd: ��[06][08]`�[06][08]>> Caught signal 2: Attempting to exit gracefully...>> --> Terminating on signal 15>> --> pppd: ��[06][08]`�[06][08]>> --> Connect time 1.0 minutes.>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> Disconnecting at Mon Jan 19 12:07:15 2009>>>> So then I tried commenting out the passive mode (completing reversing>> Anthony Brown's suggested strategy), ran wvdial, and still had the same>> result:>>>> $ wvdial>> --> WvDial: Internet dialer version 1.60>> --> Cannot get information for serial port.>> --> Initializing modem.>> --> Sending: ATZ>> ATZ>> OK>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>> OK>> --> Modem initialized.>> --> Sending: ATDT4951000>> --> Waiting for carrier.>> ATDT4951000>> CONNECT 48000/ARQ/V90/LAPM/V42BIS>> --> Carrier detected. Starting PPP immediately.>> --> Starting pppd at Mon Jan 19 12:08:27 2009>> --> Pid of pppd: 6181>> --> Using interface ppp0>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> local IP address 66.109.195.65>> --> pppd: ��[06][08]`�[06][08]>> --> remote IP address 10.64.64.64>> --> pppd: ��[06][08]`�[06][08]>> --> primary DNS address 64.40.40.51>> --> pppd: ��[06][08]`�[06][08]>> --> secondary DNS address 66.54.140.10>> --> pppd: ��[06][08]`�[06][08]>> Caught signal 2: Attempting to exit gracefully...>> --> Terminating on signal 15>> --> pppd: ��[06][08]`�[06][08]>> --> Connect time 0.9 minutes.>> --> pppd: ��[06][08]`�[06][08]>> --> pppd: ��[06][08]`�[06][08]>> --> Disconnecting at Mon Jan 19 12:09:21 2009>>>> What else do you recommend trying?>>>> Thanks again,>>>> Devon>>>> --- On Mon, 1/19/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:>>>> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>>> Subject: Re: USR 5637 USB ext modem Linux compatible but problem>> connecting>> To: "D Brewer" <interscientific@xxxxxxxxx>>> Cc: "anthony" <anthonykbrown@xxxxxxxxxxxx>, discuss@xxxxxxxxxxxxx>> Date: Monday, January 19, 2009, 11:45 AM>>>>>> -----Inline Attachment Follows----->>>> DB>>>> With your current settings below, echos are being sent continuously>> and there is a disconnect after the first failure>>>> # If this option is given, pppd will send an LCP echo-request frame to the>> # peer every n seconds. Normally the peer should respond to the>> echo-request>> # by sending an echo-reply. This option can be used with the>> # lcp-echo-failure option to detect that the peer is no longer connected.>> lcp-echo-interval 0>>>> # If this option is given, pppd will presume the peer to be dead if n>> # LCP echo-requests are sent without receiving a valid LCP echo-reply.>> # If this happens, pppd will terminate the connection. Use of this>> # option requires a non-zero value for the lcp-echo-interval parameter.>> # This option can be used to enable pppd to terminate after the physical>> # connection has been broken (e.g., the modem has hung up) in>> # situations where no hardware modem control lines are available.>> lcp-echo-failure 0>> ======>>>> So try commenting them both out, per below:>>>> # If this option is given, pppd will send an LCP echo-request frame to the>> # peer every n seconds. Normally the peer should respond to the>> echo-request>> # by sending an echo-reply. This option can be used with the>> # lcp-echo-failure option to detect that the peer is no longer connected.>> # lcp-echo-interval 0>>>> # If this option is given, pppd will presume the peer to be dead if n>> # LCP echo-requests are sent without receiving a valid LCP echo-reply.>> # If this happens, pppd will terminate the connection. Use of this>> # option requires a non-zero value for the lcp-echo-interval parameter.>> # This option can be used to enable pppd to terminate after the physical>> # connection has been broken (e.g., the modem has hung up) in>> # situations where no hardware modem control lines are available.>> # lcp-echo-failure 0>>>>>> marvS>>>>>>>>>> On Mon, Jan 19, 2009 at 11:02 AM, D Brewer <interscientific@xxxxxxxxx>>> wrote:>>> MarvS,>>>>>> Thank you for the continuing advice.>>>>>> I tried enabling auth, but it didn't make any difference and produced the>>> same output from wvdial as before. I lack the insight about which other>>> commands might or might not be relevant, so I would be very grateful for>>> your expert's examination of what might be wrog with my options file,>>> which>>> follows here (the only settings changed from the default on my system are>>> those recommended in Anthony Brown's post):>>>>>> # /etc/ppp/options>>> #>>> # Originally created by Jim Knoble <jmknoble@xxxxxxxxxxxxxxxxxxxxx>>>> # Modified for Debian by alvar Bray <alvar@xxxxxxxxxxx>>>> # Modified for PPP Server setup by Christoph Lameter>>> <clameter@xxxxxxxxxx>>>> #>>> # To quickly see what options are active in this file, use this command:>>> # egrep -v '#|^ *$' /etc/ppp/options>>>>>> # 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. 0x00000001>>> # represents '\x01', and 0x80000000 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>>> #noauth>>> # ... Unfortunately, fixing this properly in the peers file>>> # (/etc/ppp/peers/ppp0, typically) is apparently incompatible with the>>> # paradigm used by gnome-system-tools and system-tools-backend for>>> # managing the peers files. So in Ubuntu Feisty we change the default.>>>>>> # 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>>>>>> # Don't show the passwords when logging the contents of PAP packets.>>> # This is the default.>>> hide-password>>>>>> # When logging the contents of PAP packets, this option causes pppd to>>> # show the password string in the log message.>>> #show-password>>>>>> # 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 542>>>>>> # 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 IPCP negotiation and IP communication. This option should>>> # only be required if the peer is buggy and gets confused by requests>>> # from pppd for IPCP negotiation.>>> #noip>>>>>> # Disable magic number negotiation. With this option, pppd cannot>>> # detect a looped-back line.>>> #-mn>>>>>> # Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.>>> # 1500).>>> #-mru>>>>>> # Disable protocol field compression negotiation (use default, i.e.>>> # protocol field compression disabled).>>> #-pc>>>>>> # Require the peer to authenticate itself using PAP.>>> #+pap>>>>>> # Don't agree to authenticate using PAP.>>> #-pap>>>>>> # Require the peer to authenticate itself using CHAP [Cryptographic>>> # Handshake Authentication Protocol] authentication.>>> #+chap>>>>>> # Don't agree to authenticate using CHAP.>>> #-chap>>>>>> # Disable negotiation of Van Jacobson style IP header compression (use>>> # default, i.e. no compression).>>> #-vj>>>>>> # Increase debugging level (same as -d). If this option is given, pppd>>> # will log the contents of all control packets sent or received in a>>> # readable form. The packets are logged through syslog with facility>>> # daemon and level debug. This information can be directed to a file by>>> # setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If>>> # pppd is compiled with extra debugging enabled, it will log messages>>> # using facility local2 instead of daemon).>>> #debug>>>>>> # Append the domain name <d> to the local host name for authentication>>> # purposes. For example, if gethostname() returns the name porsche,>>> # but the fully qualified domain name is porsche.Quotron.COM, you would>>> # use the domain option to set the domain name to Quotron.COM.>>> #domain <d>>>>>>> # Enable debugging code in the kernel-level PPP driver. The argument n>>> # is a number which is the sum of the following values: 1 to enable>>> # general debug messages, 2 to request that the contents of received>>> # packets be printed, and 4 to request that the contents of transmitted>>> # packets be printed.>>> #kdebug n>>>>>> # Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer>>> # requests a smaller value via MRU negotiation, pppd will request that>>> # the kernel networking code send data packets of no more than n bytes>>> # through the PPP network interface.>>> #mtu <n>>>>>>> # Set the name of the local system for authentication purposes to <n>.>>> # This is a privileged option. With this option, pppd will use lines in>>> the>>> # secrets files which have <n> as the second field when looking for a>>> # secret to use in authenticating the peer. In addition, unless>>> overridden>>> # with the user option, <n> will be used as the name to send to the peer>>> # when authenticating the local system to the peer. (Note that pppd does>>> # not append the domain name to <n>.)>>> #name <n>>>>>>> # Enforce the use of the hostname as the name of the local system for>>> # authentication purposes (overrides the name option).>>> #usehostname>>>>>> # Set the assumed name of the remote system for authentication purposes>>> # to <n>.>>> #remotename <n>>>>>>> # Add an entry to this system's ARP [Address Resolution Protocol]>>> # table with the IP address of the peer and the Ethernet address of this>>> # system.>>> proxyarp>>>>>> # Use the system password database for authenticating the peer using>>> # PAP. Note: mgetty already provides this option. If this is specified>>> # then dialin from users using a script under Linux to fire up ppp wont>>> work.>>> # login>>>>>> # If this option is given, pppd will send an LCP echo-request frame to>>> the>>> # peer every n seconds. Normally the peer should respond to the>>> echo-request>>> # by sending an echo-reply. This option can be used with the>>> # lcp-echo-failure option to detect that the peer is no longer connected.>>> lcp-echo-interval 0>>>>>> # If this option is given, pppd will presume the peer to be dead if n>>> # LCP echo-requests are sent without receiving a valid LCP echo-reply.>>> # If this happens, pppd will terminate the connection. Use of this>>> # option requires a non-zero value for the lcp-echo-interval parameter.>>> # This option can be used to enable pppd to terminate after the physical>>> # connection has been broken (e.g., the modem has hung up) in>>> # situations where no hardware modem control lines are available.>>> lcp-echo-failure 0>>>>>> # Set the LCP restart interval (retransmission timeout) to <n> seconds>>> # (default 3).>>> #lcp-restart <n>>>>>>> # Set the maximum number of LCP terminate-request transmissions to <n>>>> # (default 3).>>> #lcp-max-terminate <n>>>>>>> # Set the maximum number of LCP configure-request transmissions to <n>>>> # (default 10).>>> #lcp-max-configure <n>>>>>>> # Set the maximum number of LCP configure-NAKs returned before starting>>> # to send configure-Rejects instead to <n> (default 10).>>> #lcp-max-failure <n>>>>>>> # Set the IPCP restart interval (retransmission timeout) to <n>>>> # seconds (default 3).>>> #ipcp-restart <n>>>>>>> # Set the maximum number of IPCP terminate-request transmissions to <n>>>> # (default 3).>>> #ipcp-max-terminate <n>>>>>>> # Set the maximum number of IPCP configure-request transmissions to <n>>>> # (default 10).>>> #ipcp-max-configure <n>>>>>>> # Set the maximum number of IPCP configure-NAKs returned before starting>>> # to send configure-Rejects instead to <n> (default 10).>>> #ipcp-max-failure <n>>>>>>> # Set the PAP restart interval (retransmission timeout) to <n> seconds>>> # (default 3).>>> #pap-restart <n>>>>>>> # Set the maximum number of PAP authenticate-request transmissions to>>> # <n> (default 10).>>> #pap-max-authreq <n>>>>>>> # Set the maximum time that pppd will wait for the peer to authenticate>>> # itself with PAP to <n> seconds (0 means no limit).>>> #pap-timeout <n>>>>>>> # Set the CHAP restart interval (retransmission timeout for>>> # challenges) to <n> seconds (default 3).>>> #chap-restart <n>>>>>>> # Set the maximum number of CHAP challenge transmissions to <n>>>> # (default 10).>>> #chap-max-challenge>>>>>> # If this option is given, pppd will rechallenge the peer every <n>>>> # seconds.>>> #chap-interval <n>>>>>>> # With this option, pppd will accept the peer's idea of our local IP>>> # address, even if the local IP address was specified in an option.>>> #ipcp-accept-local>>>>>> # With this option, pppd will accept the peer's idea of its (remote) IP>>> # address, even if the remote IP address was specified in an option.>>> #ipcp-accept-remote>>>>>> # Disable the IPXCP and IPX protocols.>>> # To let pppd pass IPX packets comment this out --- you'll probably also>>> # want to install ipxripd, and have the Internal IPX Network option>>> enabled>>> # in your kernel. /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.>>> noipx>>>>>> # Exit once a connection has been made and terminated. This is the>>> default,>>> # unless the `persist' or `demand' option has been specified.>>> #nopersist>>>>>> # Do not exit after a connection is terminated; instead try to reopen>>> # the connection.>>> #persist>>>>>> # Terminate after n consecutive failed connection attempts.>>> # A value of 0 means no limit. The default value is 10.>>> #maxfail <n>>>>>>> # Initiate the link only on demand, i.e. when data traffic is present.>>> # With this option, the remote IP address must be specified by the user>>> on>>> # the command line or in an options file. Pppd will initially configure>>> # the interface and enable it for IP traffic without connecting to the>>> peer.>>> # When traffic is available, pppd will connect to the peer and perform>>> # negotiation, authentication, etc. When this is completed, pppd will>>> # commence passing data packets (i.e., IP packets) across the link.>>> #demand>>>>>> # Specifies that pppd should disconnect if the link is idle for <n>>>> seconds.>>> # The link is idle when no data packets (i.e. IP packets) are being sent>>> or>>> # received. Note: it is not advisable to use this option with the>>> persist>>> # option without the demand option. If the active-filter option is>>> given,>>> # data packets which are rejected by the specified activity filter also>>> # count as the link being idle.>>> #idle <n>>>>>>> # Specifies how many seconds to wait before re-initiating the link after>>> # it terminates. This option only has any effect if the persist or>>> demand>>> # option is used. The holdoff period is not applied if the link was>>> # terminated because it was idle.>>> #holdoff <n>>>>>>> # Wait for up n milliseconds after the connect script finishes for a>>> valid>>> # PPP packet from the peer. At the end of this time, or when a valid PPP>>> # packet is received from the peer, pppd will commence negotiation by>>> # sending its first LCP packet. The default value is 1000 (1 second).>>> # This wait period only applies if the connect or pty option is used.>>> #connect-delay <n>>>>>>> # Packet filtering: for more information, see pppd(8)>>> # Any packets matching the filter expression will be interpreted as link>>> # activity, and will cause a "demand" connection to be activated, and>>> reset>>> # the idle connection timer. (idle option)>>> # The filter expression is akin to that of tcpdump(1)>>> #active-filter <filter-expression>>>>>>> Thank you again for your help!>>>>>> Devon>>>>>>>>>>>> --- On Sun, 1/18/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:>>>>>> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>>>> Subject: Re: USR 5637 USB ext modem Linux compatible but problem>>> connecting>>> To: "D Brewer" <interscientific@xxxxxxxxx>>>> Cc: "anthony" <anthonykbrown@xxxxxxxxxxxx>, discuss@xxxxxxxxxxxxx>>> Date: Sunday, January 18, 2009, 10:15 PM>>>>>>>>> -----Inline Attachment Follows----->>>>>> DB>>>>>> error 2 - An error was detected in processing the options given,>>> such as two mutually exclusive options being used.>>> ------>>>>>> This indicates that something is wrong/contradictory in the>>> /etc/ppp/options settings.>>>>>> Try using your changes one at a time, and send the options file to us>>> if you can't solve it.>>>>>> Seems that for your IP>>> Stupid mode>>> is necessary.>>>>>> MarvS>>>>>>>>> On Sun, Jan 18, 2009 at 6:11 PM, D Brewer <interscientific@xxxxxxxxx>>>> wrote:>>>> MarvS,>>>>>>>> Thank you for these tips. I made the chmod changes for PAP and CHAP>>>> according to the thread you referred me to. I am still not able to>>>> connect>>>> successfully. Here is the output from wvdial:>>>>>>>> $ wvdial>>>> --> WvDial: Internet dialer version 1.60>>>> --> Cannot get information for serial port.>>>> --> Initializing modem.>>>> --> Sending: ATZ>>>> ATZ>>>> OK>>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>>>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>>>> OK>>>> --> Modem initialized.>>>> --> Sending: ATDT4951000>>>> --> Waiting for carrier.>>>> ATDT4951000>>>> CONNECT 49333/ARQ/V90/LAPM/V42BIS>>>> --> Carrier detected. Starting PPP immediately.>>>> --> Starting pppd at Sun Jan 18 14:59:29 2009>>>> --> Pid of pppd: 7078>>>> --> Using interface ppp0>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> local IP address 64.40.61.252>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> remote IP address 64.40.40.6>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> primary DNS address 64.40.40.53>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> secondary DNS address 66.54.140.10>>>> --> pppd: ��[06][08]`�[06][08]>>>> Caught signal 2: Attempting to exit gracefully...>>>> --> Terminating on signal 15>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> Connect time 1.6 minutes.>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> pppd: ��[06][08]`�[06][08]>>>> --> Disconnecting at Sun Jan 18 15:01:08 2009>>>>>>>> When I commented out "stupid mode = yes", it seemed to have more>>>> troubles.>>>> Here is the wvdial output after commenting it out:>>>>>>>> $ wvdial>>>> --> WvDial: Internet dialer version 1.60>>>> --> Cannot get information for serial port.>>>> --> Initializing modem.>>>> --> Sending: ATZ>>>> ATZ>>>> OK>>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>>>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>>>> OK>>>> --> Modem initialized.>>>> --> Sending: ATDT4951000>>>> --> Waiting for carrier.>>>> ATDT4951000>>>> CONNECT 48000/ARQ/V90/LAPM/V42BIS>>>> --> Carrier detected. Waiting for prompt.>>>> CVX Access Switch.>>>> Access is restricted to authorized users only.>>>> login:>>>> --> Looks like a login prompt.>>>> --> Sending: guest>>>> guest>>>> password:>>>> --> Looks like a password prompt.>>>> --> Sending: (password)>>>> Valid commands are:>>>> quit Hang up and disconnect>>>> help List valid commands>>>>>>>>> --> Hmm... a prompt. Sending "ppp".>>>> ppp>>>> 'ppp' is not a valid command.>>>> Valid commands are:>>>> quit Hang up and disconnect>>>> help List valid commands>>>>>>>>> --> Hmm... a prompt. Sending "ppp".>>>> ppp>>>> 'ppp' is not a valid command.>>>> Valid commands are:>>>> quit Hang up and disconnect>>>> help List valid commands>>>>>>>>> --> Hmm... a prompt. Sending "ppp".>>>> ppp>>>> 'ppp' is not a valid command.>>>> Valid commands are:>>>> quit Hang up and disconnect>>>> help List valid commands>>>>>>>>> --> Don't know what to do! Starting pppd and hoping for the best.>>>> --> Starting pppd at Sun Jan 18 14:55:41 2009>>>> --> Pid of pppd: 7070>>>> --> Using interface ppp0>>>> --> pppd: Ч[06][08]��[06][08]>>>> --> pppd: Ч[06][08]��[06][08]>>>> --> pppd: Ч[06][08]��[06][08]>>>> --> pppd: Ч[06][08]��[06][08]>>>> Caught signal 2: Attempting to exit gracefully...>>>> --> Terminating on signal 15>>>> --> pppd: Ч[06][08]��[06][08]>>>> --> pppd: Ч[06][08]��[06][08]>>>> --> Disconnecting at Sun Jan 18 14:57:41 2009>>>>>>>> Thank you for pushing the solution attempt along. Any further ideas>>>> about>>>> how to overcome the remaining problem(s)?>>>>>>>> Devon>>>>>>>> --- On Sun, 1/18/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>>>>> wrote:>>>>>>>> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>>>>> Subject: Re: USR 5637 USB ext modem Linux compatible but problem>>>> connecting>>>> To: "D Brewer" <interscientific@xxxxxxxxx>>>>> Cc: "anthony" <anthonykbrown@xxxxxxxxxxxx>, discuss@xxxxxxxxxxxxx>>>> Date: Sunday, January 18, 2009, 2:32 PM>>>>>>>>>>>> -----Inline Attachment Follows----->>>>>>>> DB>>>>>>>> RE: --> Warning: Could not modify /etc/ppp/pap-secrets: Permission>>>> denied>>>> --> --> PAP (Password Authentication Protocol) may be flaky.>>>> ---->>>> This is a known problem, with solution:>>>> http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html>>>>>>>> Minor issue:>>>>> --> Carrier detected. Starting PPP immediately.>>>> If your wvdial.conf has enabled>>>> Stupid Modem = 1 (or yes)>>>> try commenting it out. There will be then be more negotiation with the>>>> IP,>>>> which may enable higher speeds.>>>>>>>> MarvS>>>>>>>>>>>>>>>>>>>> On Sun, Jan 18, 2009 at 4:33 PM, D Brewer <interscientific@xxxxxxxxx>>>>> wrote:>>>>> Thank you, MarvS. I enabled passive mode in the /etc/ppp/options file>>>>> (by>>>>> removing the # before the corresponding line) and set both lcp-echo>>>>> interval>>>>> and lcp-echo-failure to 0.>>>>>>>>>> Here is the output from lsusb:>>>>> ~$ lsusb>>>>> Bus 003 Device 004: ID 0baf:0303 U.S. Robotics>>>>> Bus 003 Device 001: ID 0000:0000>>>>> Bus 002 Device 001: ID 0000:0000>>>>> Bus 001 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card>>>>> Reader>>>>> Bus 001 Device 003: ID 0a81:0101 Chesen Electronics Corp. Keyboard>>>>> Bus 001 Device 001: ID 0000:0000>>>>>>>>>> After making the changes to /etc/ppp/options, I tried both wvdial and>>>>> the>>>>> Ubuntu network manager several times, but failed to connect>>>>> successfully>>>>> each time (that is, similar behavior as before the changes to the>>>>> options>>>>> file). Here is the output from wvdial:>>>>>>>>>> $ wvdial>>>>> --> WvDial: Internet dialer version 1.60>>>>> --> Cannot get information for serial port.>>>>> --> Initializing modem.>>>>> --> Sending: ATZ>>>>> ATZ>>>>> OK>>>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>>>>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>>>>> OK>>>>> --> Modem initialized.>>>>> --> Sending: ATDT4951000>>>>> --> Waiting for carrier.>>>>> ATDT4951000>>>>> CONNECT 49333/ARQ/V90/LAPM/V42BIS>>>>> --> Carrier detected. Starting PPP immediately.>>>>> --> Starting pppd at Sun Jan 18 13:19:07 2009>>>>> --> Warning: Could not modify /etc/ppp/pap-secrets: Permission denied>>>>> --> --> PAP (Password Authentication Protocol) may be flaky.>>>>> --> Warning: Could not modify /etc/ppp/chap-secrets: Permission denied>>>>> --> --> CHAP (Challenge Handshake) may be flaky.>>>>> --> Pid of pppd: 6902>>>>> --> Using interface ppp0>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> local IP address 66.109.195.74>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> remote IP address 10.64.64.64>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> primary DNS address 64.40.40.51>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> secondary DNS address 66.54.140.10>>>>> --> pppd: ��[06][08]б[06][08]>>>>> Caught signal 2: Attempting to exit gracefully...>>>>> --> Terminating on signal 15>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> Connect time 1.1 minutes.>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> pppd: ��[06][08]б[06][08]>>>>> --> Disconnecting at Sun Jan 18 13:20:17 2009>>>>>>>>>> By the way, I've been canceling the connection attempts in wvdial by>>>>> hitting>>>>> Ctrl C.>>>>>>>>>> I don't know why the errors appear with respect to the secrets files.>>>>> I've>>>>> been trying two different ISPs, and before trying Anthony's procedures,>>>>> I>>>>> switched back to the ISP I mentioned in my prior message. I've checked>>>>> both>>>>> secrets files and they have the required login names and passwords for>>>>> the>>>>> selected ISP.>>>>>>>>>> Any ideas?>>>>>>>>>> Thank you very much!>>>>>>>>>> Devon>>>>>>>>>>>>>>> --- On Sun, 1/18/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>>>>>> wrote:>>>>>>>>>> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>>>>>> Subject: Re: USR 5637 USB ext modem Linux compatible but problem>>>>> connecting>>>>> To: "D Brewer" <interscientific@xxxxxxxxx>, "anthony">>>>> <anthonykbrown@xxxxxxxxxxxx>>>>>> Cc: discuss@xxxxxxxxxxxxx>>>>> Date: Sunday, January 18, 2009, 9:44 AM>>>>>>>>>>>>>>> -----Inline Attachment Follows----->>>>>>>>>> Anthony,>>>>>>>>>> Please work with DB>>>>>>>>>> DB>>>>>>>>>> You can do requried edits with:>>>>> $ sudo gedit /etc/ppp/options>>>>>>>>>> for>>>>> error 15 - The link was terminated because the peer is not>>>>> responding to echo requests.>>>>> ---->>>>> Seems like the problem solved by:>>>>> ============================>>>>> anthony <anthonykbrown@xxxxxxxxxxxx>>>>>> date Wed, Dec 24, 2008 at 9:54 PM>>>>> subject Re: Anthony Brown , US Ubuntu kernel 2.6.24-19-generic Agere>>>>> softmodem>>>>>>>>>>>>>>> Just wanted to update you on my progress. I am finally writing from>>>>> within Linux!!! I have successfully connected via the softmodem. I>>>>> enabled passive mode in /etc/ppp/options and earlier today had changed>>>>> lcp-echo interval and lcp-echo-failure to 0, which also got the>>>>> notebook>>>>> to connect via USB modem.>>>>>>>>>> ------------------------->>>>> On Sun, Jan 18, 2009 at 10:02 AM, Marvin Stodolsky>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:>>>>>> DB,>>>>>>>>>>>> Do>>>>>> $ man pppd>>>>>> enter a>>>>>> /error>>>>>> to search down to the errors section.An "n" will take you to the next>>>>>> "error" instance. Thus see what>>>>>> error>>>>>> 15>>>>>> is.>>>>>>>>>>>> Also please do a>>>>>> $ lsusb>>>>>> and report to us the info on your modem.>>>>>>>>>>>> I'm not under Linux now, so cannot yet suggest more.>>>>>>>>>>>> MarvS>>>>>>>>>>>>>>>>>>>>>>>> On Sun, Jan 18, 2009 at 12:57 AM, D Brewer <interscientific@xxxxxxxxx>>>>>>> wrote:>>>>>>> My last request for help from this list a couple of weeks ago ended>>>>>>> with>>>>>>> the conclusion that my internal modem was not able to work with Linux>>>>>>> (the>>>>>>> machine runs Ubuntu 8.04). So I bought an external USB modem that is>>>>>>> advertised as Linux compatible (the USR 5637 -- see>>>>>>> http://www.usr.com/support/product-template.asp?prod=5637). When I>>>>>>> plugged>>>>>>> the modem in at first it was not recognized. I searched around on>>>>>>> the>>>>>>> web>>>>>>> and found some instructions that were useful>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (http://www.linuxquestions.org/questions/dreamlinux-82/dell-1535-ubundu-modem-disaster-690995/).>>>>>>> I followed the instructions, and was able to get the modem to be>>>>>>> recognized>>>>>>> by wvdial (I edited the Ubuntu desktop network manager to include the>>>>>>> dev/ttyACM0 modem as well).>>>>>>>>>>>>>> The modem seems to connect with wvdial, but I'm not able to browse>>>>>>> web>>>>>>> pages in Firefox (browse active online sites). The modem's power and>>>>>>> data>>>>>>> lights are on when the modem communicates with the ISP.>>>>>>>>>>>>>> Here is the output from wvdial:>>>>>>>>>>>>>> $ sudo wvdial>>>>>>> --> WvDial: Internet dialer version 1.60>>>>>>> --> Cannot get information for serial port.>>>>>>> --> Initializing modem.>>>>>>> --> Sending: ATZ>>>>>>> ATZ>>>>>>> OK>>>>>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>>>>>>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0>>>>>>> OK>>>>>>> --> Modem initialized.>>>>>>> --> Sending: ATDT4951000>>>>>>> --> Waiting for carrier.>>>>>>> ATDT4951000>>>>>>> CONNECT 49333/ARQ/V90/LAPM/V42BIS>>>>>>> --> Carrier detected. Waiting for prompt.>>>>>>> CVX Access Switch.>>>>>>> Access is restricted to authorized users only.>>>>>>> login:>>>>>>> --> Looks like a login prompt.>>>>>>> --> Sending: guest>>>>>>> guest>>>>>>> password:>>>>>>> --> Looks like a password prompt.>>>>>>> --> Sending: (password)>>>>>>> Exiting shell, and starting PPP session.>>>>>>> ~[7f]}#@!}!}!} }8}!}$}%\}"}&} }*} } }%}&%59n}'}"}(}"iH~>>>>>>> --> PPP negotiation detected.>>>>>>> --> Starting pppd at Sat Jan 17 19:40:21 2009>>>>>>> --> Pid of pppd: 8231>>>>>>> --> Using interface ppp0>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> local IP address 64.40.61.66>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> remote IP address 64.40.40.6>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> primary DNS address 64.40.40.53>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> secondary DNS address 66.54.140.10>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> Caught signal 2: Attempting to exit gracefully...>>>>>>> --> Terminating on signal 15>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> Connect time 2.6 minutes.>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> pppd: Ч[06][08]��[06][08]>>>>>>> --> Disconnecting at Sat Jan 17 19:43:02 2009>>>>>>>>>>>>>>>>>>>>> The login name "guest" is standard for this ISP (it's a free ISP,>>>>>>> nocharge.com).>>>>>>>>>>>>>> I've tried this many times from wvdial with the same result (even>>>>>>> after>>>>>>> rebooting), and I've also tried to connect with the Ubuntu network>>>>>>> manager,>>>>>>> but it shows no visible sign of connection (network manager icon>>>>>>> shows>>>>>>> no>>>>>>> connection and Firefox is unable to connect with web sites).>>>>>>>>>>>>>> Do any of you have an idea what might be the problem? What other>>>>>>> information do you need to help diagnose the problem?>>>>>>>>>>>>>> Thank you yet again for your help!>>>>>>>>>>>>>> Devon>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
