Hi Matt, sorry last time I answered to Tom I was using another email address. Maybe that way it wasn't tracked correctly.
Hi Tom, I had a dump attached to the first mail (22th Dec) and attached it here again. I created it using shorewall dump > shorewall_dump.txt. Is it something else you need? Regards Markus Am Do., 2. Jan. 2020 um 19:47 Uhr schrieb Tom Eastep <teas...@shorewall.net >: > On 1/2/20 9:57 AM, Matt Darfeuille wrote: > >> > >> > >> In shorewall.conf, what is the RELATED_DISPOSITION setting? And > >> do you > >> have entries in the RELATED section of the rules file? > >> > > > > It looks like you didn't answer to Tom's question (bottom of this > > e-mail), > > He actually did, and I'm concerned about having all of the rules in the > ALL section. > > > In general, a rule in the rules file needs to be used to open port > > (SSH in this case. > > Unless the applicable policy is ACCEPT. > > > > > For connection issue we will need a dump file collected as described at > (1). > > I agree -- we have seen snippets of the configuration, but a dump will > tell us exactly what the network configuration and the Shorewall > configuration look like. > > > > > > > 1) https://shorewall.org/support.htm#Guidelines > > > > -Tom > > -- > Tom Eastep \ Q: What do you get when you cross a mobster with > Shoreline, \ an international standard? > Washington, USA \ A: Someone who makes you an offer you can't > http://shorewall.org \ understand > \_______________________________________________ > > _______________________________________________ > Shorewall-users mailing list > Shorewall-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shorewall-users >
shorewall_dump.tar.bz2
Description: application/bzip
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
