Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have a Cisco 1921 routing via NVI that is seemingly causing odd issues with rsync. The connection works for a little bit at the beginning, ACK starts lagging SEQ by a wide margin, and then there's some chaos. It seems that the remote host is receiv...
I have a Cisco 1921 router running 15.7(3)M2 that is consistently dropping certain packets but not others for reasons that are not clear. As an example, a DNS response for stltoday.com (from any server) gets completely dropped (no return packet on Wi...
I installed a Cisco 4402 WLC and a Cisco 4948E-E switch together, with a single tagged non-LAG copper link from the first slot on the WLC to a port on the switch. For some reason, they are not able to pass any traffic or to ping each other, even on t...
Hi, Georg. Upon further testing, I do not think that the remaining problem (just with rsync so far as I can tell) is an MTU issue after all. Could you take another look at my patched configuration in the new issue for other possible sources of errati...
Thanks, Georg! I applied a few changes at a time to see the critical point, if any. DNS packets started transiting properly after the second of these steps below, with the others included since they seem closely related. access-list 1 permit 192.168....
Hi, Deepak. Per my original message, the problem is that the router is not passing some DNS packets between the NAT outside and inside, so setting 8.8.8.8 as the first DNS server for internal DHCP clients would cause them to be unable to access some ...
I tested and investigated a bit more and finally figured out what was happening. The wireless controller has no concept of native VLAN on the trunk-designated link. It tags all traffic, expects all traffic to be tagged, and discards anything untagged...
I just realized that, at the other sites, we did not use the primary VLAN, so this (presumably a tag scheme mismatch) was probably happening but non-problematic. I'll experiment a bit more next week.
