On Mon, 22 Mar 2004, Chris Pepper wrote:
[...]
This is causing me some aggravation, as localhost connections
(such as apachectl fullstatus) are from [client ::1] instead of
the old-fashioned 127.0.0.1. To my surprise,
At 11:53 AM -0500 2004/03/22, Teodor Iliescu wrote:
On Mon, 22 Mar 2004, Chris Pepper wrote:
[...]
This is causing me some aggravation, as localhost connections
(such as apachectl fullstatus) are from [client ::1] instead of
the old-fashioned 127.0.0.1. To my surprise,
On Mon, 22 Mar 2004, Chris Pepper wrote:
At 11:53 AM -0500 2004/03/22, Teodor Iliescu wrote:
On Mon, 22 Mar 2004, Chris Pepper wrote:
[...]
This is causing me some aggravation, as localhost connections
(such as apachectl fullstatus) are from [client ::1] instead of
the
* Matthew Emmerton [EMAIL PROTECTED] [2004-03-22 10:54]:
On Mon, 22 Mar 2004, Chris Pepper wrote:
At 11:53 AM -0500 2004/03/22, Teodor Iliescu wrote:
On Mon, 22 Mar 2004, Chris Pepper wrote:
[...]
This is causing me some aggravation, as localhost connections
(such as
At 11:20 AM -0800 2004/03/22, Joshua Lokken wrote:
* Matthew Emmerton [EMAIL PROTECTED] [2004-03-22 10:54]:
On Mon, 22 Mar 2004, Chris Pepper wrote:
At 11:53 AM -0500 2004/03/22, Teodor Iliescu wrote:
On Mon, 22 Mar 2004, Chris Pepper wrote:
[...]
This is causing me some
Chris Pepper writes:
Well, I really do want to disable the IPv6 interface
entirely, so it doesn't show up in ifconfig,
... and that's not gonna happen unless you rip IPv6 out of the
kernel.
The next best thing I can think of would be to install ipfw6
and put in a rule
I have two systems, named www guest. Both are tracking
FreeBSD 4.9-STABLE, but guest is a bit more current. Neither has IPv6
explicitly enabled, but for some reason, guest insists on configuring
an inet6 interface at boot time (ifconfig xl0 shows an additional
inet6 address line, not present
