@projects, I am not at all sure what GLi is specifically doing to address (Repeater) Bridge, but as you want to use standard OpenWrt without the GLi GUI, you are pretty much back in OpenWrt land.
Not clear if you are using wireless or wired as you only include the network file. If you are running wired between the Gli and “upstream” device, then you may want to see this wiki. [OpenWrt Wiki] Wireless Access Point / Dumb Access Point You can do this in Luci.
If the GLi device is wireless on both sides then you should read the following WIKIs:
Relayd is only needed if both sides of the same radio are wireless.
If you have control of the “upstream” DHCP device you have more options depending on hardware (see first wiki). Using relayd pretty much allows you to confine all config to a device you have control over (yours), and your best alternative from a support perspective, though definitely more complex.
UCI or editing files should be the same, though some elements in the network file are chipset dependent (ifnames I think). Luci also works for most of this. I edit files in Windows using WinSCP or use Luci.
While it seems unrelated ATM, I strongly suggest setting a fixed IP for the device. If you let the main DHCP router assign the IP it may change after a reboot and you may have trouble accessing the device if needed. May or may not be relevant in your config environment. Have not done this in a year so it’s a bit foggy.
Yes, the other person is not understanding my need and what he is saying is much more complicated than what I am asking.
I simply need to bridge the two interfaces together, with the device acting as a DHCP client (no dhcp server or firewall is installed on device) so that I can inspect packets between the two interfaces.
The file is, as you know, in files/etc/config/network
Can you just post exactly the file I should use. I’m not clear on what you are suggesting.
Once I see it done, I’ll know what you mean, can use it and can save the note.
LOL, I created the file as I thought you meant and built a new firmware. I got locked out of the device which ended up having no network what so ever. The only way I was able to recover was the user TTL and to send echo commands of each line into the network file. Eventually, I was able to reboot it, gain network again then fix the problem.
It was interesting that I could not make it go into any factory default mode where it would look for a firmware by tftp however.
So, to prevent making that mistake again, I will post the contents of the file. I’ve asked you if you could post the full content so I don’t make any error because it is not clear what you are telling me when you are highlighting and crossing things out :).
Actually, I will never need a router mode, I only ever need the device in bridge mode. It should have only two ways of connecting it.
One, connecting to LAN when only wanting to use the device as a client, no pass-through.
Two, pass-through, connecting LAN side of network to the LAN port of the device, then connecting the upstream router/modem/firewall with DHCP server to the WAN port of the device. This will allow us to use tcpdump on the device to do troubleshooting. The device could remain in place this way.
Also, the dhcp option, ignore 1, is this basically to prevent the dhcp server from starting on the device? I don’t need a dhcp server on the device, I only need the device to be a dhcp client. I built using the above, without a dhcp file so have the factory default.
The device does pick up a dhcp address from the upstream. The only dhcp process I see running on the device is;
If you plan to use packages with the trunk build, you should also download all the packages in the subfolder packages (try wget) and also the packages for the architecture here: Index of /snapshots/packages/mipsel_24kc/ LEDE manages packages differently than OpenWrt.
They should be from the same build event or they may not install. You will need to search on how to manage your package repository. I usually just FTP (WINSCP) them to the tmp folder. This is a stripped image and will not include Luci, USB, etc.
Not tried these.
There is no date on LEDE stable versions, but as there is trunk there should be stable when available.