On 18/04/2020 21:48, Marvin Jones via trinity-users wrote:
> On Sat, 18 Apr 2020, Michael Howard via trinity-users wrote:
>
>> On 18/04/2020 21:00, Marvin Jones via trinity-users wrote:
>>> Years go by between the times I install a new Ubuntu/Trinty.
>>> It is now time again -- this time to build a machine
>>> to replace my wife's antique Win XP.
>>>
>>> I just did the install with Trinity's CD image Ubuntu 18.02/Trinity 14.07.
>>>
>>> I want to set a static IP for the box -- and get rid of the DHCP crap.
>>>
>>> All the searching either shows
>>>
>>> Make changes to the /etc/netplan yaml file
>>> 	-- there isn't any - just an empty directory!
>>>
>>>   -or-
>>>
>>> "Click on top right network icon and select settings corresponding to
>>> the network interface you wish to assign with the static IP address."
>>> 	--- ya, well, this is Trinity.
>>>
>>> ..and, of course NONE of this resembles anything I remember from
>>> hacking my Ubuntu 16.04 with Trinity from a WAY LONG time ago.
>>>
>>> Could someone please point me where to start?
>>>
>>> Thank you!
>>> Jonesy
>> Well, setting your ip isn't specifically a TDE job, more an OS task.
>>
>> If you wand a static IP, set it in the '/etc/network/interfaces' file. You can
>> access it from the desktop if you wish but easier from the command line.
>>
>> Edit the file with your favourite editor. On the line for the interface you are
>> interested in, change 'dhcp' to 'static' then add something like the following
>> immediately after that line (but change to suit your network);
>>
>> address 192.168.1.5
>> netmask 255.255.255.0
>> gateway 192.168.1.254
> It's never easy.....
>
>   |bea@nix-bea:~$ cat /etc/network/interfaces
>   |# interfaces(5) file used by ifup(8) and ifdown(8)
>   |auto lo
>   |iface lo inet loopback
>   |bea@nix-bea:~$
>
> Do you mean add at the bottom:
> .
> dhcp static
> address 192.168.1.5
> netmask 255.255.255.0
> gateway 192.168.1.254
>
> ... using my network's values....?
>
> Jonesy
Ah, your using ubuntu 18. I was a bit quick of the mark :) I'm a debian 
guy but ...

If you have no *.yaml file in your /etc/netplan directory then you might 
not have any networking setup. If you have no networking setup, it might 
be you are not connected to your router by any means?

To check your current settings, use 'ip a' and 'ip route show' at a 
command prompt. This will give you a view of you current setup, i.e. ip 
range and gateway etc, if you have any, which you probably haven't.

If not then create one as '99_config.yaml' with your specific details. 
If when you did the 'ip a' above, you got info, great, if not you will 
need to get the ip range info from your router. You could do this by 
setting up dhcp first (not sure why you don't want to use dhcp, it is 
easier). The yaml file for dhcp would be;

network:
 ��� ��� version: 2
 ��� ��� renderer: networkd
 ��� ��� ethernets:
 ��� ����� enp3s0:
 ��������� dhcp4: true

where enp3s0 would need to be the device name returned by 'ip a'. 
probably the second stanza of that printout. Once dhcp is setup, you 
will know the network details you need to setup static addressing.

Your yaml file for static would be along the lines of (but not with the 
10.10.10.0 ip range or the eth0 device name);

network:
 � version: 2
 � renderer: networkd
 � ethernets:
 ��� eth0:
 ����� addresses:
 ������� - 10.10.10.2/24
 ����� gateway4: 10.10.10.1
 ����� nameservers:
 ��������� search: [mydomain, otherdomain]
 ��������� addresses: [10.10.10.1, 1.1.1.1]

Change the device name and ip details above to match your own. Or ask 
again when you know more details.

-- 
Michael Howard