Jan Engelhardt wrote:
On Thursday 2008-04-03 15:44, Patrick McHardy wrote:
> I don't like exporting this since, as you say, userspace doesn't
> need it
Somehow you have to say that an extension if for arp only.
We could abuse ETH_P_ARP, but using just the same name and value
across both user and kernelspace seems just more logical.
static struct xtables_target new_arp_mangle = {
.family = ETH_P_ARP,
};
Whats the problem with moving NF_ARP outside userspace
visibility and defining it to AF_MAX + 1?
I guess it would work. Given that my currently running kernel
did not break on removing NF_ARP entirely and substituting it
by PF_ARP=21...
can we at least go for a more verbose name like NFPROTO_ARP?
Sure. I'd suggest to do something like this:
enum nf_protos {
__NF_PROTO_MIN = AF_MAX,
NF_PROTO_ARP,
};
BTW, I'll go over your remaining non-arptables patch today,
please only repost the arptables patchces (and the ebtables
one if it logically belongs together) as one series with
some explanations on what it is trying to do as a whole
and the concept.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html