From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martijn Lievaart Subject: Re: Debugging network problems Date: Fri, 31 Aug 2007 07:33:08 +0200 Message-ID: <46D7A814.40108@rtij.nl> References: <1188383622.29330.9.camel@sonoda.bioscene.co.jp> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1188383622.29330.9.camel@sonoda.bioscene.co.jp> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii"; format="flowed" To: netfilter@leangen.net Cc: netfilter@lists.netfilter.org David Leangen wrote: > Hello! > > My network was just changed from a vanilla ADSL connection to direct > ftth. There is now a network connector with a 100MB/s entry, which gets > routed to a Buffalo Broad station. > > I'm having some troubles and my debugging so far has not been > successful, so I'm hoping some more experienced hands can give me some > advice. > > > First of all, my previous setup was working exactly as I wanted. > Essentially, when making the switch to the new network, on my > firewall/proxy machine, I just did: > > adsl-stop (to stop the pppoe daemon) > ifconfig eth0 new.ip.address up > route add default gw ip.address.of.broad.station > > Then in my iptables, I changed: > > -A POSTROUTING -o ppp0 -j MASQUERADE > > to > > -A POSTROUTING -o eth0 -j MASQUERADE > > > Here's what's happening now... > > Generally, I can connect to the outside world, and the outside world can > connect to me. By this, I mean that each of the local machines behind my > proxy can connect. > > However, the connections back to my own URL are sporadic. In other > words, sometimes I can connect, sometimes I can't. Assuming my domain is > my.company.com, when I try to connect to my.company.com from within my > network, sometimes I can, sometimes I can't, but I have not at all > figured out a pattern. > > When this happens, domain names are being resolved, but I get > "Connection timed out" errors. > > I guess I first need to check to see if I can't get out, or I can't get > back in. > Sounds like an PMTUD issue. Do you allow all ESTABLISHED packets in, not just tcp? M4