modem connection

I am trying to set up my modem. It is a hardware modem, so I don’t think drivers should be an issue. At first I was trying to connect with KPPP, but have switched to KInternet. It seems to recognize the modem, dial in, and even make a successful connection. However, I cannot do anything (the browser thinks it is offline, ping results in 100% packet loss). Here is the Kinternet log:

SuSE Meta pppd (smpppd-ifcfg), Version 1.59_SVN31 on linux-9ubn.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: → WvDial: Internet dialer version 1.60
pppd[0]: → Initializing modem.
pppd[0]: → Sending: ATZ
pppd[0]: ATZ
pppd[0]: OK
pppd[0]: → Sending: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: OK
pppd[0]: → Sending: ATM1
pppd[0]: ATM1
pppd[0]: OK
pppd[0]: → Modem initialized.
pppd[0]: → Sending: ATDT9805000
pppd[0]: → Waiting for carrier.
pppd[0]: ATDT9805000
pppd[0]: CONNECT 28800 V42bis
pppd[0]: → Carrier detected. Waiting for prompt.
pppd[0]: ** Ascend TNT Terminal Server **
pppd[0]: Login:
pppd[0]: → Looks like a login prompt.
pppd[0]: → Sending: dial
pppd[0]: dial
pppd[0]: Password:
pppd[0]: → Looks like a password prompt.
pppd[0]: → Sending: (password)
pppd[0]: Entering PPP Session.
pppd[0]: IP address is 209.172.23.217
pppd[0]: MTU is 1524.
pppd[0]: → Looks like a welcome message.
pppd[0]: Script /usr/bin/wvdial --chat --no-syslog --config /var/run/smpppd/chat-modem0.conf smpppd finished (pid 13236), status = 0x0
pppd[0]: Serial connection established.
pppd[0]: Renamed interface ppp0 to modem0
pppd[0]: Using interface modem0
Status is: connecting
pppd[0]: Connect: modem0 <–> /dev/ttyS4
pppd[0]: local IP address 209.172.23.217
pppd[0]: remote IP address 209.172.12.137
pppd[0]: primary DNS address 209.172.0.5
pppd[0]: secondary DNS address 209.172.0.8
pppd[0]: Script /etc/ppp/ip-up finished (pid 13260), status = 0x0
Status is: connected
Status is: disconnecting
pppd[0]: Terminating on signal 15
pppd[0]: Connect time 8.4 minutes.
pppd[0]: Sent 1084 bytes, received 296 bytes.
pppd[0]: Connection terminated.
pppd[0]: Script /etc/ppp/ip-down finished (pid 13520), status = 0x0
Status is: disconnected
pppd[0] died: pppd received a signal (exit code 5)

The disconnect occurred when I asked it to, not spontaneously. Any ideas?

thomasscofield wrote:
> I am trying to set up my modem. It is a hardware modem, so I don’t
> think drivers should be an issue. At first I was trying to connect with
> KPPP, but have switched to KInternet. It seems to recognize the modem,
> dial in, and even make a successful connection. However, I cannot do
> anything (the browser thinks it is offline, ping results in 100% packet
> loss). Here is the Kinternet log:
…]
> Status is: connecting
> pppd[0]: Connect: modem0 <–> /dev/ttyS4
> pppd[0]: local IP address 209.172.23.217
> pppd[0]: remote IP address 209.172.12.137
> pppd[0]: primary DNS address 209.172.0.5
> pppd[0]: secondary DNS address 209.172.0.8
> pppd[0]: Script /etc/ppp/ip-up finished (pid 13260), status = 0x0
> Status is: connected
>
> The disconnect occurred when I asked it to, not spontaneously. Any
> ideas?

Most likely your resolv.conf or route tables haven’t been updated.
Do ‘/sbin/ip route show’ (or ‘/sbin/route -n’) and ‘cat /etc/resolv.conf’?

/sbin/ip route show
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.79 metric 1
127.0.0.0/8 dev lo scope link
default via 192.168.1.254 dev eth0 proto static

cat /etc/resolv.conf

/etc/resolv.conf file autogenerated by netconfig!

Before you change this file manually, consider to define the

static DNS configuration using the following variables in the

/etc/sysconfig/network/config file:

NETCONFIG_DNS_STATIC_SEARCHLIST

