Find the answer to your Linux question:
Results 1 to 4 of 4
I changed my ISP just before X-mas, and had not booted into Gentoo again until quite recently. The new ISP shipped a shiny new Wireless router which I hooked up ...
  1. 01-26-2010 #1
    Jonathan183
    Jonathan183 is offline
    Linux Guru Jonathan183's Avatar
    Join Date
    Oct 2007
    Posts
    2,941

    Changed router and some versions of Linux stopped working

    I changed my ISP just before X-mas, and had not booted into Gentoo again until quite recently. The new ISP shipped a shiny new Wireless router which I hooked up and started using. I must have manually updated Arch /etc/resolv.conf at the time ... don't remember doing any update to Funtoo - I think it just worked.

    When I started Gentoo I tried to do an emerge --sync and got
    Code:
    Notice: [Errno -2] Name or service not known
>>> Starting rsync with rsync://rsync.uk.gentoo.org/gentoo-portage/...
>>> Checking server timestamp ...
timed out
>>> Retrying...
Notice: [Errno -2] Name or service not known


>>> Starting retry 1 of 3 with rsync://rsync.uk.gentoo.org/gentoo-portage/
>>> Checking server timestamp ...
timed out
>>> Retrying...
Notice: [Errno -2] Name or service not known


>>> Starting retry 2 of 3 with rsync://rsync.uk.gentoo.org/gentoo-portage/
>>> Checking server timestamp ...
timed out
>>> Retrying...
Notice: [Errno -2] Name or service not known


>>> Starting retry 3 of 3 with rsync://rsync.uk.gentoo.org/gentoo-portage/
>>> Checking server timestamp ...
timed out
    I finally figured out /etc/resolv.conf needed updating ... nameserver 192.168.1.1 instead of 192.168.0.1 for the old router. Anyway I just thought I'd share
    Reply With Quote Reply With Quote
  2. 01-27-2010 #2
    rcgreen
    rcgreen is offline
    Linux Engineer rcgreen's Avatar
    Join Date
    May 2006
    Location
    the hills
    Posts
    1,114
    Your dhcp client daemon handles this. Most likely it is
    dhcpcd. Ordinarily it will update your /etc/resolv.conf
    automatically, along with obtaining an IP address. If it fails
    to work, you can tweak its configuration file.
    Reply With Quote Reply With Quote
  3. 01-27-2010 #3
    elija
    elija is offline
    Trusted Penguin elija's Avatar
    Join Date
    Jul 2004
    Location
    Either at home or at work or down the pub
    Posts
    2,298
    Ah but for those of us who only use static IP addresses it's worth bearing in mind
    If we hit that bullseye, the rest of the dominoes will fall like a house of cards. Checkmate! (Zapp Brannigan)


    My new blog. It's probably not as good as I think it is.
    Reply With Quote Reply With Quote
  4. 01-27-2010 #4
    Jonathan183
    Jonathan183 is offline
    Linux Guru Jonathan183's Avatar
    Join Date
    Oct 2007
    Posts
    2,941
    Quote Originally Posted by rcgreen View Post
    Your dhcp client daemon handles this. Most likely it is
    dhcpcd. Ordinarily it will update your /etc/resolv.conf
    automatically, along with obtaining an IP address. If it fails
    to work, you can tweak its configuration file.
    That's what I expected ... and I was looking for a problem with emerge ... I searched for the issue but the only things I found were installation related - the system has been working for over a year so I did not read any further.

    I was even beginning to trawl back through config archives from dispatch-conf ... the penny dropped for me when I tried to use wget to download something while I fixed emerge.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules

...