Re: [Shorewall-users] Shorewall Dump

Hi Tom, Thanks for the response, sadly didn't work. Please find the 2 requested shorewall dumps attached Roland On Tue, Aug 8, 2017 at 6:44 AM, Tom Eastep wrote: > On 08/05/2017 04:50 PM, Roland Schmid wrote: > > Hi All, > > > > I just can't get shorewall to send

Re: [Shorewall-users] Shorewall Dump

On 08/05/2017 04:50 PM, Roland Schmid wrote: > Hi All, > > I just can't get shorewall to send internet network traffic to my docker > container. > > Inside my docker I'm running bind (53) and webmin (10001) > > If I'm on my server I can telnet to ports 53/10001 fine (docker > container ip is

[Shorewall-users] Shorewall Dump

Hi All, I just can't get shorewall to send internet network traffic to my docker container. Inside my docker I'm running bind (53) and webmin (10001) If I'm on my server I can telnet to ports 53/10001 fine (docker container ip is 172.17.0.2) from the internet I continually get telnet: Unable

Re: [Shorewall-users] Shorewall Dump

Marcus Limosani wrote: Hi tom, I set things up as per your recommendation. I can browse the net from the internal network, and then applied the other rules as you indicated. I still get the FORWARD:REJECT response on traffic destined to the servers. I have attached the

Re: [Shorewall-users] Shorewall Dump

Tom Eastep wrote: Marcus Limosani wrote: Hi tom, I set things up as per your recommendation. I can browse the net from the internal network, and then applied the other rules as you indicated. I still get the FORWARD:REJECT response on traffic destined to the servers. I have

Re: [Shorewall-users] Shorewall Dump

Tom Eastep wrote: Tom Eastep wrote: Marcus Limosani wrote: Hi tom, I set things up as per your recommendation. I can browse the net from the internal network, and then applied the other rules as you indicated. I still get the FORWARD:REJECT response on traffic destined to the

Re: [Shorewall-users] shorewall dump on Multi-ISP traffic shaping problem

Roalt Zijlstra wrote: Roalt Zijlstra wrote: Hi there, Here is the shorewall dump. It is a little messy with the number of connections, as it is a production server (non-fail-over). Have you sent a problem report to the mailing list? We can do nothing with the dump without knowing what