Tom,
Providers file contains:
############################################################################################
#NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY
OPTIONS COPY
virtua 1 255 - eth1 detect
track,balance=1 -
vivo 3 254 - $VIVO_IFACE -
track,balance=100 -
*VIVO_IFACE is equal to "ppp0" in my case.*
*It is defined on params file as:*
VIVO_IFACE=$(pidfile=/var/run/ppp-vivo.pid && if test -e $pidfile; then
echo `awk '$1 ~ /ppp[0-9]+/' $pidfile`; else echo ppp0; fi)
VIVO_IFACE=$(if test -n "$VIVO_IFACE"; then echo $VIVO_IFACE; else echo
ppp0; fi)
>
---------- Forwarded message ----------
> From: Tom Eastep <[email protected]>
> To: Shorewall Users <[email protected]>
> Cc:
> Date: Tue, 2 Aug 2016 09:30:37 -0700
> Subject: Re: [Shorewall-users] Bug moving to version 5.0.4 (ubuntu
> 16.04LTS)
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 08/01/2016 01:33 PM, Marcelo Bello wrote:
> > Hello,
> >
> > I just updated my server from Ubuntu 14.04LTS to Ubuntu 16.04LTS
> > and with it I got Shorewall version 5.0.4.
> >
> > I ran "shorewall update" to convert the tcrules file to mangle and
> > everything went fine except for an error:
> >
> > "WARNING: Interface ppp0 is not usable -- Provider vivo (3) not
> > Started"
> >
> > Interface ppp0 was perfectly fine. I know that the ISP "vivo" was
> > working just fine just before I issued the "shorewall restart"
> > command that got me that error message for the first time, and
> > immediately I started getting ISP is down messages from my
> > monitoring software. So I am 100% sure that the problem is not with
> > the ppp0 interface.
> >
> > I tried running "shorewall enable vivo" with no success (same
> > error message). I googled and found a workaround suggested for a
> > similar problem reported back in 2011:
> >
> >
> http://www.engardelinux.org/modules/index/list_archives.cgi?list=shorewall-users&page=0097.html&month=2011-08
> >
> > However, I did not need the entire work around, the problem went
> > away by just changing the file in this way:
> >
> > *I had originally:* net ppp+ -
> > optional,wait=10,nosmurfs,tcpflags,nets=(!10.0.0.0/8
> > <http://10.0.0.0/8>)
> >
> > *I changed to:* net ppp0 -
> > optional,wait=10,nosmurfs,tcpflags,nets=(!10.0.0.0/8
> > <http://10.0.0.0/8>) net ppp+ -
> > optional,wait=10,nosmurfs,tcpflags,nets=(!10.0.0.0/8
> > <http://10.0.0.0/8>)
> >
> > Therefore, I actually had to add a ppp0 interface, ppp+ was not
> > enough. This is bad because this ISP's interface could become ppp1
> > or ppp2, ... in the future.
> >
> > I believe this is a bug, am I right? If it is so, is this a know
> > bug of version 5.0.4 and should I file a bug report on Ubuntu's bug
> > tracking system? Or is it enough to report it here?
> >
>
> What have you specified in /etc/shorewall/providers?
>
> - -Tom
> - --
> Tom Eastep \ When I die, I want to go like my Grandfather who
> Shoreline, \ died peacefully in his sleep. Not screaming like
> Washington, USA \ all of the passengers in his car
> http://shorewall.net \_____________________________
------------------------------------------------------------------------------
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
