Skip to main content
11 events
when toggle format what by license comment
Oct 7, 2021 at 7:34 history edited CommunityBot
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
Feb 2, 2019 at 15:52 history edited Melebius CC BY-SA 4.0
link added, link titles
Nov 24, 2017 at 14:35 comment added Daniel B @dirkt Well you could certainly use ebtables or whatever on bridged traffic. If you use a full-fledged Linux router. Most people don’t. Also, the performance impact makes bridge filtering impractical. You could also use proxy_ndp and routing to make this work with a single /64. However, again, this requires advanced setup.
Nov 24, 2017 at 14:04 comment added dirkt @DanielB: If you want a firewall, then add a firewall. That's unrelated to the question of "routing or bridging".
Nov 24, 2017 at 12:47 comment added Daniel B @dirkt How to it? Well by using a firewall of course. You can use connection tracking even without NAT. Unrelated traffic is simply dropped.
Nov 24, 2017 at 11:17 comment added dirkt @DanielB: How exactly do you want to avoid "exposing your internal network to others" in IPv6? Global IPv6 addresses are reachable from everywhere, and IPv6 NAT is icky. Ok, you can stop link-local broadcasts etc. by not briding, but that's about all you can do, I think.
Nov 24, 2017 at 11:17 history edited Melebius CC BY-SA 3.0
explanation added
Oct 17, 2016 at 6:38 comment added Melebius @DanielB Yes, this is kind of a way, not the preferred one. I am still asking for a better solution.
Oct 17, 2016 at 6:33 history edited Melebius CC BY-SA 3.0
small improvents
Oct 17, 2016 at 6:26 comment added Daniel B Well I wouldn’t really call that a solution. I’d rather forgo IPv6 than expose my internal network to others.
Oct 16, 2016 at 19:32 history answered Melebius CC BY-SA 3.0