Sponsored Content
Operating Systems Solaris SUNW, hme0: Link Down - Cable problem Post 302328780 by incredible on Thursday 25th of June 2009 07:56:59 AM
Old 06-25-2009
Can you ping your gateway IP 172.25.4.1 ?
 

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
gateways(4)						     Kernel Interfaces Manual						       gateways(4)

NAME
gateways - Specifies Internet routing information to the routed daemon SYNOPSIS
/etc/gateways DESCRIPTION
The /etc/gateways file identifies gateways for the routed daemon. Ordinarily, the routed daemon queries the network and builds routing tables. The routed daemon builds the tables from routing information transmitted by other hosts directly connected to the network. How- ever, there may be gateways that this command cannot identify through its queries. These unidentified gateways are known as distant gate- ways. Such gateways should be identified in the /etc/gateways file, which the routed daemon reads when it starts. The general format of an file entry in the /etc/gateways file is: Destination Name1 gateway Name2 metric Value Type The following is a brief description of each element in an /etc/gateways file entry: A keyword that indicates whether the route is to a network or to a specific host. The two possible keywords are net and host. The name associated with Destination. Name1 can be either a symbolic name (as used in the /etc/hosts or /etc/networks file) or an Internet address specified in dotted-decimal format. An indicator that the following string identifies the gateway host. The name or address of the gateway host to which messages should be forwarded. An indicator that the next string represents the hop count to the destination host or network. The hop count, or number of gateways, from the local network to the destination network. A keyword that indicates whether the gateway should be treated as active, passive, or external. The three possible keywords are as follows: An active gateway is treated like a network interface. That is, it is expected to exchange RIP (Routing Information Protocol) routing information. Information about it is maintained in the internal routing tables as long as it is active and is included in any routing information that is transmitted through RIP. If it does not respond for a period of time, the route associated with it is deleted from the internal routing tables. A passive gateway is not expected to exchange RIP routing information. Information about it is maintained in the routing tables indefinitely and is included in any routing information that is transmitted through RIP. An external gateway is identified to inform the routed daemon that another routing process will install such a route and that alternative routes to that destination should not be installed. Information about external gateways is not maintained in the internal rout- ing tables and is not transmitted through RIP. Note that these routes must be to networks. EXAMPLES
To specify a route to a network through a gateway host with an entry in the gateways file, enter: net net2 gateway host4 metric 4 passive This example specifies a route to a network, net2, through the gateway host4. The hop count metric to net2 is 4, and the gateway is treated as passive. To specify a route to a host through a gateway host with an entry in the gateways file, enter: host host2 gate- way host4 metric 4 passive This example specifies a route to a host, host2, through the gateway host4. The hop count metric to host2 is 4, and the gateway is treated as passive. To specify a route to a host through an active Internet gateway with an entry in the gateways file, enter: host host10 gateway 192.100.11.5 metric 9 active This example specifies a route to a specific host, host10, through the gateway 192.100.11.5. The hop count metric to host10 is 9 and the gateway is treated as active. To specify a route to a host through a passive Internet gateway with an entry in the gateways file, enter: host host10 gateway 192.100.11.5 metric 9 passive This example specifies a route to a specific host, host10, through the gateway 192.100.11.5. The hop metric count to host10 is 9 and the gateway is treated as passive. To specify a route to a network through an external gateway, enter a line in the following format: net net5 gateway host7 metric 11 external This example specifies a route to a network, net5, through the gateway host7. The hop count metric to net5 is 11 and the gateway is treated as external (that is, it is not advertised through RIP, but is advertised through an unspecified routing protocol). RELATED INFORMATION
Daemons: gated(8), routed(8) delim off gateways(4)
All times are GMT -4. The time now is 01:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy