search for: my_chain

Displaying 5 results from an estimated 5 matches for "my_chain".

2012 Nov 14
4
firewallchain issues w/ 1.0.0 release
Hi, First, some software versions, just to get them out of the way: - CentOS 5.x through Centos 6.2 - Ruby 1.8.5 - 1.8.7 - Puppet 2.7.19 - Facter 1.6.11 Just a note - we''re working from the EPEL repos almost exclusively. I am working with the firewall module, and so far I am unable to use firewallchain. Some digging suggests that it''s not completely user error (though I
2006 Jun 23
0
[Bug 489] New: IP address with leading zerrow and trailing nine fails
...re is poibly a bug on filtering by IP address. If I add a rule to a chain and filter by IP address like 192.168.12.0*9, I got an error (* could be a number from 0 to 9). All other IP Addresses wokrs fine e.g. 192.168.12.0*8 or 192.168.123.*9. An example instruction that gives an error: iptables -A my_chain -d 192.168.12.059 -j ACCEPT The error message: iptables v1.3.3: host/network `192.168.12.059' not found Example instructions that works: iptables -A my_chain -d 192.168.12.056 -j ACCEPT iptables -A my_chain -d 192.168.12.59 -j ACCEPT Best Regards Sebastian -- Configure bugmail: https://bugz...
2018 Feb 15
3
[Bug 1226] New: Segmentation fault when printing a rule checking byte zero of NFT_PAYLOAD_LL_HEADER
...nftnl_expr *payload_expr, *cmp_expr; uint8_t mac[6] = {0, 0, 0, 0, 0, 0}; rule = nftnl_rule_alloc(); // The segfault is only triggered if the rule is an NFPROTO_INET rule. nftnl_rule_set(rule, NFTNL_RULE_TABLE, "my_table"); nftnl_rule_set(rule, NFTNL_RULE_CHAIN, "my_chain"); nftnl_rule_set_u32(rule, NFTNL_RULE_FAMILY, NFPROTO_INET); payload_expr = nftnl_expr_alloc("payload"); nftnl_expr_set_u32(payload_expr, NFTNL_EXPR_PAYLOAD_BASE, NFT_PAYLOAD_LL_HEADER); nftnl_expr_set_u32(payload_expr, NFTNL_EXPR_PAYLOAD_DREG, NFT_REG_1); nftn...
2019 Apr 12
2
Mailbox INBOX: Opening INBOX failed: Mailbox doesn't exist: INBOX. Maybe master user + namespace problem?
2019 Apr 12
0
Mailbox INBOX: Opening INBOX failed: Mailbox doesn't exist: INBOX. Maybe master user + namespace problem?