Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: Ubuntu 16.04 - Where is IP4.ADDRESS set and/or stored?

  1. #11
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    26,047
    Distro
    Ubuntu Development Release

    Re: Ubuntu 16.04 - Where is IP4.ADDRESS set and/or stored?

    Any thoughts? Should dhcp be true?
    Not if you want a static address. See my example above.

    What, exactly, is http://192.168.80.170/ and why do you want to reach it?

    I doin't think you shoud eliminate the 127.0.1.1 line in /etc/hosts. For comparison, my hosts file reads, in part:
    Code:
    127.0.0.1       localhost
    127.0.1.1       T440p
    
    # The following lines are desirable for IPv6 capable hosts
    ::1     ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    Where T440p is the name of my computer and agrees with:
    Code:
    cat /etc/hostname
    mydomain@ubuntu07
    This suggests that the hostname is ubuntu07. I believe that should be reflected in hosts opposite 127.0.1.1.

    Please make some corrections, test and I'll check in tomorrow.
    Last edited by chili555; July 23rd, 2018 at 03:23 AM.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.

  2. #12
    Join Date
    Apr 2017
    Beans
    7

    Re: Ubuntu 16.04 - Where is IP4.ADDRESS set and/or stored?

    chili555, I want to say thank you so very much for your help.

    As usual, when one cannot find a bug, one is likely looking in the wrong place.

    I was so frustrated at not being able to track down why things were not working on 18.04 I reinstalled 16.04.

    Things did not work in 16.04. Huh? I have another machine running 16.04 where everything works.

    All the stuff in my new 16.04 was nearly identical to the 16.04 on my other machine. A real head scratcher.

    After pulling out the last strands of hair on my head I found the problem. It was in the VMWare setup of the network adapter. Specifically, on the machine that works, I had the adapter set to bridged. On the one that was giving bizarre results the network adapter was set to NAT.

    Again, chili55, I thank you for your time and effort. I hope all of this helps others.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

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