forwarding iptable packets



I'm having a major problem trying to forward packets from either a workstation of the LAn to the Internet.
I want to be sure I'm doing this correctly.

I set a forward rule:
$IPT -A FORWARD -i $INT_IFACE -o eth1 -p tcp --dport 1262 -j ACCEPT

Then I set a PREROUTING rule 
$IPT -A PREROUTING -i $EXT_IFACE -p tcp --dport 1262 -j DNAT --to-destination 192.168.xxx.xxx

All I can see using tethereal on the network is SYN packets.

Any idea what I'm doing wrong?

Thanks



Relevant Pages

  • RE: Firewall Rule Set not allowing access to DNS servers?
    ... > My LAN is configured with static IP addresses, ... > I have full connectivity with the internet from every machine on my ... > # Allow out access to my ISP's Domain name server. ... > # Interrogate packets originating from the public internet ...
    (freebsd-questions)
  • Re: iptables: DROP or REJECT?
    ... my firewall rules explicitly DROP any packets from the internet to ... >my LAN that don't meet my requirements for passage (ie trying to access ... my firewall rules explicitly REJECT any packets from my LAN to the ...
    (comp.os.linux.security)
  • problem with dmz firewall script - cant connect to inet via plan
    ... Everything is fine but I can not access the internet from my private ... I have a dmz and seperate trusted private lan multihomed on the ... # Create chain for bad tcp packets ...
    (comp.os.linux.security)
  • RE: Error with daemon natd
    ... win boxes on your lan then you would want to install DHCP server on ... need to access the public internet through your gateway. ... # Only valid response to the packets I've sent out are allowed in. ... # the "dynamic" rules table by an allow keep-state statement. ...
    (freebsd-questions)
  • Re: Port 135 Probes Continue
    ... Yeah, for any LAN without windows machines, that port could be blocked on ... For internet, there should be no 135-139/445 port ... packets coming in, period, so those can be blocked. ...
    (comp.security.misc)