I didn't realise that you were on ADSL...

What model Zyxel?

Do you have access to the web-interface?

ZyXEL P-660HW-T1 v2, yes I have access to the interface

I used this exact router on ADSL with public IPs.

So, all you do is set the same address on the LAN as the WAN...I does sound crazy...

WAN IPs will be "bridged" across to the LAN side.

I then used a second router (Zywall) to do NAT on my 1st usable IP (.242) and devices that had public IPs were plugged directly into the P-660 NAT and WiFi were also disabled.

When I went to FTTC I used exactly the same setup with a Zyxel NBG334W cable router before I got the 2130N

know-dice wrote: So, all you do is set the same address on the LAN as the WAN...I does sound crazy...

where? on the 2130? or on the zyxel?

know-dice wrote: I then used a second router (Zywall) to do NAT on my 1st usable IP (.242) and devices that had public IPs were plugged directly into the P-660 NAT and WiFi were also disabled

this sounds exactly like setup I had before (with an apple airport used as a bridge), but with the 2130n does not work. You're saying that I leave the 2130N only to the NAT and handle the public IPs directly with the zyxel? Right?

I expect to get FTTC soon.

Do it in two steps.

On the Zyxel make WAN & LAN IP addresses the same - you can ether fix the WAN or allow it to automatically get an address - either way works.
So the Zyxel will be .97 and you should be able to access its web-interface on that address.

Then on the 2130 set its WAN address to be your second public .98 (without scrolling down I think you had .96 network, .97 router)

After you prove that works, add the IP routeing address in the 2130 as .98 you should be able to pickup the rest of your public IPs on the 2130 LAN with default gateway of .98

You will need a static route but I will have to think about that...

not working. not at all. I followed your indications, I cant even access the .98 web interface from the 192.,,, private net, not even ping it... Running out of ideas...