350 client card insertion disables wired side of mult-homed host
I am running into an issue establishing a cross sub-net connection. I am hoping that some one has "been there, done that" Thanks for sharing any lessions learned.
My notebook hosts a PCM350 wireless nic and a Realtek RTL8139 wired nic. IPs are static non-routable (192.168.0.0). Each points to the other as its default gateway. The wire goes to a hub which supports several hosts. The 350 talks to a 350 WAP/Bridge hanging off a single host. All IPs are 192.168.0.0 (and unique) and netmask is 255.255.0.0
All components communicate properly in a standalone mode. When the 350 card is inserted communication thru the Reltek (e.g. ping -t) to a "host beyond" drops off (Request timed out). When the card is removed communication across the wire returns. The Realtek nic maintains a constant ping during insertion of the 350.
Why does insertion of the 350 prevent communication beyond the Realtek nic. Or more importantly how can communication be maintained across all components of the subnets?
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...
I have created a Powershell script to automatically add a Wireless Guest
User on Cisco WLCs. (tested on 2500 Series) The script should be
completely self explanatory. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...