Sponsored Content
Special Forums IP Networking Problem with Static route through peer to peer connection Post 302734719 by ImranBD on Thursday 22nd of November 2012 02:35:30 PM
Old 11-22-2012
I think routing between S2 & S3 will be easy way rather than thinking port forwarding or static routing. I will try & let you know the result.
 

9 More Discussions You Might Find Interesting

1. IP Networking

connection reset by peer

:confused: HI, We have 2 servers ( win 2003 + sun 5.8 ) and we run a rsh from the NT to the UNIX. The program runs a shell script on the UNIX and waits for the answer in the EOF. How ever, after period of appx 2 min there is a reply "Recv failed:Connection reset by peer". while the... (5 Replies)
Discussion started by: eyalush
5 Replies

2. Shell Programming and Scripting

ssh - connection reset by peer

I use ssh to work on the server (OS X 10.4.x) remotely from home (Debian / OS X 10.5.3). If I leave my machine idle, I get disconnected after a couple of minutes. I get the following error message: Read from remote host "server name": Connection reset by peer Connection to "server name" closed.... (2 Replies)
Discussion started by: osxhawk
2 Replies

3. Shell Programming and Scripting

Connection reset by peer

hi i am connecting to a remote server using sftp protocol. i am using the command like "sftp USER01@122.10.12.45" then i got the error "Couldn't read packet: Connection reset by peer" please help its very urgent (5 Replies)
Discussion started by: Satyak
5 Replies

4. IP Networking

connection reset by peer on freebsd

hi all. am running postgresql in a vm on debian server. i have some client programs connecting to the db. when i check the logs of postgresql i see "connection reset by peer" can someone help me with this issue... thanks. (1 Reply)
Discussion started by: coolatt
1 Replies

5. Solaris

peer-to-peer connection on solaris and windows

hi everyone. As a solaris/unix beginner, I am trying a peer-to-peer connection with my Sun and Windows. Here is my setup: -Windows XP -Sun System (Netra T1) which is connected to the console of the WinXP machine. -Windows XP has wireless connection which enables me to access internet ... (3 Replies)
Discussion started by: graboid888
3 Replies

6. UNIX for Advanced & Expert Users

Connection reset by peer..closing connection

Hello I'm facing the above problem while doing a performance run. I've a script which I'm launching from my windows desktop using mozilla. The script will invoke backend action on a Solaris host which in turn feeds the records to a driver located on a linux box(Cent OS). What's happening is... (1 Reply)
Discussion started by: subramanyab
1 Replies

7. IP Networking

Firewall stopping Peer to Peer File sharing

I am looking for advice on a router. I am new to Linux and am trying to use Limewire and Ktorent and can make no connection. Limewire indicates I have a firewall. I have a Linksys router WRK54G and my guess is that is the problem. I have spent hours upon hours trying to get it to work using info... (0 Replies)
Discussion started by: Paul K
0 Replies

8. UNIX for Dummies Questions & Answers

cat: write error: Connection reset by peer

I have created a script to cat the contents of a log file and pipe it to head and tail so I can get specific lines. When I do this I sometimes randomly get the error "cat: write error: Connection reset by peer". It is completely sporatic and sometimes it doesnt happen and sometimes it does... (4 Replies)
Discussion started by: atelford
4 Replies

9. Red Hat

Can't SSH - Connection reset by Peer

Hi Guys, I can't SSH to a remote system - connection reset by peer..any ideas ? -The Source is Linux, the Remote is Windows -The remote has OpenSSH running on Port 22 - Telnet confirms port is open -User1 has a RSA2 Key (2048) key, which is capture in the 1010101-pub.key specified by the... (1 Reply)
Discussion started by: stevie_velvet
1 Replies
routeadm(1M)															      routeadm(1M)

