Sponsored Content
Special Forums IP Networking SSH Port Forwarding - sharing the same port Post 302417742 by regmaster on Friday 30th of April 2010 12:29:44 PM
Old 04-30-2010
I think yes.

Because the main purpose of that hopping station is established connection (tunneling) to different apps in different servers.

So I will send configuration for my users to use port 1081 and 1082 in their Citrix Firewall settings, 127.0.0.1 1082 or 1081

Then before that they have to login to my server via Putty.

Now all I want is to share the same port in my linux box. Is it possible?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

port forwarding

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

2. UNIX for Advanced & Expert Users

Port forwarding

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

3. UNIX for Dummies Questions & Answers

SSH port forwarding/tunneling

So this seems like something that should be simple...but I can't quite seem to get it up and running. I have a machine, .107 with a GUI on port 8443. The problem is that I can't connect directly to .107 from my laptop. Now I have another machine, .69 that can connect to .107. So shouldn't I be able... (4 Replies)
Discussion started by: DeCoTwc
4 Replies

4. IP Networking

Totally stucked in ssh port forwarding

Hello my friends , i am totally stuck in ssh port forwarding topic i had learn iptables and other networking topic without any problem but ssh port forwarding is headache 1. local port = what is this ? is this incoming traffic or outgoing traffic 2. remote port = same as above 3. dynamic... (2 Replies)
Discussion started by: rink
2 Replies

5. IP Networking

Ftp over SSH port forwarding

Hi, I'm trying to connect ftp over ssh port forwarding to a sever(UnixC) behind FireWall(F/W). here's my env and question. UnixA(SSH Client) ----F/W ---- UnixB(SSH Svr) ---- UnixC (FTP, 21) UnixA wants to connect ftp service of UnixC via SSH port forwarding on UnixB. Unix A,... (3 Replies)
Discussion started by: hanyunq
3 Replies

6. IP Networking

Port forwarding issue

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

7. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies

8. IP Networking

Ssh port forwarding through a pseudo terminal

Here's a situation: I do all my work on a Mac. I have mysql installed on my mac. 1. There's a certain linux server 'server01' that provides access to another linux server 'server02' via a pseudo terminal So, to ssh into 'server02', I do this from my mac: ssh -t server01... (1 Reply)
Discussion started by: imperialguy
1 Replies

9. UNIX for Advanced & Expert Users

Help on port forwarding please..

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

10. Red Hat

iptables port forwarding

Hello All, I would like to ask you very kindly with /etc/sysconfig/iptables file I have to setup port forwarding on RHEL6 router. Users from public network must be able to ssh to servers in private network behind RHEL6 router. Problem is that servers in private network must be isolated. My... (2 Replies)
Discussion started by: oidipus
2 Replies
AX25D.CONF(5)						     Linux Programmer's Manual						     AX25D.CONF(5)

