Sagem

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)

Sagem error Only one WAN connection can be enslaved by each bridge : Resolved

Symptoms: You want to change IP settings, change IP address ( local Ip address, default 192.168.1.1 ) but Sagem router returns a message: “Only one WAN connection can be enslaved by each bridge” Reason: Other VLAN interfaces are enabled and should be disabled when changing the LAN settings. Solution: You do not need VLAN , … Read moreSagem error Only one WAN connection can be enslaved by each bridge : Resolved