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 REDHAT
atalkd
ATALKD(8) System Manager's Manual ATALKD(8)NAME
atalkd - AppleTalk RTMP, NBP, ZIP, and AEP manager
SYNOPSIS
/usr/sbin/atalkd [ -f configfile ] [ -1 | -2 ]
DESCRIPTION
atalkd is responsible for all user level AppleTalk network management. This includes routing, name registration and lookup, zone lookup,
and the AppleTalk Echo Protocol (similar to ping(8)). atalkd is typically started at boot time, out of /etc/rc. It first reads from its
configuration file, /etc/atalk//atalkd.conf. If there is no configuration file, atalkd will attempt to configure all available interfaces
and will create a configuration file. The file consists of a series of interfaces, one per line. Lines with `#' in the first column are
ignored, as are blank lines. The syntax is
interface [ -seed ] [ -phase number ] [ -net net-range ] [ -addr address ] [ -zone zonename ] ...
Note that all field except the interface are optional. The loopback interface is configured automatically. If -seed is specified, all
other fields must be present. Also, atalkd will exit during bootstrapping, if a router disagrees with its seed information. If -seed is
not given, all other information may be overriden during auto-configuration. If no -phase option is given, the default phase as given on
the command line is used (the default is 2). If -addr is given and -net is not, a net-range of one is assumed.
The first -zone directive for each interface is the ``default'' zone. Under Phase 1, there is only one zone. Under Phase 2, all routers
on the network are configured with the default zone and must agree. atalkd maps ``*'' to the default zone of the first interface. Note:
The default zone for a machine is determined by the configuration of the local routers; to appear in a non-default zone, each service, e.g.
afpd, must individually specify the desired zone. See also nbp_name(3).
ROUTING
If you are connecting a netatalk router to an existing AppleTalk internet, you should first contact your local network administrators to
obtain appropriate network addresses.
atalkd can provide routing between interfaces by configuring multiple interfaces. Each interface must be assigned a unique net-range
between 1 and 65279 (0 and 65535 are illegal, and addresses between 65280 and 65534 are reserved for startup). It is best to choose the
smallest useful net-range, i.e. if you have three machines on an Ethernet, don't chose a net-range of 1000-2000. Each net-range may have
an arbitrary list of zones associated with it.
EXAMPLE
Below is an example configuration file for a sun4/40. The machine has two interfaces, ``le0'' and ``le1''. The ``le0'' interface is con-
figured automatically from other routers on the network. The machine is the only router for the ``le1'' interface.
le0
le1 -seed -net 9461-9471 -zone netatalk -zone Argus
atalkd automatically acts as a router if there is more than one interface.
FILES
/etc/atalk//atalkd.conf configuration file
BUGS
On some systems, atalkd can not be restarted.
netatalk 1.3 17 Nov 1995 ATALKD(8)