09-10-2010
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Is het possible to block everyone (all IP addresses) except a given (white)list? How can I do this?
Regards,
Kevin (2 Replies)
Discussion started by: kever
2 Replies
2. IP Networking
Hi Am trying to check the service of iptables using
/etc/init.d/iptables status
but I am not even getting this file.
# /etc/init.d/iptables status
-bash: /etc/init.d/iptables: No such file or directory
#
I tried to check whether iptables rpm is installed or not, and it is... (2 Replies)
Discussion started by: mangeshpardhi
2 Replies
3. UNIX for Advanced & Expert Users
Hello,
I have implimented a dansguardian system using dansguardian and privoxy. I borrowed a script from Ubuntu CE that makes it where a firewall program like firehol is not needed and it doesn't need a reconfigure of the proxy settings in browsers to be changed. I really like it that way. All... (7 Replies)
Discussion started by: Narnie
7 Replies
4. Red Hat
Hi,
We have a router and devices for testing. We route devices with below command
iptables -t nat -A PREROUTING -p tcp -d 0/0 --dport 80 -s 10.111.111.22 -j DNAT --to-destination 10.13.0.16:3128
where 10.111.111.22 is device IP. and 10.13.0.16 is our Linux box machine.
Likewise we... (4 Replies)
Discussion started by: Dhruvak
4 Replies
5. Ubuntu
Hi,
I have the doubt which involved following configuration.
comp1<--->main<--->comp2
Comp1 sends icmp packet to main. Main takes that packet and changes destination address to comp2 and source address to it own.
I can capture the packet send from comp1 to main using netfilter. I can see the... (0 Replies)
Discussion started by: arsipk
0 Replies
6. Red Hat
Hi Gurus,
I am facing an issue with firewalls on one of my Linux Box.
Issue : Port 8001 looks open to me and there is a weblogic process running on it
netstat -alnp | grep 8001
tcp 0 0 ::ffff:3.20.247.165:8001 :::* LISTEN 28768/java
lsof -ni... (5 Replies)
Discussion started by: rama krishna
5 Replies
7. Ubuntu
hello,
first of all i am new to unix so maybe my problem is very easy for many of you but is very important to me.
So the idea is that i want to use a ubuntu 10.4 machine as a router from eth0 to eth1.
but the traffic routing is nor working properly
i configured the 2 interfaces to be... (2 Replies)
Discussion started by: florin.bv
2 Replies
8. Red Hat
Hi,
How can I config iptables to allow port forwarding from one WAN interface to second lan interface .
In my system I have one wan interface 61.93.204.56 (eth0),and lan interface 10.2.1.52(eth1)
I want to make port forward port no 22 from 61.93.204.56 to
port 22 , 10.2.1.52 , tcp and udp... (1 Reply)
Discussion started by: chuikingman
1 Replies
9. 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
10. Proxy Server
Hi there,
I have a VPS and am working on a little side project for myself and friend which is a DNS proxy. Everything was great till recently. My VPS IP has been detected by some botnet or something, and I believe SMURF attacks are occuring. The VPS provider keeps shutting down my VPS... (3 Replies)
Discussion started by: phi0x
3 Replies
LEARN ABOUT FREEBSD
nos-tun
NOS-TUN(8) BSD System Manager's Manual NOS-TUN(8)
NAME
nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel
SYNOPSIS
nos-tun -t tunnel -s source -d destination -p protocol_number [source] target
DESCRIPTION
The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.
Tunnel is the name of the tunnel device /dev/tun0 for example.
Source and destination are the addresses used on the tunnel device. If you configure the tunnel against a cisco router, use a netmask of
``255.255.255.252'' on the cisco. This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
really implement.
Protocol number sets tunnel mode. Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.
Target is the address of the remote tunnel device, this must match the source address set on the remote end.
EXAMPLES
This end, a FreeBSD box on address 192.168.59.34:
nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45
Remote cisco on address 192.168.56.45:
interface tunnel 0
ip address 192.168.61.2 255.255.255.252
tunnel mode nos
tunnel destination 192.168.59.34
tunnel source 192.168.56.45
AUTHORS
Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page. Isao SEKI
<iseki@gongon.com> added a new flag, IP protocol number.
BUGS
We do not allow for setting our source address for multihomed machines.
BSD
April 11, 1998 BSD