Saturday, January 8, 2011

Trinity Rescue Kit (TRK) 3.4 does not resolve DNS out of the box

If you boot the Trinity Rescue Kit (TRK) 3.4 build 367 and try to run a tool that requires the internet, such as a virus scan, you may get an error like this:

Neither DNS nor proxy parameters for wget found so no internet connection, cannot fetch AV engine

Attempting to ping google.com from a shell returns this error:
ping: unknown host google.com

The solution seems to be to launch dhcpcd from the command line:

9 comments:

  1. Thank you this was super helpful. Is 3.4 bugged?

    ReplyDelete
  2. I haven't seen any other comments around the internet on this issue, so maybe it works for most people. I'm not sure why we ran into this problem...

    ReplyDelete
  3. I recently downloaded v3.4 and had the same problem when letting TRK obtain an IP address via DHCP at startup. The problem was that "/etc/resolv.conf" did not exist. The missing file and "nameserver" line was created when I manually ran the "setip" command.

    ReplyDelete
  4. I was having this problem as well, even as of 3.4 build 372! Thank you for your blog entry. Running dhcpcd fixed the issue. (I don't know why it was necessary because the Trinity system found an IP address at boot time via DHCP just fine.)

    ReplyDelete
  5. This worked for me, Thx

    ReplyDelete
  6. My many thanks !

    ReplyDelete
  7. Great thanks. I could never figure this one out!

    ReplyDelete
  8. On an HP Pavilion i5 system, had to add the following 2 lines to the file ~/.wgetrc:

    use_proxy=yes
    http_proxy=127.0.0.1:8080

    Hint came from http://stackoverflow.com/questions/11211705/setting-proxy-in-wget

    Still had problems pinging google.com, etc., but was able to get the AV definitions, etc.

    ReplyDelete
  9. On an HP Pavilion i5, had to add the following 2 lines at the top of the ~/.wgetrc file:

    use_proxy=yes
    http_proxy=127.0.0.1:8080

    After that, I could get the AV updates, but still had problems pinging google.com, etc. Neither of the previous 2 solutions worked for me.

    The hint came from http://stackoverflow.com/questions/11211705/setting-proxy-in-wget

    ReplyDelete