Hello, I own a BRUME2 which is connected via its WAN port with my main router, a Telekom Speedport Smart4 A
When I connect a single Computer to my BRUME2s LAN port everything works fine: BRUME can be accessed and delivers what its supposed to do.
BUT...soon as I want to connect all my other devices which are behind a TP-LINK TL108 Switch by connecting the switch with the LAN port of BRUME2 nothing seems to work: No internet access, no access to the GUI of BRUME2
The only way I found to make it work is Connecting the TP Link Switch again with the main routers LAN socket and the BRUME2 s WAN socket connected with one of the switches LAN sockets, but only in Drop-In Menu mode. Soon as I disable Drop-In, every connection gets lost.
I've been trying and trying but without success.
Fun Fact: Main router is 192.168.2.1 and when all devices were attached to it before I baught BRUME2 the DHCP server of it provided adresses between 192.168.2.20-254
To make Drop work I followed the instruction and disabled the DHCP server of the main router and enabled it on BRUME2 with a DHCP range from 192.168.8.100-249 as factory default.
However BRUME still keeps the 192.168.2. range and even IP reservations can be done in that range without any error from the GUI which is odd. Even after uncounted reboots, etc. (also a complete switch of of my apartments energy supply did not resolve this.
So...any idea whats wrong? I mean I know that the main router's DHCP must be kept turned of but soon as I want to switch back to non Drop-In all connections break down.
It shows that the router requires to connect to the interface WAN not LAN if it uses as the drop-in gateway in your currently network topology.
The IP range also is 192.168.2.x when the Brume 2 completes the setting of drop-in gateway and as the DHCP server, since the network gateway is main router, so Brume 2 also has to follow the main router IP range.
Hi Bruce, thanks for your feedback.
All devices should use the drop in gateway. However the first issue is that if I only connect 1 Computer the the LAN port of the Brume 2 it workts. Soon as I connect the TL-SG108 switch to it I have no connectivity at any other port of the TL-SG108. That means I cannot distribute the connection if Brume 2 LAN port via a switch to any other device.
Thats what I mentioned above. And I just tried it again.
Strange thing is: Soon as I connect the brume to the speedport and the switch to the brume I get a mixture of IPs:
Speedport (IP 192.168.2.1) keeps with DHCP on the range 192.168.2.10-254
However even though the brume DHCP server is off the client pc which I want to connect to brume stays in the 192.168.8 range and can access the internet but not all other devices including the speedport.
The speedport contains the necessaray DSL modem. Also it contains the DECT base for my home phone. And I also use the guest network wifi for my business laptop which connects to our company VPN.
If my described configuration does not work in your setup, how to make it work then?
What confuses me even more is what Bruce mentioned:
The IP range also is 192.168.2.x when the Brume 2 completes the setting of drop-in gateway and as the DHCP server, since the network gateway is main router, so Brume 2 also has to follow the main router IP range.<
It highly depends on what you want to get at the end. My personal way would be replacing the Brume with a router that offers Wi-Fi and disable everything on the speedport except DECT.
So it would be double NAT but, well, you can't always get what you want.
The Drop-In feature, in my opinion, is more some emergency thingy to make it work. Not a real solution for a professional and reliable network.
Since the TP-LINK TL108 is unmanged you won't even know what's happening there.
If you want to go the Drop-In-Gateway ... way (hehe) ... you need to make sure that the Brume DHCP is on, the Speedports DHCP is off. You might even need to reconnect all devices to Brume so they will release the 192.168.8.x IP.
Well I had the following setup which worked except DDNS and only with Drop-In ON!
Brume WAN connected to one of the LAN ports of the switch and Drop-In Gateway on. DHCP on on the Brume, DHCP off on the speedport.
However the Brume still provided DHCP adresses in the 192.168.2.x range and allowed corresponding IP address reservation within that range. Only devices that were attached to the LAN port of Brume obained adresses in the 192.168.8.x range
That worked fine so far. The issue was that I could not use DDNS as it always complained that the BRUME2 IP address did not match the WAN interface IP adress.
This won't change in your setup because the Brume will never know about the real WAN address due to NAT of the Speedport. You could go with other DDNS services which don't need to know the WAN and will set it based on the IP the request comes from.
If you saved the full config using luci, you can restore it on the same way.
If you just saved a bunch of files, you need to copy them back into the original files using SSH.
By the way, I remembered that I created a script for this case - so for using GLDDNS behind another router. I did not maintain it anymore (at least not actively) but you can give it a try if you like, @AirMax
By the way: This is an extract of the logfile after a reboot: I am not sure if all lines are correct?
Mon Nov 4 18:54:55 2024 daemon.info dnsmasq-dhcp[10421]: DHCPOFFER(eth0) 192.168.2.195 94:83:c4:44:d2:ec
Mon Nov 4 18:55:17 2024 daemon.info dnsmasq[10421]: exiting on receipt of SIGTERM
Mon Nov 4 18:55:18 2024 daemon.err dnsmasq[14383]: failed to allocate -1 bytes
Mon Nov 4 18:55:18 2024 daemon.err dnsmasq[14383]: failed to parse lease database cleanly
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: Connected to system UBus
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: started, version 2.85 cachesize 150
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: DNS service limited to local subnets
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: UBus support enabled: connected to system bus
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq-dhcp[14383]: DHCP, IP range 192.168.2.2 -- 192.168.2.253, lease time 12h
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq-dhcp[14383]: DHCP, IP range 192.168.8.100 -- 192.168.8.249, lease time 12h
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: using only locally-known addresses for domain test
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: using only locally-known addresses for domain onion
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: using only locally-known addresses for domain localhost
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: using only locally-known addresses for domain local
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: using only locally-known addresses for domain invalid
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: using only locally-known addresses for domain bind
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: using nameserver 127.0.0.1#5453
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: using only locally-known addresses for domain lan
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: read /etc/hosts - 4 addresses
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq[14383]: read /tmp/hosts/dhcp.cfg01411c - 4 addresses
Mon Nov 4 18:55:18 2024 daemon.info dnsmasq-dhcp[14383]: read /etc/ethers - 0 addresses
Mon Nov 4 18:55:44 2024 daemon.err dnsmasq[14383]: Conntrack connection mark retrieval failed: No such file or directory
