Change host "access profile"

[Hochiss]

Don't know if appropriate to ask here:

Would it be possible or How to change access profile, e.g. disable/enable certain host/ip's internet access?

thanks!

[kbr]

By the web-backend it is possible to block a device via "Internet -> Filters -> Parental Controls". May be there is a TR-064 service/action combination to change this settings. If you find a proper combination in the AVM documentation please feel free to post it here. Sorry for not having a better answer.

[Hochiss]

@kbr thanks for your reply. Yes that was what I mean to realize via API or TR064.
Checking your "further reading", I guess it may relate to "service X_AVM-DE_HostFilter":
https://avm.de/fileadmin/user_upload/Global/Service/Schnittstellen/AVM_TR-064_first_steps.pdf

But I am afraid the "X_AVM" series haven't been implemented into your API/Python library?

Another 2 methods I think would be possible is via headless web-parsing, or WebDAV method, but sounds very ugly.

[kbr]

Yes, you are right: web-parsing is a bad idea. Fortunately FritzConnection can access every service provided by AVM, even currently undefined upcoming ones. Available services may depend on the box model, but not on the library.

[Hochiss]

@kbr:
I was desperately searching in the above TR064 manual for the service: X_AVM-DE_HostFilter, which was noted on P.24/31 as last service, cannot find this specific service for my 7581(with latest FW:07.14). Hereby I use 2 methods for the discovery:

1. Manually(cf. above PDF p.7/31): http://192.168.178.1:49000/tr64desc.xml
2. or using your lib: fritzconnection -i 192.168.178.1 -c > api.txt

It can list the services up to 6.1.32 Service X_AVM-DE_Auth, only the last service, i.e. X_AVM-DE_HostFilter is not there, strange!

My intention was to find fc.call_action(), what action name predefined for certain IP/mac-adress, which are needed for :
call_action() missing 2 required positional arguments: 'service_name' and 'action_name'
which is also needed for fritzhosts.py for calling action.

Don't know if anyone could confirm with other models if service : X_AVM-DE_HostFilter is there using above 2 methods.

[kbr]

Does you FritzBox support this service at all?
Available services can vary on different models.

Here is an excerpt from my 7590 providing the X_AVM-DE_HostFilter service:

$ fritzconnection -i 192.168.178.1 -p <the_password> -s

fritzconnection v1.4.2
FRITZ!Box 7590 at http://192.168.178.1
FRITZ!OS: 7.21

Servicenames:
                    any1
                    WANCommonIFC1
                    WANDSLLinkC1
                    WANIPConn1
                    WANIPv6Firewall1
                    DeviceInfo1
                    DeviceConfig1
                    Layer3Forwarding1
                    LANConfigSecurity1
                    ManagementServer1
                    Time1
                    UserInterface1
                    X_AVM-DE_Storage1
                    X_AVM-DE_WebDAVClient1
                    X_AVM-DE_UPnP1
                    X_AVM-DE_Speedtest1
                    X_AVM-DE_RemoteAccess1
                    X_AVM-DE_MyFritz1
                    X_VoIP1
                    X_AVM-DE_OnTel1
                    X_AVM-DE_Dect1
                    X_AVM-DE_TAM1
                    X_AVM-DE_AppSetup1
                    X_AVM-DE_Homeauto1
                    X_AVM-DE_Homeplug1
                    X_AVM-DE_Filelinks1
                    X_AVM-DE_Auth1
                    X_AVM-DE_HostFilter1
                    WLANConfiguration1
                    WLANConfiguration2
                    WLANConfiguration3
                    Hosts1
                    LANEthernetInterfaceConfig1
                    LANHostConfigManagement1
                    WANCommonInterfaceConfig1
                    WANDSLInterfaceConfig1
                    WANDSLLinkConfig1
                    WANEthernetLinkConfig1
                    WANPPPConnection1
                    WANIPConnection1

$ fritzconnection -i 192.168.178.1 -p <the_password> -S X_AVM-DE_HostFilter1

fritzconnection v1.4.2
FRITZ!Box 7590 at http://192.168.178.1
FRITZ!OS: 7.21


