[Shorewall-users] newer iproute2 revision in gentoo causes issues with activated traffic control

2017-12-18 Thread Alexander Stoll
Hello I want to bring to your attention that at least gentoo stabilized iproute 4.14.x (4.4.0 was old stable) which obviously needs new parameters for tc command when enabled in shorewall. Are you already aware of this issue? Please refer also to this bug: https://bugs.gentoo.org/640766 No

Re: [Shorewall-users] Shorewall 5.2.0 Beta 1

2018-02-23 Thread Alexander Stoll
Am 21.02.2018 um 01:38 schrieb Tom Eastep: 3) With the wide availability of ipset-based blacklisting, the need for the 'refresh' command has been largely eliminated. As a result, that command has been removed. Dear Tom, I use traffic shaping on multiple hosts, all connected via

[Shorewall-users] tc problem on new GENTOO kernel

2018-11-08 Thread Alexander Stoll
Hi Tom, posting to the list because until know I am not shure what is to blame... - working config with kernel 4.18.14 (gentoo-sources-4.18.14) - introduced with gentoo-sources-4.18.15 tc rules are not loading anymore on startup, gentoo-sources-4.19.x also affected - set up a testenv on

Re: [Shorewall-users] tc problem on new GENTOO kernel

2018-11-09 Thread Alexander Stoll
Am 09.11.2018 um 17:46 schrieb Thomas Deutschmann: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, 1) We (Gentoo) don't patch anything tc-related in gentoo-sources. 2) The only change between gentoo-sources 4.18.14 and 4.18.15 was the addition of "linux-4.18.15.patch"

Re: [Shorewall-users] last missing Shorewall6 piece, ping6 from LAN to 'NET ?

2021-05-20 Thread Alexander Stoll
Am 20.05.2021 um 13:04 schrieb tha...@letterboxes.org: So with this I end up with NAT'd IPv6. Which I thought you weren't supposed to do. yes, this is ugly and something to avoid when ever possible... But I guess if I'm going to have private internal IPv6 addresses, either static &/or