[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: forcedeth?



On Saturday 25 May 2019 07:33:01 am Andy Smith wrote:

> On Sat, May 25, 2019 at 06:52:00AM -0400, Gene Heskett wrote:
> > the installer locked me to ipv6, and the nearest ipv6 connectivity
> > is probably in Pittsburgh PA, 140 some miles north of me. The
> > installer hasn't brains enough to try ipv4 when it can't find
> > anything working in ipv6.
>
> My recollection was that none of that was ever established in any of
> the threads you posted here, so that is a really weird thing to keep
> stating. Did IPv6 use all your toilet paper and kick your dog or
> something?
>
> Andy

You just pulled my trigger.

No Andy, it didn't drink my last beer (Murphy does that), or kill any 
kittens but it did totally disable ipv4. How? Simply by refusing to 
apply a route/gateway to the ipv4 settings we do manually. And depending 
on the phase of the moon, those of us on host file networks are forced 
to edit the /e/n/i/config files and immediately chattr +i them in order 
to protect them from N-M's incessant meddling, ditto for resolv.conf, 
which we have to make into a real file, and chattr +i it for the same 
reason.  For a while we could remove N-M on armhf-jessie but now its 
somehow linked to our choice of desktops so the only way is to rm it by 
hand, or chattr +i everything it touches. N-M at least has the common 
decency to not complain or go crazy when it finds itself locked out of 
its playpen. Unforch I can't say the same for hpfax, in the hplip 
package you get with cups.  Its crashed this machine 6 or 7 times by 
killing hid-common, leaving the only working button the reset button on 
the machines front panel. Somebody put a call to hpfax in the root 
crontab, and when it gets called with nothing to do it goes postal 
killing all input devices on the usb bus by killing hid-common.  A 
separate problem of course, one that hp needs to fix before buster goes 
live.

You folks with ipv6 all think we should all just switch and be done with 
it, but the nearest ipv6 connection to me is probably 140 miles north of 
here in Pittsburgh.  So we're stuck on ipv4. My router doesn't pass it, 
my isp supplied cable modem doesn't pass it and you folks should be 
aware, first and foremost, that ipv6 does NOT cover the planet yet. 10% 
of it maybe on a geographical basis.  The rest of us are stuck on ipv4 
and we are being punished because there's nothing we can do about it.

You all claim that N-M won't bother an interface defined as static. Thats 
an outright blatant lie, I've had it tear down working interfaces half a 
dozen times in the last month on two different stretch installs, one 
arm64 and one amd64 because I wasn't quick enough with the sudo chattr 
to lock a file I had just edited with the properly marked as static 
data. I took the time to ping yahoo.com, got a response and N-M tore it 
down before I could lock it.

Put a kill switch in that puppy. defaulted to off. And take a survey to 
see how many have turned it on a year from now. I'll be apologetic if 
its more than the 5% carrying their lappy to dunkin donuts.

/ipv6 rant.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>


Reply to: