10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi experts,
We have windows machine ( A ) in one network & 2 Linux Servers ( B & C ) in another network. There is a firewall between these 2 networks and SSH (TCP/22) & HTTPS (TCP/443) are allowed from A to B only (but not to C). There is no personal firewall / iptables running on any machine.... (1 Reply)
Discussion started by: magnus29
1 Replies
2. IP Networking
hi guys
i have a simple question !
i have two ips . a valid and internal(172.16.11.2)
i want to use port forwarding to forward any request to valid IP port 8001 to internal ip port 80 .
i use this rule :
sysctl -w net.ipv4.ip_forward=1
iptables -t nat -A PREROUTING -p tcp... (1 Reply)
Discussion started by: mhs
1 Replies
3. UNIX for Advanced & Expert Users
Hello,
I have a routeur linksys (192.168.1.1 ) a firewall (192.168.1.55 IN ----> 192.168.2.254 OUT) which using iptable
I want to acces to an equipment (lorex video camera serveur 192.168.2.44) which using an ddns service on the port 9000
So i don t know which redirection a will do on the... (2 Replies)
Discussion started by: tapharule
2 Replies
4. IP Networking
Hi Linux/Unix Guru,
I am setting Linux Hopping Station to another different servers.
My current config to connect to another servers is using different port to connect.
e.g
ssh -D 1080 -p 22 username@server1.com
ssh -D 1081 -p 22 username@server2.com
Now what I would like to have... (3 Replies)
Discussion started by: regmaster
3 Replies
5. Solaris
Hi; I have the following issue:
I have a Solaris server running an old applications which connects to an http server in other server at certain port. The thing is that the http server has changed its ip and port and the addres in the app is hard coded and touching the app by now is out of the... (0 Replies)
Discussion started by: ppereira
0 Replies
6. Solaris
Hi,
I am looking out a way to forward all UDP traffic coming on ports 3001,3002,3003 and 3004 on server 10.2.45.200
to
corresponding ports of server 10.2.45.197.
I am using Solaris 10.0.
-bash-3.00$ uname -a
SunOS airtelussd2 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V445
Is... (6 Replies)
Discussion started by: vikas027
6 Replies
7. UNIX for Advanced & Expert Users
Hi
I want to set up port forwarding from one network to another network. I already have this configured on the Linux box using iptables.
iptables -t nat -A PREROUTING -p tcp -i eth1 --dport 1521 -j DNAT --to 10.218.146.230
iptables -A FORWARD -p tcp -i eth1 -d 10.218.146.230 -j ACCEPT
... (2 Replies)
Discussion started by: slash_blog
2 Replies
8. AIX
Hi friends
i have the following setup
machine1 two network adapters one connected to lan the other connected directly to machine2
machine2 is not connected to lan
i need to access machine2 directly from the LAN
how to force machine1 to forward all traffic received on a specific port the... (1 Reply)
Discussion started by: Husam
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have to install an application that has a built in tftp server. Tftp comes in on port 69. As i am not installing this application as a root user i am running into trouble because only the root user can listen to ports < 1024. So changing the port i listen to to one greater than 1023 isn't... (1 Reply)
Discussion started by: imloaded24_7
1 Replies
10. UNIX for Dummies Questions & Answers
I've been googling for a while now, trying to forward port 3000 to port 80....
In the past I used to DLink router to forward port 3000 to 80. I recently finished (well, is it ever done anyhow?) setting up my linux box and got it acting as a router.
I want to continue to run Apache on port 80... (1 Reply)
Discussion started by: meeps
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)