http://bugzilla.novell.com/show_bug.cgi?id=620848 http://bugzilla.novell.com/show_bug.cgi?id=620848#c0 Summary: yast2-network modem provider Automatically Reconnect not reconnecting Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: marko.kohtala@gmail.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fi; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 ( .NET CLR 3.5.30729) Provider with setting Automatically Reconnect enabled does not reconnect. Reproducible: Always Steps to Reproduce: 1. Add a Network Device Modem with provider Automatically Reconnect setting enabled. 2. Establish connection. 3. Have it hang up. Actual Results: Interface goes down and stays down. Expected Results: Interface to redial and try to establish the connection. I configured a modem using the YaST Network Devices and wanted it to automatically reconnect when hung-up. It created a /etc/sysconfig/network/providers/provider0 with AUTO_RECONNECT='yes'. However once the connection hung up, it did not reconnect. A look into smpppd sources revealed that AUTO_RECONNECT_EXITS is by default empty. Since the provider0 file did not specify a value for it, the reconnect is not done for any pppd exit code. The provider file needs to also have AUTO_RECONNECT='0 15' (and maybe 16? see man pppd for exit codes) to reconnect. This might just as well be a bug for smpppd for having a bad default. But since it might be useful to set the exit codes I report it first for Yast. smpppd supports also an AUTO_RECONNECT_DELAY for specifying the delay before reconnect. I see no way to set this value. Manual editing of the files may help around the problem. I've yet to see a second connection loss to verify it... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.