Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I did that with a GL.iNet travel router after flashing stock OpenWRT, and used it as a wireless bridge for several years. It uses relayd to bridge the Wifi station interface and Ethernet. Once you have an ethernet bridge, you can connect another AP or do whatever from there.
If you create a second wifi interface in AP mode (in addition to the station/client one connected to the upstream), you should be able to add that to the LAN bridge alongside the ethernet interfaces. That bridge will then be part of the relayd bridge, and it all should just work (should, lol. I haven't tested that config since I only needed to turn wifi into wired ethernet with this setup).
Interfaces:
LAN Bridge: Ethernet interfaces to be bridged to the wifi
I have both of its interfaces in this bridge, and it also has a static management IP (outside of the WLAN subnet). This management IP is a static out-of-band IP since the devices connected over ethernet won't be able to access it's WLAN IP (in the main LAN) to manage it. To access this IP, I just statically set an additional IP on one of the downstream ethernet client devices.
The LAN bridge is in a firewall zone called LAN.
WWAN: Wireless station interface that's configured as a client to the AP providing upstream access. I have this configured statically, but DHCP is fine too. Firewall zone is WLAN.
WLANBRIDGE: The relayd bridge (Protocol: relay bridge). It's interfaces are the LAN bridge and the WWAN interface.
Disregard the WGMesh parts; that's separate and not related to the wireless bridging mode.
I've tried to match your setup, but to no avail.
Interfaces:
lan
Static address (192.168.2.1) Firewall zone: lan
wwan
Static address (192.168.0.211) Device: phy0-sta0 (listed as the client in the dropdown) Gateway: 192.168.0.1 Use custom DNS servers: 1.1.1.1 (using root router's IP causes DNS to stop working) Firewall zone: WLAN
repeater_bridge
Relay bridge Relay between: lan wwan Firewall zone: unspecified
Firewall zones: lan ⇒ WLAN accept accept accept WLAN ⇒ lan accept accept accept
With this, I am able to ping google.com from a openwrt ssh session, but not my laptop connected w/ ethernet (and a static ip). In the interfaces list, lan is green, repeater_bridge is grey, and wwan is red. I tried running /etc/init.d/firewall stop but still no luck.
Hmm. Is the upstream AP some kind of fancy deal or a run of the mill consumer router?
I've seen some Cisco APs configured to not allow multiple MAC addresses from the same station. Caused problems when trying to do VMs on my laptop that had the network in bridge mode.
Are you able to put your phone into hotspot, connect to that instead of the upstream AP, and see if it works?
It's an ordinary consumer wifi 4 router (by a company named Renkforce). I was able to use WDS with it previously, but I haven't got it working since flashing openwrt, which is why I was trying relayd. A hotspot from my phone works (but is really slow obviously). I suspect something is wrong with my interface or firewall setup, given the colors of the interfaces.
I've always thought the firewall color codes were arbitrary, though I might just have not paid attention all these years lol.
Just to clarify: I meant connect your OpenWRT device to your hotspot instead of the AP you've been working with. Just to rule out multiple MACs being blocked on the AP.
Beyond that, I'm not really able to help troubleshoot further, but worst case and if all you need is internet, you can set your OpenWRT device up so that it just NATs your downstream connections. Double-NAT, in most cases, is fine.