You can access it at the bridge IP.
Your main router will be giving it a client IP which should be accessible.
Problem after update 1.8->1.10 WDS systems
Moderator: Moderators
Re: Problem after update 1.8->1.10 WDS systems
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
Re: Problem after update 1.8->1.10 WDS systems
Got it! I'll check later. Is there any advantage in using WDS instead of Client Bridge?
Re: Problem after update 1.8->1.10 WDS systems
WDS truly puts all devices in the same subnet, but it can be a bit flakey when being used by different devices with different chipsets (the implementation isn’t quite standardised and every manufacturer has their own take on it).
Client bridge does a pseudo bridge to get everyone on the same network.
It generally works pretty well but there is some things that don’t work.
I think IGMP packets sometimes don’t get through? But there’s a way to fix that.
Client bridge does a pseudo bridge to get everyone on the same network.
It generally works pretty well but there is some things that don’t work.
I think IGMP packets sometimes don’t get through? But there’s a way to fix that.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
Re: Problem after update 1.8->1.10 WDS systems
Nope... didn't work. Seems that WDS is broken here. I had to revert to Client Bridge.