Comments for packetqueue.net

Comment on Windows 7 and IPv6 by Merrill

Merrill — Tue, 01 May 2012 02:43:08 +0000

I also ran into the voice vlan issue with my IPv6 deployment. I opened up a TAC case, but pretty much got shuffled off into being ignored. I felt like the person I was working with didn't understand my issue. His solution was to disable the voice vlan assignment on the ports. Since IPv6 on my VoIP side wasn't a big deal at the time, I did the same thing you did, block the RA on the VoIP SVI.

I found the matter mentioned in Cisco's book IPv6 for Enterprise Networks:

(Pg 121)
VLAN considerations for IPv6 are the same as for IPv4. When dual-stack configurations
are used, both IPv4 and IPv6 traverse the same VLAN. When tunneling is used, IPv4 and
the tunneled IPv6 (protocol 41) traffic traverse the VLAN.
IPv6 on data VLANs that are trunked along with voice VLANs (behind IP phones) is fully
supported. Depending on the configuration of the data and voice VLANs, you might
experience an issue where the Layer 2 multicast router advertisements from the Layer 3
data VLAN interface might bleed over to the attached host (connected to the IP phone or
a voice VLAN–enabled switch port). Basically, a PC connected to an IP phone can
receive RAs for both the data and voice VLANs. This is an issue that can be manifest
regardless of vendor and switch/phone version. Stay tuned for updated best practices on
how to properly deal with this on the Layer 3 VLAN configurations or through a possible
setting in the Cisco IP Phones that prevents flooding of IPv6 router advertisements
on the data VLAN.

I still haven't found the best practice to work around this issue. It seems the mighty vlan wall isn't so impervious.

Comment on Why Bonjour Hates my Wireless Network by Giuliano

Giuliano — Mon, 23 Apr 2012 15:05:08 +0000

I mostly got a similar setup working but am facing an issue where Service Discovery randomly breaks. Client is wireless and server is wired, on the same VLAN. I'm using "dns-sd -B _raop._tcp" (or "_airplay._tcp") to check what Mac OS is currently seeing. Stuff disappears then gets found again. Was just curious to know if that's the "hiccups" you mention?
It looks like every now and then multicast packets are dropped in our network. Next thing I'm gonna do is try and prioritize them.

cheers,
–
Giuliano

Comment on Why Bonjour Hates my Wireless Network by _SomeClown

_SomeClown — Sun, 18 Mar 2012 02:49:18 +0000

For another follow-up, I've moved my Apple TV back to one of my wired networks. Even with N running on two 1142 APs and a controller, I was still having some hiccups. The connection between the Apple TV and the host with iTunes (MBP) kept breaking. I believe this has more to do with either the Apple TV or MBP, than with anything in the backend networking at this point.

All of my other Bonjour-goodness (wireless printing, file sharing, iPad streaming) is still working great across the wireless network. As I said above, my setup doesn't exactly mirror what I started this post with, but Joe's post above is correct for that equipment–it will work.

Comment on iTunes Home Sharing by Digital signage using the Apple TV « Der Flounder

Digital signage using the Apple TV « Der Flounder — Sun, 11 Mar 2012 02:55:30 +0000

[...] Your Apple TVs and central iTunes server need to be on the same subnet – For reasons that are well-explained here, iTunes Home Sharing will only work on one subnet: the one that the central iTunes server is on. [...]

Comment on Musings on Storage by _SomeClown

_SomeClown — Sat, 10 Mar 2012 20:07:32 +0000

It is the default in 2008 R2 at the very least. As I said, however, the defrag task is *turned off* by default. In other words, it doesn't run by default. It is there are ready for you, though. The main thing I've found is that server admins reflexively *enable* these types of things, especially defragmentation, after years of having the benefits drilled into them by Microsoft. Operating virtually and on SANs requires a shift in thinking.

Comment on Musings on Storage by anon

anon — Sat, 10 Mar 2012 19:54:54 +0000

Not convinced this is the default.

Comment on Why Bonjour Hates my Wireless Network by _SomeClown

_SomeClown — Mon, 26 Dec 2011 18:59:52 +0000

Scott–I can confirm that it does work for me now, though my configuration has changed slightly since I wrote the post. I\’m using a 3945 with the 1142 APs connected to a PoE switch module in the router. After I read Joe\’s comments, then went back and looked at my archived configuration, I couldn\’t find any significant differences so I decided to rebuild everything from scratch. And it now works. Not sure what I missed the first time around, but it\’s easy to overlook things and I obviously did. I can try to post the relevant configuration items from my config if you have questions, but the bottom line is that it does work for me now.

Comment on Why Bonjour Hates my Wireless Network by Scott

Scott — Sat, 24 Dec 2011 10:16:25 +0000

Any word on this? I tried the settings that Joe said worked for him but no luck on my end. Can someone confirm that this does indeed work? Cheers

Comment on Screen and Reverse Telnet with Macbook Pro by _SomeClown

_SomeClown — Wed, 07 Sep 2011 16:31:34 +0000

Good point! I tend not to bother when it's my lab gear, but for production I'd definitely go that route.

Comment on Screen and Reverse Telnet with Macbook Pro by Jon Still

Jon Still — Wed, 07 Sep 2011 08:57:23 +0000

You can also access the terminal server via ssh (if you have transport input ssh on the async lines):

# ssh -l jon:18 10.1.1.1
Password:

Router>

The 18 after the : in the username is obviously the line number you want to reverse SSH to.