NETCONFIG_DNS_STATIC_SERVERS

NETCONFIG_DNS_FORWARDER

or disable DNS configuration updates via netconfig by setting:

NETCONFIG_DNS_POLICY=’’

See also the netconfig(8) manual page and other documentation.

Note: Manual change of this file disables netconfig too, but

may get lost when this file contains comments or empty lines

only, the netconfig settings are same with settings in this

file and in case of a “netconfig update -f” call.

Please remove (at least) this line when you modify the file!

search gateway.2wire.net
nameserver 192.168.1.254

Right now I have this machine hooked to a DSL modem, which may be what is showing up with the line “search gateway.2wire.nte”. This is a computer I’m setting up for someone else, and the norm will be that nothing but dialup is available.

What should I be looking for?

thomasscofield wrote:
> /sbin/ip route show
> 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.79
> metric 1
> 127.0.0.0/8 dev lo scope link
> default via 192.168.1.254 dev eth0 proto static
>
> cat /etc/resolv.conf
> search gateway.2wire.net
> nameserver 192.168.1.254
>
> Right now I have this machine hooked to a DSL modem, which may be what
> is showing up with the line “search gateway.2wire.nte”. This is a
> computer I’m setting up for someone else, and the norm will be that
> nothing but dialup is available.
>
> What should I be looking for?

The default route should go to 209.172.12.137 and in resolv.conf the addresses
209.172.0.5 and 209.172.0.should be named with ‘nameserver’.

This should be done by pppd, so if it isn’t, there’s a problem with the dial-up
script.

I have not had any direct interaction with a script. In YaST I ran the Modem tool, and after it detected the modem I entered the provider information. Then I installed KInternet. Obviously something happens when I disconnect the DSL modem and try to connect using the modem—one of the ip addresses you mentioned shows up. But what you said should appear in resolv.con does not. Any suggestions?

linux-9ubn:/home/thomas # /sbin/ip route show
209.172.12.137 dev modem0 proto kernel scope link src 209.172.23.218
127.0.0.0/8 dev lo scope link
default dev modem0 scope link

linux-9ubn:/home/thomas # cat /etc/resolv.conf

/etc/resolv.conf file autogenerated by netconfig!

Before you change this file manually, consider to define the

static DNS configuration using the following variables in the

/etc/sysconfig/network/config file:

NETCONFIG_DNS_STATIC_SEARCHLIST

NETCONFIG_DNS_STATIC_SERVERS

NETCONFIG_DNS_FORWARDER

or disable DNS configuration updates via netconfig by setting:

NETCONFIG_DNS_POLICY=’’

See also the netconfig(8) manual page and other documentation.

Note: Manual change of this file disables netconfig too, but

may get lost when this file contains comments or empty lines

only, the netconfig settings are same with settings in this

file and in case of a “netconfig update -f” call.

Please remove (at least) this line when you modify the file!

See this thread:

problem in connecting with wvdial - openSUSE Forums

thomasscofield wrote:
> I have not had any direct interaction with a script. In YaST I ran the
> Modem tool, and after it detected the modem I entered the provider
> information. Then I installed KInternet. Obviously something happens
> when I disconnect the DSL modem and try to connect using the modem—one
> of the ip addresses you mentioned shows up. But what you said should
> appear in resolv.con does not. Any suggestions?

Other than manually creating these entries? No. I haven’t used any modem
scripts for a long time, so I can’t say anything to help you further.

>
> linux-9ubn:/home/thomas # /sbin/ip route show
> 209.172.12.137 dev modem0 proto kernel scope link src 209.172.23.218
>
> 127.0.0.0/8 dev lo scope link
> default dev modem0 scope link

That looks fine at least.

> linux-9ubn:/home/thomas # cat /etc/resolv.conf
> ### /etc/resolv.conf file autogenerated by netconfig!

But there is not nameserver entry here, so that’s why you can’t connect to any
site by name.

I’m afraid I don’t know what to put for a nameserver. I found a couple public nameservers listed online at

Free fast Public DNS Servers List

and while I was hooked up via ethernet there was a nameserver listed. So, I kept the one that was there when I was wired and added two from the website above, making the final lines in resolv.conf appear as

search gateway.2wire.net
nameserver 67.138.54.100
nameserver 156.154.70.1
nameserver 192.168.1.254

