From: John Haxby <john.haxby@oracle.com>
To: TheOldFellow <theoldfellow@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: www.adobe.com
Date: Fri, 14 Nov 2008 09:30:27 +0000 [thread overview]
Message-ID: <491D4533.5030501@oracle.com> (raw)
In-Reply-To: <20081113120030.1f039cb6@gmail.com>
TheOldFellow wrote:
> On Thu, 13 Nov 2008 12:22:00 +0100
> Pascal Hambourg <pascal.mail@plouf.fr.eu.org> wrote:
>
>
>> The problem may lie in your router, your network interface card or its
>> driver. Anyway it does not seem to be related to netfilter/iptables, as
>> tcpdump sees the packet as malformed before it enters the netfilter
>> code. Can you try with another router, machine, kernel or network
>> interface ?
>>
>
> Yes, but it will take time to arrange. It's very strange that it only
> occurs on that range if IP addresses, which are also very similar to
> the 192.168.0.0/16 private address range. I wonder if this would
> improve if I changed the address range used on the ADSL router -
> firewall to, say, 172.20.1.0. If it's software/firmware in the router
> or NIC that might avoid it.
>
It's perhaps not that strange. I had a similar problem a little while
ago -- the networks guy had a set of blacklisted addresses in the router
that was rather out of date. He blamed his predecessor :-)
jch
next prev parent reply other threads:[~2008-11-14 9:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 7:52 www.adobe.com TheOldFellow
2008-11-13 8:33 ` www.adobe.com Покотиленко Костик
2008-11-13 8:42 ` www.adobe.com Wessel
2008-11-13 8:44 ` www.adobe.com Amos Jeffries
2008-11-13 8:59 ` www.adobe.com Покотиленко Костик
2008-11-13 9:15 ` www.adobe.com Gilad Benjamini
2008-11-13 10:02 ` www.adobe.com Pascal Hambourg
2008-11-13 10:52 ` www.adobe.com TheOldFellow
2008-11-13 11:22 ` www.adobe.com Pascal Hambourg
2008-11-13 12:00 ` www.adobe.com TheOldFellow
2008-11-14 9:30 ` John Haxby [this message]
2008-11-15 3:39 ` www.adobe.com Grant Taylor
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=491D4533.5030501@oracle.com \
--to=john.haxby@oracle.com \
--cc=netfilter@vger.kernel.org \
--cc=theoldfellow@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox