Re: Suggestion: default /etc/resolv.conf
arne anka writes: >> Yes, but I'd like it to use DHCP for its usb IP address, as well. > >what stops you? the dhcp client will overwrite resolv.conf, then. This is actually a reprise of a discussion a week or so ago -- as a matter of fact, that is what I do. But, since it's not set up that way in the default /etc/network/interfaces, there's some extra pain every time I reflash. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
> Yes, but I'd like it to use DHCP for its usb IP address, as well. what stops you? the dhcp client will overwrite resolv.conf, then. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
ian douglas writes: >Joe Pfeiffer wrote: >> Much better to get resolv.conf, along with IP address, from DHCP. > >Typically, I'd agree -- except the Freerunner doesn't get its IP from >DHCP for the USB port, which is where pretty much all of the DNS >questions come from to the list (until GRPS starts working reliably...) Yes, but I'd like it to use DHCP for its usb IP address, as well. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
Joe Pfeiffer wrote: > Much better to get resolv.conf, along with IP address, from DHCP. Typically, I'd agree -- except the Freerunner doesn't get its IP from DHCP for the USB port, which is where pretty much all of the DNS questions come from to the list (until GRPS starts working reliably...) Personally I don't think there's any harm in having an open/public DNS server pair in the default out-of-the-box /etc/resolv.conf file. In fact, I bundled a whole bunch of configuration files together for wifi, dns, etc. for the guys who were part of the Los Angeles group -- first thing I did for most of them was get that tarball unpacked on their Freerunners. Saved them all some grief. -id ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
On Thu, Jul 24, 2008 at 10:52 AM, Andy Green <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > > | There's the DHCP issue that other emails talk about. Another problem > | is that you have to trust your DNSs and somehow it would mean that > | OpenMoko trusts (blindly) a few DNS servers. I feel that trusting a > | DNS is a very sensitive issue and that's why I only trust my own. > > Running your own caching DNS resolver is not too hard with djbdns and > bind in the distros. But even then you have to "blindly" trust the root > servers... > > http://www.renesys.com/blog/2008/05/identity_theft_hits_the_root_n_1.shtml So I read. This was a big issue! I really wonder they did with that privilege. We definitely have to trust the root name servers :-( Anyway I think we-re going offtopic here :-) Regards, N.- -- http://arhuaco.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | There's the DHCP issue that other emails talk about. Another problem | is that you have to trust your DNSs and somehow it would mean that | OpenMoko trusts (blindly) a few DNS servers. I feel that trusting a | DNS is a very sensitive issue and that's why I only trust my own. Running your own caching DNS resolver is not too hard with djbdns and bind in the distros. But even then you have to "blindly" trust the root servers... http://www.renesys.com/blog/2008/05/identity_theft_hits_the_root_n_1.shtml I think DHCP is the answer, maybe when the ASU applet for WLAN is working and the NetworkManager replacement is up it won't be an issue. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiIpSkACgkQOjLpvpq7dMqYpACfZ8xPYUazAFKpKNM05XAShd6d IJ8AoJIf7Y4C1XVX/2fj11JaAvhrIGDd =IPyv -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
> if they have to ssh in and edit resolv.conf - i see it as no big > addition to > having to issue iptables, ifconfig etc. commands to enable your host > desktop to > route packets for your freerunner anyway - so one way or another you'd > fiddling with scripts and command-line goop. the same script to set up > ifconfig/iptables could ALSO scp a resolv.conf over that works (eg a > copy of > your host system's resolv.conf). :) distributions like suse shield the user mostly from commandline actions (and as the suse problems recently show, sometime even prevent successfully executing them). thus, there will be no script to setup routing, perforate firewall, ... the user might even use a graphic frontend to ssh into the fr. additionally, while vi is a nice editor it might not be everybody's choice, let alone easily usable for the common suse user (no offence) -- fiddling w/ vi just to change a number in a file might not be that funny, then. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
On Thu, 24 Jul 2008 17:06:33 +0200 "arne anka" <[EMAIL PROTECTED]> babbled: > > Stuff like dhclient/udhcpcd and/or NetworkManager manages the > > resolv.conf for you. AFIAK the problem is that the current firmwares do > > not properly support this via GUI. > > what he's talking about is, probably, that most people try the first steps > by _usb_ connection! > and usually (even if you run a dhcp server on your computer) usb > networking is no scenario for dynamic address allocation. > thus, new users see themselves rather fast confronted with the need to > edit the resolv.conf thru an ssh connection with vi -- because desktops > ususally do not do name resolution but rely on a router or so. > therefore the current default 192.168.0.200 is not much help either. > > insofar it's probably a better idea to put some open dn servers into the > default resolv.conf -- it gets overwritten by networkmanager/whatever soon > enough. if they have to ssh in and edit resolv.conf - i see it as no big addition to having to issue iptables, ifconfig etc. commands to enable your host desktop to route packets for your freerunner anyway - so one way or another you'd fiddling with scripts and command-line goop. the same script to set up ifconfig/iptables could ALSO scp a resolv.conf over that works (eg a copy of your host system's resolv.conf). :) -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
On Thu, Jul 24, 2008 at 9:15 AM, Brian C <[EMAIL PROTECTED]> wrote: > Suggestion: > > The rootfs should contain a resolv.conf that lists some > publicly-available dns servers so that people with new FreeRunners would > have a chance of getting net access without editing that file first. Hi Brian. There's the DHCP issue that other emails talk about. Another problem is that you have to trust your DNSs and somehow it would mean that OpenMoko trusts (blindly) a few DNS servers. I feel that trusting a DNS is a very sensitive issue and that's why I only trust my own. Best regards, N.- -- http://arhuaco.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
> Stuff like dhclient/udhcpcd and/or NetworkManager manages the > resolv.conf for you. AFIAK the problem is that the current firmwares do > not properly support this via GUI. what he's talking about is, probably, that most people try the first steps by _usb_ connection! and usually (even if you run a dhcp server on your computer) usb networking is no scenario for dynamic address allocation. thus, new users see themselves rather fast confronted with the need to edit the resolv.conf thru an ssh connection with vi -- because desktops ususally do not do name resolution but rely on a router or so. therefore the current default 192.168.0.200 is not much help either. insofar it's probably a better idea to put some open dn servers into the default resolv.conf -- it gets overwritten by networkmanager/whatever soon enough. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Suggestion: default /etc/resolv.conf
Suggestion: The rootfs should contain a resolv.conf that lists some publicly-available dns servers so that people with new FreeRunners would have a chance of getting net access without editing that file first. Despite clear instructions on the wiki, this issue continues to cause people problems and so the question comes up constantly on the list. Brian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
Hi, I am not sure that this is a good suggestion. Brian C schrieb: > Suggestion: > > The rootfs should contain a resolv.conf that lists some > publicly-available dns servers so that people with new FreeRunners would > have a chance of getting net access without editing that file first. Stuff like dhclient/udhcpcd and/or NetworkManager manages the resolv.conf for you. AFIAK the problem is that the current firmwares do not properly support this via GUI. Regards Robert signature.asc Description: OpenPGP digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Suggestion: default /etc/resolv.conf
As far as I know .. it's useless because every time you get a DHCP lease from a different server, it overrides your resolv.conf with it's own favourite DNS servers. On Thu, Jul 24, 2008 at 5:15 PM, Brian C <[EMAIL PROTECTED]> wrote: > Suggestion: > > The rootfs should contain a resolv.conf that lists some > publicly-available dns servers so that people with new FreeRunners would > have a chance of getting net access without editing that file first. > > Despite clear instructions on the wiki, this issue continues to cause > people problems and so the question comes up constantly on the list. > > Brian > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
