I might have found it.

despite all the dladm and svccfg stuff, there's evidence that the netcfg is
wrong

<Rant>
Just what the hell was wrong with editing 3 or 4 files in /etc? It worked
</Rant>

I've got to say this has to be the most overengineered rubbish since the
printing and dhcp-server subsystems (and hell, lets add getty/terminal
stuff in too) in Solaris ever.

netcfg> export
create ncp "Home"
create ncu phys "net0"
set activation-mode=manual
set priority-group=0
set priority-mode=shared
end
create ncu ip "net0"
set ip-version=ipv4,ipv6
set ipv4-addrsrc=static
set ipv4-addr="192.168.0.1/24"
set ipv4-default-route="192.168.0.200"
set ipv6-addrsrc=dhcp,autoconf,static
set ipv6-addr="fc00:dead:beef::0:0001/48"
end
create ncu ip "vnic1"
set ip-version=ipv4,ipv6
set ipv4-addrsrc=static
set ipv4-addr="192.168.254.1"
end
end
create loc "User"
set activation-mode=manual
set nameservices=dns
set nameservices-config-file="/etc/nwam/loc/User/nsswitch.conf"
set dns-nameservice-configsrc=manual
set dns-nameservice-domain="crispi.com"
set dns-nameservice-servers="192.168.0.200"
end
netcfg>



So which part of Solaris 11 is the source of truth?

/Regards/
Chris







On Sun, Mar 29, 2020 at 3:10 PM Chris Wells <[email protected]>
wrote:

