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

WORKED AROUND (Re: unable to disable IPv6 for some reason)



<quote who="nate">
> this is drivin me up the wall.
>
> I just replaced 2 NICs in this system and recompiled the
> kernel to support the new ones, and now when I try to run
> bitchx I get the message 'Address family not supported by
> protocol' when trying to connect to a server.

after almost 3 hours of work i finally worked around this
and my other problem. this problem was solved by recompiling
BitchX with --disable-ipv6. it no longer givs me errors(yay)
my other problem with the eggdrop was due to my god damned
cisco 2503 router. it's NAT tables must've been screwed
up since i switched NICs on it a few times. once i rebooted
the router things worked immediately. i tried removing
and reinstalling the original bitchx to see if the router
switchover may of fixed it(i didn't think it would but
wanted to try anyways) and it didn't. so i reinstalled
my self-compiled bitchx again and its working again

FINALLY. i can't remember having so much frustration over
something since i stopped using MS win. glad it wasn't
linux's fault, but cisco's.

i mean i was getting weird shit like the router could
not ping the machine but another machine on the same
subnet could ping it. i fooled with all kinds of
settings and got it so at some points some ips would
ping, others would not, then a few minutes later
the ones that did ping could not anymore, and the ones
that did not, could. talk about going nowhere fast!
if i set the main ip to one of my alternates it would
ping sometimes, sometimes i could get the static nat
to map correctly so i could ping the box from the outside
other times it would not(always seemed to happen only
on the ethernet aliases, never on the primary IP).
once i reloaded the router everything worked within
seconds.


nate





Reply to: