Maybe this is a permissions issue?
No, it's not. Please remember that from the outside (where your laptop is) the whole infrastructure behind the hybrid (actually core) is considered all to be 1 IP - that is the "external" IP on your core (192.168.1.x, could be 3 or 2 or whatever in the end you assigned)... This is what NATing does for you.
You can now go 3 routes, each with pros and cons:
1. Move your wireless AP (WRT54G) to the internal network (like the Gb switch) - remember to disable DHCP on the wireless router, and remember to set its own IP to be in the 192.168.80.xx range - and connect one of the LAN ports to this network, NOT the WAN port. This will make it an Access Point, rather than a router... Downside, all you wireless stuff will now be in the domain of LMCE, and access to internet is routed through the core - so lets hope it is stable!
2. Allow the core to route traffic between the 2 subnets (the external and internal on the core) - not recommended for most use.
3. The easy and controllable one. Allow port forwarding through the core, with port mapping. You should forward i.e. port 12080 from the cores external IP (could be 192.168.1.3) to the internal IP 192.168.80.132 - BUT ON PORT 80!! now you can from the outside access the LMCE web interface on port 80 by typing 192.168.1.3 (port 80 is given), and if this is your external IP on the core, you should get the LMCE web interface. If your type 192.168.1.3:12080 you should get to the NAS.. The downside here could be that from the INSIDE of the LMCE network the best way to communicate with the NAS is via 192.168.80.132 - i.e. there is a risk of confusion...
Unless you have other specific reasons (like I do), and granted your core is running stable - I would go for option 1.
(there is actually a fourth option with 2 discrete wireless networks, where you would choose between the 2 when you log on to WiFi - this can have some major benefits and ease of use for the rest of the household and guests)