site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
984
Share Topic
Posting?
Post a:
Post a:
AuthorAll Replies

Infoman1

join:2001-03-21
Hubbard, OH

USG 50 series

Where do you enter simple port forwarding to a static LAN in the menu options. Coming from the 35 series their is a learning curve. UDP Ports 10k-20k to static LAN IP.


Anav
Sarcastic Llama? Naw, Just Acerbic
Premium
join:2001-07-16
Dartmouth, NS
kudos:3

Configuration Selection on Main Menu (Left hand side).
Select NETWORK and sub-selection NAT.

You need to add what is called a VIRTUAL Server on the port mapping type. YOu may need to define some objects first. Word of advice dont use Loopback it has locked some stuff up for me......... might be my issue LOL"

Dont forget you will need to make corresponding firewall changes WAN to LAN



Anav
Sarcastic Llama? Naw, Just Acerbic
Premium
join:2001-07-16
Dartmouth, NS
kudos:3

Click for full size
Here is an example of an entered FTP port forwarding. I have already defined the object STUDY (an IP address basically) and used the defaul already available port service for FTP (If I wanted to use a non-standard FTP port I would have defined one as an object).

Infoman1

join:2001-03-21
Hubbard, OH

Thanks. Create an object based Host Address. Create a Virtual Server under NAT. Assign to an interface wan1. Create Service Group object for ports 10000-20000udp. Mapped IP, the machine the packets are forwarded to. Orignal Port= service group previously created. Mapped Port=Service group created.

Firewall rule to permit service group created from wan1--->lan

Does this sound correct?



Brad Bishop
Premium
join:2002-09-27
Atlanta, GA

Except for the 'assign an interface' part.

- Create an address / host object representing your server
- Use an existing Service Object or create a new one. If you need to you can group them
- Configuration -> Network -> NAT. Create a virtual Server using those host/service objects
- create a firewall rule foe the service to allow the traffic in.

That should be all there is to it.


Infoman1

join:2001-03-21
Hubbard, OH

- Create an address / host object representing your server

I am not sure I understand this?



Brad Bishop
Premium
join:2002-09-27
Atlanta, GA

In Configuration:

Object -> Address
Add
Name: Some name representing the object in your USG
Address Type: Host
IP: IP Address of your host on your LAN

If you're using a common service (FTP, HTTP, VPN, etc) then you can use one of the pre-defined services under:
Object->Service (still under Configuration here).

You can create an Service Group (I did for VPN since it required several Services - just a neater way to keep them together).

If you're doing some home-grown deal or need a range of ports then create your own service object and give it a name.

You then reference these objects elsewhere (as in the Network->NAT menu and the Firewall menu) so you have one reference for the IP and ports (in case you need to change them later) instead of many (which would be a pain if you decided to change the IP/Ports later). You also don't need to remember the IP/ports with this method as you only need to remember the names such as SomeServer and MyNeededPorts.


Infoman1

join:2001-03-21
Hubbard, OH

Got it. My "Virtual Server" (Object) sets on Port p5 where as the zone is labeled DMZ.

For the firewall rule it would be allow "service group, service, port, etc.) wan1 ---> Zywal or DMZ? The default configuration is allow any from wan1---->DMZ.

This covention is quite a bit different than my ole 35.


Infoman1

join:2001-03-21
Hubbard, OH

I couldn't get this to work. To make things simple, this series ALG doesn't play well with a Vonage PAP2 adapter interface. It periodically does not allow incoming calls. They had recommend forwarding the following ports. 5060-5061 TCP/UDP 69 UDP, 53 UDP, and 10000-20000UDP. I can't find a way to forward all those different ports to a static address. The menu does not allow service groups, so that option did not work.

I created a virtual server called "pap2", I created an object address Host (IP address of the adapter). From this point I am confused. Interface is Wan1, Original IP is pap2, Mapped IP is pap2.

The Zywall 35 had no problem just plug and play, what is so different about this series. It's beginning to be a PITA.



Anav
Sarcastic Llama? Naw, Just Acerbic
Premium
join:2001-07-16
Dartmouth, NS
kudos:3

So the router is forwarding packets to the vonage device correct.

Your rule looks okay. Yes the port forwarding is a biotch for groupings, the firewall rule men does not have this limitation and allows it.

I am afraid you will have to create an object for each one and have individual port forwarding (virtual server rules).

Also stupidly one cannot put in both protocols for a port or range of ports you have to create two rules if you want both UDP and TCP.