NAME
routeadm - IP forwarding and routing configuration SYNOPSIS
routeadm [-p] routeadm [-R root-dir] [-e option...] [-d option...] [-r option...] [-s var=value] routeadm [-u] The routeadm command is used to administer system-wide configuration for IP forwarding and routing. IP forwarding is the passing of IP packets from one network to another; IP routing is the use of a routing protocol to determine routes. routeadm is used to enable or disable each function independently, overriding any system default setting for each function. The first usage, above, reports the current configuration. The following command-line options are supported: -p Print the configuration in parseable format. -R root-dir Specify an alternate root directory where routeadm applies changes. This can be useful from within JumpStart scripts, where the root directory of the system being modified is mounted elsewhere. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -e option... Enable the specified option. -d option... Disable the specified option. -r option... Revert the specified option to the system default. The system defaults are specified in the description of each option. -u Apply the currently configured options to the running system. Enable or disable IP forwarding, and/or launch or kill routing daemons. It does not alter the state of the system for those settings that have been set to default. This option is meant to be used by adminis- trators who do not want to reboot to apply their changes. -s var=value Specify string values for specific variables in a comma-separated list with no intervening spaces. If invalid options are specified, a warning message is printed and the program exits. The following variables can be specified: ipv4-routing-daemon=<full_path_to_routing_daemon> Specifies the routing daemon to be started when ipv4-routing is enabled. The routing daemon specified must be an executable binary or shell-script. Default: "/usr/sbin/in.routed" ipv4-routing-daemon-args=<args> Specifies the startup arguments to be passed to the ipv4-routing-daemon when ipv4-routing is enabled. Default: no arguments ipv4-routing-stop-cmd=<command> Specifies the command to be executed to stop the routing daemon when ipv4-routing is disabled. <command> may be an executable binary or shell-script, or a string that can be parsed by system(3C). Default: "kill -TERM `cat /var/run/in.routed.pid`" ipv6-routing-daemon=<full_path_to_routing_daemon> Specifies the routing daemon to be started when ipv6-routing is enabled. The routing daemon specified must be an executable binary or shell-script. Default: "/usr/lib/inet/in.ripngd" ipv6-routing-daemon-args=<args> Specifies the startup arguments to be passed to the ipv6-routing-daemon when ipv6-routing is enabled. Default: "-s" ipv6-routing-stop-cmd=<command> Specifies the command to be executed to stop the routing daemon when ipv6-routing is disabled. <command> can be an executable binary or shell-script, or a string that can be parsed by system(3C). Default: "kill -TERM `cat /var/run/in.ripngd.pid`" Note that, if you change the routing daemon and stop commands from their defaults, routeadm does not monitor these daemons or commands. This is because the status of these programs depends on user configuration. When non-default daemons or stop commands are in use, routeadm always returns a status of "unknown". Multiple -e, -d, and -r options can be specified on the command line. Changes made by -e, -d, and -r are persistent, but are not applied to the running system unless routeadm is called later with the -u option. Use the following options as arguments to the -e, -d, and -r options (shown above as option...). ipv4-forwarding Controls the global forwarding configuration for all IPv4 interfaces. The system default is disabled. If enabled, IP will forward IPv4 packets to and from interfaces when appropriate. If disabled, IP will not forward IPv4 packets to and from interfaces when appropriate. ipv4-routing Determines whether or not an IPv4 routing daemon is run. The system default is enabled unless the /etc/defaultrouter file exists, in which case the default is disabled. The routing daemon for IPv4 is /usr/sbin/in.routed. ipv6-forwarding Controls the global forwarding configuration for all IPv6 interfaces. The system default is disabled. If enabled, IP will forward IPv6 packets to and from interfaces when appropriate. If disabled, IP will not forward IPv6 packets to and from interfaces when appropriate. ipv6-routing Determines whether or not an IPv6 routing daemon is run. The system default is disabled. The routing daemon for IPv6 is /usr/lib/inet/in.ripngd. If not set, the system boot scripts' current default logic determines whether or not to run in.ripngd. Note that even if this option is enabled, an IPv6 routing daemon will run only if ipv6-forwarding is enabled. The forwarding and routing settings are related but not mutually dependent. For example, a router will typically forward IP packets and use a routing protocol, but nothing would prevent an administrator from configuring a router that forwards packets and does not use a routing protocol. In that case, the administrator would enable forwarding, disable routing, and populate the router's routing table with static routes. The forwarding settings are global settings. Each interface also has an IFF_ROUTER forwarding flag that determines whether packets can be forwarded to or from a particular interface. That flag can be independently controlled by means of ifconfig(1M)'s router option. When the global forwarding setting is changed (that is, -u is issued to change the value from enabled to disabled or vice-versa), all interface flags in the system are changed simultaneously to reflect the new global policy. Interfaces configured by means of DHCP automatically have their interface-specific IFF_ROUTER flag cleared. When a new interface is plumbed by means of ifconfig(1M), the value of the interface-specific forwarding flag is set according to the cur- rent global forwarding value. Thus, the forwarding value forms the "default" for all new interfaces. The following exit values are returned: 0 Successful completion. !=0 An error occurred while obtaining or modifying the system configuration. Example 1: Enabling IPv4 Forwarding IPv4 forwarding is disabled by default. The following command enables IPv4 forwarding: example# routeadm -e ipv4-forwarding Example 2: Apply Configured Settings to the Running System In the previous example, a system setting was changed, but will not take effect until the next reboot unless a command such as the follow- ing is used: example# routeadm -u Example 3: Making a Setting Revert to its Default To make the setting changed in the first example revert to its default, enter the following: example# routeadm -r ipv4-forwarding example# routeadm -u Example 4: Starting in.routed with the -q Flag The following sequence of commands starts in.routed with the -q flag: example# routeadm -s ipv4-routing-daemon-args="-q" example# routeadm -u See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ ifconfig(1M), in.routed(1M), gateways(4), attributes(5) 8 Apr 2005 routeadm(1M)
All times are GMT -4. The time now is 04:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy