68
www.cooperbussmann.com/wirelessresources
Cooper Bussmann 245U-E Wireless Ethernet Modem & Device Server User Manual
Rev Version 2.19
Management IP
The management IP is the address of the module if only one VLAN group is
configured. Access to the module’s internal Web-based configuration and
IP-based functions (such as serial gateway, or Modbus server) is provided via this
management IP address and subnet mask.
NOTE If only one VLAN group is configured, it must have a management IP
and netmask. If further VLAN groups are configured (groups 2-9) they only
need a management IP and subnet if access to the modules IP-based
functions (such as Modbus or webpages) is required.
Management
Netmask
The IP network mask of the management IP (see above).
Bridge STP
Turns on Spanning Tree Protocol (STP) for the bridge. STP prevents network loops
that can cause broadcast storms.
Bridge Priority
The STP priority number for the bridge. This value should be set in context with other
devices that are connected on the same network.
Interface Membership
Each VLAN group has a configurable interface membership list. The membership list will allow up to 12 possible
interfaces to be added. The following configurable parameters will apply to each entry:
Interface
Select interface from the drop-down list to be used for the VLAN group. Available
interfaces are, Ethernet, Wireless or one of the 10 WDS Repeater connections
that correspond to configured entries on the Repeaters page.
Type
Specifies whether the interface is to support VLAN tagged or untagged frames.
When untagged is specified, all incoming frames on the interface must be
untagged, and all outgoing frames will be sent untagged. When tagged is
specified, all incoming frames must have a VLAN tag with VLAN ID matching the
configured VLAN ID for the VLAN group; all outgoing frames on this interface will
have a VLAN tag added with the configured VLAN ID and priority for that VLAN
group.
Example 1: Basic VLAN
A common use for VLAN functionality in a module is to tag data from a VLAN unaware device and send this to a
VLAN trunk. A simple example of this involves bridging between Ethernet and wireless ports for just one VLAN.
In Figure 69, the Ethernet interface is tagged and the wireless interface is untagged. Any data arriving at the
Ethernet port is expected to have VLAN tagged data with “VLAN ID 10,” and any data sent from the Ethernet port
will have the VLAN tag added. This example allows wireless data from VLAN-unaware devices to be bridged with
the Ethernet interface and have VLAN tags added (the Ethernet connection is now part of a VLAN trunk that will
send/receive data to/from other VLAN-aware devices).