Sponsored Content
Operating Systems Solaris SUNW, hme0: Link Down - Cable problem Post 302328393 by AlSmith1964 on Wednesday 24th of June 2009 08:58:52 AM
Old 06-24-2009
Yes the ip address is reserved as what it was originally on DHCP and I've reverted the etc/hosts file back to its original address.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

hme0 babble -- ?

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

Hme0 interfaces...

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

cable modem problem

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

Is the cable you are using a null modem cable or a modem cable

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

hme0 problem after reboot

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

sun 420r hme0 not responding

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

cannot telnet/ftp to solaris machine by straight cable makes problem ..

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

what is going on with SUNW.HAStoragePlus?!!!!!

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

Cable link down

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

Different hostnames with reboot while lan cable, no lan cable

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
avahi-autoipd(8)					      System Manager's Manual						  avahi-autoipd(8)

NAME
avahi-autoipd - IPv4LL network address configuration daemon SYNOPSIS
avahi-autoipd [options] interface avahi-autoipd --kill interface avahi-autoipd --refresh interface avahi-autoipd --check interface DESCRIPTION
avahi-autoipd implements IPv4LL, "Dynamic Configuration of IPv4 Link-Local Addresses" (IETF RFC3927), a protocol for automatic IP address configuration from the link-local 169.254.0.0/16 range without the need for a central server. It is primarily intended to be used in ad-hoc networks which lack a DHCP server. IPv4LL is part of the Zeroconf stack. avahi-autoipd can be used as stand-alone address allocator or as plugin for a DHCP client such as ISC's dhclient, where it can be used as fallback solution if no DHCP server is found. To allow communication between hosts that have only an IPv4LL address assigned and hosts that only have a routable IP address assigned you may add the following routes to both network configurations: route add -net 169.254.0.0 netmask 255.255.0.0 dev eth0 metric 99 route add default dev eth0 metric 99 See http://developer.apple.com/qa/qa2004/qa1357.html for more information. OPTIONS
-D | --daemonize Daemonize after startup. Implies --syslog. -k | --kill Kill an already running avahi-autoipd on the specified network interface. (Equivalent to sending a SIGTERM) -r | --refresh Tell an already running avahi-autoipd to reannounce the acquired IP address on the specified network interface. (Equivalent to send- ing a SIGHUP) -c | --check Return 0 as return code if avahi-autoipd is already running for the specified network interface. -s | --syslog Log to syslog instead of STDERR. Implied by --daemonize. --debug Enable verbose mode. --no-drop-root Don't drop root priviliges after startup. We recommend not to use this option. --no-chroot Don't chroot(2) the daemon. This option is only available when compiled with chroot() support. -S | --start= Try to acquire the specified IP address, which must be from the IPv4LL range 169.254.0.0/16. -w | --wait Wait until a IP address has been sucessfully acquired before detaching. Only valid in combination with --daemonize. --force-bind Acquire an IPv4LL address, even if a routable address has been configured on the interface. --no-proc-title Don't change the process name while running. Unless this option is specified avahi-autoipd will reflect its current state and the IP address in the process title. -h | --help Show help. -v | --version Show version information. FILES
/etc/avahi/avahi-autoipd.action: the script to run when an IP address as been acquired or is lost. SIGNALS
SIGINT, SIGTERM, SIGQUIT: avahi-autoipd will shutdown. (Same as --kill) SIGHUP: avahi-autoipd will reannounce the acquired IP address. (Same as --refresh) AUTHORS
The Avahi Developers <avahi (at) lists (dot) freedesktop (dot) org>; Avahi is available from http://avahi.org/ SEE ALSO
autoipd.action(8), dhclient(8) http://avahi.org/wiki/AvahiAutoipd documents how avahi-autoipd is best packaged and integrated into distributions. COMMENTS
This man page was written using xml2man(1) by Oliver Kurth. Manuals User avahi-autoipd(8)
All times are GMT -4. The time now is 05:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy