Hi all,
I tried to use this command
ndd -set /dev/eri adv_1000fdx_cap 1
but i get a "operation failed, Invalid argument"
anyone can help ? Thanks (5 Replies)
I have a TOSHIBA AS7000 B150 Sun Box
I wanted to run it with 100M/full duplex
I had added this to the /etc/system file to make to setting permenant So it would be set correctly on reboot.
set eri:eri_adv_100fdx_cap=1
set eri:eri_adv_100hdx_cap=0
set eri:eri_adv_autoneg_cap=0
But when I... (4 Replies)
Hello all,
I`ve the following problem - I cannot start inetd in any way possible:
bash-3.00# svcs inetd
STATE STIME FMRI
offline Jul_30 svc:/network/inetd:default
bash-3.00#
bash-3.00# svcadm enable -r inetd
bash-3.00# svcs inetd
STATE STIME FMRI... (6 Replies)
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 Replies)
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
I'm trying to migrate a Solaris 10 flar archive from a Sun M3000 to a T4-1. When I first created the zone I followed the Oracle instructions here: Transitioning an Oracle Solaris 10 Instance to an Oracle Solaris 11 System - Transitioning From Oracle Solaris 10 to Oracle Solaris 11 That worked... (6 Replies)
Discussion started by: Michele31416
6 Replies
LEARN ABOUT DEBIAN
atalkd
ATALKD(8) Netatalk 2.2 ATALKD(8)NAME
atalkd - AppleTalk RTMP, NBP, ZIP, and AEP manager
SYNOPSIS
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/netatalk/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 fields 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.
EXAMPLES
Below is an example configuration file for a sun4/40. The machine has two interfaces, ``le0'' and ``le1''. The ``le0'' interface is
configured 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/netatalk/atalkd.conf configuration file
BUGS
On some systems, atalkd can not be restarted.
SEE ALSO atalkd.conf(5)Netatalk 2.2 06 Sep 2004 ATALKD(8)