other machines with similar setup are sitting on the same subnet.
I want to shift one machine behind a cisco router that has one interface connected to the subnet 192.168.1.0 "192.168.1.1"
and the otherside on subnet 192.168.2.0 "192.168.2.1"
I want to add route to point from 192.168.1.0 to 192.168.2.0 and revrse.
what gateway should I use in the local machine and in the remote machine. qe1 or the router local interface
show in details please.
see attached file for sketch
hi,
below is the situation:
my server is in 128.10.200.xxx network.
i have a solaris computer running in a subnet. this computer got 2 nic card.
1 is 172.18.198.xxx , another 1 is 10.100.xxx.11
there is a machine stick with this computer, ip is 10.100.xxx.12
so, 10.100.xxx.11 and... (3 Replies)
Hi All, :(:confused:
I have scoured the web and can't find this anywhere.
What I am trying to do is set up a static route through an available gateway on a server, and then test connectivity through TELNET.
I have done this on AIX (I already had this procedure).
On AIX I would use SMIT. ... (7 Replies)
Does anyone know how to delete a an ip off the routing table ? i tried route delete 10.0.0.0 and gateway but it still comes back. i have 2 zones sharing one interface. help... (4 Replies)
hi all,
how do i make sure that the new routing should take effect on the os memory right away? what should i run after i add all the new "route add ....".
I have an example below:
bash-2.03# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface... (1 Reply)
Hi,
I got problem of Sun Solaris 8 routing.
IP of SunA is 10.16.64.164, and have routing table:
10.16.64.0 10.16.64.164 U 1 19236 bge1
10.6.0.0 10.6.0.3 U 1 16534 bge0
224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
Hello
Hope someone can help with this problem. We are running Solaris 10 with a current kernel patch of 142900-09.
We appear to be getting a serious issue with the routing table as shown below:
Output from netstat -rnv
Destination ....Mask ............Gateway ........Device... (2 Replies)
Hello All,
Problem is that redundancy doesn't work, probably a routing issue I need to get sorted out When 172.29.11.x net is down, neither node3 nor node4 is trying 172.29.12.x network,The problem lies in network 172.29.13.x
if 172.29.11.x network is down, node3/node4 should route to... (6 Replies)
Discussion started by: nadeemahmed
6 Replies
LEARN ABOUT DEBIAN
prips
PRIPS(1) BSD General Commands Manual PRIPS(1)NAME
prips -- print the IP addresses in a given range
SYNOPSIS
prips [-c] [-d delim] [-e exclude] [-f format] [-i incr] start end
prips [-c] [-d delim] [-e exclude] [-f format] [-i incr] CIDR-block
prips -h
DESCRIPTION
The prips tool can be used to print all of the IP addresses in a given range. It can enhance tools that only work on one host at a time,
e.g. whois(1).
The prips tool accepts the following command-line options:
-c Print the range in CIDR notation.
-d delim
Set the delimiter to the character with ASCII code delim where 0 <= delim <= 255.
-e <x.x.x,x.x>
Exclude ranges from the output.
-f format
Set the format of addresses (hex, dec, or dot).
-h Show summary of options.
-i incr
Set the increment to 'x'.
ENVIRONMENT
The prips tool's operation is not influenced by any environment variables.
FILES
The prips tool's operation is not influenced by any files.
EXAMPLES
Display all the addresses in a reserved subnet:
prips 192.168.32.0 192.168.32.255
The same, using CIDR notation:
prips 192.168.32/24
Display only the usable addresses in a class A reserved subnet using a space instead of a newline for a delimiter:
prips -d 32 10.0.0.1 10.255.255.255
Display every fourth address in a weird block:
prips -i 4 192.168.32.7 192.168.33.5
Determine the smallest CIDR block containing two addresses:
prips -c 192.168.32.5 192.168.32.11
DIAGNOSTICS
The prips utility exits 0 on success, and >0 if an error occurs.
SEE ALSO ipsc(1), gipsc(1)STANDARDS
No standards were harmed in the writing of the prips tool.
HISTORY
The prips tool was originally written by Daniel Kelly and later adopted by Peter Pentchev. This manual page was originally written by Juan
Alvarez for the Debian GNU/Linux system and later added to the prips distribution and converted to mdoc format by Peter Pentchev.
AUTHORS
Daniel Kelly <dan@vertekcorp.com>
Juan Alvarez <jalvarez@fluidsignal.com>
Peter Pentchev <roam@ringlet.net>
BUGS
Please report any bugs in the prips tool to its current maintainer, Peter Pentchev.
BSD March 1, 2011 BSD