Re: [j-nsp] PAT on a single external IP Address?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hm, there is one problem with this though: If you want to VIP port 80, the box tells you that this port is used for management purposes and won't work: Firewall- set int e0/0 vip interface-ip 80 http 1.2.3.4 manual Not supported service:

Re: [j-nsp] PAT on a single external IP Address?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aha, reconfiguring the HTTP-adminport does the trick. Could someone document this please? ;) Cheers, sven03 Sven Juergensen (KielNET) wrote: | Hm, | | there is one problem with this though: | If you want to VIP port 80, the box | tells you that

Re: [j-nsp] PAT on a single external IP Address?

Well, although not documented to my knowledge, assigning a static IP via ppp to a pppoe interface and referencing it in a mip seems to work. ScreenOS somehow holds the last ppp-assigned IP sticky in the config so the MIP is valid even after a reboot. Surely this is a dirty hack though ;) Is

[j-nsp] PAT on a single external IP Address?

Hi list, is it possible to have a static PAT on ScreenOS when the external (public/WAN) IP-Address is dynamic and point-to-point? E.g. have port 25 on the external IP map to a single private (1918) internal host? VIPs seem to always reference a static IP (destination PAT) and, like MIPs,

Re: [j-nsp] PAT on a single external IP Address?

You can use VIP and the option: use the IP from the external interface And you can use and external DynDNS service to map the dynamic address to a fixed name. Well, although not documented to my knowledge, assigning a static IP via ppp to a pppoe interface and referencing it in a mip seems