These two lines appear in wvdial.conf (don’t know if they’re relevant or not)

Auto DNS = 1
Check DNS = 1

(Perhaps obviously,) I’ve never explicitly indicated a nameserver before, and I haven’t the least idea how to choose one.

i dont know if it will help or if it is relevant.
i once had a similar problem.i changed the ‘network setup method’ to traditional method of ifup instead of network manager (under network settings/global options ) and everything was fine.

i use a dsl modem but my isp provides all the name servers and gateways dynamically.so i dontknow about setting nameservers and all.so i may be wrong

On Thu January 29 2009 10:46 pm, thomasscofield wrote:

>
> I’m afraid I don’t know what to put for a nameserver. I found a couple
> public nameservers listed online at
>
> ‘Free fast Public DNS Servers List’
> (http://theos.in/windows-xp/free-fast-public-dns-server-list/)
>
> and while I was hooked up via ethernet there was a nameserver listed.
> So, I kept the one that was there when I was wired and added two from
> the website above, making the final lines in resolv.conf appear as
>
> search gateway.2wire.net
> nameserver 67.138.54.100
> nameserver 156.154.70.1
> nameserver 192.168.1.254
>
> These two lines appear in wvdial.conf (don’t know if they’re relevant
> or not)
>
> Auto DNS = 1
> Check DNS = 1
>
> (Perhaps obviously,) I’ve never explicitly indicated a nameserver
> before, and I haven’t the least idea how to choose one.
>
>
Thomas;
Usually the ISP provides the nameserver. When you dial in you must be using
some ISP. You should be able to get the nameserver address through them.
192.168.x.y is a private address range, so unless you are on a private
network 192.168.1.254 will most likely be invalid.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

I have a laptop that I used for the first time to connect to this same ISP in Windows. Once connected, it was using these nameservers

DNS address 209.172.0.5
DNS address 209.172.0.8

which I have now in my resolv.conf:

linux-9ubn:/home/thomas # cat /etc/resolv.conf

/etc/resolv.conf file autogenerated by netconfig!

Before you change this file manually, consider to define the

static DNS configuration using the following variables in the

/etc/sysconfig/network/config file:

NETCONFIG_DNS_STATIC_SEARCHLIST

NETCONFIG_DNS_STATIC_SERVERS

NETCONFIG_DNS_FORWARDER

or disable DNS configuration updates via netconfig by setting:

NETCONFIG_DNS_POLICY=’’

See also the netconfig(8) manual page and other documentation.

Note: Manual change of this file disables netconfig too, but

may get lost when this file contains comments or empty lines

only, the netconfig settings are same with settings in this

file and in case of a “netconfig update -f” call.

#search gateway.2wire.net
#nameserver 67.138.54.100
#nameserver 156.154.70.1
#nameserver 192.168.1.254

#nameserver 69.111.95.106
#nameserver 206.196.151.153
#nameserver 69.111.95.107
nameserver 209.172.0.5
nameserver 209.172.0.8

Nevertheless, wvdial cannot seem to interact with them.

linux-9ubn:/home/thomas # wvdial
→ WvDial: Internet dialer version 1.60
→ 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.
→ Idle Seconds = 300, disabling automatic reconnect.
→ Please enter password (or empty password to stop):
→ Sending: ATDT9805000
→ Waiting for carrier.
ATDT9805000
CONNECT 28800 V42bis
→ Carrier detected. Starting PPP immediately.
→ Starting pppd at Fri Jan 30 05:50:28 2009
→ Pid of pppd: 5742
→ Using interface ppp0
→ pppd: ������[06][08]��[06][08][01]
→ pppd: ������[06][08]��[06][08][01]
→ pppd: ������[06][08]��[06][08][01]
→ pppd: ������[06][08]��[06][08][01]
→ pppd: ������[06][08]��[06][08][01]
→ local IP address 209.172.21.105
→ pppd: ������[06][08]��[06][08][01]
→ remote IP address 209.172.12.137
→ pppd: ������[06][08]��[06][08][01]
→ primary DNS address 209.172.0.5
→ pppd: ������[06][08]��[06][08][01]
→ secondary DNS address 209.172.0.8
→ pppd: ������[06][08]��[06][08][01]
→ Script /etc/ppp/ip-up run successful
→ Default route Ok.
→ warning, can’t find address for www.suse.de
→ warning, address lookup does not work
→ Nameserver (DNS) failure, the connection may not work.
→ Connected… Press Ctrl-C to disconnect
→ pppd: ������[06][08]��[06][08][01]
^CCaught signal 2: Attempting to exit gracefully…
→ Terminating on signal 15
→ pppd: ������[06][08]��[06][08][01]
→ Connect time 4.3 minutes.
→ pppd: ������[06][08]��[06][08][01]
→ pppd: ������[06][08]��[06][08][01]
→ Disconnecting at Fri Jan 30 05:54:49 2009

Is it possible that this ISP is set up having no ability to communicate with a linux machine?

On Fri January 30 2009 05:56 am, thomasscofield wrote:

>
> I have a laptop that I used for the first time to connect to this same
> ISP in Windows. Once connected, it was using these nameservers
>
> DNS address 209.172.0.5
> DNS address 209.172.0.8
>
> which I have now in my resolv.conf:
>
<snip>
>
> Nevertheless, wvdial cannot seem to interact with them.
>
<snip>
Thomas;

Can you ping them? What about Google ?


ping -c5 209.172.0.5
ping -c5 64.233.169.103


P. V.
“We’re all in this together, I’m pulling for you.” Red Green

I cannot ping either one—100% packet loss.

thomas@linux-9ubn:~> ping -c5 209.172.0.5
PING 209.172.0.5 (209.172.0.5) 56(84) bytes of data.
From 192.168.1.79 icmp_seq=3 Destination Host Unreachable
From 192.168.1.79 icmp_seq=4 Destination Host Unreachable
From 192.168.1.79 icmp_seq=5 Destination Host Unreachable
^C
— 209.172.0.5 ping statistics —
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4018ms
, pipe 2
thomas@linux-9ubn:~> ping -c5 64.233.169.103
PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.
From 192.168.1.79 icmp_seq=3 Destination Host Unreachable
From 192.168.1.79 icmp_seq=4 Destination Host Unreachable
From 192.168.1.79 icmp_seq=5 Destination Host Unreachable

— 64.233.169.103 ping statistics —
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4016ms
, pipe 2

On Sat January 31 2009 08:36 am, thomasscofield wrote:

>
> I cannot ping either one—100% packet loss.
>
> thomas@linux-9ubn:~> ping -c5 209.172.0.5
> PING 209.172.0.5 (209.172.0.5) 56(84) bytes of data.
> From 192.168.1.79 icmp_seq=3 Destination Host Unreachable
> From 192.168.1.79 icmp_seq=4 Destination Host Unreachable
> From 192.168.1.79 icmp_seq=5 Destination Host Unreachable
> ^C
> — 209.172.0.5 ping statistics —
> 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time
> 4018ms
> , pipe 2
> thomas@linux-9ubn:~> ping -c5 64.233.169.103
> PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.
> From 192.168.1.79 icmp_seq=3 Destination Host Unreachable
> From 192.168.1.79 icmp_seq=4 Destination Host Unreachable
> From 192.168.1.79 icmp_seq=5 Destination Host Unreachable
>
> — 64.233.169.103 ping statistics —
> 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time
> 4016ms
> , pipe 2
>
>
Thomas;
It appears to me, you are not actually connecting to your ISP.

  1. For the time being try disabling the firewall, just to make sure it is not
    getting in the way.
  2. If dropping the firewall does not help ( and I don’t think it will); go
    over all your modem settings in YAST. Did YAST automatically detect your
    modem? Be sure to verify your username/password is correct.
  3. Google is your friend.

    P. V.
    “We’re all in this together, I’m pulling for you.” Red Green

I seem to have found my answer at this link:

https://www.linuxquestions.org/questions/linux-general-1/modem-works-but-no-internet.-ethernet-ok-153780/

The upshot seems to be that I have to take down eth0 before I can connect. I am using dialup to post this reply.

On Sat January 31 2009 05:16 pm, thomasscofield wrote:

>
> I seem to have found my answer at this link:
>
> http://tinyurl.com/catgwy
>
> The upshot seems to be that I have to take down eth0 before I can
> connect. I am using dialup to post this reply.
>
>
Glad to hear you got it to work. Thanks for the update.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green