Ad Schellevis
Ad Schellevis
this will undo https://github.com/opnsense/core/commit/66fd0e4699ae06bc9a1038ecdb441a6c6b71a875 and reintroduce issues reported earlier (for both net30 as p2p).
@laozhoubuluo my mistake, I tightened the scope earlier for https://github.com/opnsense/core/issues/7228 in https://github.com/opnsense/core/commit/833765fafe9c3c0b357b6d4f706f68da0536a646, I'm just doubting changing this will be necessary as this will impact people with a `p2p` combined with...
I'm not sure what the question is, but if the p2p serves a larger net (
@doktornotor a bit more noisy than intended indeed, thanks.
@doktornotor thanks
I don't mind extending the examples, but it should fit somewhere in the documentation. The most logic option is likely to add some common scenario's here https://docs.opnsense.org/development/how-tos/api.html
a generic example using curl is probably better indeed.
@fichtner not sure if it's the same thing, but the `ip6_forward()` looks suspicious when this traffic was intended for the host itself. maybe @belotv would be so kind to add...
could be https://github.com/squid-cache/squid/commit/0129396e16573b92e7e0c81c46653f5d488968e6 , which might point to a logger issue in the configuration.
To exclude configuration issues in our templates, I tried to execute squid using the `/usr/local/etc/squid/squid.conf.sample` file as well, which also seems to coredump. At a first glance it dies on...