Re: Blocking incoming IP address immediately
From: Nico Declerck (Nico.Declerck_at_UGent.be)
Date: 11/30/04
- Next message: Jeff Franks: "Re: Blocking incoming IP address immediately"
- Previous message: Jeff Franks: "Re: Blocking incoming IP address immediately"
- In reply to: Jeff Franks: "Re: Blocking incoming IP address immediately"
- Next in thread: Jeff Franks: "Re: Blocking incoming IP address immediately"
- Reply: Jeff Franks: "Re: Blocking incoming IP address immediately"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 30 Nov 2004 15:23:38 +0100
Jeff Franks wrote:
>> Just one question to be on the safe side... The iptables-firewall and the
>> "Roger Wilco" game are one and the same machine??? right?
>
> No the iptables firewall is on a stand-alone RedHat 9 server. It's only
> function right now is to provide NAT and a firewall for my internal LAN.
> The game and the Roger Wilco are on a seperate server and the ports are
> forwarded in to it. That, by the way, is working like a champ. The game
> is
> up and the RW is working fine. My only issue is how to block specific IP
> addresses on the fly without effecting the other connections.
What I don't understand then is why you try to block them in the
INPUT-chain.... You should try the FORWARD chain...
The INPUT chain is used strictly for processes that run on your firewall, if
the game server is another machine, the packets will go through the FORWARD
chain, even if the firewall has to perform NAT.
prompt
- Next message: Jeff Franks: "Re: Blocking incoming IP address immediately"
- Previous message: Jeff Franks: "Re: Blocking incoming IP address immediately"
- In reply to: Jeff Franks: "Re: Blocking incoming IP address immediately"
- Next in thread: Jeff Franks: "Re: Blocking incoming IP address immediately"
- Reply: Jeff Franks: "Re: Blocking incoming IP address immediately"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|