Excentis Config File Editor Download
Antonio Hadfield
The program is built on top of the powerful Perl based DOCSIS::ConfigFile library. Have a look at the complete configuration parameters to see what is possible or simply try out an example config and start editing.
Tell that to the bunch of SB5100/5101 modems I have out there not doing DOCSIS2 even after upgrading them. I have to put that TLV in to get those to register as D2 modems on the ATDMA upstreams. scm mac shows them as DOC1.1 DOC1.1 until I push the config with that TLV.
That would be correct, there are particular breeds of the 5100/5101 series modems that *DO REQUIRE* a motorola specific TLV in the modem config file in order to function in docsis 2 mode. Fortunately, the tlv is only recognized by those modems, and other modems will ignore it as unrecognized, so it is safe to put it in your general modem configs.
Can you post the Motorola Specific TLV mentioned that needs to be added to the config file to get them to register 2.0? I have TLV39 set properly already, but I have a bunch of 5101s and some 941s that wont register with QOS Provisioning higher than 1.1...the config file is built specifically with 2.0 options only....any help is greatly appreciated.
In the case of all other SB510x (1,2) it could be that the DOCSIS 2.0 (ATDMA) mode was deactivated in the Nonvol-Area of the configuration. For this you have to use the Mib CM-CONFIG-MIB::cmDocsis20Capable to enable it. BUT there is a bug: If you have already the DOCSIS 2.0 (ATDMA) mode via SNMP and the SB510x is still connected on a TDMA upstream, the docsis-cm-capable mib from CableLabs will show you the capability for DOCSIS 1.1 only on the SB510x. First after a new registration on a TDMA-ATDMA (mixed-mode) or ATDMA-Only Upstream the capability mib from CableLabs will show you DOCSIS 2.0.
You can use a server, desktop, or VM with three network interfaces running Ubuntu Server 22.04. One NIC is for management and has an IP address so I can SSH to it. The other two NICs are configured in a bridge. Or 4 NICs for two bridges. I did my testing with a Hyper-V VM. For a VM make sure MAC spoofing is allowed for the two bridge NICs.
When you no longer need a DHCP option set, use the following procedure to delete it. You can't delete a DHCP option set if it's in use. For each VPC associated with the DHCP option set to delete, you must associate a different DHCP option set with the VPC or configure the VPC to use no DHCP option set. For more information, see Change the option set associated with a VPC.
In general, the left side will show context related information, the middle partwill show information about the current capture file, and the right side willshow the selected configuration profile. Drag the handles between the text areasto change the size.
Some interfaces allow or require configuration prior to capture.This will be indicated by a configuration icon()to the left of the interface name.Clicking on the icon will show the configuration dialog for that interface.
Name resolution tries to convert some of the numerical address values into ahuman readable format. There are two possible ways to do these conversions,depending on the resolution to be done: calling system/network services (likethe gethostname() function) and/or resolving from Wireshark specificconfiguration files. For details about the configuration files Wireshark usesfor name resolution and alike, see Appendix B, Files and Folders.
Most applications use synchronously DNS name resolution.For example, your web browser must resolve the host name portion of a URL before it can connect to the server.Capture file analysis is different.A given file might have hundreds, thousands, or millions of IP addresses so for usability and performance reasons Wireshark uses asynchronous resolution.Both mechanisms convert IP addresses to human readable (domain) names and typically use different sources such as the system hosts file (/etc/hosts) and any configured DNS servers.
As shown above, this window contains a chart drawing area along with a customizable list of graphs.Graphs are saved in your current profile.They are divided into time intervals, which can be set as described below.Hovering over the graph shows the last packet in each interval except as noted below.Clicking on the graph takes you to the associated packet in the packet list.Individual graphs can be configured using the following options:
RTP Player must store decoded data somewhere to be able to play it. When data are decoded, there are audio samples and dictionary for fast navigation. Both types of data are stored in memory for default, but you can configure Wireshark to store it on disk. There are two settings:
When any data are configured to be stored on disk, one file is created for each stream. Therefore, there might be up to two files for one RTP stream (audio samples and dictionary). If your OS or user has OS enforced limit for count of opened files (most of Unix/Linux systems), you can see fewer streams that was added to playlist. Warnings are printed on console in this case and you will see fewer streams in the playlist than you send to it from other tools.
Make sure that you have at least one pane configured to contain the Packet list.Three panes can be active at the same time and they can be layed out as shown in the top layer.The exact sizes of these panes can be changed as needed once a capture file is opened.
Selecting Show column definition in column context menu make the column context menu wider to show the currently configured field type for the column.This may help identify the column to select or modify.
Selecting Capture packets in promiscuous mode causes the network interface(s) to capture on to be configured in promiscuous mode.This allows all (Ethernet) frames to be received by the network interface to be capture, not only those that are addressed to the capture interface.
The preference Interval between updates (ms) allows you to configure how often the packet list is updated during the packet capture process.A higher interval reduces processing, but causes more delay between capture and display in the packet list.
These preferences allow you to configure which numeric identifiers in protocols are translated into human readable text.For some of these identifiers the readable texts are read from configurable external sources.
As long as you can somehow extract the PMK from either the client or the RadiusServer and configure the key (as PSK) all supported Wireshark versions will decodethe traffic just fine up to the first EAPOL rekey.
EAPoL rekey is often enabled for WPA/WPA2 enterprise and will change the usedencryption key similar to the procedure for the initial connect, but it can alsobe configured and used for pre-shared (personal) mode.
The TKs are the actual transient keys used to encrypt packets, which are derivedduring the handshake. If known, they can decrypt packets without having thehandshake packets in a capture. However, having TKs as encryption keys in thetable will affect IEEE 802.11 dissector performance as each encryptedpacket will be tested against every TK until decryption is successful.If the table is configured with many TKs, none of which match anyencrypted frame in the capture, performance can be slow.
Once a match is found, an association is formed similar to in the usualmethod and decryption of other frames with the same key should be onpar with normal decryption flow. Thus, if most frames in the capturematch TKs (or other keys), and only a limited number of TKs are configured,the performance impact is slight.
Thebinary wire formatof Protocol Buffers (Protobuf) messages are not self-described protocol. Forexample, the varint wire type in protobuf packet may be converted to int32, int64,uint32, uint64, sint32, sint64, bool or enum field types ofprotocol buffers language.Wireshark should be configured with Protocol Buffers language files (*.proto) toenable proper dissection of protobuf data (which may be payload ofgRPC) based on the message, enum and field definitions.
MATE is a Wireshark plugin that allows the user to specify how differentframes are related to each other. To do so, MATE extracts data from the frames'tree and then, using that information, tries to group the frames based on howMATE is configured. Once the PDUs are related, MATE will create a "protocol"tree with fields the user can filter with. The fields will be almost the samefor all the related frames, so one can filter a complete session spanningseveral frames containing more protocols based on an attribute appearing insome related frame. Other than that MATE allows to filter frames based onresponse times, number of PDUs in a group and a lot more.
MATE creates a filterable tree based on information contained in frames thatshare some relationship with information obtained from other frames. The waythese relationships are made is described in a configuration file. Theconfiguration file tells MATE what makes a PDU and how to relate it to otherPDUs.
Every time a Gop is assigned a new PDU, MATE will check if it matches theconditions to make it belong to a "Group of Groups" (Gog). Naturally theconditions that make a Gop belong to a Gog are taken from the configurationfile as well.
Information in MATE is contained in Attribute/Value Pairs (AVPs). AVPs are madeof two strings: the name and the value. AVPs are used in the configuration andthere they have an operator as well. There are various ways AVPs can be matchedagainst each other using those operators.
Information used by MATE to relate different frames is contained in Attribute/Value Pairs (AVPs). AVPs are made of two strings - the name and the value. WhenAVPs are used in the configuration, an operator is defined as well. There arevarious ways AVPs can be matched against each other using those operators.
The Match declarations instruct MATE what and how to match against the dataAVPL and how to modify the data AVPL if the match succeeds. They will beexecuted in the order they appear in the config file whenever they are invoked.
35fe9a5643