BBox2 Sagem Blocked – NAT out failed First packet in connection is not a SYN packet (part 2)
I have been experimenting again with the ” First packet in connection is not a SYN packet: TCP 192.168.1.51:1036->157.55.133.202:80 on ppp0 ” error in my SAGEM F@ST router. What I found was that the Sagem firewall and/or NAT throws this messages whenever tcp packets are fragmented and this has to do with the MTU (maximum … Read moreBBox2 Sagem Blocked – NAT out failed First packet in connection is not a SYN packet (part 2)