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:EVENT FWNOTIFY EVENT
| BoxMatrix >> System >> EVENT_FWNOTIFY_EVENT | @ 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 |
| Devices | Filesystems | Partitions | Sockets | Netlink | Pipes | Interfaces | Bridges | Ports | Events | Sources | Sinks | AVMIPC | Processes | Watchdogs | Memory | Slab | Vmalloc | ProcFS | SysFS | Research |
AVMIPC-Event
| AVMIPC-Event: | EVENT_FWNOTIFY_EVENT - type Event | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> AVMIPC-Datastore - Origin: AVM | ||||||
| Listeners: | me_anony-ctlmgr-($num)-($num).ctl, me_dsld.ctl | ||||||
| Properties: | Firmware: 7.01 - 7.90 - Senders: dsld, libavmfwnotify.so | ||||||
| Function: | Target event to send Firewall state information to. | ||||||
Goto: JSON-Data - Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
EVENT_FWNOTIFY_EVENT is the target event to send Firewall state information to.
It is maintained by libavmfwnotify.so, the client / server Firewall state notification library (ports open to the internet).
Clients call the fwnotify_client_query function which sends the EVENT_FWNOTIFY_EVENT_query avmipc event.
This function is used by showopenports and libcmapi.so for ctlmgr.
The server then calls the fwnotify_server_notify function responding with EVENT_FWNOTIFY_EVENT avmipc events.
This function is used by dsld. The response events contain the Firewall state in JSON format.
The response consists of one or more events which are stacked, like all avmipc events.
The JSON-Data below shows a snapshot of the last received event.
aicmd is of no help to fetch the complete list, Use showopenports to see them all.
The Model-Matrix shows that this event is zero size in IP-Client mode since port openings only work in router mode.
JSON-Data
Sample output of a 7520 fw 7.29 calling aicmd avmipcd datastore query EVENT_FWNOTIFY_EVENT full.
If the sample contains a size info then it's a snippet of aicmd avmipcd datastore show full from Supportdata2.
@EVENT_FWNOTIFY_EVENT : size 286, set by local , local:_anony1300-1382297367
DATA: <<!EOF!
fwnotify {
eventnr = 13;
event = fwnotifyevent_update;
uniqid = 0;
dsliface = "internet";
itemtype = "IGDPROBE";
protocol = 6;
iaddr = 192.168.178.1;
iport = 9;
iport_end = 9;
eaddr = 88.69.xx.xx;
eport = 9;
eport_end = 9;
desc = "IGDPROBE4";
iprefixlen = 0;
eprefixlen = 0;
}
// EOF
!EOF!
The event = fwnotifyevent_* line shows which part of the result it is. This can be one of:
- fwnotifyevent_add
- fwnotifyevent_update
- fwnotifyevent_delete
- fwnotifyevent_init
- fwnotifyevent_end
- fwnotifyevent_no_openports
Dependencies
Daily updated index of all dependencies of this event. Last update: 2024-04-18 04:27 GMT.
A ** in the Mod column marks info from Supportdata2 probes, which will always stay incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the Object occurs, not the Relation.
| Relation | Typ | Object | Mod | Firmware | Info | Origin |
|---|---|---|---|---|---|---|
| Listener | sock | me_anony-ctlmgr-($num)-($num).ctl | 21** | 7.01 - 7.90 | Anonymous avmipc endpoint of ctlmgr | AVM |
| Sender | cmd | dsld (avmcmd) | - | 1.120 - 7.90 | Internet routing daemon. | AVM |
| Sender | lib | libavmfwnotify.so | - | 6.36 - 7.90 | Firewall state notification. | AVM |
| 3 dependencies for this event | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this event for each model. Last update: 2024-04-18 04:27 GMT.
Showing all models using this event. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list comes from Supportdata2 probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata2 file or just a disabled feature.
Help Supportdata2
The data in this article is incomplete since it was manually collected using the Supportdata2 project.
Unlike the Supportdata-Probes which have been collected for years Supportdata2 is brand new and only has a few probes.
If you have access to a shell then please help to extend the Supportdata2 collection to improve this data.
It's easy and it's done in minutes. Please send created data as an Email attachment to the address listed here. Thanks!
