Redirect Website... - Page 2

Kymmy · 08-07-2010, 15:02

If you enable the NAT then you'll reduce the external throughput down to a single WAN IP..

Do you have a cable router? If yes then put it behind the Zyxel and allocate it one of the external IP's (set teh doamin A record to the same IP) then use this 2nd router as your internal LAN..

Otherwise just allocate the NAS to one of your external IP's and point the domain towards that IP

---------- Post added at 14:02 ---------- Previous post was at 13:51 ----------

The firewall will become semi-redundant as NAT itself is a form of firewall..(just between two subnets rather than a single IP)

As I asked already do you have a 2nd router?? (cable router with a WAN ethernet and not a ADSL router)

08-07-2010, 15:15

OK - I think I'll have to put it on a public static.

@Kymmy: Sorry - I'm on ADSL. ADSL Zyxel Router and a seperate WatchGuard Edge Firewall.

Kymmy · 08-07-2010, 15:20

I know you're on ADSL, but the ADSL router you have can not be used as a NAT router at the same time as servicing multiple WAN IP's, so with NAT turned off your Zyxel is simple a modem<>firewall<>hub device.

What I'm asking is do you have a seperate cable router as that will need to go behind the Zyxel, programmed on one of your external IP's and that will provide your local 192.168.*.* network..

So do you have a 2nd cable style router???

If not then you are NOT going to be able to do the 192.168.*.* address on the NAS and keep all of your external IP's and will have to put the NAS on one of your WAN IP's

""Sorry not sure how many different ways there are to repeat the same information""

08-07-2010, 17:45

Kymmy: No - don't have any other devices I could use.

OK - So external IP it is!

Xaccers · 08-07-2010, 18:00

Does this help?
http://static.highspeedbackbone.net/...e-e-Manual.pdf

If that's the same model as yours, then on the back you should have a row of network ports.
2 WAN ports (external), 1 Opt port (DMZ) and 3 LAN ports (trusted)

Seems to be that anything connected to the LAN ports can talk to each other, but access to it from the internet (WAN) can be restricted.
The Opt port would be for connecting something which you want to access internally and externally, without giving external access to your internal network, such as a web server or your NAS.

08-07-2010, 18:18

Quote:

Originally Posted by Xaccers

Does this help?
http://static.highspeedbackbone.net/...e-e-Manual.pdf

If that's the same model as yours, then on the back you should have a row of network ports.
2 WAN ports (external), 1 Opt port (DMZ) and 3 LAN ports (trusted)

Seems to be that anything connected to the LAN ports can talk to each other, but access to it from the internet (WAN) can be restricted.
The Opt port would be for connecting something which you want to access internally and externally, without giving external access to your internal network, such as a web server or your NAS.

Yep - that's what I have.

Problem with then Optional port is that after 15 connections are made you'll get a dead response.

I just tried giving my NAS an external IP from my range but I could not connect to it. I had to change my NIC to a IP in the same range to get access to it. I've got it back on an internal 192.168.x.x static at the moment....

Kymmy · 08-07-2010, 18:24

So this isn't a adsl router??

08-07-2010, 18:28

Quote:

Originally Posted by Kymmy

So this isn't a adsl router??

??

I've got 3 devices: Zyxel ADSL Router, WatchGuard Edge Firewall and a Synology NAS device

Kymmy · 08-07-2010, 18:32

I take it the watchguard that has 2 wan ports and is NAT capaple?? If yes then can that device do NAT on a single port only leaving the other port as purely firewalled??

If yes then you already have the 2nd "ethernet router" as it's built into the watchguard

08-07-2010, 18:38

I have two WAN ports on the WatchGuard, yes.

Ahh fair enough - see what you mean now.

Not sure were / how I configure the NAT settings on the WatchGuard though - I think that may be the key I'm missing that will unlock my mess!!

Kymmy · 08-07-2010, 18:42

With 2 WAN ports each port can be set a seperate IP.. If you can NAT just one of them then that will cover the internal address and allow the port forward..

You might though find that the NAT coveres both and the two WAN ports is just for load balancing..

I don;t know the peice of equipment myself but will be interested to know

08-07-2010, 18:51

Quote:

Originally Posted by Kymmy

With 2 WAN ports each port can be set a seperate IP.. If you can NAT just one of them then that will cover the internal address and allow the port forward..

You might though find that the NAT coveres both and the two WAN ports is just for load balancing..

I don;t know the peice of equipment myself but will be interested to know

From the manual:

Quote:

The WAN Failover option supplies redundant support for the external interface. With this option, the FireboxÂ® X Edge e-Series starts a connection through the WAN2 port when the primary external interface
(WAN1) cannot send traffic. Companies use this option if they must have a constant Internet connection.

You must have a second Internet connection to use this option. You can have a second broadband connection connected to the Edge to supply a failover Internet connection. It is not necessary to configure new services to use this option. The failover interface uses the same services
and network properties as the external interface.

Suppose that answers that one! It's just for failover by the looks of it. The external setting cover both ports - there's no settings for WAN 1 and WAN2 - just "External" which covers both.

Kymmy · 08-07-2010, 19:50

Question for you, you have 8 IP's (5 usable) so what currently do you have connected on external addresses?

08-07-2010, 20:12

Quote:

Originally Posted by Kymmy

Question for you, you have 8 IP's (5 usable) so what currently do you have connected on external addresses?

Just the firewall at the moment - I have the 5 'cus I thought I'd try and learn some stuff like this!

Kymmy · 08-07-2010, 20:20

Why not then use the firewall in NAT mode and put behind it all the internal stuff and use the open IP's (not behind the firewall) for a server or anything that needs a NO-NAT situation.

In my case I have the modem (cable modem 5 IP's) feeding a switch. From that switch is the servers and anything that needs a WAN IP (they're all software firewalled or too single ported to be a security risk). One port of the switch though feeds a netgear and it's behind that I have the workstations and internal equipment