Also I have a 15Gb Stick, that I just formatted with FAT32 fs.
Can I somehow mount the USB-Dsik so, that all packages or whatever Parts of the Filesystem on the internal Flash I can do this with, will be installed there and my Spaceproblems are solved?
Will I re-format to EXT4 or which Filesystem do I need for this?
Hoe can I see if the Stick has been properly detected?
fdisk or sfdisk don't exist on the Router..
And I have another Problem:
I also have a Ubiquity Wifi-AP.
I would like to configure it so, that it connect to my other Router via Wifi.
Then I would like to open a Wifi-Hotspot with the other Wifi-Interface.
Then I want to be able to connect to the new hotstop and via cable.
How would I configure this properly? I couldn't find a Tutorial for this.
Also can I completely use the DHCP of my first Router?
Because at the moment if I connect to the Ubiquity, i get no DHCP-assigned IP.
One is RAM, which with only 32 or 64 MB of it (your TP-Link 1043ND's version isn't clear to me), you are likely to run out of memory when running things.
The other is flash storage. With what looks like 8 MB of flash, you are likely storage when installing packages. This, from "filesystem full", sounds like what has happened to you.
You might want to look at "extroot" as a way of "replacing" the internal flash storage with a USB stick or the like.
There are many ways of doing this, depending on your needs, as well as your hardware and its drivers. Perhaps the easiest to configure is "WDS" connection between the two. You should be able to plug in a cabled-device to the second router's switch as well as connect over its wireless AP.
Any wireless "repeater" or "bridge" on the same radio as providing the AP for its clients will reduce the available bandwidth by at least a factor of two. Part of the "physics" of it and not an OpenWRT restriction, unfortunately.
Two radios are shown, one for each of the two bands, 2.4 GHz and 5 GHz.
Well I dont want to repeat the wifi to avoid exactly this.
I want to connect to my existing wifi, which is 2ghz and then open another, different one with 5ghz.
there should be no bandwindth restrictions then, right?
except, that 2ghz is slower than 5ghz in the first place..
Regarding the radios:
I dont mean the radio0 and radio1, that can be seen under "wireless overview".
that is clear to me.
i mean the top: there is radio1: client "SSID", radio1: client "SSID" and radio0; "SSID".
why is radio1 there twice?
"OpenWrt WLAN" is a SSID, that i created earlier, but removed it then. This shouldnt be there.
If you installed it with opkg, then I'd remove it with opkg.
(You can't really "remove" packages that are built into the ROM itself, just hide them.)
There are very few times that I'd even consider manipulating the overlay file system directly. About the only time I'd even remotely consider it is if you've overwritten a file on the ROM that you want to restore. Even then, a backup/reset/restore process is a safer course of action.
overlayfs:/overlay 4.2M 4.1M 104.0K 98% /
suggests that you're out of file-system space. Adding swap isn't going to help that problem. (I'd also not suggest using flash for swap for a number of reasons.)
It puzzles me how you've installed something that is 5.6 MB on a file system that only is 4.2 MB. That just seems strange to me!
Regarding the "phantom" SSID, it might be something "stale" in your config file.
Why would you advise against using swap on a pend rive? Only because of lower read/write?
I configured it like this now and it works so far.
But I am thinking about using a raspberry pi as dns server, so I will have some more memory on my Router.
Should I install OpenWRT on my pi for that too or are there some other more fitting distros for this use case? Or maybe I will just use Debian..
The most certain way to recover from overfilling the flash is to run firstboot to reformat the overlay file system. This will require you to reconfigure the router from scratch and reinstall all the packages. Doing a re-flash of the same version with sysupgrade might work to save your configuration.
I was thinking you were considering swap on the built-in flash, which has the major disadvantages of flash wear and speed. On a USB stick, the flash wear tends to be hidden from you and the speed can be significantly better.
I've never found swap to be a necessity, but then again, I don't load my router up will all kinds of services.
On the Raspberry Pi, as you've got the luxury of significantly more storage and RAM and aren't running it for the purposes that OpenWRT is focused on, I'd run Debian myself. My choice of DNS servers for "local" use is unbound. I find it robust, flexible, and relatively easy to configure. I'd also suggest git or another version-control system to help you manage the config files for something like DNS that can be more than a few lines long.
I need to enable my ISPs DHCP for a fallback-wlan (openwrt seems not to be configured correctly yet...)
Can I re-enable the DHCP of my ISP Router and still run the DHCP on my OpenWRT, that's not yet configured correctly?
Or would devices connecting to my openwrt also get an ip address from my ISPs Router?
If so, can I prevent this by blocking any Ports on my OpenWrt? LAN1 of my ISP Router is connected to WAN in openwrt and has its own firewall rule.
OpenWrt s IP on that Port is static, so I don't need DHCP for that.
"Double NAT" is generally not recommended as it is a maintenance nightmare. (One NAT in your modem, one in the OpenWRT box.)
The "best of all worlds" is if your modem supports a "pass-through" or "bridged" mode that give the DHCP assignment of the "outside" IP address to your router directly. Some modems automatically switch modes, others require manual configuration, and some can't be configured for that type of operation. In some cases, it might take some time for your ISP to "release" the old DHCP assignment and provide a new one directly to the router.
DHCP is an "on-link" kind of thing, so trying to configure a "DHCP relay" to enable clients on your LAN to get DHCP from your ISP's server is non-trivial. If your sure you can't get your modem into pass-through mode, then things get complex quickly without resorting to double NAT. There are ways of accomplishing it involving bridging and firewalling the bridge, but you'll probably lose a lot of the ease of use of OpenWRT's GUI if you do so.
I'd explore getting your modem into pass-through mode and OpenWRT configured to accept the DHCP directly from your ISP before diving into alternative topologies.
Expanding what jeff said, if you want to enable wlan on your ISP modem-router, you're almost guaranteed to push it out of modem-mode (transparent bridge, which is what you want to have in order to avoid double NAT) into router-mode, which comes with all the problems listed above.
