Actually, this would be enough, and it would also be easily parseable:
# shorewall reload
FATAL ERROR: found another process with PID $PID
...
and the exit code would be non-zero.
Vieri
___
Shorewall-users mailing list
On Wednesday, October 10, 2018, 12:23:20 PM GMT+2, Vieri Di Paola via
Shorewall-users wrote:
>
> So in the end, the guilty party seems to be the pppd daemon, or the way I
> configure it.
>
> A simple solution would be to run "shorewall reload" within an ip-up.d
> script. However, I'm not
On Tuesday, October 9, 2018, 11:23:40 PM GMT+2, Tom Eastep
wrote:
>
> * If the modem is rebooted, things don't work until the ppp script is run.
> * If the ppp script is run, routing is changed behind Shorewall's back
> so that, at least in some cases, only a 'reload' can put things
On 10/09/2018 02:10 AM, Vieri Di Paola via Shorewall-users wrote:
>
>
> On Monday, October 8, 2018, 7:30:45 PM GMT+2, Tom Eastep
> wrote:
>> default via 192.168.144.1 dev ppp3 metric 4009
>>
>> 'reenable' does not delete that route, but 'restart' and 'reload' do
>> delete the route.
On Tuesday, October 9, 2018, 11:12:32 AM GMT+2, Vieri Di Paola via
Shorewall-users wrote:
>
> Still don't quite get why I'm getting the "Network is unreachable" message
> before reenabling in the last test.
I forgot to add this info:
--- routing_after_ppp3_restart 2018-10-09
On Monday, October 8, 2018, 7:30:45 PM GMT+2, Tom Eastep
wrote:
>
> default via 192.168.144.1 dev ppp3 metric 4009
>
> 'reenable' does not delete that route, but 'restart' and 'reload' do
> delete the route.
>
> This issue will be corrected by omitting 'defaultroute' from your
> ppp
On 10/08/2018 05:53 AM, Vieri Di Paola via Shorewall-users wrote:
> On Friday, October 5, 2018, 6:51:04 PM GMT+2, Tom Eastep
> wrote:
>
>>>
>>> Finally, a shorewall restart (full stop and start) actually DID solve the
>>> issue. I magically got my ppp3 link working again.
>>> So, of course,
On 10/08/2018 06:01 AM, Vieri Di Paola via Shorewall-users wrote:
>
>
> On Friday, October 5, 2018, 6:42:46 PM GMT+2, Tom Eastep
> wrote:
>
>>>
>>> However, all 3 providers are up and running, ie., I can successfully ping
>>> to a remote host through their interfaces.
>>> I need to
On Friday, October 5, 2018, 6:42:46 PM GMT+2, Tom Eastep
wrote:
>>
>> However, all 3 providers are up and running, ie., I can successfully ping to
>> a remote host through their interfaces.
>> I need to manually run "shorewall enable INTERFACE" and restart shorewall.
>> No issues from
On Friday, October 5, 2018, 6:51:04 PM GMT+2, Tom Eastep
wrote:
>>
>> Finally, a shorewall restart (full stop and start) actually DID solve the
>> issue. I magically got my ppp3 link working again.
>> So, of course, I'm worried that if there's a power outage or if someone
>> reboots the
On 10/04/2018 11:30 PM, Vieri Di Paola via Shorewall-users wrote:
> I finally got it working, but I still have a few doubts (see below).
>
> On Thursday, October 4, 2018, 12:25:05 PM GMT+2, Vieri Di Paola via
> Shorewall-users wrote:
>>
>> If I were to move to my 3-ppp setup, I guess I would
On 10/04/2018 03:19 AM, Vieri Di Paola via Shorewall-users wrote:
>
>
> On Wednesday, October 3, 2018, 11:55:30 PM GMT+2, Tom Eastep
> wrote:
>
>>
>> Looks to me like an issue with whatever program you are runninq to
>> service NFQUEUE...
>
> Please note that I have the "bypass" option set
I finally got it working, but I still have a few doubts (see below).
On Thursday, October 4, 2018, 12:25:05 PM GMT+2, Vieri Di Paola via
Shorewall-users wrote:
>
> If I were to move to my 3-ppp setup, I guess I would need to specify the ppp
> option "defaultroute" for each ppp interface,
On Wednesday, October 3, 2018, 11:55:30 PM GMT+2, Tom Eastep
wrote:
>
> Looks to me like an issue with whatever program you are runninq to
> service NFQUEUE...
Please note that I have the "bypass" option set for NFQUEUE. In any case, I
removed NFQUEUE from my Shorewall configuration to
On 10/03/2018 10:21 AM, Vieri Di Paola via Shorewall-users wrote:
> I finally managed to reconnect to my shorewall gateway. Here are two dump
> files:
>
> The 3 ISPs are accessed via 3 pppoe links, and I'm trying to ping a remote
> host on any one of these links with something like:
>
> # ping
I finally managed to reconnect to my shorewall gateway. Here are two dump files:
The 3 ISPs are accessed via 3 pppoe links, and I'm trying to ping a remote host
on any one of these links with something like:
# ping -n -I ppp1 8.8.8.8
First ICMP request is succesfully replied. Subsequent
On 10/03/2018 07:03 AM, Vieri Di Paola via Shorewall-users wrote:
> On Tuesday, October 2, 2018, 4:46:34 PM GMT+2, Tom Eastep
> wrote:
>>
>> As I pointed out in my response to your later post, those rules won't
>> make any difference even if correct code was generated. What I suspect
>> is
On Tuesday, October 2, 2018, 4:46:34 PM GMT+2, Tom Eastep
wrote:
>
> As I pointed out in my response to your later post, those rules won't
> make any difference even if correct code was generated. What I suspect
> is that you are running into a PMTU problem that will be corrected if
> you set
On 10/02/2018 07:32 AM, Tom Eastep wrote:
>
> So you can remove them and eliminate the incorrect code generation. That
> having been said, the compiler should still not generate code with
> invalid syntax in this case. If you can supply me with a compiler trace,
> I'll try to understand why that
On 10/01/2018 10:31 AM, Vieri Di Paola via Shorewall-users wrote:
> On Monday, October 1, 2018, 5:50:59 PM GMT+2, Tom Eastep
> wrote:
>> For this type of error, I really need to see the .start file itself.
>
> I'll copy the .start file ASAP.
>
> In the meantime, I removed the following lines
On 10/02/2018 03:14 AM, Vieri Di Paola wrote:
> Hi,
>
> This is a follow-up to my previous e-mail "From: Vieri Di Paola
> - 2018-10-01 17:31:37". I'm writing from my
> gmail account because as stated in my previous post, I can't access
> mail.yahoo.com through my shorewall gateway for some
On Monday, October 1, 2018, 5:50:59 PM GMT+2, Tom Eastep
wrote:
> For this type of error, I really need to see the .start file itself.
I'll copy the .start file ASAP.
In the meantime, I removed the following lines from the snat file:
SNAT($IF_ISP3_IP) $IF_LAN $IF_ISP3
SNAT($IF_ISP2_IP)
On 10/01/2018 05:40 AM, Vieri Di Paola via Shorewall-users wrote:
> Hi,
>
> I'm having trouble with my new multi-ISP setup with 3 pppoe links to my
> internet providers.
> I have no previous knowledge of the IP addresses the providers will assign
> nor the gateway I should use. It's
23 matches
Mail list logo
