All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko@ursulin.net>
To: netfilter@vger.kernel.org
Subject: Strange problem with HTTPS POST (maybe) through router from Linux
Date: Tue, 8 Jun 2010 22:03:22 +0100	[thread overview]
Message-ID: <201006082203.22238.tvrtko@ursulin.net> (raw)


Hi all,

Not really sure it is appropriate for this mailing list but I have a hunch it 
could be netfilter related, or at least people who could know something about 
it are likely to visit this place. :)

I have a small home network behind a cheap ADSL router and a bizarre problem 
where I am not getting responses from some web sites in some situations. I 
suspect it is when a POST needs to go over the connection because it is always 
when I need to log in somewhere over HTTPS. Also it happens when a number of 
unrelated sites.

This only happens from Linux! Just today I tried four different distributions 
on two different machines and it is a total pattern. From Windows it all works 
fine. Also I tried three or four browsers on Linux and all behave exactly the 
same.

I had a look at the iptables setup on the router (see below) and it looks 
reasonable (at least short) to me, but it have been some years since I last 
used it so my knowledge is a bit thin here.

Or could it be that something has changed in recent kernels which could make 
the router unhappy and lose packets?

Anything more I could try to diagnose this? Any hints are appreciated!

Regards,

Tvrtko

 > iptables -L -n -t nat
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  0.0.0.0/0            224.0.0.0/3         
DNAT       tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:*** 
to:192.168.1.2:22 
DNAT       udp  --  0.0.0.0/0            192.168.1.1         udp dpt:53 
to:212.139.132.44    

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination         
MASQUERADE  all  --  192.168.1.0/24       0.0.0.0/0           

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
 > iptables -L -n       
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     2    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state 
RELATED,ESTABLISHED 
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:500               
ACCEPT     esp  --  0.0.0.0/0            0.0.0.0/0                                     
ACCEPT    !esp  --  0.0.0.0/0            0.0.0.0/0           MARK match 
0x10000000/0x10000000 
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:30005                    
LOG        tcp  --  0.0.0.0/0            0.0.0.0/0           tcp 
flags:0x17/0x02 limit: avg 6/hour burst 5 LOG flags 0 level 1 prefix `Intrusion -
> '                                                                                       
DROP       all  --  0.0.0.0/0            0.0.0.0/0                                                                    

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
DROP       all  --  0.0.0.0/0            224.0.0.22
DROP       all  --  0.0.0.0/0            224.0.0.2
ACCEPT     all  --  0.0.0.0/0            224.0.0.251
ACCEPT     all  --  0.0.0.0/0            239.255.255.250
TCPMSS     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp 
flags:0x06/0x02 TCPMSS set 1452
TCPMSS     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp 
flags:0x06/0x02 TCPMSS set 1452
ACCEPT     all  --  0.0.0.0/0            224.0.0.0/3
ACCEPT     tcp  --  0.0.0.0/0            192.168.1.2         tcp dpt:22
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state 
RELATED,ESTABLISHED
ACCEPT    !esp  --  0.0.0.0/0            0.0.0.0/0           MARK match 
0x10000000/0x10000000
LOG        tcp  --  0.0.0.0/0            0.0.0.0/0           tcp 
flags:0x17/0x02 limit: avg 6/hour burst 5 LOG flags 0 level 1 prefix `Intrusion -
> '
DROP       all  --  0.0.0.0/0            0.0.0.0/0

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
DROP       all  --  0.0.0.0/0            239.255.255.250

             reply	other threads:[~2010-06-08 21:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 21:03 Tvrtko Ursulin [this message]
2010-06-08 21:36 ` Strange problem with HTTPS POST (maybe) through router from Linux Jan Engelhardt
2010-06-09  8:00   ` Tvrtko Ursulin
2010-06-09 10:02     ` Jan Engelhardt
2010-06-09 13:41       ` Tvrtko Ursulin
2010-06-09 15:02         ` Jan Engelhardt
2010-06-09 17:51           ` Tvrtko Ursulin
2010-06-09 22:03             ` Tvrtko Ursulin
2010-06-09 22:05               ` Tvrtko Ursulin
2010-06-08 21:46 ` Thanasis
2010-06-09  7:46   ` Tvrtko Ursulin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201006082203.22238.tvrtko@ursulin.net \
    --to=tvrtko@ursulin.net \
    --cc=netfilter@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.