User guide
Release9.5ReleaseNotes
Issue2,October2009 Page36
Ref #
Description Explanation
10053 Translation
Bridge Table
Access via
SNMP
When Translation Bridge is enabled, every SM maintains a translation
bridge table. The entries of this table are now also accessible via SNMP
(Read only access). The entries in this table are dynamically
added/deleted based upon the devices are under the SM. The max
number of entries for this table is 128.
Translation Bridge Table OIDs
10094 DNS Proxy/Relay
for NAT SMs
In 9.5, a NAT SM will now act as the DNS Server to all devices underneath
of it. When the SM gives out a DHCP lease, it will specify itself as the DNS
server. This fixes problems where the DNS servers change or the radio
WAN interface is specified to automatically get DNS information via DHCP
or PPPoE. In these cases, when the DNS servers change, or when a radio
first get a lease, any devices below the NAT SM that already have
retrieved a lease would not know about the new DNS servers. They would
have to be rebooted or their leases would have to be manually renewed.
Now, with the SM acting as the DNS server, devices underneath will
always point to the SM for DNS queries. The SM will then forward the
packet onto the proper DNS server based on the radios current DNS
settings and will forward the response to the customer device. This is all
done with the existing NAT implementation. When the radio sees a DNS
query, it simply swaps out the destination IP with one of the DNS servers,
then sends the packet through the NAPT for translation and forwarding.
Once the response comes back, it’s translated back through the NAPT,
then the source IP is swapped out with the radio IP so that the customer
equipment thinks that it came from the radio. There are no new OID or
GUI changes.
Please see Section 4: Known Open Issues - SM - DNS below a NATed
SM (R9.5)