Multicast packets are going through admin interface because it is managed by /lib/svc/method/net-svc configuration. One of its parameter says
It says multicast should go via NODENAME. That means, whatever is hostname and uname -n returns. By default hostname is set to admin interface. Two changes I made :
-Changed hostname and zonename in /etc/hosts, so at zonemanager level, it look to pubic IP
-In zonecfg, I moved up the public interface, so it goes FIRST in zone description file.
These 2 Users Gave Thanks to solaris_1977 For This Post:
Hello all,
I have the following question:
if you join a multicast group (with setsockopt() and IP_ADD_MEMBERSHIP) and specify INADDR_ANY as network interface to join on, the kernel is supposed to choose which interface to use (if there are multiple network interfaces, of course).
Does... (2 Replies)
Double question here ... Running on Debian Etch and Apache 2.0
1) Using mod_proxy and/or mod_proxy_http in apache 2.0.
The basics of using mod_proxy are pretty simple so long as you're using a static config. I'm trying to figure out how to do it dynamically - that is, allow the entry of a... (4 Replies)
I'm not an advanced user by any strech, that being said here is my problem:
I ran "reboot" on a sun blade 2500
When loading up it runs through the usual routine, checking disks, filesystems and then it locks up
after the following message:
*****
starting rpc services: rpcbind... (6 Replies)
Hi all,
I encounter some problem with my e1000g interface running on sol 10. I can't permanently change the auto-nego to disable, if i use ndd commands, it will only stay until the next reboot.
But i can't change the link speed either is set to /etc/init.d/nddconfig or using ndd commands.
... (1 Reply)
Hello,
I'm writing to you because I encountered the following problem. My program displayes all network interfaces that are available in the system, but I would like to add a functionality in which a user can enter a destination address IP (ex. the IP address of the Google search engine) and will... (1 Reply)
Hi,
I am using the ce interface on my Solaris 9 server and there is significant packet loss when transmitting large packets. Does anyone have a fix for this?
----10.1.0.0 PING Statistics----
51 packets transmitted, 42 packets received, 17% packet loss
round-trip (ms) min/avg/max =... (12 Replies)
RHEL 7.0, IPV6
Scenario:
I have routed specific network using network scripts.
1. "ip -6 route show" shows that route has been added. ( with metric 1024)
2. Ping of the specific IP through that route is successful.
3. Now after few days, for some reason, we see that cache route appears for... (3 Replies)
Discussion started by: msr1981
3 Replies
LEARN ABOUT NETBSD
compat_osf1
COMPAT_OSF1(8) BSD System Manager's Manual COMPAT_OSF1(8)NAME
compat_osf1 -- setup procedure for running OSF/1 binaries
DESCRIPTION
NetBSD supports running OSF/1 (a.k.a Digital Unix, a.k.a. Tru64) binaries on NetBSD/alpha systems. Most programs should work, including the
ones that use the shared object libraries. Programs that make direct MACH system calls will not work. The OSF/1 compatibility feature is
active for kernels compiled with the COMPAT_OSF1 option enabled (see options(4)).
To run dynamically linked programs, you will need the OSF/1 shared libraries, runtime linker, and certain configuration files found in /etc.
These are installed in a ``shadow root'' directory called /emul/osf1. Any file operations done by OSF/1 programs run under NetBSD will look
in this directory first, and fall back to the file system proper. So, if an OSF/1 program opens /etc/svc.conf, NetBSD will first try to open
/emul/osf1/etc/svc.conf, and if that file does not exist it will then try /etc/svc.conf. Shared libraries and configuration specific to
OSF/1 should be installed in the shadow tree.
Setting up /emul/osf1
The simple technique is to install pkgsrc/emulators/osf1_lib. (You may also want to install pkgsrc/www/navigator and/or pkgsrc/www/communi-
cator.)
Alternatively, if you have access to an OSF/1 machine and if the licensing details permit, you can copy the contents of:
/shlib
/usr/shlib
/etc/sia
/usr/lib/X11/locale
(The latter is required to run Netscape Navigator or Communicator.)
Also copy
/etc/svc.conf
/usr/ccs/lib/cmplrs/otabase/libots.so
/sbin/loader
Or, simply NFS mount the appropriate directories under /emul/osf1.
SEE ALSO config(1), options(4)BUGS
Your hostname(1) must contain a dot or your resolv.conf(5) must contain a search line. Without one of those, the OSF/1 resolver will die and
no hostname resolution will be possible.
Certain values in /emul/osf1/etc/svc.conf can cause programs to fail with ``Bad system call''.
Pathnames pointed to by symbolic links are not looked up in the shadow root when running an OSF/1 executable. This is not consistent.
BSD November 4, 1999 BSD