News: This forum is now permanently frozen.
Pages: [1]
Topic: 4 days of screwing with NAT/firwall rules and still no go  (Read 3422 times)
« on: March 20, 2007, 19:58:11 »
The_Jizzler *
Posts: 3

i have monowall setup wit 3 nics. 1 wan, 1 lan, 1 DMZ. Ive followed the example instuctions on setting up the DMZ (14.1.2-14.1.4 pages in the manual) right, that all went well. all machines can get to the internet fine.
 
 now i have a machine that runs a ftp server and bittorrent on the DMZ. I cant seem to figure out how to properly forward ports to the DMZ! this was so much more straight forward in smoothwall.
 
 ok, lets try and get my bittorrrent working since thats the easier of the two. 

wan=public IP
lan-192.168.1.1
DMZ=192.168.2.1

host on DMZ=192.168.2.5

Bittorrent needs port 49271 open for both tcp and udp.

heres what ive tried so far.

from the "NAT:inbound" screen

If          Proto     Ext. port range     NAT IP     Int. port range     Description     
DMZ    TCP/UDP    49271              192.168.2.5           49271                  Bittorrent


from the "Firewall:rules" dmz tab

    Proto     Source     Port     Destination     Port                 Description     
    *        DMZ net      *        ! LAN net          *    permit DMZ to any *but* LAN     
   
     TCP/UDP    *             *       192.168.2.5    49271             NAT Bittorrent


and thats what i have going on. ive tried several differnt ways, all failing. anyone got any clues what im doing wrong here?
« Reply #1 on: March 20, 2007, 20:10:57 »
rpsmith
Guest

Try WAN for the NAT interface.

Roy...
« Reply #2 on: March 23, 2007, 06:43:52 »
The_Jizzler *
Posts: 3

figured it out. had to  change the NAT rule it made in teh firewall to wan instead of dmz
« Reply #3 on: March 23, 2007, 16:43:23 »
bitonw **
Posts: 79

Well if you want to allow traffic from the Internet going to your DMZ box you should have a rule that allows traffic.

So you need to allow traffic going from the WAN interface to your DMZ interface / Bittorent box. This is nothing special and for sure the same in every Firewall...
« Reply #4 on: May 29, 2007, 03:26:47 »
Bryanz0r *
Posts: 3

figured it out. had to  change the NAT rule it made in teh firewall to wan instead of dmz


That helped me alot, thank you very much jizzler!!! Grin
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines