after accepting, traffic shaping with multiple WANs isnīt working properly yet, I found a strange error I canīt explain at all.
I do have a weave server running on my home server adressed via https. Syncing my Firefox at work (via WAN) is working fine but doing this at home via my external IP an unknown error is reported. So I did a packet capture for 192.168.1.100/31 and port 443:
External IP: 220.127.116.11
22:37:33.081368 IP 192.168.1.101.53846 > 18.104.22.168.443: tcp 1173
22:37:33.081446 IP 22.214.171.124.443 > 192.168.1.101.53846: tcp 0
22:37:33.081550 IP 192.168.1.1.21588 > 192.168.1.100.443: tcp 1024
22:37:33.116078 IP 192.168.1.100.443 > 192.168.1.1.21588: tcp 0
22:37:33.116160 IP 192.168.1.1.21588 > 192.168.1.100.443: tcp 149
22:37:33.119189 IP 192.168.1.100.443 > 192.168.1.1.21588: tcp 0
It looks like the packet sent from the client is split in 2 packets. Never seen pfSense doing so. Is that behaviour corresponding to tcp-protocol?
By defining a forwarding rule explicit for LAN-adapter with destination on my WAN-adress (which normally should be covered by the rule for WAN + reflection) the weave-service is working locally but further services running at 443 are getting unavailable.
Thanks for your reply...