setup of 18.04

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

setup of 18.04

Ian A. Taylor

Sir/Madam

I have just upgraded to 18.04

I currently have two issues that I am having some trouble restoring

a) I have a static IP on my ethernet adapter

    I can set the DNS servers ok but I cannot see howto set the search pass parameter ,

     which was so easy to set in 16.04


b) I like to run various virtual windows

    I have two monitors

    currently only on of the monitors is in a particular virtual window

    the other monitor is visible to all the virtual windows

    I want to put both monitors in a particular virtual window

    and then move from virtual window to virtual window

    like I could do so effortlessly in 14.04 & 16.04

I regret to inform that it is not easy to see how to restore the system to the state it was in before

Thanking you.

Yours sincerely



Ian Taylor
University of St.Andrews,
School of Physics & Astronomy,
North Haugh,
St.Andrews,
Fife  KY16 9SS,
Scotland.

e-Mail :- [hidden email]
Tel    :- (0)1334-463141
Fax    :- (0)1334-463104

The University of St Andrews 
is a charity registered in 
Scotland : No SC013532.



--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: setup of 18.04

Pin2
Hi this is a graphic driver issue please update the same will be resolved.





   Sent from my iPhone

On 06-Jun-2018, at 10:08 PM, Ian A. Taylor <[hidden email]> wrote:

Sir/Madam

I have just upgraded to 18.04

I currently have two issues that I am having some trouble restoring

a) I have a static IP on my ethernet adapter

    I can set the DNS servers ok but I cannot see howto set the search pass parameter ,

     which was so easy to set in 16.04


b) I like to run various virtual windows

    I have two monitors

    currently only on of the monitors is in a particular virtual window

    the other monitor is visible to all the virtual windows

    I want to put both monitors in a particular virtual window

    and then move from virtual window to virtual window

    like I could do so effortlessly in 14.04 & 16.04

I regret to inform that it is not easy to see how to restore the system to the state it was in before

Thanking you.

Yours sincerely



Ian Taylor
University of St.Andrews,
School of Physics & Astronomy,
North Haugh,
St.Andrews,
Fife  KY16 9SS,
Scotland.

e-Mail :- [hidden email]
Tel    :- (0)1334-463141
Fax    :- (0)1334-463104

The University of St Andrews 
is a charity registered in 
Scotland : No SC013532.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: setup of 18.04

Tom H-4
In reply to this post by Ian A. Taylor
On Wed, Jun 6, 2018 at 6:38 PM, Ian A. Taylor <[hidden email]> wrote:

>
> I have just upgraded to 18.04
>
> I currently have two issues that I am having some trouble restoring
>
> a) I have a static IP on my ethernet adapter
>
> I can set the DNS servers ok but I cannot see howto set the search
> pass parameter ,
>
> which was so easy to set in 16.04

How is your network set up? Via netplan? Is resolv.conf a regular file
or a symlink? If it's a symlink, to what file? And what's in it?

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: setup of 18.04

Ian A. Taylor
Tom

Thank you for your reply but I regret to inform you it does not help me

Ok I run     systemd-resolve --status

Global
           DNSSEC NTA: 10.in-addr.arpa
                       16.172.in-addr.arpa
                       168.192.in-addr.arpa
                       17.172.in-addr.arpa
                       18.172.in-addr.arpa
                       19.172.in-addr.arpa
                       20.172.in-addr.arpa
                       21.172.in-addr.arpa
                       22.172.in-addr.arpa
                       23.172.in-addr.arpa
                       24.172.in-addr.arpa
                       25.172.in-addr.arpa
                       26.172.in-addr.arpa
                       27.172.in-addr.arpa
                       28.172.in-addr.arpa
                       29.172.in-addr.arpa
         systemd-resolve --status
