modem monitor does not connect or do anything useful

Bug #14103 reported by lexual
8
Affects Status Importance Assigned to Milestone
gnome-applets (Ubuntu)
Fix Released
High
Michael Vogt

Bug Description

modem monitor doesn't connect to the internet, it asks for password and it asks
me if I want to connect but it doesn't do anything. I can connect perfectly via
pon. I am using hoary.

Also, if I have connected via pon, the tooltip for modem monitor still tells me
I am "not connected".

Revision history for this message
Sebastien Bacher (seb128) wrote :

reassign to the right email

Revision history for this message
rubinstein (rubinstein) wrote :

The same here with a Dell Latitude Laptop and a ELSA Microlink 56k Modem. Modem
applet does nothing when I want to connect; pon and poff work as expected.

Revision history for this message
Michael Vogt (mvo) wrote :

I just uploaded gnome-applets_2.10.0-0ubuntu4. This should fix the problem. Can
you please confirm that it works for you with the new version?

Thanks,
 Michael

Revision history for this message
lexual (lexhider) wrote :

I just upgraded and this didn't fix it.

Here's /var/log/messages after trying to connect twice with modem monitor.

Mar 29 10:57:06 localhost pppd[9651]: pppd 2.4.2 started by root, uid 0
Mar 29 10:57:08 localhost pppd[9651]: Exit.
Mar 29 10:59:32 localhost pppd[10406]: pppd 2.4.2 started by root, uid 0
Mar 29 10:59:34 localhost pppd[10406]: Exit.

Then it worked fine with pon.

Mar 29 10:59:55 localhost pppd[10549]: pppd 2.4.2 started by lexhider, uid 1000
Mar 29 11:00:23 localhost pppd[10549]: Serial connection established.
Mar 29 11:00:23 localhost pppd[10549]: Using interface ppp0
Mar 29 11:00:23 localhost pppd[10549]: Connect: ppp0 <--> /dev/ttyS1
Mar 29 11:00:25 localhost pppd[10549]: CHAP authentication succeeded
Mar 29 11:00:26 localhost pppd[10549]: local IP address 220.235.84.250
Mar 29 11:00:26 localhost pppd[10549]: remote IP address 202.173.159.33
Mar 29 11:00:26 localhost pppd[10549]: primary DNS address 203.21.20.20
Mar 29 11:00:26 localhost pppd[10549]: secondary DNS address 203.10.1.9

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for this update.

What happens if you call "ifup ppp0"? This is what modem-applet uses internally.

Revision history for this message
Michael Vogt (mvo) wrote :

Sorry Seb128, mouse went to the wrong button

Revision history for this message
lexual (lexhider) wrote :

Created an attachment (id=1934)
/var/log/messages

Revision history for this message
lexual (lexhider) wrote :

Created an attachment (id=1935)
resolv.conf

I know seem able to connect via the modem monitor applet. But the network still
isn't available. "ping www.yahoo.com" fails as does going to any webpage. I'm
guessing this is a dns issue?

I have attached /var/log/messages and /etc/resolv.conf

Revision history for this message
Michael Vogt (mvo) wrote :

Have you set "Properties/Options/Set modem as default route to the internet"?

Revision history for this message
lexual (lexhider) wrote :

the behaviour is the same regardless of whether the default-route setting is
enabled or not.

I'm pretty sure it a DNS thing, there is no DNS thing showing up in
/var/log/messages and no /etc/resolv.conf is created.

Both of these things happen when I connect via pon.

Revision history for this message
Michael Vogt (mvo) wrote :

(In reply to comment #10)
> the behaviour is the same regardless of whether the default-route setting is
> enabled or not.
>
> I'm pretty sure it a DNS thing, there is no DNS thing showing up in
> /var/log/messages and no /etc/resolv.conf is created.
>
> Both of these things happen when I connect via pon.

You are right. Modem-applet does not set the dns of your provider. I consider
this a pretty serious problem that need to be fixed before the release. I will
have a look now.

Revision history for this message
Michael Vogt (mvo) wrote :

I uploaded gnome-system-tools_1.2.0-0ubuntu4 today that will fix the DNS
problem. It will use the peer dns if you set "Set modem as default route to the
internet". It would be nice if you could confirm that it works with the new version.

Thanks,
 Michael

Revision history for this message
lexual (lexhider) wrote :

Seems to be working fine, thanks.
I'm not sure if I'm allowed to tag as fixed so I'll that to you.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks. You are allowed to close bugs, but I do it now :)

Thanks again for helping to find and fix that bug and confirming that it finally
works.

Cheers,
 Michael

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.