08-20-2012
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 port = same as above
i know this topic is very easy but seriosly i am stucked in this topic
I could not find any proper documentation on this topic on internet , every topic that i found is not well documentated , i mean topics are not properly written or explained .
Any Help
Thanks
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. Cybersecurity
Hi,
from my workplace we use a proxy to connect to the outside world, including external ssh servers.
The problem is that the server is seeing the connection coming from the proxy and knows nothing about the client behind it. The ssh connection itself works fine, but x-forwarding does not work as... (1 Reply)
Discussion started by: vampirodolce
1 Replies
5. 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
6. UNIX for Dummies Questions & Answers
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
7. IP Networking
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
8. IP Networking
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
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
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
LEARN ABOUT DEBIAN
git-review
GIT-REVIEW(1) BSD General Commands Manual GIT-REVIEW(1)
NAME
git-review -- Submit changes to Gerrit for review
SYNOPSIS
git-review [-r remote] [-uv] -d change [branch]
git-review [-r remote] [-fnuv] -s [branch]
git-review [-fnuvDR] [-r remote] [-t topic] [branch]
git-review --version
DESCRIPTION
git-review automates and streamlines some of the tasks involved with submitting local changes to a Gerrit server for review. It is designed
to make it easier to apprehend Gerrit, especially for users that have recently switched to Git from another version control system.
The following options are available:
-d change, --download=change
Download change from Gerrit into a local branch. The branch will be named after the patch author and the name of a topic. If the
local branch already exists, it will attempt to update with the latest patchset for this change.
-f, --finish
Close down the local branch and switch back to the target branch on successful submission.
-n, --dry-run
Don't actually perform any commands that have direct effects. Print them instead.
-r remote, --remote=remote
Git remote to use for Gerrit.
-s, --setup
Just run the repo setup commands but don't submit anything.
-t topic, --topic=topic
Sets the target topic for this change on the gerrit server. If not specified, a bug number from the commit summary will be used.
Alternatively, the local branch name will be used if different from remote branch.
-u, --update
Skip cached local copies and force updates from network resources.
-l, --list
List the available reviews on the gerrit server for this project.
-y, --yes
Indicate that you do, in fact, understand if you are submitting more than one patch.
-v --verbose
Turns on more verbose output.
-D, --draft
Submit review as a draft. Requires Gerrit 2.3 or newer.
-R, --no-rebase
Do not automatically perform a rebase before submitting the change to Gerrit.
When submitting a change for review, you will usually want it to be based on the tip of upstream branch in order to avoid possible
conflicts. When amending a change and rebasing the new patchset, the Gerrit web interface will show a difference between the two
patchsets which contains all commits in between. This may confuse many reviewers that would expect to see a much simpler difference.
--version
Print the version number and exit.
FILES
To use git-review with your project, it is recommended that you create a file at the root of the repository named .gitreview and place infor-
mation about your gerrit installation in it. The format is similar to the Windows .ini file format:
[gerrit]
host=hostname
port=TCP port number of gerrit
project=project name
defaultbranch=branch to work on
It is also possible to specify optional default name for the Git remote using the defaultremote configuration parameter.
Setting defaultrebase to zero will make git-review not to rebase changes by default (same as the -R command line option)
[gerrit]
host=review.example.com
port=29418
project=department/project.git
defaultbranch=master
defaultremote=review
defaultrebase=0
EXAMPLES
To fetch a remote change number 3004:
$ git-review -d 3004
Downloading refs/changes/04/3004/1 from gerrit into
review/someone/topic_name
Switched to branch 'review/someone/topic_name
$ git branch
master
* review/author/topic_name
Gerrit looks up both name of the author and the topic name from Gerrit to name a local branch. This facilitates easier identification of
changes.
To send a change for review and delete local branch afterwards:
$ git-review -f
remote: Resolving deltas: 0% (0/8)
To ssh://username@review.example.com/departement/project.git
* [new branch] HEAD -> refs/for/master/topic_name
Switched to branch 'master'
Deleted branch 'review/someone/topic_name'
$ git branch
* master
An example .gitreview configuration file for a project department/project hosted on review.example.com port 29418 in the branch master :
[gerrit]
host=review.example.com
port=29418
project=department/project.git
defaultbranch=master
BUGS
Bug reports can be submitted to
https://launchpad.net/git-review
AUTHORS
git-review is maintained by OpenStack, LLC
This manpage has been enhanced by:
Antoine Musso <hashar@free.fr>
Marcin Cieslak <saper@saper.info>
April 4th, 2012