Error #384
tancatHooks deleted in testing branch
Descripció
In the testing branch almost all of the hooks are missing and, in consequence, several devices won't have the network configured properly.
If there is no special reason to keep them deleted, the hooks should be added again to the testing branch.
Actualitzat per Roger Pueyo Centelles fa aproximadament 8 anys
- Estat ha canviat de Nou a Tancat
- % realitzat ha canviat de 0 a 100
The network interfaces autodetection script was improved, so the hooks were no longer needed.
Actualitzat per Jorge L. Florit fa aproximadament 8 anys
And what about VLANs in "cheap switches"?
For example, a TP-Link TL-WDR3600 (and surely with 4300) with a testing image, doesn't connect to the Mesh via cable.
Previously the last port (4) of the switch was used for Mesh via cable, configured with vlan 12.
What is the way to do it now without hooks nor setting it manually?
Actualitzat per Roger Pueyo Centelles fa aproximadament 8 anys
- Categoria ha canviat de qMp a Network
- Prioritat ha canviat de Urgent a Baixa
Jorge L. Florit va escriure:
This has been explained in the mailing lists. The switches are configured by OpenWrt using 802.1q VLANs, so you get two interfaces:And what about VLANs in "cheap switches"?
- eth0.1 => LAN
- eth0.2 => WAN
Now qMp uses 802.1ad (i.e. QinQ) VLANs, so that you can apply them on top of the 802.1q VLANs used for managing the switches. Therefore, if you want to use the [eth0.2 interface/WAN port] for meshing, you just configure it on the web interface as if it was a regular (i.e. non-switched) interface (e.g. eth2).
For example, a TP-Link TL-WDR3600 (and surely with 4300) with a testing image, doesn't connect to the Mesh via cable.
Indeed, it does. Please have in mind that we are using 802.1ad VLANs for tagging the BMX6 packets, so the testing firmware binaries are not backwards-compatible with previous qMp versions.
Previously the last port (4) of the switch was used for Mesh via cable, configured with vlan 12.
What is the way to do it now without hooks nor setting it manually?
The VLAN12 hook was a dirty workaround which does not make sense anymore. You can mesh via any of the ports, you just have to configure it on the web interface (or in /etc/config/qmp).