wvdial problem on slack 10

[exceed]

hi there,

i've tried everything i know ... i searched the web ... i've spent more than 12 hours trying and trying ... nothing. than i decided to ask in this forum.

i have a problem with dial-up connection using wvdial on slack 10. it just don't work. i have 3com ISDN modem connected on /dev/ttyS0. no problems here, the slack detects it as cham. since i don't use X (yep, i love console ) i tried to connect to net via wvdial ...

--> Modem initialized.
--> Sending ATDT [my ISP number here]
--> Connect 64000
--> Carrier detected. Starting PPP imediately.
--> starting ppp at Mon Nov 1 23:36:30: 2004

*and it stops here*

no pppd pid ... nothing ... it just hangs

i have changed some settings in /etc/ppp/options like recomended here:

httpp://www.uklinux.net/support/connect.php3

but it didn't worked. i think it is something in my pppd configuration, but i just can't figure it out. i have also tried to connect via minicom and the sad story continues

here's the output:

--> initializing modem
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
AT [i'm checking the modem)
OK [it seems everything's OK]
--> Dialing directory
--> dialing ...
--> Connected. Press any key to continue.
--> CONNECTED! 64000
--> [some char string here]
--> NO CARRIER

you see, that my problem
i would really appreciate if anyone can help. thanx for your time...

[gaxprels]

Show us the contents of your pppd config files including the pap and chap scripts. Also make sure you are using the method (pap or chap) supported by your ISP. Just mangle your username and give us a string of *** for your password when you show them

[exceed]

thanx for reply. here are the /etc/ppp config scripts. some comments were removed for abrevation:

/etc/ppp/options

# /etc/ppp/options
# ...........
# Two Servers can be remotely configured
# dns-addr 192.168.1.1
# dns-addr 192.168.1.2

# Specify which WINS Servers the incoming connection Win95 or WinNT should use
# wins-addr 192.168.1.50
# wins-addr 192.168.1.51

# .......
#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.
# For a PPP Server with script based logins not using PAP or CHAP
# you need to disable this setting.
#auth

# Do not require the other end of the connection to authenticate itself.
# This option is dangerous if pppd is setuid.
# If you also have ethernet and are having problems getting PPP to connect
# over a modem, try this option.
noauth

# 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

# ...........
#escape 11,13,ff

# Don't use the modem control lines.
#local

# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
lock

# Use the modem control lines.* On Ultrix, this option implies hardware
# flow control, as for the crtscts option.* (This option is not fully
# implemented.)
modem

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation.* pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128.* The default MRU value is 1500.* A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data).
#mru 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 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

# ..........
#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>

# 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. Under Linux, the echo-request is sent when
# no packets have been received from the peer for 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 30

# 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 4

# 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 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


/etc/ppp/chap-secrets

# Secrets for authemtication using CHAP
# client* * *server* * *secret* * * * * IP address
exceed ** * *password


/etc/ppp/pap-secrets

# Secrets for authemtication using PAP
# client* * *server* * *secret* * * * * IP address
exceed ** * *password


/etc/ppp/resolv.conf

nameserver 217.72.64.10
nameserver 217.72.64.11


/etc/wvdial.conf

[Dialer Defaults]
Modem = /dev/ttyS0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55
Phone = 088832480
Username = exceed
Password = password


if you need any other information just let me know ...

[friskydrifter]

in /etc/wvdial.conf under your dialer defaults you need to add

New PPPD

I think that might help

[exceed]

i have added the line New PPPD in /etc/wvdial.conf but it didn't work. here's the output:

--> WvDial: Internet dialer version 1.41
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending ATQ0 V1 E1 S0=0 &C1 &D2 S11=55
OK
--> Modem initialized.
--> Sending: ATDT [my ISP phone number]
--> Wainting for carrier.
ATDT [my ISP phone number]
CONNECT 64000
--> Carrier detected. Waiting for prompt.
[some char sting here]
--> PPP negotiation detected.
--> Starting pppd at Wed Nov 3 17:43:31 2004

and it stops here...
it doesn't hangs. it just waits and nothing happens. i can't connect to net or use ping, traceroute ...
i executed ps -aux and i saw pppd is running. it seems that everything works ok. strange ...

[friskydrifter]

type ifconfig

what does that show when you are connected.
what is the output of ping

[exceed]

here's the output:

ifconfig

lo Link encap: Local Loopback
inetd addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:!
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

ppp0 Link encp:Point-to-Point Protocol
inetd addr:217.72.87.225 P-t-P:217.72.64.175 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:323 (232.0 b) TX bytes:221 (221.0 b)


ping 216.239.59.104
PING 216.239.59.104 (216.239.59.104) 56(84) bytes of data.
64 bytes from 216.239.59.104: icmp_seq=1 ttl=247 time=101 ms
64 bytes from 216.239.59.104: icmp_seq=2 ttl=247 time=100 ms
64 bytes from 216.239.59.104: icmp_seq=3 ttl=247 time=100 ms

--- 216.239.59.104 ping statistics ---

3 packets transmited, 3 received, 0% packets loss
rtt min/avg/max/mdev = 99.965/102.128/109.985/3.960 ms

it looks ok, but i can't connetc through links or lynx. it seems that it's something wrong with my DNS configuration...

[paradox]

Well your definitely connected. What I am thinking is you don't have dhcp or pump running. You definitely have connection if you can ping addresses. You need to get dhcpd or pump(my personal favorite) and install it then run that after you connect. This of course serves as your resolver and after that you should be able to use any browser.

Aragorn

[exceed]

Thanx for info Aragorn. I have installed dhcpcd. I did exactly as explaned here:

http://yolinux.com/MINI-HOWTO/DHCP.html

it works. yep, i'm connected now, but i can use links or lynx only through IP address and not hostname. unable to connect to hostname is the response from both browsers. it seems that i have misconfigured /etc/resolve.conf or some other DNS configuration script.

[paradox]

Well lets have a copy of your /etc/resolv.conf file

Oh lets also have a copy of your /etc/dhcpd.conf

Aragorn