On 3/14/2012 11:04 AM, gene heskett wrote:
> The ipv6 address is what an ifconfig spits out for this machine.  Its there
> but I have no clue if it works.  The 'shop' box doesn't have ipv6 disabled,
> and it shows inet6 addr: fe80::3a60:77ff:fe4e:381b/64 Scope:Link in the
> ifconfig output.  A ping6 fe80::3a60:77ff:fe4e:381b doesn't work, acts like
> a syntax error, and of course there is no man page for ping6.  Figures...
> According to 'man ping' there are switches to make it use ipv6 stuff, but
> when you try them, its all unk host errors.  If they want this ipv6 crap
> to go live about 100 days from now, there is going to be a lot of gored
> oxen around with the "its all a big secret" manpages we have now.
Gene:

I truly sympathize because I've also been in situations where everything 
I did seemed to make things worse, but I think this is overreacting to 
IPv6.

My recent Linux/Windows installs have all added IPv6 interfaces as shown 
by ifconfig (renamed ipconfig in Windows, thanks to some MS-dweb) even 
though I'm not setting up IPv6 intentionally. I agree the documentation 
is sorry but when was that not the case with Unix/Linux? Let the 
LinuxCNC author without sin cast the first stone regarding documentation.

Still, my hosts all "just work." As a latest for instance: I just 
installed LinHES (MythTV on ArchLinux) on a host in the basement on the 
wired-LAN side of a wireless client bridge I created from a Linksys AP 
running DD-WRT. Running Ubuntu 11.10 inside VirtualBox on a Windows 7 
host on the wired-LAN side of a stock wireless AP upstairs, I was 
immediately able to ssh -Y into the LinHES box without my fingers 
leaving my hands. (Most of those details are irrelevant other than to 
show that mixing and matching a bunch of stuff using default settings 
has worked well enough for me.)

Speaking figuratively, I can't help but think that in the process of 
"fixing" (in the veterinarian sense) the IPv6 issues on your new host 
some wires have gotten crossed. My first car (it had fins!) didn't run 
too well either after I managed to cross several spark plug wires.

As soon as Comcast offers IPv6-service to me here in Gaithersburg I 
expect to test their connectivity. My grandmother liked to say "there's 
many a slip twixt the fork and the lip." I think most of the slips with 
IPv6 are going to take place twixt us end users and the world.

Have you tried running from a LiveCD/LiveUSBStick on whichever host 
isn't cooperating (coyote, is it?)  to see if at least the basic 
distribution works?

Truth in advertising: Sometimes I'm brilliantly correct. Sometimes I'm 
spectacularly incorrect. Mostly I just muddle through, but I always 
sound like I know what I'm talking about.

Regards,
Kent

PS - whenever I get an error message I slap it into my search engine du 
jour. Surprise---"X11 forwarding request failed on channel 0" gets a lot 
of play.


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to