search for: 843d

Displaying 4 results from an estimated 4 matches for "843d".

Did you mean: 8439
2020 Apr 18
1
CentO 8 and nftables default policy
...75d6fd6a347? allow-incoming-ipv4 > ?d37b017f-8f21-4ad0-9fa6-052a5cb1ed2e? allow-ipv4 > ?a8c740d5-328c-452e-bae7-9828c54f95b7? clean-traffic > ?296bdfad-11d9-4aa0-9817-4656ef2be6e5? clean-traffic-gateway > ?69215a61-bff5-482a-b913-589bb1ce18f2? no-arp-ip-spoofing > ?70c61f0a-c005-407f-843d-d13c2495f05d? no-arp-mac-spoofing > ?386cd2f4-7272-43e2-ba1f-80cb3518649c? no-arp-spoofing > ?9117fa21-e3d6-4c32-9cdf-af97ebd6599e? no-ip-multicast > ?7a964470-4f74-4eef-9fec-a0e9a79e168d? no-ip-spoofing > ?8c9e45a3-5d44-4641-b23d-eded5c1f1632? no-mac-broadcast > ?82dcd4f0-f55a-43ad-...
2020 Apr 17
2
CentO 8 and nftables default policy
Hi list, I'm studying nftables. I'm using CentOS 8.1 (Gnome) and I disabled firewalld. I noticed that a default policy is created with tables and chains probably for firewalld. So I created a .nft script where I stored my rules with a flush for previous ruleset, then saved on /etc/sysconfig/nftables.conf and the enabled nftables service. Running the script with nft -f script.nft all
2020 Apr 18
0
CentO 8 and nftables default policy
...132-8738-47c2-8101-275d6fd6a347? allow-incoming-ipv4 ?d37b017f-8f21-4ad0-9fa6-052a5cb1ed2e? allow-ipv4 ?a8c740d5-328c-452e-bae7-9828c54f95b7? clean-traffic ?296bdfad-11d9-4aa0-9817-4656ef2be6e5? clean-traffic-gateway ?69215a61-bff5-482a-b913-589bb1ce18f2? no-arp-ip-spoofing ?70c61f0a-c005-407f-843d-d13c2495f05d? no-arp-mac-spoofing ?386cd2f4-7272-43e2-ba1f-80cb3518649c? no-arp-spoofing ?9117fa21-e3d6-4c32-9cdf-af97ebd6599e? no-ip-multicast ?7a964470-4f74-4eef-9fec-a0e9a79e168d? no-ip-spoofing ?8c9e45a3-5d44-4641-b23d-eded5c1f1632? no-mac-broadcast ?82dcd4f0-f55a-43ad-b520-d4c8d4bf37cd? n...
2013 Nov 20
0
[LLVMdev] unsubscribe
...2013 13:35:25 -0800 From: Bob Wilson <bob.wilson at apple.com> To: Eric Christopher <echristo at gmail.com> Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] bit code file incompatibility due to debug info changes Message-ID: <E49F63C4-F360-4F5D-843D-74EA54A271D8 at apple.com> Content-Type: text/plain; CHARSET=US-ASCII On Nov 19, 2013, at 1:31 PM, Eric Christopher <echristo at gmail.com> wrote: >> Two questions: >> >> 1) Can we reopen the bugzilla PR that I filed and use that to cover the >> additional of a...