You shouldn’t need to do any port forwarding on a local network if your wifi router is in bridging mode.
It sounds like you have a router behind a router both running NAT firewalls, so you’re going to have to explain your network setup to make any sense of that.
To avoid wasting more time (especially other peoples time) you really should explain in detail what you are trying. I assume you are trying to connect from within your LAN to the Raspberry on the IP address 192.168.1.108. And this is working when the Raspberry is connected wireless but not when it is connected wired, correct?
Unless you have given the Raspberry a static IP address that it uses when connected wireless and wired it will change the IP when connected wired (to what is assigned by DHCP) therefore you will not be able to connect on 192.168.1.108.
Easy solution check the new IP that is assigned after you plugin the cable.
More elegant solution configure the DHCP server to assign the Raspberry the same address for wireless and wired. This needs the DHCP server (your router) capable of assigning same IP to too different MAC addresses.
No the source IP should not be a problem.
So do I understand it correct that the not working scenario is Raspberry wirless on the secondary Router and Macbook wired connected to the secondary router?
If so then write down the IP addresses the Mac has in that moment and the Raspberry Pi has in that moment and we can go from there.
It’s weird that when Macbook is wireless connected to either primary or secondary router it can access the WIRED Raspberry PI.
But when Macbook is wired to secondary router, I can’t get through. It should be able to get through since they are both wired to the same router.
Scenario:
Raspberry PI and Macbook wired to secondary repeater router.
Problem:
Doesn’t work when Macbook is wired to secondary router, but works when macbook is connected wirelessly to both primary or secondary routers. At all times, the RP2 is WIRED to the secondary router. I dont have a Wifi USB Dongle.
These are the IPs at the moment when Macbook and RP2 is WIRED to secondary router:
Macbook IP - 192.168.1.122
Well Static IP’s only help to make sure you know what you connect to it will not solve your connectivity problem. As long as you ensure that DHCP is working over the wireless bridge.
Ok while generally it would also help to write down the Netmask to ensure no mistake there (I assume both have 255.255.255.0 or /24) I would always start with basic network troubleshooting. Try to ping the raspberry pi from the Mac.
Depending on that result try to ping the routers…HOLD ON, just seeing that your router are in 192.168.0.x while your Raspberry and Mac are in 192.168.100.x
I think you really need to first give a us a full understanding of your setup including IP Adresses, Netmask, DNS,…
I have to admit that I am not 100% sure about your devices and your final goal. But I just saw that you have setup a “Client Bridge (routed)” which would indicated that the two router have own networks and no DHCP would be shared between them. What you want is a bridge that means 1 subnet where each router is a switch and not a router.
lol I dont think im 100 either on what the hell im doing right now. But my goal is to get Web interface to work while Macbook is Wired to secondary router.
Not 100% sure which dot you are refering to but that manual says “Wireless Mode : Repeater Bridge” while your screenshot show “Wireless Mode: Client Bridge (routed)”
so when the macbook and pi were wired (and both 192.168.1.x) could you ping the pi or ssh in? is it just an issue with the web interface or connectivity in general?