Re: [OpenIndiana-discuss] extra entry in /etc/hosts after each reboot
This is a setting done by napp-it. It adds a entry to /etc/host like
127.0.0.1hostname
reason:
Without this setting your root console is spammed with dns warnings.
in newest nightly, i added a comment at this point
Gea
Am 17.06.2013 22:14, schrieb w...@vandenberge.us:
Thanks for the useful responses everyone. As one of the responses I received P2P
mentioned, it turned out to be a fairly welknown issue with the snippet below in
the agent-bootinit.pl script that comes with napp-it and not an OpenIndiana
issue at all.
Regards,
W
# check/update /etc/hosts: 127.0.0.1 hostname (old hostname missing)
my $ok=`hostname`;
$r=`cat /etc/hosts`; $r=~s/\n+/\n/gs;
@t=(); @t=split(/\n/,$r);
foreach my $t (@t) {
if ($t=~/^127.0.0.1\s+$ok\b/) { $ok=1; last; }
}
if ($ok ne 1) {
push (@t,127.0.0.1\t$ok\n);
$t=join(\n,@t);
open (PF, /etc/hosts);
print PF $t;
close (PF);
}
On June 17, 2013 at 3:55 PM Roel_D openindi...@out-side.nl wrote:
Aren't NWam and /network/default running together?
Kind regards,
The out-side
Op 17 jun. 2013 om 20:16 heeft James Carlson carls...@workingcode.com het
volgende geschreven:
On 06/17/13 11:59, w...@vandenberge.us wrote:
At this point the interface is plumbed with the 127.0.0.1 address and the
machine is essentially unreachable over the network. This machine is a
plain
OpenIndiana install with napp-it on it.
Its replica, installed at the same time and configured identically, is not
exhibiting this kind of behavior. I've been searching where during start-up
this
is occurring but have not been able to find anything yet.
A few ideas in no particular order:
1. Right after one of these bad boots, do an ls -l /etc/inet/hosts
to find out when the file was modified. Then do svcs -s stime to find
out what service(s) were started at around the time the file was
touched. Then go look at the method scripts for the suspicious ones.
2. Assuming it's a normal method of some sort that's doing this, grep
around in /lib/svc/method/*.
3. Try one of the napp-it lists to see if someone there knows about this
sort of behavior. I haven't seen it, and all of the old-school
automatic hosts file modifications I've seen have always had an
automatically-generated # ... comment describing the source of the
change, so this sounds like something newish.
--
James Carlson 42.703N 71.076W carls...@workingcode.com
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] NWAM for static IP on a VNIC
Hello all, I am trying to get the following with NWAM: a physical NIC is connected to whatever network is available, usually with DHCP. Also there is a VNIC on an internal etherstub which serves local zones with tests, etc. The VNIC has a fixed IP address. This all works nicely with legacy configuration via files or ipadm, except that for the latter I can not set the interface/address enabled not-temporarily (i.e. it is down after reboots). Now I am trying to configure the same with NWAM, and the vnic interface remains in offline* state (nwamadm list) after the service restart. According to ifconfig, it is not even plumbed (and becomes unplumbed if I had it set up before restarting the SMF service). Any ideas on what am I doing wrong? Disclaimer: I am pretty new to NWAM indeed :) Screenshots: root@n54l:~# ifconfig -a lo0: flags=2001000849UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL mtu 8232 index 1 inet 127.0.0.1 netmask ff00 tun0: flags=10011008d1UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,ROUTER,IPv4,FIXEDMTU mtu 1500 index 4 inet 192.168.131.50 -- 192.168.131.49 netmask ether 90:c1:21:f6:4:ff bge0: flags=1104843UP,BROADCAST,RUNNING,MULTICAST,DHCP,ROUTER,IPv4 mtu 1500 index 9 inet 192.168.1.111 netmask ff00 broadcast 192.168.1.255 ether 28:92:4a:36:b:c8 lo0: flags=2002000849UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL mtu 8252 index 1 inet6 ::1/128 bge0: flags=20002004841UP,RUNNING,MULTICAST,DHCP,IPv6 mtu 1500 index 9 inet6 fe80::2a92:4aff:fe36:bc8/10 ether 28:92:4a:36:b:c8 root@n54l:~# ipadm show-if IFNAME STATECURRENT PERSISTENT lo0ok -m-v--46 --- tun0 ok -mp---4- --- bge0 ok bm46 --- vnic127001 disabled -46 root@n54l:~# ipadm show-addr ADDROBJ TYPE STATEADDR lo0/v4static ok 127.0.0.1/8 tun0/_a static ok 192.168.131.50-192.168.131.49 bge0/_b dhcp ok 192.168.1.111/24 lo0/v6static ok ::1/128 bge0/_a addrconf ok fe80::2a92:4aff:fe36:bc8/10 vnic127001/v4 static disabled 192.168.127.1 root@n54l:~# ipadm show-addrprop ADDROBJ PROPERTY PERM CURRENT PERSISTENT DEFAULT POSSIBLE lo0/v4broadcast r- -- -- -- -- lo0/v4deprecated rw off -- off on,off lo0/v4prefixlen rw 8 -- 8 1-30,32 lo0/v4privaterw off -- off on,off lo0/v4transmit rw on -- on on,off lo0/v4zone rw global -- global -- tun0/_a broadcast r- -- -- -- -- tun0/_a deprecated rw off -- off on,off tun0/_a prefixlen rw -- -- -- -- tun0/_a privaterw off -- off on,off tun0/_a transmit rw on -- on on,off tun0/_a zone rw global -- global -- bge0/_b broadcast r- 192.168.1.255 -- 192.168.1.255 -- bge0/_b deprecated rw off -- off on,off bge0/_b prefixlen rw 24 -- 24 1-30,32 bge0/_b privaterw off -- off on,off bge0/_b transmit rw on -- on on,off bge0/_b zone rw global -- global -- lo0/v6broadcast r- -- -- -- -- lo0/v6deprecated rw off -- off on,off lo0/v6prefixlen rw 128 -- 64 1-126,128 lo0/v6privaterw off -- off on,off lo0/v6transmit rw on -- on on,off lo0/v6zone rw global -- global -- ADDROBJ PROPERTY PERM CURRENT PERSISTENT DEFAULT POSSIBLE ipadm: warning: no such object 'vnic127001/v4'Object not found vnic127001/v4 broadcast ?? ? ? ? root@n54l:~# nwamadm list TYPEPROFILESTATE ncp Automatic online ncu:physbge0 online ncu:ip bge0 online ncu:physvnic127001 online ncu:ip vnic127001 offline* loc Automatic online loc NoNet offline loc User
Re: [OpenIndiana-discuss] NWAM for static IP on a VNIC
On 2013-12-19 16:52, Jim Klimov wrote: Hello all, I am trying to get the following with NWAM: a physical NIC is connected to whatever network is available, usually with DHCP. Also there is a VNIC on an internal etherstub which serves local zones with tests, etc. The VNIC has a fixed IP address. This all works nicely with legacy configuration via files or ipadm, except that for the latter I can not set the interface/address enabled not-temporarily (i.e. it is down after reboots). Forgot to add the screenshot that the ipadm part works well by just enabling the interface (which can only be done as a temporary action, i.e. from an init-script): root@n54l:~# ipadm enable-if -t vnic127001 root@n54l:~# ipadm enable-addr -t vnic127001/v4 ipadm: could not enable address: Address object already exists root@n54l:~# ifconfig -a lo0: flags=2001000849UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL mtu 8232 index 1 inet 127.0.0.1 netmask ff00 tun0: flags=10011008d1UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,ROUTER,IPv4,FIXEDMTU mtu 1500 index 4 inet 192.168.131.50 -- 192.168.131.49 netmask ether 20:c4:21:f6:4:ff bge0: flags=1104843UP,BROADCAST,RUNNING,MULTICAST,DHCP,ROUTER,IPv4 mtu 1500 index 9 inet 192.168.1.111 netmask ff00 broadcast 192.168.1.255 ether 28:92:4a:36:b:c8 vnic127001: flags=1100843UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4 mtu 9000 index 10 inet 192.168.127.1 netmask ff00 broadcast 192.168.127.255 ether 2:8:20:3f:3f:8c lo0: flags=2002000849UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL mtu 8252 index 1 inet6 ::1/128 bge0: flags=20002004841UP,RUNNING,MULTICAST,DHCP,IPv6 mtu 1500 index 9 inet6 fe80::2a92:4aff:fe36:bc8/10 ether 28:92:4a:36:b:c8 vnic127001: flags=20002000840RUNNING,MULTICAST,IPv6 mtu 9000 index 10 inet6 ::/0 ether 2:8:20:3f:3f:8c And the NWAM config in raw mode (empty lines added for readability): root@n54l:~# cat /etc/nwam/ncp-Automatic.conf link:bge0 type=uint64,0;class=uint64,0;parent=string,Automatic;enabled=boolean,true;activation-mode=uint64,4;priority-group=uint64,0;priority-mode=uint64,1; interface:bge0 type=uint64,1;class=uint64,1;parent=string,Automatic;enabled=boolean,true;ip-version=uint64,4,6;ipv4-addrsrc=uint64,0;ipv6-addrsrc=uint64,0,1; interface:vnic127001 type=uint64,1;class=uint64,1;parent=string,Automatic;enabled=boolean,true;ipv6-addrsrc=uint64,0,1;ip-version=uint64,4;ipv4-addrsrc=uint64,2;ipv4-addr=string,192.168.127.1; link:vnic127001 type=uint64,0;class=uint64,0;parent=string,Automatic;enabled=boolean,true;activation-mode=uint64,4;priority-group=uint64,0;priority-mode=uint64,1; Thanks for ideas, //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] extra entry in /etc/hosts after each reboot
Unfortunately, for people (like myself) that put a hostname instead of an IP
address in the /etc/hostname.interface files that means the system will become
inaccessible from the network every reboot when running out-of-the-box napp-it.
A simple workaround is to just comment out the section below from the
agent-bootinit.pl script. I have not seen any DNS warnings on the console though
but then again I run headless most of the time. Personally, I'm not fond of
applications that modify system files every time they run (upon first
installation is one thing, but every restart is quite another), but that's just
me.
Wim
On December 19, 2013 at 6:36 AM Guenther Alka a...@hfg-gmuend.de wrote:
This is a setting done by napp-it. It adds a entry to /etc/host like
127.0.0.1 hostname
reason:
Without this setting your root console is spammed with dns warnings.
in newest nightly, i added a comment at this point
Gea
Am 17.06.2013 22:14, schrieb w...@vandenberge.us:
Thanks for the useful responses everyone. As one of the responses I received
P2P
mentioned, it turned out to be a fairly welknown issue with the snippet
below in
the agent-bootinit.pl script that comes with napp-it and not an OpenIndiana
issue at all.
Regards,
W
# check/update /etc/hosts: 127.0.0.1 hostname (old hostname missing)
my $ok=`hostname`;
$r=`cat /etc/hosts`; $r=~s/\n+/\n/gs;
@t=(); @t=split(/\n/,$r);
foreach my $t (@t) {
if ($t=~/^127.0.0.1\s+$ok\b/) { $ok=1; last; }
}
if ($ok ne 1) {
push (@t,127.0.0.1\t$ok\n);
$t=join(\n,@t);
open (PF, /etc/hosts);
print PF $t;
close (PF);
}
On June 17, 2013 at 3:55 PM Roel_D openindi...@out-side.nl wrote:
Aren't NWam and /network/default running together?
Kind regards,
The out-side
Op 17 jun. 2013 om 20:16 heeft James Carlson carls...@workingcode.com het
volgende geschreven:
On 06/17/13 11:59, w...@vandenberge.us wrote:
At this point the interface is plumbed with the 127.0.0.1 address and the
machine is essentially unreachable over the network. This machine is a
plain
OpenIndiana install with napp-it on it.
Its replica, installed at the same time and configured identically, is
not
exhibiting this kind of behavior. I've been searching where during
start-up
this
is occurring but have not been able to find anything yet.
A few ideas in no particular order:
1. Right after one of these bad boots, do an ls -l /etc/inet/hosts
to find out when the file was modified. Then do svcs -s stime to find
out what service(s) were started at around the time the file was
touched. Then go look at the method scripts for the suspicious ones.
2. Assuming it's a normal method of some sort that's doing this, grep
around in /lib/svc/method/*.
3. Try one of the napp-it lists to see if someone there knows about this
sort of behavior. I haven't seen it, and all of the old-school
automatic hosts file modifications I've seen have always had an
automatically-generated # ... comment describing the source of the
change, so this sounds like something newish.
--
James Carlson 42.703N 71.076W carls...@workingcode.com
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox 4.3.x (2!) and oi 151a8? working?
On 5/12/2013 11:56 AM, Carl Brewer wrote: I just bumped VB up to 4.3.4 and it seems to be working fine on OI 151a8 For the archive, this has been rock solid for me since I did it. Carl ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox 4.3.x (2!) and oi 151a8? working?
On 13-12-19 02:38 PM, Carl Brewer wrote: On 5/12/2013 11:56 AM, Carl Brewer wrote: I just bumped VB up to 4.3.4 and it seems to be working fine on OI 151a8 For the archive, this has been rock solid for me since I did it. That is good to know. Just a note 4.3.6 was released and it fixed a regression: Solaris hosts: fixed accessing the host driver from non-global zones (4.3 regression, bug #12271) Geoff ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
