I am pretty sure I was using "server and gateway mode - dialup access" using a PPPoE connection to a dual ISDN router - but this was 9 or 10 years ago on SME 6.0.1. It's possible that I had my ISDN modem setup to disconnect on inactivity, with the SME server in 'server-only' mode.
When my current SME 7.5.1 server was configured for PPPoE, my internet connection was named "ppp0", so I think the PPPoE connection is using the dialup code to control connections.
If you aren't able to set the dialup profile (with timeouts, etc), you should still be able to setup your SME for PPPoE then customize the persistence and timeout values of the connection as follows:
mkdir -p /etc/e-smith/templates-custom/etc/sysconfig/network-scripts/ifcfg-ppp0
cd /etc/e-smith/templates-custom/etc/sysconfig/network-scripts/ifcfg-ppp0
cp /etc/e-smith/templates/etc/sysconfig/network-scripts/ifcfg-ppp0/00default 00default
then edit /etc/e-smith/templates-custom/etc/sysconfig/network-scripts/ifcfg-ppp0/00default.
Looking at
http://linux.die.net/man/5/pppoe.conf, I think you can get what you want by adding the following lines:
DEMAND=30
PPPOE TIMEOUT=30
Expand the templates and restart the network when you're done with
signal-event console-save
signal-event remoteaccess-updateIf you have any errors, you can completely un-do these mods using:
rm -f /etc/e-smith/templates-custom/etc/sysconfig/network-scripts/ifcfg-ppp0/00default
signal-event console-save
signal-event remoteaccess-update
If all else fails, you can tell the crew to unplug the network cable between the SME and the Thrane & Thrane when they're not using it...