Hi
can libipq support traffic at the rate of say 90 mbps/sec ?
we can increase the ipq_queue_maxlen using sysctl system call, but is
there any upper limit on this queue size ? or can we give it any value
till sizeof(int)
has anybody here ever tried this much traffic while using ip_queue and
libipq ?
TIA
Amit
"Daniel Chemko" <dchemko@xxxxxxxxxx>@lists.netfilter.org on 05/12/2004
03:48:57 AM
Sent by: netfilter-admin@xxxxxxxxxxxxxxxxxxx
To: <alucard@xxxxxxxxx>, <netfilter@xxxxxxxxxxxxxxxxxxx>
cc:
Subject: RE: forwarding on the same NIC
> To make matters worse, the second webserver is IIS and I have no idea
> how to use IP Multiplexing on Win2k, I could do it in linux but
> Windows systems are not my expertise. What I'm going to do -if I get
> the permission- is this: Install a 2nd nic on the 2nd webserver so
> the IP address that is being used doesn't get affected and I will
> configure it's router to the linux box so it can redirect packets
> where they should go...
You are either not grasping how difficult what your trying to do, or you
haven't used proper the wording. Source Routing from windows == blah! If
you're relying on windows to do routing, I pity thou.
To the best of my knowledge, you have:
x.x.x.254 ROUTER
|--x.x.x.1 Linux Server 1 (default route x.x.x.254)
|--x.x.x.2 Windows IIS (default route x.x.x.254)
You have the router forwarding a public IP address and PATing it to
x.x.x.1. You want x.x.x.1:8080 to go to x.x.x.2:80
To get this to work, use:
# Allow any established traffic to traverse the machine
iptables -A FORWARD -m state ESTABLISHED,RELATED -j ACCEPT
# Forward the packet destined for 8080 to the windows machine on port 80
iptables -t nat -A PREROUTING --destination x.x.x.1 -p tcp --dport 8080
-j DNAT --to x.x.x.2:80
# Allow new web traffic into the network
iptables -A FORWARD --destination x.x.x.2 -p tcp --dport 80 -j ACCEPT
# Forces the windows box to route back to you before leaving the network
iptables -t nat -A POSTROUTING --destination x.x.x.2 -p tcp --dport 80
-j SNAT --to x.x.x.1
The order of traversal becomes:
Router->Firewall->Windows->Firewall->Router
Instead of
Router->Firewall->Windows->Router
The later breaks as I've described earlier.
