If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:Mesh (lexicon)
| BoxMatrix >> Lexicon >> FRITZ-Terms >> Mesh | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Computer | FRITZ | I18N | Telephony | Smarthome | Internet | Protocols | Multimedia | Formats | Hardware | Research |
 |
Name-Collision - multiple objects in this wiki use the name Mesh!
|
Term
| Term: | Mesh (lexicon) | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Short for: | Mesh configuration sharing | ||||||
| Location: | Lexicon >> FRITZ-Terms | ||||||
| Weblinks: | |||||||
| Description: | Sharing of configuration and status info between FRITZ!OS devices | ||||||
Goto: FRITZ!OS - SMW-Browser
Details
Mesh is a computer term which is pretty unspecific and used for many purposes including marketing.
FRITZ!OS
Introduction
In FRITZ!OS Mesh means sharing of configuration and status info between FRITZ!OS devices across a local network.
One device is configured to be the Mesh-Master. Further devices can be Mesh-Repeaters of this master.
The connection between the master and the repeaters can be WLAN or LAN or a mix of both.
A Mesh-Master can use any of the Box-Modes, a Mesh-Repeater must be in the same Subnet and turns an IP-Client.
For an overview of Mesh capable models see Mesh (models).
Peerings
The following FRITZ!OS parts could be merged by Mesh:
- Telephony
- Phonebook (+events)
- Online-Phonebook
- WLAN configuration (master, slave)
- WLAN steering (master, slave)
- Smarthome devices
- Event-Log
- Update-Check
- Email submission
- MAC address list
- Network device list
- Mesh configuration
- Mesh topology
- Box notification
- Timer config
- Authentification
- Automatic MyFRITZ! registration (7.39+)
Internals
AVM Mesh internally consists of 2 parts, configuration peering and topology management:
- Configuration and status info peering is performed by avmnexusd.
- Topology management and steering is performed by meshd.
WLAN guest network tunneling (auto configured by Mesh) is done by l2tpv3d.
