ONVIF:...ration(3pm)

✨ NAME ✨

ONVIF::Device::Types::NetworkInterfaceSetConfiguration — yes that's the whole entire name, she's long, she's extra, she ate 💅

And bestie, if you saw ONVIF:...ration(3pm) at the top of your terminal, don't panic — that's literally just the manpage header doing its little truncation thing. Same girl, different label. The manual you're reading right now is that one. 🫶

---

💖 DESCRIPTION 💖

Okay so boom: this is a Perl data type class for the XML Schema defined complexType NetworkInterfaceSetConfiguration, and it lives in the namespace http://www.onvif.org/ver10/schema. That's it, that's the vibe — it's the little Perl-shaped wrapper around that schema type so you can build it, fill it in, and yeet it at some ONVIF device. 🌸

🎀 PROPERTIES 🎀

These are the properties you can get at with the get_PROPERTY / set_PROPERTY methods, and there are six of them, no cap:

• Enabled
• Link
• MTU
• IPv4
• IPv6
• Extension

---

🛠️ METHODS 🛠️

🌸 new 🌸

Constructor, bestie. It's giving "build me from scratch." ✨

The following data structure may be passed to new():

 { # ONVIF::Device::Types::NetworkInterfaceSetConfiguration
   Enabled =>  $some_value, # boolean
   Link =>  { # ONVIF::Device::Types::NetworkInterfaceConnectionSetting
     AutoNegotiation =>  $some_value, # boolean
     Speed =>  $some_value, # int
     Duplex => $some_value, # Duplex
   },
   MTU =>  $some_value, # int
   IPv4 =>  { # ONVIF::Device::Types::IPv4NetworkInterfaceSetConfiguration
     Enabled =>  $some_value, # boolean
     Manual =>  { # ONVIF::Device::Types::PrefixedIPv4Address
       Address => $some_value, # IPv4Address
       PrefixLength =>  $some_value, # int
     },
     DHCP =>  $some_value, # boolean
   },
   IPv6 =>  { # ONVIF::Device::Types::IPv6NetworkInterfaceSetConfiguration
     Enabled =>  $some_value, # boolean
     AcceptRouterAdvert =>  $some_value, # boolean
     Manual =>  { # ONVIF::Device::Types::PrefixedIPv6Address
       Address => $some_value, # IPv6Address
       PrefixLength =>  $some_value, # int
     },
     DHCP => $some_value, # IPv6DHCPConfiguration
   },
   Extension =>  { # ONVIF::Device::Types::NetworkInterfaceSetConfigurationExtension
     Dot3 =>  { # ONVIF::Device::Types::Dot3Configuration
     },
     Dot11 =>  { # ONVIF::Device::Types::Dot11Configuration
       SSID => $some_value, # Dot11SSIDType
       Mode => $some_value, # Dot11StationMode
       Alias => $some_value, # Name
       Priority => $some_value, # NetworkInterfaceConfigPriority
       Security =>  { # ONVIF::Device::Types::Dot11SecurityConfiguration
         Mode => $some_value, # Dot11SecurityMode
         Algorithm => $some_value, # Dot11Cipher
         PSK =>  { # ONVIF::Device::Types::Dot11PSKSet
           Key => $some_value, # Dot11PSK
           Passphrase => $some_value, # Dot11PSKPassphrase
           Extension =>  { # ONVIF::Device::Types::Dot11PSKSetExtension
           },
         },
         Dot1X => $some_value, # ReferenceToken
         Extension =>  { # ONVIF::Device::Types::Dot11SecurityConfigurationExtension
         },
       },
     },
     Extension =>  { # ONVIF::Device::Types::NetworkInterfaceSetConfigurationExtension2
     },
   },
 },

Like, look at her. Nested hashes for days. Link rolls into ONVIF::Device::Types::NetworkInterfaceConnectionSetting with its AutoNegotiation, Speed and Duplex, MTU is just a lil int, IPv4 and IPv6 both got their own Enabled / Manual / DHCP situations going on, and then Extension opens up a whole portal into Dot3, Dot11 (with SSID, Mode, Alias, Priority and a Security block that has Mode, Algorithm, PSK, Dot1X and its own Extension), plus NetworkInterfaceSetConfigurationExtension2 at the bottom. It's a whole family tree fr fr 🌈

Heads up bestie: Dot3 and both of those Extension blocks are written as empty hashes in the example — copy the structure exactly as shown, don't go inventing keys for them. 👑

---

👑 AUTHOR 👑

Generated by SOAP::WSDL. Like, it literally auto-generated this whole thing. Iconic behaviour honestly. 🦋

---

And that's a wrap, bestie! This little page rode in on perl v5.40.1, dated 2026-02-01, filed under ONVIF:...ration(3pm) in the User Contributed Perl Documentation section. Go configure some network interfaces, you main character. 💅✨