> I've reverted to ncp to "DefaultFixed", and reset the network
> configuration:
>
> # netadm enable -p ncp DefaultFixed
> # ipadm create-addr -T addrconf net0/addr
> # ipadm create-ip net0
> # ipadm create-addr -T static -a local=192.168.0.1/24 net0/addr
>
>
>
> Going thru the manual (
> https://docs.oracle.com/cd/E23824_01/html/E24456/gliyc.html#scrolltoc)
> step by step:
>
> root@marvin:~# svccfg
> svc:> select dns/client
> svc:/network/dns/client> setprop config/search = astring: ("crispi.com")
> svc:/network/dns/client> setprop config/nameserver = net_address: (
> 192.168.0.5 192.168.0.6 )
> svc:/network/dns/client> select dns/client:default
> svc:/network/dns/client:default> refresh
> svc:/network/dns/client:default> validate
> svc:/network/dns/client:default> select name-service/switch
> svc:/system/name-service/switch> setprop config/host = astring: "files dns"
> svc:/system/name-service/switch> select system/name-service/switch:default
> svc:/system/name-service/switch:default> refresh
> svc:/system/name-service/switch:default> validate
> svc:/system/name-service/switch:default>
> root@marvin:~# svcadm enable dns/client
> root@marvin:~# svcadm refresh name-service/switch
> root@marvin:~# grep host /etc/nsswitch.conf
> hosts: files dns
>
> And in response to your previous question, no it's not running DHCP:
>
> root@marvin:~# ps -ef | grep -i dh
>     root 11572 11281   0 15:06:53 pts/2       0:00 grep -i dh
>
> root@marvin:~# cat /etc/resolv.conf
>
> #
> # _AUTOGENERATED_FROM_SMF_V1_
> #
> # WARNING: THIS FILE GENERATED FROM SMF DATA.
> #   DO NOT EDIT THIS FILE.  EDITS WILL BE LOST.
> # See resolv.conf(4) for details.
>
> domain crispi.com
> search crispi.com
> nameserver 192.168.0.200
>
>
>
> STILL WRONG!
>
>
>
> *** It looks like i've got a "svc:/network/dns/client" and a
> "svc:/network/dns/client:default" ***
>
> And it's the latter that's being used.....
>
>
> root@marvin:~# svcprop "*" | grep 192.168.0.200
> svc:/network/dns/client:default/:properties/config/nameserver net_address
> 192.168.0.200
> root@marvin:~# svccfg
> svc:> select svc:/network/dns/client:default
> svc:/network/dns/client:default> setprop config/search = astring: ("
> crispi.com")
> svc:/network/dns/client:default> setprop config/nameserver = net_address:
> ( 192.168.0.5 192.168.0.6 )
> svc:/network/dns/client:default> refresh
> svc:/network/dns/client:default> validate
> svc:/network/dns/client:default>
> root@marvin:~# ls -ald /etc/resolv.conf
> -rw-r--r-- 1 root root 246 Mar 29 15:08 /etc/resolv.conf
> root@marvin:~# cat /etc/resolv.conf
>
> #
> # _AUTOGENERATED_FROM_SMF_V1_
> #
> # WARNING: THIS FILE GENERATED FROM SMF DATA.
> #   DO NOT EDIT THIS FILE.  EDITS WILL BE LOST.
> # See resolv.conf(4) for details.
>
> domain crispi.com
> search crispi.com
> nameserver 192.168.0.5
> nameserver 192.168.0.6
>
> On Sun, Mar 29, 2020 at 2:58 PM Andre van Eyssen <[email protected]>
> wrote:
>
>>
>> What's in your name-service/switch config?
>>
>> On Sun, 29 Mar 2020, Chris Wells wrote:
>>
>> > No, static IP.
>> >
>> > Though I'm wondering whether I should go back and delete other NCP
>> configs:
>> >
>> > root@marvin:~# dladm show-phys
>> > LINK              MEDIA                STATE      SPEED  DUPLEX
>> DEVICE
>> > net0              Ethernet             up         1000   full      rge0
>> > vboxnet0          Ethernet             up         1000   full
>> vboxnet0
>> >
>> >
>> > root@marvin:~# dladm show-link
>> > LINK                CLASS     MTU    STATE    OVER
>> > net0                phys      1500   up       --
>> > vboxnet0            phys      1500   up       --
>> > vnic1               vnic      1500   up       net0
>> >
>> >
>> > root@marvin:~# ipadm show-addr
>> > ADDROBJ           TYPE     STATE        ADDR
>> > lo0/v4            static   ok           127.0.0.1/8
>> > net0/v4           static   ok           192.168.0.1/24
>> > vnic1/staticv4    static   ok           192.168.254.1/24
>> > lo0/v6            static   ok           ::1/128
>> > net0/v6           addrconf ok           fe80::224:1dff:fe26:db75/10
>> > net0/staticv6     static   ok           fc00:dead:beef::1/48
>> > net0/v6           addrconf ok           fd56:51f2:ccb3::3f6/128
>> >
>> >
>> > root@marvin:~# netadm list
>> > TYPE        PROFILE        STATE
>> > ncp         DefaultFixed   disabled
>> > ncp         Home           online
>> > ncu:phys    net0           online
>> > ncu:vnic    vnic1          online
>> > ncu:ip      net0           online
>> > ncu:ip      vnic1          online
>> > ncp         Automatic      disabled
>> > loc         NoNet          offline
>> > loc         Automatic      online
>> > loc         User           disabled
>> > loc         DefaultFixed   offline
>> >
>> >
>> >
>> > On Sun, Mar 29, 2020 at 1:25 PM Andre van Eyssen <[email protected]>
>> > wrote:
>> >
>> >>
>> >> Oh, this sounds familiar but the last time I got this run-around was a
>> few
>> >> years ago.
>> >>
>> >> I gather there isn't anything evil like DHCP happening with this host?
>> >>
>> >> On Sun, 29 Mar 2020, Chris Wells wrote:
>> >>
>> >>> Solaris 10 Intel Box seems to be an amnesiac.
>> >>>
>> >>>
>> >>>
>> >>> WHY WONT YOU WORK?????
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> root@marvin:~# svcprop "*" | grep 192.168.0.200
>> >>> svc:/network/dns/client:default/:properties/config/nameserver
>> net_address
>> >>> 192.168.0.200
>> >>>
>> >>> root@marvin:~# svccfg -s svc:/network/dns/client:default
>> >>> svc:/network/dns/client:default> setprop config/nameserver =
>> net_address:
>> >>> (192.168.0.5 192.168.0.6)
>> >>> svc:/network/dns/client:default> quit
>> >>> root@marvin:~# cat /etc/resolv.conf
>> >>>
>> >>> #
>> >>> # _AUTOGENERATED_FROM_SMF_V1_
>> >>> #
>> >>> # WARNING: THIS FILE GENERATED FROM SMF DATA.
>> >>> #   DO NOT EDIT THIS FILE.  EDITS WILL BE LOST.
>> >>> # See resolv.conf(4) for details.
>> >>>
>> >>> domain  crispi.com
>> >>> nameserver      192.168.0.200
>> >>>
>> >>> root@marvin:~# svcadm refresh network/dns/client
>> >>> root@marvin:~# cat /etc/resolv.conf
>> >>>
>> >>> #
>> >>> # _AUTOGENERATED_FROM_SMF_V1_
>> >>> #
>> >>> # WARNING: THIS FILE GENERATED FROM SMF DATA.
>> >>> #   DO NOT EDIT THIS FILE.  EDITS WILL BE LOST.
>> >>> # See resolv.conf(4) for details.
>> >>>
>> >>> domain  crispi.com
>> >>> nameserver      192.168.0.5
>> >>> nameserver      192.168.0.6
>> >>>
>> >>> root@marvin:~# sync
>> >>> root@marvin:~# init 6
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> # AFTER REBOOT:
>> >>>
>> >>>
>> >>> crispi@marvin:~$ cat /etc/resolv.conf
>> >>>
>> >>> #
>> >>> # _AUTOGENERATED_FROM_SMF_V1_
>> >>> #
>> >>> # WARNING: THIS FILE GENERATED FROM SMF DATA.
>> >>> #   DO NOT EDIT THIS FILE.  EDITS WILL BE LOST.
>> >>> # See resolv.conf(4) for details.
>> >>>
>> >>> domain  crispi.com
>> >>> nameserver      192.168.0.200
>> >>>
>> >>> crispi@marvin:~$ svcprop "*" | grep 192.168.0.200
>> >>> svc:/network/dns/client:default/:properties/config/nameserver
>> net_address
>> >>> 192.168.0.200
>> >>>
>> >>
>> >> --
>> >> Andre van Eyssen.                  Phone:     +61 417 211 788
>> >> mail:     [email protected]      http://andre.purplecow.org
>> >> About & Contact:          http://www.purplecow.org/andre.html
>> >>
>> >
>> >
>> >
>>
>> --
>> Andre van Eyssen.                  Phone:     +61 417 211 788
>> mail:     [email protected]      http://andre.purplecow.org
>> About & Contact:          http://www.purplecow.org/andre.html
>>
>
>
> --
> Best regards,
>
> Chris
> Please Support me on Tour de Cure 2018
> <https://tourdecure.com.au/profile/?memberId=85769&tourId=1015>
>


-- 
Best regards,

Chris
Please Support me on Tour de Cure 2018
<https://tourdecure.com.au/profile/?memberId=85769&tourId=1015>
_______________________________________________
msosug mailing list
[email protected]
http://mexico.purplecow.org/m/listinfo/msosug
Delivered for: [email protected]

Reply via email to