Doug H proposed the following which solved the problem for me:
For one time only command line addition it should look something like
this:
Check current state...
[root@localhost ~]# cat /etc/resolv.conf
# Generated by NetworkManager
[root@localhost ~]# ip route
[root@localhost ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
link/ether 08:00:27:ca:d8:42 brd ff:ff:ff:ff:ff:ff
[root@localhost ~]#
Use interface "enp0s3"...
(The device, network used, ip used and default route must be what would
work for your setup)
[root@localhost ~]# echo "nameserver 8.8.8.8" > /etc/resolv.conf
[root@localhost ~]# ip addr add 192.168.1.5/24 dev enp0s3
[root@localhost ~]# route add default gw 192.168.100.254 enp0s3
Verify...
[root@localhost ~]# ping -c2
google.com
PING
google.com (172.217.14.206) 56(84) bytes of data.
64 bytes from
sea30s01-in-f14.1e100.net (172.217.14.206): icmp_seq=1
ttl=55 time=38.0 ms
64 bytes from
sea30s01-in-f14.1e100.net (172.217.14.206): icmp_seq=2
ttl=55 time=38.7 ms
---
google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 38.019/38.379/38.740/0.360 ms
[root@localhost ~]#
--
Doug H.