As for the firewall rule. Wan1 to DMZ sounds right.
Destination is to the same object you used in port forwarding (pap2).

User-any, Source - any unless you had a specific IP that was accessing all the time (known static or range of static web Ips) any should be fine though.

Service,,, here is where you can group all you individual objects into one group object and then assign it in your firewall rule.
--
Ain't nuthin but the blues! "Albert Collins".
Leave your troubles at the door! "Pepe Peregil" De Sevilla. Just Don't Wifi without WPA, "Yul Brenner"

LlamaWorks Equipment



DrTCP
Yours truly
Premium,ExMod 1999-04
join:1999-11-09
Round Rock, TX

1 edit

reply to Infoman1

said by Infoman1:

I couldn't get this to work. To make things simple, this series ALG doesn't play well with a Vonage PAP2 adapter interface. It periodically does not allow incoming calls. They had recommend forwarding the following ports. 5060-5061 TCP/UDP 69 UDP, 53 UDP, and 10000-20000UDP.

It should not be necessary for you to create a virtual server unless your PAP2 is setup to accept calls from other SIP gateways (unlikely).

I think the Vonage PAP2 being a client device should maintain the connection frequent enough so that the dynamic session entries on the firewall does not expire. Did you investigate your PAP2 settings? As far as I remember they had quite elaborate setup on PAP2 which you should be able to tweak but I am not sure of Vonage branded one.

Secondly, did you enable SIP ALG on USG? It is in Configuration -> ALG. The default is not enabled. If you enable it, there is also a timeout settings over there. Perhaps, your PAP2 would perform better with SIP ALG enabled (or vice versa). I have a different outbound only VOIP service on Sipura 3000. I can function well without needing the use of SIP ALG. Also my Sipura is in the LAN zone.

Edit: If you want, there is a good support note at that covers various Virtual Server/NAT etc. issues:

»www.zyxel.ch/files/manuals/ZYWAL···Note.pdf

polarisdb

join:2004-07-12
USA

reply to Infoman1

said by Infoman1:

I couldn't get this to work. To make things simple, this series ALG doesn't play well with a Vonage PAP2 adapter interface. It periodically does not allow incoming calls.

FWIW, I've had a Vonage PAP2 working nicely behind my USG 50 for more than a year with no port forwarding required.


Brad Bishop
Premium
join:2002-09-27
Atlanta, GA

While not Vonage, I, too, have a VoIP phone working behind the USG with no port forwarding.


Infoman1

join:2001-03-21
Hubbard, OH

I figured out the port forwarding thing. Works!

I did have it configured orginally enabling ALG as I did with the 35.
It works. However after a period of time it will miss incoming calls.
So it's my assumption something is timing out. It also keeps a hearbeat alive on UDP 10000. Is there a timeout command somewhere?



DrTCP
Yours truly
Premium,ExMod 1999-04
join:1999-11-09
Round Rock, TX

said by Infoman1:

I figured out the port forwarding thing. Works!

I did have it configured orginally enabling ALG as I did with the 35.
It works. However after a period of time it will miss incoming calls.
So it's my assumption something is timing out. It also keeps a hearbeat alive on UDP 10000. Is there a timeout command somewhere?

If you are using SIP ALG support on USG, try tuning the SIP timeouts at Configuration -> Network -> ALG:

[x] Enable Configure SIP Inactivity Timeout
SIP Media Inactivity Timeout : 120 (seconds)
SIP Signaling Inactivity Timeout : 1800 (seconds)

I believe you need to increase SIP Media Inactivity Timeout to match the one configured in your PAP2.

Here is the info from help:

SIP Media Inactivity Timeout
Use this field to set how many seconds (1~86400) the ZyWALL will allow a SIP session to remain idle (without voice traffic) before dropping it.
If no voice packets go through the SIP ALG before the timeout period expires, the ZyWALL deletes the audio session. You cannot hear anything and you will need to make a new call to continue your conversation.

SIP Signaling Inactivity Timeout
Most SIP clients have an "expire" mechanism indicating the lifetime of signaling sessions. The SIP user agent sends registration packets to the SIP server periodically and keeps the session alive in the ZyWALL.
If the SIP client does not have this mechanism and makes no calls during the ZyWALL SIP timeout, the ZyWALL deletes the signaling session after the timeout period. Enter the SIP signaling session timeout value (1~86400).

Monday, 04-Jun 17:58:09 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics