2 router portforwarding

Will not work you have to have access, the default setting it to discard any incoming traffic.

There must be a cable running from the WAN port of your inner router (the one you do have access to) to the "2nd Router". Can you not trace that and find out where it is? If you find it you should be able to just connect the cable that's running from the WAN port on your 2nd Router directly to the WAN port on your "Asus Router". If they're in a separate location, you can just get an RJ45 female to female adapter like this: http://www.newegg.com/Product/Product.aspx?Item=9SIA1HE0YP1278&cm_re=rj45_extender-_-9SIA1HE0YP1278-_-Product

That'll bypass your "2nd Router" completely. As long as you can get the correct settings from your ISP to establish the Internet on your Asus router, AND no one is connected directly to the 2nd router, it should all work just fine.

So is the PPPoE box running as a router? I would think so. Is it just a standard ethernet cable running into the WAN side of the PPPoE box? It should be (PPPoE stands for point to point protocol over ethernet). Because if so, that can run straight into your Asus router and bypass the PPPoE box altogether (your Asus router, and any router for that matter, will run PPPoE itself). If you're running ADSL or its derivatives (over an old copper phone line), then it might be an ADSL modem, which does require specific hardware which is not built into many routers.

OK, I think you need to draw yourself a network diagram. We can't help unless we (and you) understand that actual network layout and know what's where.

Just some terminology, because we need to get that straight. A "router" is a device which routes (directs) traffic between different networks (usually between your home network and the Internet). In terms of consumer level gear in normal situations, if you are only using the "LAN" ports on a device and the "WAN" port is disconnected or not in use, then it is not functioning as a router. All the traffic in that case is coming to and from the same network (your LAN), so it's not a router. In those cases the device is functioning as a "switch", which simply forwards traffic within a single network.

So while you may have an Alvarion "router", if you're not using the WAN port, then it's technically functioning as a wireless access point and switch, not as a router.

The reason all this is important is because for a normal home network, you want to make sure that you only have ONE home network and ONE device operating as a router. It should look like this...

Internet -> Modem (if required, depends on type of Internet connection) -> your (one and only) router -> all devices on your network... all connected through switches and access points... NOT using "WAN" ports on any other devices.

Generally speaking you configure your sole "router" as the DHCP and DNS server for your network. If you have other devices which can function as routers (like a wireless router, for example), you make sure you turn off DHCP and DNS, give a static IP address on your single home network, and connect everything to the "LAN" ports... then it's not a router and you retain your single network design.

The primary reason this matters (though there are a few of them), is precisely for port forwarding to work. When you have ONE router and ONE internal network, then the router knows about and can direct traffic to any device on your internal network. That means you can set up a port forward and it will work properly.

So that's my suggestion. Take a little time to make sure all your devices are connected to you ONE internal network through ONE router, with any other "router" devices functioning as switches and access points. Do that and there's a very good chance your port forward will suddenly start working.

Just to be clear for others reading this, there are legitimate reasons why in some cases you may want multiple home networks (through multiple routers, or routers which provide multiple internal networks). Perhaps, for example, you want a separate network for your IP security cameras or host a web server that for security reasons you want to keep separate from your home network. As Internet accessible IoT devices become more common I can certainly see a case for putting such devices on a separate network such that if they get compromised, they can't then be used to hack your PC or NAS sitting on the same network. BUT, those sort of setups are more complicated and you need to properly understand routing before trying to set something like that up. For most cases, to keep it simple, ONE home network, ONE router... everything works!

Do you get a routerable IP on your router on the PPPoE interface or are you getting private IP addresses. If it is a routable IP you should be able to port forward. Try using the DMZ mode to test to make sure you have your ps4 setup correctly. If that does not work either the ISP is blocking some ports or you have your application misconfigured to not actually be listening on that port.

DMZ is pretty simplistic. So either the port you want is blocked by the ISP or the PS4 is not actually listening on that port. I have no clue how to troubleshoot a PS4.

That's a good suggestion from Bill001g... are you sure the WAN IP on your router is on the public range?

What is the WAN IP address on your router. Don't give us the final block of digits, keep that to yourself, but what are the first 3?

If it starts with either...
10.*...
172.16 (through to) 172.31 OR
192.168.*

Then it's a private IP range and you have double NAT going on and port forwarding will not work unless you can access the actual edge router.

If you DO have a public IP, it might be worth just trying to get a ping to it. Most routers have a setting which will allow them to respond to pings (often referred to as ICMP) on the WAN port. If you find that, enable it, then use a site like THIS to enter your WAN IP address and see if it responds to the ping.

Incidentally, the site I linked will also tell you your IP address, which should match the WAN IP on your router (otherwise, you're behind a double NAT and are stuck).

If you get the ping to respond, then you know that traffic from the internet CAN hit your router. So if the port forwarding is still not working then the issue is either with the port forward itself, or the device which is supposed to the target of the port forward.

question for bill...If you know 100% that your device is configured properly and then put the device in DMZ and it still does not function correct, is that a definitive way to test and prove an ISP layer 4 issue? such as an un-open port or an ALG? Especially if the LAN your on is doing a single NAT?