network-admin & activation response

[Raphael J. Schmid]

When you click the "Activate" button for a device, most of the time it'll
be checked and then the check box will change to "disabled" again without
any means of informing the user of what happened.

Even worse, sometimes "it works" and sometimes it doesn't. But this way
there's no way of telling except for trying or using ifconfig on the console.

http://bugzilla.gnome.org/show_bug.cgi?id=161185: http://bugzilla.gnome.org/show_bug.cgi?id=161185

[lexual (lexhider)]

(In reply to comment #0)
> When you click the "Activate" button for a device, most of the time it'll
> be checked and then the check box will change to "disabled" again without
> any means of informing the user of what happened.
>
> Even worse, sometimes "it works" and sometimes it doesn't. But this way
> there's no way of telling except for trying or using ifconfig on the console.

This may be related to the problems I have been having.
I posted to ubuntu-users with no response under subject: "network-admin not
working for my dialup"
http://lists.ubuntu.com/archives/ubuntu-users/2004-October/009302.html

Having set up the details for ppp in network-admin [i.e. "system
configuration"->Networking] it won't connect.
When I try to activate it the tick-box in the active column is ticked
for about a second that is clears.
The modem doesn't respond in anyway it doesn't even check for a
dialtone.

So I am know connected via pppconfig/pon which is working fine.

I really have no idea what the problem is but I would guess it could be
a problem with detecting my modem. My modem is a NetComm Wave SP56.
pppconfig fails to autodetect this modem and I have to manually
specify /dev/ttyS1 as the modem port.

Lex.

[Raphael J. Schmid (raphael-j-schmid)]

(In reply to comment #1)

> This may be related to the problems I have been having.
> I posted to ubuntu-users with no response under subject: "network-admin not
> working for my dialup"
> http://lists.ubuntu.com/archives/ubuntu-users/2004-October/009302.html
> [...]

One problem is that wvdial has to be installed in order for this to work.
It isn't by default installed in Ubuntu (as of the Warty preview release,
that is, dunno if they're planning to).

Even more serious is that WHEN you have wvdial installed with a hand-written
/etc/wvdial.conf, and only DARE to start the network configuration dialog,
it'll mess up your config file, making wvdial practically unusable from on
then.

[Sebastien Bacher (seb128)]

do you have some details on what is changed/broken in the wvdial config file ?

[Raphael J. Schmid (raphael-j-schmid)]

Created an attachment (id=695)
Original wvdial.conf

[Raphael J. Schmid (raphael-j-schmid)]

Created an attachment (id=696)
Modified wvdial.conf

[Raphael J. Schmid (raphael-j-schmid)]

(In reply to comment #3)
> do you have some details on what is changed/broken in the wvdial config file ?

Sure. I've attached the before and the after version of the configuration file.
This bug is especially nasty when you have to use different phone numbers at
different times of day like I do. Cost me about 300 bucks last month because I
didn't find out about it soon enough :-/. (Well, this week the DSL flatrate
should be arriving at last...)

[Sebastien Bacher (seb128)]

I've opened a bug upstream about this:
http://bugzilla.gnome.org/show_bug.cgi?id=161185

[Carlos Garnacho (carlosg)]

gnome-system-tools 1.1.3 uses chatscripts (in the same way than pppconfig) in
debian based distributions, and shows an error dialog if an interface fails to
activate, so all these issues should have been fixed. Sorry for the breakage :(

[Sebastien Bacher (seb128)]

ok, bug closed, thanks.