Re: [Shorewall-users] Invalid Zone Name

On Sun, 6 Jan 2019 15:26:58 -0800 "C. Cook" wrote: > LOGFORMAT does not seem to be the right variable, but I can't see in > the virtual machine's tiny window what might be. LOGFORMAT is the correct variable. To get longer zone names, use shorter LOGFORMAT like LOGFORMAT="%s %s ". That will give

Re: [Shorewall-users] Invalid Zone Name

On 1/6/19 3:19 PM, Justin Pryzby wrote: > On Sun, Jan 06, 2019 at 03:17:10PM -0800, C. Cook wrote: >> I am trying to set up some WireGuard VPN channels, and one of them is >> called incomingWG. >> >> Wireguard starts up just fine with this as an interface, but Shorewall >> is unhappy with this as

Re: [Shorewall-users] Invalid Zone Name

On Sun, Jan 06, 2019 at 03:17:10PM -0800, C. Cook wrote: > I am trying to set up some WireGuard VPN channels, and one of them is > called incomingWG. > > Wireguard starts up just fine with this as an interface, but Shorewall > is unhappy with this as a zone. > > I changed the zone to all

[Shorewall-users] Invalid Zone Name

I am trying to set up some WireGuard VPN channels, and one of them is called incomingWG. Wireguard starts up just fine with this as an interface, but Shorewall is unhappy with this as a zone. I changed the zone to all lower-case, but same. Why is it upset with a valid interface?