#cunts — Public Fediverse posts

Question Time.

Tony Burke is EMPHATICALLY PROUD to say that the Government received a letter of complaint from SAVE THE CHILDREN FUND, because the Government refused to help [CHILDREN].

#JFC #ALP - you have lost your way.
I am embarrassed and ashamed that I ever helped you.

.
.
.
.
.
.

#cunts

Want change?
#VoteGreen

Question Time.

Tony Burke is EMPHATICALLY PROUD to say that the Government received a letter of complaint from SAVE THE CHILDREN FUND, because the Government refused to help [CHILDREN].

#JFC #ALP - you have lost your way.
I am embarrassed and ashamed that I ever helped you.

.
.
.
.
.
.

#cunts

Want change?
#VoteGreen

"Don't use shorewall anymore, it's old" my stupid brain said. And who wants to be 'old'? Not me. No. I am hip, chic, sprightly-brained. I also live a very happy rich fantasy existence, keep that pin away from my bubble!

DuckDuckGo: 'nftables replacement for shorewall' gets:
"Just accept that Firewalld is a major player, and that iptables is on its way out with nftables being more robust and consistent. And nftables is the default Firewalld back end. Firewalld is good once you get used to what it's doing. And it's the default on Fedora/CentOS/RHEL and SUSE/openSUSE Leap/Tumbleweed. "

I am always using #Debian, (because, ahem, old? I'd dare not say) including on this firewall box. But, there's a firewalld package. Probably best to go with the flow ....

So I install firewalld, then muck about with dnsmasq, then turn back to fiirewalld, which seems enabled without me asking consciously asking for it (?) oh well ...

Then I get to:
Machine: A zone called 'work' exists.
Me: nnah, not here in my shed it doesn't.
#firewall-cmd --delete-zone=work --permanent
Machine: Error: BUILTIN_ZONE: 'work' is built-in zone

What!? Say the fuck WHAT? "work"???
What fresh hell is this? Am I not allowed to be away from work even here at my shed with the magpies and roos?

Christ on a bike. Well I'll just get my bigger stick, and do:
#rm /etc/firewalld/zones/work*
and restart firewalld.
... It is back ... 🤐
Machine: Error: BUILTIN_ZONE: 'work' is built-in zone
Oh. ComeTheFuckON!

#firewalld, unless something changes my mind in the night, you are headed for the bin in the morning.

And some unasked-for advice from me to the #firewalld people: You MIGHT, just might, have permanent built-ins for 'drop' and 'bridge', ... perhaps. But 'work'? Fuck off to the place with the fuckoff sign, read it carefully, then fuck off further, yes and your friends too. Example zones? fine. Recipes about common 'internal'/'dmz'/'external' arrangements? also fine. Helpful in fact. Demanding that I have a "work" zone???

'WORK'

#JFC #cunts

To think that I fought the good fight for the cultural insensitivity of #DMZ. (oh yeah - that little fucker? built-in too, ofCourseItIs)
What a waste of my time.

#networking people: If you had a four-port PCbox configured as a debian #firewall, what would you use to make the configuration of #nftables easy/safe/happy/fucker-free?

"Don't use shorewall anymore, it's old" my stupid brain said. And who wants to be 'old'? Not me. No. I am hip, chic, sprightly-brained. I also live a very happy rich fantasy existence, keep that pin away from my bubble!

DuckDuckGo: 'nftables replacement for shorewall' gets:
"Just accept that Firewalld is a major player, and that iptables is on its way out with nftables being more robust and consistent. And nftables is the default Firewalld back end. Firewalld is good once you get used to what it's doing. And it's the default on Fedora/CentOS/RHEL and SUSE/openSUSE Leap/Tumbleweed. "

I am always using #Debian, (because, ahem, old? I'd dare not say) including on this firewall box. But, there's a firewalld package. Probably best to go with the flow ....

So I install firewalld, then muck about with dnsmasq, then turn back to fiirewalld, which seems enabled without me asking consciously asking for it (?) oh well ...

Then I get to:
Machine: A zone called 'work' exists.
Me: nnah, not here in my shed it doesn't.
#firewall-cmd --delete-zone=work --permanent
Machine: Error: BUILTIN_ZONE: 'work' is built-in zone

What!? Say the fuck WHAT? "work"???
What fresh hell is this? Am I not allowed to be away from work even here at my shed with the magpies and roos?

Christ on a bike. Well I'll just get my bigger stick, and do:
#rm /etc/firewalld/zones/work*
and restart firewalld.
... It is back ... 🤐
Machine: Error: BUILTIN_ZONE: 'work' is built-in zone
Oh. ComeTheFuckON!

#firewalld, unless something changes my mind in the night, you are headed for the bin in the morning.

And some unasked-for advice from me to the #firewalld people: You MIGHT, just might, have permanent built-ins for 'drop' and 'bridge', ... perhaps. But 'work'? Fuck off to the place with the fuckoff sign, read it carefully, then fuck off further, yes and your friends too. Example zones? fine. Recipes about common 'internal'/'dmz'/'external' arrangements? also fine. Helpful in fact. Demanding that I have a "work" zone???

'WORK'

#JFC #cunts

To think that I fought the good fight for the cultural insensitivity of #DMZ. (oh yeah - that little fucker? built-in too, ofCourseItIs)
What a waste of my time.

#networking people: If you had a four-port PCbox configured as a debian #firewall, what would you use to make the configuration of #nftables easy/safe/happy/fucker-free?