06-16-2012
I did that but I didn't got any prompt to reconfigure my server, I event tried to get init 0 and the boot -r and that didnt worked.
After the boot the ge0 is not getting up.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am trying to change an IP address on a machine running HPUX10
After I change it I can ping it from the outside but it completely locks the console. After a reboot it returns back to its previous IP. Any ideas??
Thanks
Brian (7 Replies)
Discussion started by: breigner
7 Replies
2. OS X (Apple)
Hi,
I type (as root) "ifconfig en1 ether aa:aa: " but it doesnt change the mac of my airport. Can anyone help me?
Thx. (0 Replies)
Discussion started by: Jariya
0 Replies
3. Solaris
I know that I could use the
#ifconfig hme0 plumb
to activate the network interface.
However, how can I know the name of the interface e.g. hme0 before I could use the ifconfig to plumb it up?
I know there is a command (but I forgot it) to use in the Sparc version when you are in the... (7 Replies)
Discussion started by: heero
7 Replies
4. Shell Programming and Scripting
why the ifconfig command is not working in my machine?
it says "-bash: ifconfig: command not found"
why its says that?
actually i m looking for "how can I know the Network Interface Card physical address?"
Requesting u all for help.
thanks (3 Replies)
Discussion started by: moco
3 Replies
5. IP Networking
Hello everyone.
Im using last redhat enterprise edition and in my working environment, i'm always reconfiguring both interfaces , eth0 and eth1, everytime i change any interface, (i use ifconfig to change ip, and after i execute "/etc/init.d/network restart") my "/etc/hosts" file... (9 Replies)
Discussion started by: trutoman
9 Replies
6. Solaris
its a fresh installation. during the OS setup, it did not prompt for IP, netmask and gateway. using Solaris 10 08/07 update 4. I tried to plumb manually but encountered no such interface error. but nxge interfaces can be greped from the /etc/path_to_inst file.
getting similar error on... (3 Replies)
Discussion started by: incredible
3 Replies
7. Linux
Hi All,
I need some info on ifconfig.
ifconfig is available in Linux and Solaris. However the options available in Solaris is not there in Linux.
1. ifconfig -a == output is different in both OS. I am somewhat able to compare the output. But one thing I am not getting is after the flags... (2 Replies)
Discussion started by: ahamed101
2 Replies
8. Shell Programming and Scripting
Unable to run the ifconfig in my home dir..
I did add adding /sbin and /usr/sbin in th PATH
But still unable to get that ..
Am using red hat linux
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.3 (Tikanga) (3 Replies)
Discussion started by: mail2sant
3 Replies
9. Solaris
What would be the command to remove the IP address from an interface?
I want to remove the ip from this interface:
ce3: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 5
inet 155.216.13.74 netmask fffffff0 broadcast 155.216.13.79
ether 0:3:ba:da:a6:96 (3 Replies)
Discussion started by: Kjons76
3 Replies
10. Solaris
Hiii folks,,
I am unable to configure NIC using hme0 command. I am getting an error message as "hme0: File or directory not found.."
can someone help me...
Bhagi... (9 Replies)
Discussion started by: bhargav90
9 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