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 DEBIAN
newlist
NEWLIST(8) System Manager's Manual NEWLIST(8)NAME
newlist - Create a new, unpopulated Mailman mailing list.
SYNOPSIS
newlist [options] [listname] [listadmin-addr] [admin-password]
OPTIONS -l language, --language=language
Make the list's preferred language `language', which must be the (mostly two letter) language code as found under /usr/share/mail-
man.
-u urlhost, --urlhost=urlhost
Gives the list's web interface host name.
-e emailhost, --emailhost=emailhost
Gives the list's email domain name.
-q, --quiet
Normally the administrator is notified by email (after a prompt) that their list has been created. This option suppresses that
notification and the prompting.
-h, --help
Print a small help text and exit
SECURITY
Including the admin-password on the command line is a small security risk if you have untrusted users on the system.
NOTES
You can specify as many of the arguments as you want on the command line: you will be prompted for the missing ones.
Every Mailman list has two parameters which define the default host name for outgoing email, and the default URL for all web interfaces.
When you configured Mailman, certain defaults were calculated, but if you are running multiple virtual Mailman sites, then the defaults may
not be appropriate for the list you are creating.
You also specify the domain to create your new list in by typing the command like so:
newlist --urlhost=www.example.com mylist
where `www.example.com' should be the base hostname for the URL to this virtual hosts's lists. E.g. with this setting people will view the
general list overviews at http://www.example.com/mailman/listinfo. Also, www.example.com should be a key in the VIRTUAL_HOSTS mapping in
mm_cfg.py/Defaults.py if the email hostname to be automatically determined.
If you want the email hostname to be different from the one looked up by the VIRTUAL_HOSTS or if urlhost is not registered in VIR-
TUAL_HOSTS, you can specify `emailhost' like so:
newlist --urlhost=www.example.com --emailhost=example.com mylist
where `example.com' is the mail domain name. If you don't specify emailhost but urlhost is not in the virtual host list, then
mm_cfg.DEFAULT_EMAIL_HOST will be used for the email interface.
For backward compatibility, you can also specify the domain to create your new list in by spelling the listname like so:
mylist@www.example.com
where www.example.com is used for `urlhost' but it will also be used for `emailhost' if it is not found in the virtual host table. Note
`--urlhost' and `--emailhost' have precedence to this notation.
If you spell the list name as just `mylist', then the email hostname will be taken from DEFAULT_EMAIL_HOST and the url will be taken from
DEFAULT_URL (as defined in your Defaults.py file or overridden by settings in mm_cfg.py).
Note that listnames are forced to lowercase.
The list admin address need to be a fully-qualified address, like owner@example.com, not just owner.
AUTHOR
Author of Mailman is the Mailman Cabal, see http://www.list.org/ for information. This manpage is written by Tollef Fog Heen
<tfheen@debian.org> for Debian, but may be used by others.
SEE ALSO
Mailman documentation on http://www.list.org/ and in /usr/share/doc/mailman.
2008-06-14 NEWLIST(8)