Global
           DNSSEC NTA: 10.in-addr.arpa
                       16.172.in-addr.arpa
                       168.192.in-addr.arpa
                       17.172.in-addr.arpa
                       18.172.in-addr.arpa
                       19.172.in-addr.arpa
                       20.172.in-addr.arpa
                       21.172.in-addr.arpa
                       22.172.in-addr.arpa
                       23.172.in-addr.arpa
                       24.172.in-addr.arpa
                       25.172.in-addr.arpa
                       26.172.in-addr.arpa
                       27.172.in-addr.arpa
                       28.172.in-addr.arpa
                       29.172.in-addr.arpa
                       30.172.in-addr.arpa
                       31.172.in-addr.arpa
                       corp
                       d.f.ip6.arpa
                       home
                       internal
                       intranet
                       lan
                       local
                       private
                       test

Link 3 (enp8s0)
       Current Scopes: none
        LLMNR setting: yes
MulticastDNS setting: no
       DNSSEC setting: no
     DNSSEC supported: no

Link 2 (enp7s0)
       Current Scopes: DNS
        LLMNR setting: yes
MulticastDNS setting: no
       DNSSEC setting: no
     DNSSEC supported: no
          DNS Servers: 138.251.10.53
                       138.251.10.54
               30.172.in-addr.arpa
                       31.172.in-addr.arpa
                       corp
                       d.f.ip6.arpa
                       home
                       internal
                       intranet
                       lan
                       local
                       private
                       test

Link 3 (enp8s0)
       Current Scopes: none
        LLMNR setting: yes
MulticastDNS setting: no
       DNSSEC setting: no
     DNSSEC supported: no

Link 2 (enp7s0)
       Current Scopes: DNS
        LLMNR setting: yes
MulticastDNS setting: no
       DNSSEC setting: no
     DNSSEC supported: no
          DNS Servers: 138.251.10.53
                       138.251.10.54


So what is styled as Link2 (enp7s0)  has the correct DNS servers

Now it used to be that you hacked /etc/resolv.conf and SOLVED the problem

Not so now (this is progress.....

ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 39 May 31 14:10 /etc/resolv.conf ->
../run/systemd/resolve/stub-resolv.conf

cat /run/systemd/resolve/stub-resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only
through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported
modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53


So I am confused I don't know which file to edit

cat /etc/systemd/resolved.conf

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
#FallbackDNS=
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#Cache=yes
#DNSStubListener=yes

#iat 11june2018
Domains=st-andrews.ac.uk

When I click on the icon in top rhs

select my network card, click on wired settings, click on the setup for
the network card

I see the dns servers set correct but alas I cannot see how to set the
search path

In my view this used to be in this menu but has been removed in 18.04

So how do I do something as simple as setting a search path........

Yours in frustration

Ian Taylor




On 09/06/18 11:15, Tom H wrote:

> [You've emailed me off-list]
>
> On Thu, Jun 7, 2018 at 10:21 AM Ian A. Taylor <[hidden email]> wrote:
>> On 06/06/18 20:15, Tom H wrote:
>>> On Wed, Jun 6, 2018 at 6:38 PM, Ian A. Taylor <[hidden email]> wrote:
>>>> I have just upgraded to 18.04
>>>>
>>>> I currently have two issues that I am having some trouble restoring
>>>>
>>>> a) I have a static IP on my ethernet adapter
>>>>
>>>> I can set the DNS servers ok but I cannot see howto set the search
>>>> pass parameter, which was so easy to set in 16.04
>>> How is your network set up? Via netplan? Is resolv.conf a regular file
>>> or a symlink? If it's a symlink, to what file? And what's in it?
>> etc/systemd/resolved.conf
>>
>>    ls -la resolv*
>> lrwxrwxrwx 1 root root   39 May 31 14:10 resolv.conf ->
>> ../run/systemd/resolve/stub-resolv.conf
>>
>> cat stub-resolv.conf
>> nameserver 127.0.0.53
>>
>> How is network setup
>>
>> When I login there is an icon in top right for network
>> click that, select ethernet settings, wired network
>>
>> Is that what you style as netplan ?
> No, netplan is an Ubuntu-specific text configuration that's stored in
> "/etc/netplan/" to generate networkd or NM configuration at boot.
>
> The top-right icon is an NM applet. I don't use NM so I can't check
> whether these two solutions'll work.
>
> 1.a) Set the "search" or "domain" in the NM applet
>
> 1.b) Set "dns=systemd-resolved" in "/etc/NetworkManager/NetworkManager.conf
>
> or
>
> 2) Set "Domains=your_search_domain" in "/etc/systemd/resolved.conf"

