10-07-2005
But the problem is
im at PC 1, and cant send UDP to the gate to get out externally:
PC1 --- Network (UDP dropped)---GATE------(no Drops)-------WWW
I have SSH access to GATE which is a unix system, but still UDP packets dropped on way there.
maybe that's better explained
imma quite newb at terminology
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I have tried the following:
on PC1 (win xp) I have created ssh connection with port forwarding
(local 8888 to remote 8888) to server1.
>From server1 I have created another ssh connection with port
forwarding to server2(local 8888 to remote 1521).
When I try to connect to oracle... (3 Replies)
Discussion started by: goran00
3 Replies
2. UNIX for Advanced & Expert Users
Hi all
question -
there are 2 servers A + B. server A is connected to the internet and running a squid proxy server - server B is behind a firewall. I can ssh from A to B but not from B to A. I need internet access on B to update some files. I thought I could use some sort of ssh tunnel to... (1 Reply)
Discussion started by: silvaman
1 Replies
3. Filesystems, Disks and Memory
Hello Folks,
Im trying to pass the NFS Shared data through the SSH tunnel. Following are the Steps for my Executions:
A) Commands Executed on Server (NFS Server + SSHD Server running)
i) share -F nfs -o rw=<NFS Server IP> /home
ii) Start the NFS Server Services and SSHD Services.
... (3 Replies)
Discussion started by: ImpeccableCode
3 Replies
4. Infrastructure Monitoring
Performing UDP tunneling through an SSH connection
Found this while looking for a way to temporarily forward SNMP requests across otherwise disconnected networks. Might be useful for someone else, too. (1 Reply)
Discussion started by: pludi
1 Replies
5. 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
6. IP Networking
Hi Guys
I'm newbie here, so how are You.
I have 3 servers, but only 1 I can access directly from my computer and my network, here is the diagram :
PC SSH Connect (22) -- (3338) 192.168.1.1 --- (22) Serv1 --- (22) Serv2 --- (22) Serv3 ... (0 Replies)
Discussion started by: AdziE
0 Replies
7. UNIX for Advanced & Expert Users
Hi!
I came to know about SSH Tunneling to bypass the Firewall.
I will have to setup a free access SSH server to tunnel data access through PUTTY or OpenSSH.
The problem is that I don't know about any free access servers.
So, can anyone of you guide me for that, for any type of help? (1 Reply)
Discussion started by: nixhead
1 Replies
8. UNIX for Dummies Questions & Answers
I have googled a bit but i think I don't know if I am even looking in the right places.
The following I want to achieve and I don't even know if it is possible.
If I write a web application I can view in my web-browser (on the localhost). But eventually if I want to upload it to a server... (1 Reply)
Discussion started by: kevincobain2000
1 Replies
9. UNIX for Dummies Questions & Answers
I want to perform ssh tunnelling for which I have been using PuTTy. Config is as follows:
Host IP: 172.XX.XX.111Port: 22Tunnel setting source port: 19005Destination: 172.XX.XX.40:1521After entering my user ID and password, I am able to see in my command prompt that 127.0.0.1:19005 is listening.... (1 Reply)
Discussion started by: aakashsoor
1 Replies
10. Shell Programming and Scripting
I have a process running on my local server.
http://dev.techx.com:6060/proct
I wish to block port 6060 and expose port 7777 to the outside world.
I block port 6060 and open port 7777 on the firewall.
What should be the PuTTY Settings -> Connection -> SSH -> Tunnels
1. Destination ... (3 Replies)
Discussion started by: mohtashims
3 Replies
LEARN ABOUT FREEBSD
blackhole
BLACKHOLE(4) BSD Kernel Interfaces Manual BLACKHOLE(4)
NAME
blackhole -- a sysctl(8) MIB for manipulating behaviour in respect of refused TCP or UDP connection attempts
SYNOPSIS
sysctl net.inet.tcp.blackhole[=[0 | 1 | 2]]
sysctl net.inet.udp.blackhole[=[0 | 1]]
DESCRIPTION
The blackhole sysctl(8) MIB is used to control system behaviour when connection requests are received on TCP or UDP ports where there is no
socket listening.
Normal behaviour, when a TCP SYN segment is received on a port where there is no socket accepting connections, is for the system to return a
RST segment, and drop the connection. The connecting system will see this as a ``Connection refused''. By setting the TCP blackhole MIB to
a numeric value of one, the incoming SYN segment is merely dropped, and no RST is sent, making the system appear as a blackhole. By setting
the MIB value to two, any segment arriving on a closed port is dropped without returning a RST. This provides some degree of protection
against stealth port scans.
In the UDP instance, enabling blackhole behaviour turns off the sending of an ICMP port unreachable message in response to a UDP datagram
which arrives on a port where there is no socket listening. It must be noted that this behaviour will prevent remote systems from running
traceroute(8) to a system.
The blackhole behaviour is useful to slow down anyone who is port scanning a system, attempting to detect vulnerable services on a system.
It could potentially also slow down someone who is attempting a denial of service attack.
WARNING
The TCP and UDP blackhole features should not be regarded as a replacement for firewall solutions. Better security would consist of the
blackhole sysctl(8) MIB used in conjunction with one of the available firewall packages.
This mechanism is not a substitute for securing a system. It should be used together with other security mechanisms.
SEE ALSO
ip(4), tcp(4), udp(4), ipf(8), ipfw(8), pfctl(8), sysctl(8)
HISTORY
The TCP and UDP blackhole MIBs first appeared in FreeBSD 4.0.
AUTHORS
Geoffrey M. Rehmet
BSD
January 1, 2007 BSD