04-23-2002
Ethernet
We are trying to Establish Network using Linux.Now we are facing the problem in configring Ethernet.In out network we are giving eth0 in server and activating it at the boot time,so it is activating as it is but when we define the Ethernet of node on server and allowing it to activate at boot time then it is not activating.so i want to know that what is the reason behind this and what should i have to do to overcome this problem.When i give the ethernet on nodes seprately then also Linux displays it failed at boot time.Plaese Help Me
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am using Red Hat 7.1 . I have installed one Server and trying to make network installing workstations on other system of a network. The Ethernet of the server has been mounted and working properly. I am getting problem installing /mounting the Ethernet of the workstations .I have tryed this by... (1 Reply)
Discussion started by: at_renai2001
1 Replies
2. Cybersecurity
I suspect that someone is using a sniffer on my Ethernet connection,
OS X 10.3.9, DSL,
ok, I'm in terminal using the "ifconfig" command >
flags=8049<UP,LOOPBACK,RUNNING,MULTICAST>mtu 16384
right, it's not in "promiscuous mode", but i think it's Trojaned, can anyone point me in the... (1 Reply)
Discussion started by: su"do"er
1 Replies
3. UNIX for Advanced & Expert Users
I understand that one should setup virtual ethernet adapters in the lpars which is the best way for various lpars to communicate with each other - Does anyone have info on this or can point me to a doc that explains how to set this up? (1 Reply)
Discussion started by: capeme
1 Replies
4. IP Networking
What command do I use to show mw the ethernet card, I have tried ipconfig -a (1 Reply)
Discussion started by: dhlopomo
1 Replies
5. Solaris
Boot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w500000e0103c3391,0:a File and args:
SunOS Release 5.8 Version Generic_108528-29 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
ifconfig: plumb: qfe2: Bad file number
configuring IPv4 interfaces: eri0.
moving addresses... (1 Reply)
Discussion started by: fredginting
1 Replies
6. AIX
Hello everyone
I have a problem with one server, has Aix 5.3 in the errpt has this message
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
F3931284 0105133009 I H ent0 ETHERNET NETWORK RECOVERY MODE
EC0BCCD4 0105133009 T H ent0 ETHERNET DOWN
F3931284 ... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
7. Solaris
my solris box network is unreachable how to solve this
ipaddress assiagning and entry in vi /etc/host
how to solve network is unreachable (2 Replies)
Discussion started by: tirupathi
2 Replies
8. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
9. Linux
I need to enable Ethernet Bonding on three systems, connected together via switch. What I tried ended up with failure, slaves cannot be detected n added to bon0.
Here's what I did:
created file /etc/modprobe.d/bonding.d and added the following to it:
alias bond0 bonding
options bonding... (2 Replies)
Discussion started by: dr_mabuse
2 Replies
LEARN ABOUT NETBSD
rbootd
RBOOTD(8) BSD System Manager's Manual RBOOTD(8)
NAME
rbootd -- HP remote boot server
SYNOPSIS
rbootd [-ad] [-i interface] [config_file]
DESCRIPTION
The rbootd utility services boot requests from Hewlett-Packard workstations over a local area network. All boot files must reside in the
boot file directory; further, if a client supplies path information in its boot request, it will be silently stripped away before processing.
By default, rbootd only responds to requests from machines listed in its configuration file. If the client doesn't supply a file name (HP700
series machines don't), the first one listed for this machine will be supplied.
The options are as follows:
-a Respond to boot requests from any machine. The configuration file is ignored if this option is specified.
-d Run rbootd in debug mode. Packets sent and received are displayed to the terminal.
-i interface
Service boot requests on specified interface. If unspecified, rbootd searches the system interface list for the lowest numbered,
configured ``up'' interface (excluding loopback). Ties are broken by choosing the earliest match.
Specifying config_file on the command line causes rbootd to use a different configuration file from the default.
The configuration file is a text file where each line describes a particular machine. A line must start with a machine's Ethernet address
followed by an optional list of boot file names. An Ethernet address is specified in hexadecimal with each of its six octets separated by a
colon. The boot file names come from the boot file directory. The ethernet address and boot file(s) must be separated by white-space and/or
comma characters. A pound sign causes the remainder of a line to be ignored.
Here is a sample configuration file:
#
# ethernet addr boot file(s) comments
#
08:00:09:0:66:ad SYSHPBSD # snake (4.3BSD)
08:00:09:0:59:5b # vandy (anything)
8::9:1:C6:75 SYSHPBSD,SYSHPUX # jaguar (either)
rbootd logs status and error messages via syslog(3). A startup message is always logged, and in the case of fatal errors (or deadly signals)
a message is logged announcing the server's termination. In general, a non-fatal error is handled by ignoring the event that caused it (e.g.
an invalid Ethernet address in the config file causes that line to be invalidated).
The following signals have the specified effect when sent to the server process using the kill(1) command:
SIGHUP Drop all active connections and reconfigure.
SIGUSR1 Turn on debugging, do nothing if already on.
SIGUSR2 Turn off debugging, do nothing if already off.
FILES
/dev/bpf packet-filter device
/etc/rbootd.conf configuration file
/tmp/rbootd.dbg debug output
/usr/mdec/rbootd directory containing boot files
/var/run/rbootd.pid process id
SEE ALSO
kill(1), socket(2), signal(3), syslog(3)
BUGS
If multiple servers are started on the same interface, each will receive and respond to the same boot packets.
BSD
December 11, 1993 BSD