--

Thanking you.

Yours sincerely



Ian Taylor
University of St.Andrews,
School of Physics & Astronomy,
North Haugh,
St.Andrews,
Fife  KY16 9SS,
Scotland.

e-Mail :- [hidden email]
Tel    :- (0)1334-463141
Fax    :- (0)1334-463104

The University of St Andrews
is a charity registered in
Scotland : No SC013532.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: setup of 18.04 SOLVED

Ian A. Taylor
Sir/Madam

I have solved this


Added dns-search path in /etc/NetworkManager/system-connections/Wired\
connection\ 1

it was not set

When I restarted the network-manager service then it works



On 14/06/18 15:12, Ian A. Taylor wrote:

> Tom
>
> Thank you for your reply but I regret to inform you it does not help me
>
> Ok I run     systemd-resolve --status
>
> Global
>           DNSSEC NTA: 10.in-addr.arpa
>                       16.172.in-addr.arpa
>                       168.192.in-addr.arpa
>                       17.172.in-addr.arpa
>                       18.172.in-addr.arpa
>                       19.172.in-addr.arpa
>                       20.172.in-addr.arpa
>                       21.172.in-addr.arpa
>                       22.172.in-addr.arpa
>                       23.172.in-addr.arpa
>                       24.172.in-addr.arpa
>                       25.172.in-addr.arpa
>                       26.172.in-addr.arpa
>                       27.172.in-addr.arpa
>                       28.172.in-addr.arpa
>                       29.172.in-addr.arpa
>         systemd-resolve --status
> Global
>           DNSSEC NTA: 10.in-addr.arpa
>                       16.172.in-addr.arpa
>                       168.192.in-addr.arpa
>                       17.172.in-addr.arpa
>                       18.172.in-addr.arpa
>                       19.172.in-addr.arpa
>                       20.172.in-addr.arpa
>                       21.172.in-addr.arpa
>                       22.172.in-addr.arpa
>                       23.172.in-addr.arpa
>                       24.172.in-addr.arpa
>                       25.172.in-addr.arpa
>                       26.172.in-addr.arpa
>                       27.172.in-addr.arpa
>                       28.172.in-addr.arpa
>                       29.172.in-addr.arpa
>                       30.172.in-addr.arpa
>                       31.172.in-addr.arpa
>                       corp
>                       d.f.ip6.arpa
>                       home
>                       internal
>                       intranet
>                       lan
>                       local
>                       private
>                       test
>
> Link 3 (enp8s0)
>       Current Scopes: none
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>
> Link 2 (enp7s0)
>       Current Scopes: DNS
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>          DNS Servers: 138.251.10.53
>                       138.251.10.54
>               30.172.in-addr.arpa
>                       31.172.in-addr.arpa
>                       corp
>                       d.f.ip6.arpa
>                       home
>                       internal
>                       intranet
>                       lan
>                       local
>                       private
>                       test
>
> Link 3 (enp8s0)
>       Current Scopes: none
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>
> Link 2 (enp7s0)
>       Current Scopes: DNS
>        LLMNR setting: yes
> MulticastDNS setting: no
>       DNSSEC setting: no
>     DNSSEC supported: no
>          DNS Servers: 138.251.10.53
>                       138.251.10.54
>
>
> So what is styled as Link2 (enp7s0)  has the correct DNS servers
>
> Now it used to be that you hacked /etc/resolv.conf and SOLVED the problem
>
> Not so now (this is progress.....
>
> ls -la /etc/resolv.conf
> lrwxrwxrwx 1 root root 39 May 31 14:10 /etc/resolv.conf ->
> ../run/systemd/resolve/stub-resolv.conf
>
> cat /run/systemd/resolve/stub-resolv.conf
> # This file is managed by man:systemd-resolved(8). Do not edit.
> #
> # This is a dynamic resolv.conf file for connecting local clients to the
> # internal DNS stub resolver of systemd-resolved. This file lists all
> # configured search domains.
> #
> # Run "systemd-resolve --status" to see details about the uplink DNS
> servers
> # currently in use.
> #
> # Third party programs must not access this file directly, but only
> through the
> # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
> different way,
> # replace this symlink by a static file or a different symlink.
> #
> # See man:systemd-resolved.service(8) for details about the supported
> modes of
> # operation for /etc/resolv.conf.
>
> nameserver 127.0.0.53
>
>
> So I am confused I don't know which file to edit
>
> cat /etc/systemd/resolved.conf
>
> #  This file is part of systemd.
> #
> #  systemd is free software; you can redistribute it and/or modify it
> #  under the terms of the GNU Lesser General Public License as
> published by
> #  the Free Software Foundation; either version 2.1 of the License, or
> #  (at your option) any later version.
> #
> # Entries in this file show the compile time defaults.
> # You can change settings by editing this file.
> # Defaults can be restored by simply deleting this file.
> #
> # See resolved.conf(5) for details
>
> [Resolve]
> #DNS=
> #FallbackDNS=
> #Domains=
> #LLMNR=no
> #MulticastDNS=no
> #DNSSEC=no
> #Cache=yes
> #DNSStubListener=yes
>
> #iat 11june2018
> Domains=st-andrews.ac.uk
>
> When I click on the icon in top rhs
>
> select my network card, click on wired settings, click on the setup
> for the network card
>
> I see the dns servers set correct but alas I cannot see how to set the
> search path
>
> In my view this used to be in this menu but has been removed in 18.04
>
> So how do I do something as simple as setting a search path........
>
> Yours in frustration
>
> Ian Taylor
>
>
>
>
> On 09/06/18 11:15, Tom H wrote:
>> [You've emailed me off-list]
>>
>> On Thu, Jun 7, 2018 at 10:21 AM Ian A. Taylor <[hidden email]>
>> wrote:
>>> On 06/06/18 20:15, Tom H wrote:
>>>> On Wed, Jun 6, 2018 at 6:38 PM, Ian A. Taylor
>>>> <[hidden email]> wrote:
>>>>> I have just upgraded to 18.04
>>>>>
>>>>> I currently have two issues that I am having some trouble restoring
>>>>>
>>>>> a) I have a static IP on my ethernet adapter
>>>>>
>>>>> I can set the DNS servers ok but I cannot see howto set the search
>>>>> pass parameter, which was so easy to set in 16.04
>>>> How is your network set up? Via netplan? Is resolv.conf a regular file
>>>> or a symlink? If it's a symlink, to what file? And what's in it?
>>> etc/systemd/resolved.conf
>>>
>>>    ls -la resolv*
>>> lrwxrwxrwx 1 root root   39 May 31 14:10 resolv.conf ->
>>> ../run/systemd/resolve/stub-resolv.conf
>>>
>>> cat stub-resolv.conf
>>> nameserver 127.0.0.53
>>>
>>> How is network setup
>>>
>>> When I login there is an icon in top right for network
>>> click that, select ethernet settings, wired network
>>>
>>> Is that what you style as netplan ?
>> No, netplan is an Ubuntu-specific text configuration that's stored in
>> "/etc/netplan/" to generate networkd or NM configuration at boot.
>>
>> The top-right icon is an NM applet. I don't use NM so I can't check
>> whether these two solutions'll work.
>>
>> 1.a) Set the "search" or "domain" in the NM applet
>>
>> 1.b) Set "dns=systemd-resolved" in
>> "/etc/NetworkManager/NetworkManager.conf
>>
>> or
>>
>> 2) Set "Domains=your_search_domain" in "/etc/systemd/resolved.conf"
>

--

Thanking you.

Yours sincerely



Ian Taylor
University of St.Andrews,
School of Physics & Astronomy,
North Haugh,
St.Andrews,
Fife  KY16 9SS,
Scotland.

e-Mail :- [hidden email]
Tel    :- (0)1334-463141
Fax    :- (0)1334-463104

The University of St Andrews
is a charity registered in
Scotland : No SC013532.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users