My device is not meant to be a system (or full blown) router per se. It is a specialized custom device that for some cases needs to be able to act as a router. It does not act as a DNS server, and in most cases there will be other routers in the system (at least on the eth0 network, and my device is usually set up as a DHCP client on eth0).That's as "router-ish" as routers get. Don't think of it as "not a full-blown router". It may be expected to only have a light packet load but that doesn't make it anything less than a router.
I get what you're saying, and I don't really disagree, it's just that on this device there's still quite a few things missing (on purpose) that a "full blown" router has. Hence I said what I did.
First I am going to juggle your addresses a little to get your device
(and all of eth1), that is the inner protected network ("PRO") out of
<detailed explanation snipped for brevity>Thanks for writing down all of that. It is useful, even though I actually had most of it down working already. As also mentioned in the subject, the real point of this thread was to find out if packet marking is actually the best/easiest way to solve my problem, and both you and others have confirmed that now.
I'm also using nftables (as mentioned in the OP), so the rules you used in iptables are different than mine. The principles are the same though (and netfilter is of course still the underlying framework), so your answer is still useful as a guide to where and when.
I've struggled with this for quite some time, and it is a relief to finally have a better grip on it.
Again, apologies. Being told I missed "something" wasn't as helpful as being told what thing I missed. /D'oh
No apologies needed. You've been very helpful, to misunderstand is only human. :-)
-- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
