How can I prevent this from occurring?
I am using openSUSE 11.0 (Kde3 and Gnome) and it works fine connecting
and staying connected whilst I am active using the Internet. I tried
Live-CD of
Fedora 10 and ubuntu 8.10 and they both work fine, i.e. no
disconnections due to lack of activity.
Modem is E160G and configured for “3MobileBroadband Prepaid” in
Australia (uses APN:“3services” [3netacces is post-paid]).
/var/log/localmessages
pppd[6074]: Terminating connection due to lack of activity.
pppd[6074]: Connection terminated.
pppd[6074]: Terminating on signal 15
pppd[6074]: Exit.
linux-5t8z:~ # lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 1267:0201 Logic3 / SpectraVideo plc A4Tech SWOP-3
Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 12d1:1003 Huawei Technologies Co., Ltd. E220
HSDPA Modem / E270 HSDPA/HSUPA Modem
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
linux-5t8z:~ #
linux-5t8z:~ # ls /dev/ttyU*
/dev/ttyUSB0 /dev/ttyUSB1
linux-5t8z:~ #
NB: Also, once disconnected, for whatever reason, it is not possible to
reconnect (it locks up) without restarting the “network” service several
times (I use following console command: service --full-restart network).
foresthill wrote:
> What program are you using to connect?
>
> There should be a setting for idle timeout, which is set for 600
> seconds (10 minutes) by default. Set it to zero and you will stay
> connected.
Sorry for omission, I am using NetworkManager Applet 0.7.0 and I have
not seen any options for idle timeout (did not need anything on Fedora
10 or Ubuntu 8.10). If you could point me to a config file or some
settings tab I have missed, I would be most grateful.
I started with openSUSE 10.2 and just upgraded (i.e. fresh install) from
10.3 to 11.0 and don’t want to muck around with installing Fedora 10 (or
much less Ubuntu 8.10) as I have limited download quotas and like
openSUSE as an OS.
There are several config files that various network programs use, but i don’t know which file that particular program uses for its settings.
However if you decided to use kinternet to connect with your mobile broadband like I do, the setting for timeouts is in the “wizard” in YAST / Network / Modems. Just install kinternet and then run that wizard and you’re all set. Kinternet sits in the lower right taskbar.
Or if you went with wvdial, the config file for that is in /etc/wvdial.conf
However wvdial is kind of primitive, so I don’t know if you’d want to use a program you have to start from the command line. Though it is possible to have it start automatically at log in time and just keep you connected all the time.
Hopefully someone will come along who knows where the config file is for Network Manager, but I thought I’d give you some other options until that person comes along. HTH!
foresthill wrote:
> There are several config files that various network programs use, but i
> don’t know which file that particular program uses for its settings.
I think the openSUSE Network Manager 0.7.0 has been a little neglected
and seems to be missing some fine-tuning that Fedora 10 has applied to
it. I have had a look around and there are some config files that Fedora
10 has that are not there in suse 11.0. I tried the backports from the
following repo: http://download.opensuse.org/repositories/home%3A/tambet/openSUSE_11.0/
but they crashed my network and I lost my internet connection (luckily I
had my DVD and was able to restore my system). I think he is the Suse
guy (or one of the guys) that works on the Network Manager Applet.
> Hopefully someone will come along who knows where the config file is
> for Network Manager, but I thought I’d give you some other options until
> that person comes along. HTH!
I think this modem is a bit tricky to get working the old-fashioned way
but is very simple and easy to setup with NM 0.7.0 >. If I don’t get any
help here in sorting the idle timeout issue, I will submit a bug report
for it.