06-24-2009
Quote:
Originally Posted by
AlSmith1964
My IT guys have now re-reserved its ip address on the dhcp server
Was this reverted back?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Dear Reader,
I have a very unique problem. Quite often my on board ethernet port( hme0 ) related message is appearing in /var/adm/messages.
The message is hme0: babble.. The port is up and alive.
What does this message mean.. Is the on board port is about to fail??
Thanks in advance, (2 Replies)
Discussion started by: joseph_shibu
2 Replies
2. UNIX for Advanced & Expert Users
How do you configure more than one network on a single hme0 interface under SunOS? And why would you want to do this?
Thanx :)
-Michelle (1 Reply)
Discussion started by: Michelle1977
1 Replies
3. BSD
hi
I want to setup my cable modem under OpenBSD. I did not configure my network while installing the system.
When I type, I get
# ifconfig -a
lo0 : ....
...
...
rl0 : ....
...
...
vr0 : ...
...
...
I have two network cards (the machine will be a router).
I created... (1 Reply)
Discussion started by: fnoyan
1 Replies
4. Solaris
Hi all,
Is there any difference between a null modem cable or a modem cable ?
i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup.
please correct if i am wrong,
thks (2 Replies)
Discussion started by: waterbear
2 Replies
5. Solaris
Hi .....
My problem is that when i reboot the system i can't connect to the network because my ethernet ( hme0 ) is down , i must up it by ifconfig command
after reboot :
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask... (1 Reply)
Discussion started by: tt155
1 Replies
6. Solaris
I have a 420r server it boots up all of the network settings are correct, however the machines network connection is not working. Cant ping anything from it, cant ping it from another machine on the network.
If I ping 127.0.0.1 it says alive.
Is there a chance the network card has been... (2 Replies)
Discussion started by: alanj4
2 Replies
7. Solaris
Hi All,
1. modify /etc/default/login file as
make commented # console=
2.put my laptops ip at both
/etc/inet/ipnodes and /etc/host file
still i can login via telnet/ftp through a DB9-serial cable, but when i tried
through a lan stratight cable directly connected that machine... (7 Replies)
Discussion started by: mahadib
7 Replies
8. Solaris
Hi all,
really interesting thing I have encountered . So :
root@host4 # uname -a
SunOS host4 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-880
root@host4 # scinstall -p
3.2
latest recommended patches applied ..all SUN cluster patches applied.
SUN cluster software installed without... (2 Replies)
Discussion started by: samar
2 Replies
9. Solaris
We are unable to ping from Sun Ultra 60 to Ultra 10 machine and vice versa. We are getting an error message Cable Link Down ?. It was working fine.
Troubleshooting steps taken.
1) Changed the IPaddresses on both machines 192.168.10.10 and 192.168.10.20. These machines connected through 8 port... (2 Replies)
Discussion started by: vijaykrishna
2 Replies
10. Red Hat
I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable
Reboot with lan cable:
The hostname is ubunut
Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies
LEARN ABOUT DEBIAN
dhcp-helper
DHCP-HELPER(8) System Manager's Manual DHCP-HELPER(8)
NAME
dhcp-helper - A DHCP/BOOTP relay agent.
SYNOPSIS
dhcp-helper [OPTION]...
DESCRIPTION
dhcp-helper is a DHCP and BOOTP relay agent. It listens for DHCP and BOOTP broadcasts on directly connected subnets and relays them to DHCP
or BOOTP servers elsewhere. It also relays replies from the remote servers back to partially configured hosts. Once hosts are fully config-
ured they can communicate directly with their servers and no longer need the services of a relay.
OPTIONS
The only required option is at least one DHCP server to relay to. The simplest way to configure dhcp-helper on a router is just to give the
interface to the network containing the DHCP server with a -b option. All the other interfaces present on the machine will then accept DHCP
requests. On a machine which does not have an interface on the network containing the DHCP server, use a -s option instead.
-s <server>
Specify a DHCP or BOOTP server to relay to. The server may be given as a machine name or dotted-quad IP address. More than one
server may be specified.
-b <interface>
Relay to a DHCP or BOOTP server using broadcast via <interface>. This eliminates the need to give a server address. <interface> is
automatically added to the list of interfaces which will not receive DHCP requests.
-i <interface>
Specify which local interfaces to listen on for DHCP/BOOTP broadcasts. If no -i flags are given all interfaces are used except those
specified by -e flags and those specified by -b flags.
-e <interface>
Specify which local interfaces to exclude.
-p Use alternative ports (1067/1068) for the DHCP client and server.
-v Report the software release version and copyright information.
-d Debug mode, do not change UID, write a pid-file or go into the background.
-r <file>
Specify an alternate path for dhcp-helper to record its process-id in. Normally /var/run/dhcp-helper.pid.
-u <username>
Specify the userid to which dhcp-helper will change after startup. The daemon must normally be started as root, but it will drop
root priviledges after startup by changing id to another user. Normally this user is "nobody" but that can be over-ridden with this
switch.
NOTES
Dhcp-helper requires a 2.2 or later Linux kernel. The "Linux packet filter" and "packet socket" facilities are not required, which is the
chief advantage of this software over the ISC DHCP relay daemon.
AUTHOR
This manual page was written by Simon Kelley <simon@thekelleys.org.uk>.
DHCP-HELPER(8)