NAME
ax25d.conf - ax25d configuration file. DESCRIPTION
Ax25d.conf controls the functioning of ax25d. Its purpose is to specify on which ports to listen on, which applications are available, and to whom they are available to. The configuration file is common to both AX.25, NET/ROM and Rose and their is similarity between the two parts of the file. The general layout for an entry for a given port is as follows: interface control callsign entry 1 . . callsign entry n The interface control line determines which port and callsigns apply to the following callsign entry lines, until the next interface con- trol is read. There are four different variants of the interface control line: 1. [AX.25 Port Name] 2. [Callsign VIA AX.25 Port Name] 3. <NET/ROM Port Name> 4. {Callsign VIA Rose Port Name} Version 1 allows the following callsign entry lines to listen on the AX.25 port specified by the AX.25 port name using the default callsign of that AX.25 port. Version 2 allows the following callsign entry lines to listen on the AX.25 port specified by the AX.25 port name using the callsign speci- fied instead of the default callsign of that AX.25 port. Specifying a * for the AX.25 port name allows the following callsign entries to be valid for all the operating AX.25 ports using the callsign specified. VIA can be abbreviated to just V. If the callsign has an asterisk appended to it then the system will be listening on the port with the callsign, but as a pseudo-digipeater instead of being the normal des- tination callsign. Version 3 allows the following callsign entry lines to listen on the NET/ROM port specified by the NET/ROM port name using the default callsign of that NET/ROM port. Version 4 allows the following callsign entry lines to listen on the Rose port using the specified Rose port name using the callsign speci- fied as the service access point (SAP). A * may be specified for a callsign to allow matching to any incoming Call Requests with any SAP. The callsign entry lines have a similar layout for both AX.25, NET/ROM and Rose, the layout is: peer window t1 t2 t3 idle n2 mode uid exec args... All values must be entered for all entries even when they are not used (ie window for NET/ROM, just enter a * instead), The meanings of each of the fields is given below. All timings apart from the idle value are given in seconds, the idle values is given in minutes. peer This specifies the callsign of the remote end of the connection that should have the following parameters and executable set up for them. The syntax of the peer argument is explained below. window This sets the the value of the window size, if a value of * is entered in this field then the default value for the port is taken from the "parameters" entry (see below) or lacking such an entry, the kernel default value is used. This entry is used by AX.25 but not by NET/ROM or Rose. t1 This sets the the value of the T1 timer, if a value of * is entered in this field then the default value for the port is taken from the "parameters" entry (see below) or lacking such an entry, the kernel default value is used. This entry is used by both AX.25 and NET/ROM but not by Rose. t2 This sets the the value of the T2 timer, if a value of * is entered in this field then the default value for the port is taken from the "parameters" entry (see below) or lacking such an entry, the kernel default value is used. This entry is used by both AX.25 and NET/ROM but not by Rose. t3 This sets the the value of the T3 timer, if a value of * is entered in this field then the default value for the port is taken from the "parameters" entry (see below) or lacking such an entry, the kernel default value is used. This entry is used by AX.25 but not by NET/ROM or Rose. idle This sets the the value of the idle timer, if a value of * is entered in this field then the default value for the port is taken from the "parameters" entry (see below) or lacking such an entry, the kernel default value is used. n2 This sets the the value of the N2 counter, if a value of * is entered in this field then the default value for the port is taken from the "parameters" entry (see below) or lacking such an entry, the kernel default value is used. This entry is used by both AX.25 and NET/ROM but not by Rose. mode This is a set of flags that control the various properties associated with the incoming connection. The flags are single letters, may be in either upper or lower case, and there may not be any spaces between them. If no flags are to be speci- fied either a 0, - or a * must be entered instead. The valid mode flag letters are: D Do not allow connections that have passed via any digipeaters. AX.25 only. L Do not allow this station to connect, they are Locked out. N Check that the NET/ROM neighbour is allowed, currently unused. Q Do not make an entry into the log file for this connection. V Validate the callsign of the incoming connection, currently unused. uid This is the userid that the following command should run under when executing. exec This is the executable that should be executed when an incoming connection matches the criteria of both the interface con- trol and the callsign entry . args... These are the optional arguments that are passed to the executable. All of the arguments are passed literally apart from the following: %d The name of the port that the connection is on. %U The username (callsign) of the remote station in upper case without the SSID. %u The username (callsign) of the remote station in lower case without the SSID. %S The username (callsign) of the remote station in upper case with the SSID. %s The username (callsign) of the remote station in lower case with the SSID. %P The nodename of the remote station in upper case without the SSID. This is only valid under NET/ROM and Rose, under AX.25 a % is substituted instead. %p The nodename of the remote station in lower case without the SSID. This is only valid under NET/ROM and Rose, under AX.25 a % is substituted instead. %R The nodename of the remote station in upper case with the SSID. This is only valid under NET/ROM and Rose, under AX.25 a % is substituted instead. %r The nodename of the remote station in lower case with the SSID. This is only valid under NET/ROM and Rose, under AX.25 a % is substituted instead. %% A %. The peer argument is dependant upon whether AX.25, NET/ROM or Rose is being used. There are five formats of this argument: 1. default 2. parameters 3. callsign 4. callsign@node 5. @node The first version is used by AX.25, NET/ROM and Rose to specify that all callsigns on a given port are to be matched. The default line is usually the last of the callsign entry lines, so that more specific entries may have the chance to be matched first. The second version is not a callsign entry that is used by any incoming connections. It is a means to specify default values for parameters such as Window, T1, T2, T3, Idle and N2. It is used for both AX.25, NET/ROM and Rose. The third version is used by both AX.25, NET/ROM and Rose to specify the callsign of the remote station to match the callsign entry line. If no SSID is specified then the callsign will be matched with any that has the same callsign and any SSID. Specifying an SSID causes the callsign to be matched exactly. In the case of NET/ROM and Rose this entry does not specify which node the originating callsign comes from. The fourth version is used by NET/ROM and Rose to specify the callsign of the remote station and the remote node to match the callsign entry line. If no SSID is specified in the callsign section then the callsign will be matched with any that has the same callsign and any SSID. Specifying an SSID causes the callsign to be matched exactly. The fifth version is used by NET/ROM and Rose to specify only the address of the remote node to match the callsign entry line. This entry will mean that all remote users at the given node will match the entry. Comments may be embedded in the configuration file by placing a # in the first column. ax25d can now honour AX.25 TCP/IP mode-VC connections in a special way. Therefore, a new port specific option "parameters_extAX25" is available, with the following options, which are seperated by space. parameters_extAX25 VC-debug VC-reject-login|VC-wait-login|VC-login-ok VC-disc-on-linkfailure-msg, VC-send-failure-msg, VC-log-connections Recommended settings in ax25d.conf: parameters_extAX25 VC-wait-login VC-disc-on-linkfailure-msg VC-log-connections or parameters_extAX25 VC-reject-login VC-send-failure-msg VC-log-connections FILES
/etc/ax25/ax25d.conf SEE ALSO
ax25(4), netrom(4), rose(4), axports(5), nrports(5), rsports(5), ax25d(8). Linux 17 January 1997 AX25D.CONF(5)
All times are GMT -4. The time now is 05:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy