Sponsored Content
Full Discussion: Static route on router
Special Forums IP Networking Static route on router Post 302834091 by Corona688 on Thursday 18th of July 2013 11:00:33 AM
Old 07-18-2013
I believe it's required. It won't forward all traffic to all interfaces without asking, it needs to be told.
 

10 More Discussions You Might Find Interesting

1. IP Networking

static route ?

Hi, I have a machine that sits on 10.2 network. I need to ssh from this to another box that is on both 10.125 & 10.140 VLANs what should I need to do? Thanks! (3 Replies)
Discussion started by: chaandana
3 Replies

2. HP-UX

Static route for hpux 11.22

I want to make static route how would I proceed? I'm using "route add DestinationIP gatewayIP hop to 1 I would like to make this permanent, so when it reboots I don't want to loose it, would I do this in netconf file? If so where? I did a search got this site, it didn't help much. ... (2 Replies)
Discussion started by: catwomen
2 Replies

3. UNIX for Dummies Questions & Answers

Static Route

Hi, Request you to please tell me the command or the process to add the static route in redhat linux. Thanks in Advance. Regards Arun (2 Replies)
Discussion started by: Arun.Kakarla
2 Replies

4. AIX

removing static route

#netstat -nr (shows the following with more static routes) 192.168.18.202 10.129.155.1 UGH 0 29 en0 - - and i just want to remove the above one i tried #smitty rmroute destination type= net dest add = 192.168.18.202 default gateway= 10.129.155.1 net... (1 Reply)
Discussion started by: pchangba1
1 Replies

5. IP Networking

When to use static route on server?

Hi guys, sorry for asking noob question. When do we really need to add a static route on the server? I encounter this situation whereby a client trigger a network packet to the destination but the destination does not know how to return the traffic back to the client (source). The issue was... (4 Replies)
Discussion started by: DrivesMeCrazy
4 Replies

6. AIX

Can not remove static route from AIX 5.3

Dear all, I Try to remove a static route with smitty, but recieve this error: Method error (/usr/lib/methods/chginet): 0514-009 Cannot delete an object from the device configuration database. 0821-216 chginet: Cannot delete route (net,192.168.30.101,192.168.30.1)... (2 Replies)
Discussion started by: hrkama
2 Replies

7. IP Networking

I need HELP to Set up Coyote Linux router with 1 static IP & 64 internal static IP

hello, i need help on setting my coyote linux, i've working on this for last 5 days, can't get it to work. I've been posting this message to coyote forum, and other linux forum, but haven't get any answer yet. Hope someone here can help me...... please see my attached picture first. ... (0 Replies)
Discussion started by: dlwoaud
0 Replies

8. Solaris

Error adding static route

Hi all i have a simple question here I'm kind of newbie on solaris development currently i'm trying to add static route to solaris environment and i got error, each time i add this static route to it btw this is my command : root@xxxxxx # ping 1.2.3.1 1.2.3.1 is alive echo ... (15 Replies)
Discussion started by: l33tbot_if
15 Replies

9. AIX

Edit Static Route

Anyone know how to edit a static route in AIX? I find myself deleting and then recreating the route with the new information. Would be nice to know how to edit the route. (3 Replies)
Discussion started by: bbbngowc
3 Replies

10. Red Hat

Static route not added

Hello Guys.. I am facing this weird problem of static route not added after reboot!! Following is my route-<interface> file.. # cat /etc/sysconfig/network-scripts/route-eth0 ADDRESS0=172.31.0.1 NETMASK0=255.255.255.255 GATEWAY0=192.168.208.1 ADDRESS1=172.31.15.2... (3 Replies)
Discussion started by: parth_buch
3 Replies
niffconfig(8)						      System Manager's Manual						     niffconfig(8)

NAME
niffconfig - Configuration program for the Network Interface Failure Finder (NIFF) SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d num] [-o num] [-t num] [interface1 interface2...] OPTIONS
Adds an interface or interfaces, specified by the interface parameter. You cannot specify the -a option with the -m, -s, -r, or -u options. Specifies the time period, in seconds, that the traffic monitor thread uses between reads of the interface counters when it suspects there is a connectivity problem. This number must be smaller than the number given for the -t option. The default time period is 5 seconds. If num is not specified, niffconfig uses the default. Specifies the total number of traffic-free seconds that must elapse before the traffic monitor thread determines that a network interface has failed. This number must be at least the sum of the -d option and two times the -t option. That is, given the default time period for -d and -t, the -o option must be at least 20 seconds. The default time period for this option is 60 seconds. If num is not specified, niffconfig uses the default. Modifies the timing parameters of an interface that is already being monitored. Typically, this option is specified along with one or more of -t num, -d num, or -o num options. If none of these parame- ters are specified, the default value is used. You cannot specify the -m option with the -a, -s, -r, or -u options. Stops monitoring the specified interface. Obtains the status of the specified interface. Specifies the time period, in seconds, that the traffic monitor thread delays between reads of the interface counters when the network is running normally. The default time period is 20 seconds. If num is not specified, niffconfig uses the default. Displays the status of all interfaces currently being monitored to standard out (stdout). Displays the status, timer values, and description (verbose mode) of all interfaces currently being monitored to standard out (stdout). DESCRIPTION
The niffconfig command arranges for one or more network interfaces to be monitored for possible loss of connectivity. Timing parameters that govern how quickly an interface can be declared suspect or dead may be manipulated with this command. You can specify multiple inter- faces, separated by a space, on the command line. Note, you must be superuser to use the niffconfig command. Except for the -u and -u options, all niffconfig options require one or more network interfaces to be specified. EXAMPLES
To add the tu0 and tu1 interfaces to the list of monitored interfaces, enter: # niffconfig -a tu0 tu1 To change the time it takes to declare failure on the tu1 interface to 90 seconds, enter: # niffconfig -o 90 tu1 To display the status of all interfaces that are being monitored: # niffconfig -u To stop monitoring the tu0 interface: # niffconfig -r tu0 SEE ALSO
Daemons: niffd(8) Information: EVM(5), nifftmt(7) niffconfig(8)
All times are GMT -4. The time now is 12:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy