Re: [Shorewall-devel] [Shorewall-users] shorewall-init fails & 1 provider (vpn) interface unusable on boot -- but sys ends up fully up & running after boot anyway. why?

[PGNd <de...@pg...>]

Poking at this piece by piece, I find that  if I `restart`

	shorewall-lite restart
		Restarting Shorewall Lite....
		  OK ping @ INTFC=eth0
		  OK ping @ INTFC=tun1
		Initializing...
		Processing init user exit ...
		Processing tcclear user exit ...
		Setting up Route Filtering...
		Setting up Martian Logging...
		Setting up Accept Source Routing...
		Setting up Proxy ARP...
		Adding Providers...
		Preparing iptables-restore input...
		Running /usr/sbin/iptables-restore...
		IPv4 Forwarding Enabled
		Processing start user exit ...
		Processing started user exit ...
		done.

all's OK.  But if I `stop` then `start`, 

	shorewall-lite stop
		Stopping Shorewall Lite....
		  OK ping @ INTFC=eth0
		  OK ping @ INTFC=tun1
		Processing stop user exit ...
		Processing tcclear user exit ...
		Running /usr/sbin/iptables-restore...
		IPv4 Forwarding Enabled
		Processing stopped user exit ...
		done.
	shorewall-lite start
		Starting Shorewall Lite....
		  BAD ping @ INTFC=eth0
		  BAD ping @ INTFC=tun1
		Initializing...
		Processing init user exit ...
		Processing tcclear user exit ...
		Setting up Route Filtering...
		Setting up Martian Logging...
		Setting up Accept Source Routing...
		Setting up Proxy ARP...
		Adding Providers...
		   WARNING: Interface eth0 is not usable -- Provider prov1 (1) not Started
		   WARNING: Interface tun1 is not usable -- Provider prov2 (2) not Started
		   WARNING: No Default route added (all 'balance' providers are down)
		   NOTICE: Default route restored
		Preparing iptables-restore input...
		Running /usr/sbin/iptables-restore...
		IPv4 Forwarding Enabled
		Processing start user exit ...
		Processing started user exit ...
		done.

then it all seems to act up.

Exploring what the difference between restart & start+stop is ...