I can confirm that my original config from 2.3 also would not route when it was imported to 2.4. This related more to performance differences between NanoBSD and FreeBSD; as it applied to hardware devices (APU & SG-1000). The gateways would not route through OpenVPN bridged connections. Due mostly to my imperfect use of static routes. A re-write of the config was required.
On Fri, Nov 3, 2017 at 2:59 AM, Fabian Bosch <[email protected]> wrote: > Hello > > A weird problem occurred after upgrading Proxmox from 2.3.3 to Version 2.4. > > > Everything worked as before except for the subnets located at one > LAN-Interface. > > The two subnets with this LAN-Interface as a gateway (using different > Virtual-IPs) worked internally for themselves and had access to the > WAN-Interface but the routing between those subnets over the LAN-Interface > didn't work. > > There were definetly no Fw-rules blocking traffic between those subnets, > even the "Bypass firewall rules for traffic on the same interface" option > was checked. > > pings returned "TTL exceeded" or simply "destination host unreachable" > which can be caused by routing-loop (gateway-to-gateway) > > > Are there any new parameters in the 2.4 configuration which can influence > the routing on the same interface in a way that the former configuration of > v 2.3.x doesn't suffice any more? > I didn't add new gateways or made changes on interfaces nor did I change > any of the parameters of the working configuration before the update. > > Thanks! > > > Fabian Bosch > > > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