Servicename:        X_AVM-DE_HostFilter1
Actionnames:
                    MarkTicket
                    GetTicketIDStatus
                    DiscardAllTickets
                    DisallowWANAccessByIP
                    GetWANAccessByIP

$ fritzconnection -i 192.168.178.1 -p <the_password> -A X_AVM-DE_HostFilter1 DisallowWANAccessByIP

fritzconnection v1.4.2
FRITZ!Box 7590 at http://192.168.178.1
FRITZ!OS: 7.21


Service:            X_AVM-DE_HostFilter1
Action:             DisallowWANAccessByIP
Parameters:

    Name                                  direction     data type

    NewIPv4Address                        -> in         string
    NewDisallow                           -> in         boolean

For every service/action combination not provided by one of the lib-modules, you can use fritzconnection directly:

from fritzconnection import FritzConnection

fc = FritzConnection(<your access parameters here>)
arguments = {
    "NewIPv4Address": "x.x.x.x",
    "NewDisallow": True|False
}
fc.call_action(
    "X_AVM-DE_HostFilter1", 
    "DisallowWANAccessByIP", 
    arguments=arguments
)

The library modules are just convenience-wrappers for these kind of calls.

[Hochiss]

very strange, mine doesn't have the filter service!

$ fritzconnection -i 192.168.178.1 -p <the_password> -s

fritzconnection v1.4.2
FRITZ!Box 7581 at http://192.168.178.1
FRITZ!OS: 7.14

Servicenames:
                    any1
                    WANCommonIFC1
                    WANDSLLinkC1
                    WANIPConn1
                    WANIPv6Firewall1
                    DeviceInfo1
                    DeviceConfig1
                    Layer3Forwarding1
                    LANConfigSecurity1
                    ManagementServer1
                    Time1
                    UserInterface1
                    X_AVM-DE_Storage1
                    X_AVM-DE_WebDAVClient1
                    X_AVM-DE_UPnP1
                    X_AVM-DE_Speedtest1
                    X_AVM-DE_RemoteAccess1
                    X_AVM-DE_MyFritz1
                    X_VoIP1
                    X_AVM-DE_OnTel1
                    X_AVM-DE_Dect1
                    X_AVM-DE_TAM1
                    X_AVM-DE_AppSetup1
                    X_AVM-DE_Homeauto1
                    X_AVM-DE_Homeplug1
                    X_AVM-DE_Filelinks1
                    X_AVM-DE_Auth1
                    WLANConfiguration1
                    WLANConfiguration2
                    WLANConfiguration3
                    Hosts1
                    LANEthernetInterfaceConfig1
                    LANHostConfigManagement1
                    WANCommonInterfaceConfig1
                    WANDSLInterfaceConfig1
                    WANDSLLinkConfig1
                    WANEthernetLinkConfig1
                    WANPPPConnection1
                    WANIPConnection1

feel discriminated ... but the fritz web has those functions!

[Hochiss]

Ultimate solutions:

driver.find_elements_by_id('uiPass')[0].send_keys(PWD)
driver.find_elements_by_id('submitLoginBtn')[0].click()

[jedie]

For my https://github.com/jedie/django-fritzconnection project, i start Implementing a API class for X_AVM-DE_HostFilter1 in similar way fritzconnection does. See: https://github.com/jedie/django-fritzconnection/blob/02b3a38ec22b058ec0f184fac0029f5069a2951d/djfritz/fritz_connection.py#L31-L106

I create the helper methods to get the current "WAN access state" and to change it...
It works with my FRITZ!Box 7530 AX v7.29 ... But it takes some time: From changing the status, until the box reports this changed status back and again until the change is really active on the host. Is that normal?

I can create a pull request, to move this into fritzconnection. Should i?

[kbr]

Thank you for the idea to provide a pull-request. Browsing the code I can think of three additional methods like set_host_wan_access, get_host_wan_access and host_has_wan_access for handling the basic tasks leaving everything else to the application. I think the proper module would be fritzhosts. I can also put this on my to do list.

On my 7590 (v7.29) it takes about 1-2 seconds until changes are reported in the web-frontend. May be the command waits in a queue to get processed – but I don't know the AVM internals.