BADTCP usually means that the connection doesn't comeback by following the same path.
So in your case could be that the request made by 192.168.0.53 to 192.168.1.20 is passing through 192.168.0.5 but comeback to your PC directly instead of passing back through 192.168.0.5

hello i have a routed problem with endian 3.3

my configuration is

green 192.168.0.1 red 82.x.x.x
in the same LAN there is a gateway(192.168.0.5) to do vpn to external network 192.168.1.0

in endian a i have created a route to redirect traffic to 192.168.1.0 using 192.168.0.5

the route works if i made ping o tracert on a Windows machine, bat if i try to use remote desktop or ssh or lan access dosn't work.

in a log firewall i see:

BADTCP:DROP TCP (br0) 192.168.0.53:54159 -> 192.168.1.20:22 (br0) -
MAC=00:0c:29:0d:c0:bf:00:0c:29:ae:1d:72:08:00 LEN=40 TOS=00 PREC=0x00 TTL=127 ID=21819 DF SEQ=2300448212 ACK=173446266 WINDOW=260 ACK URGP=0 MARK=0

from endian shell instead ssh to this network works.

i have made many search in this forum and the only way to resolv this problem is disable BADTCP like this post:

h ttp://efwsupport.com/index.php?topic=5548.0

but i don't want to disable badtcp.

there is no way to exclude remote network from badtcp without disable it?

Hello,

just wondering what's the right procedure to add a custom RBL (Proxy -> SMTP -> Black & Whitelist -> Realtime Blacklist).
Does enyone have experience on this? Shoud I just go manually on SA config?

Thanks
Gabriele

hi there
i can't find l2tp option in community appliance 3.3.0

Does Endian assign Ubuntu an IP address from DHCP?

Can you ping the IP of the green interface?

What DNS server do you have set?

Sounds odd. Did you inline upgrade to 3.3? Maybe do a clean install and restore from backup?

Like you, I have it running on multiple hyper-v hosts without a problem.

I dont know if drivers in the kernel are missing.

Yes it can be a certificate problem but you should see it in the logs
What's the output of:

ipsec up <your-tunnel-name>

and the output of:

cat /var/log/ipsec/ipsec.log

after trying to bring up the tunnel?

Missing drivers maybe?

Boot during installation stops with (UEFI and non UEFI):
pnp: PnP ACPI: found 4 devices