Hi, If your DNS are changed, I think that your network card is configured in DHCP mode. To dissallow DNS changes (in /etc/resolv.conf) by DHCP updates, you can add this line to /etc/dhclient.conf : prepend domain-name-servers <DNS_IP_adress_1>,<DNS_IP_adresse_2>,<DNS_IP_adresse_3>; After you must restart your network card and voilà.
Alexandre. --- En date de : Mer 31.3.10, Alejandro Imass <a...@p2ee.org> a écrit : > De: Alejandro Imass <a...@p2ee.org> > Objet: Re: u3g network problem > À: "Patrick Lamaiziere" <patf...@davenulle.org> > Cc: freebsd-questions@freebsd.org > Date: Mercredi 31 mars 2010, 12h18 > On Tue, Mar 30, 2010 at 5:27 PM, > Patrick Lamaiziere > <patf...@davenulle.org> > 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-unsubscr...@freebsd.org" > > > _______________________________________________ > freebsd-questions@freebsd.org > mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
