From owner-freebsd-questions@FreeBSD.ORG Wed Mar 31 12:18:27 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 769E61065678 for ; Wed, 31 Mar 2010 12:18:27 +0000 (UTC) (envelope-from aimass@yabarana.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA798FC0C for ; Wed, 31 Mar 2010 12:18:26 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 3so6202qwe.7 for ; Wed, 31 Mar 2010 05:18:26 -0700 (PDT) MIME-Version: 1.0 Sender: aimass@yabarana.com Received: by 10.229.98.138 with HTTP; Wed, 31 Mar 2010 05:18:26 -0700 (PDT) In-Reply-To: <20100330232725.7419673a@davenulle.org> References: <20100330232725.7419673a@davenulle.org> Date: Wed, 31 Mar 2010 08:18:26 -0400 X-Google-Sender-Auth: 7c44d6dd88037b79 Received: by 10.229.216.76 with SMTP id hh12mr455456qcb.47.1270037906281; Wed, 31 Mar 2010 05:18:26 -0700 (PDT) Message-ID: From: Alejandro Imass To: Patrick Lamaiziere Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-questions@freebsd.org Subject: Re: u3g network problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2010 12:18:27 -0000 On Tue, Mar 30, 2010 at 5:27 PM, Patrick Lamaiziere wrote: > (8-STABLE/i386) > > Hi, > > I've got some troubles with a 3G connection. I don't know which things > I should check to debug this: > > I use ppp to connect and it works fine. But after a while (not a long > time), I don't have any reply to DNS requests, as far I can see with > wireshark... > What are you using to dial to your 3g network? (I use wvdial, and love it) I've seen this happen on my 3g network as well. It seems that the ISP randomly updates the DNS to a broken one. So write down the DNSs when it's actually working (cat /etc/resolv.conf) and make yourself a little script that updates them back to the working DNSs here is mine for example (adjust to your working DNSs): # cat ./dnsdigitel #!/bin/sh echo "nameserver 204.59.152.208" > /etc/resolv.conf echo "nameserver 57.73.127.195" >> /etc/resolv.conf So when it stops resolving I just ./dnsdigitel and that's it. Of course, this could be easily automated, etc. but it's a quick fix to your problem. Now, the interesting this is that your ISP does exactly the same as my ISP, it changes the DNS randomly to non-working ones, curious. Best, Alejandro Imass > Then if I use an IP, it works. So it looks like it is a problem with > DNS. I've tried with an other dns server with the same result. I've > also tried with a local dns server to cache the requests. It looks to > help a bit. > > Anyway I also use a ssh tunnel to connect to my server and (on the > server) I can see a lot of CLOSED sockets with netstat, and a lot of > sshd processes stuck, even after days. So there is something wrong with > the connection. > > Any idea or suggestion? > > Thanks, regards. > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >