Date: Wed, 8 Aug 2001 16:31:39 +0100 From: Paul Robinson <paul@akita.co.uk> To: alexus <ml@db.nexgen.com> Cc: "Forrest W. Christian" <forrestc@imach.com>, Marius Strom <marius@marius.org>, freebsd-isp@FreeBSD.ORG Subject: Re: (OT) Re: another ip as alias on NIC doesn't work properly Message-ID: <20010808163139.B29584@jake.akitanet.co.uk> In-Reply-To: <017901c1201b$3e178860$0d00a8c0@alexus>; from ml@db.nexgen.com on Wed, Aug 08, 2001 at 11:03:11AM -0400 References: <Pine.BSF.4.21.0108080025430.26258-100000@workhorse.iMach.com> <017901c1201b$3e178860$0d00a8c0@alexus>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 8, alexus <ml@db.nexgen.com> wrote:
> I disagree, I'm a little ISP and my users can't use 2nd ip for their irc,
> thats why i'm here asking this question and this is not a user related
> problem, this is definatly not. I already tryed 3 different clients so this
> is isn't software issue at least not irc client software
OK, I've been watching this thread from afar, and this is just on the very
tip of a flamewar because the people on this list have exhausted their ideas
and because you're frustrated at not being able to solve your problem. So,
let's recap a few points here:
- You have helpfully supplied a large amount of information regarding your
problem, and many of us have looked at it. Some people have offered
suggestions and work-arounds.
- You have tried the workarounds and much more besides but it's still not
working. You've tried different IRC client software and it still has the
same problem.
- You've tried different IRC servers (which is in the domain of something we
are likely to understand on this list), and it still doesn't work.
- You maintain that FreeBSD must be b0rked because none of the suggested
workaround work for you. This is a sensible suggestion, and perhaps with
your particular hardware might be indeed true.
- We maintain it's not, because we have very similar/identical
configurations all over the world, and we know IP aliases work fine on our
sites. We really can't think what is causing the hassles.
- We know about running ISPs, but we're not au fait with the internals of
the stack because we didn't write it, therefore, perhaps we're not the best
people to ask when it comes to stack internals (which is where I think the
problems may lie).
So, in other words, because this is not a problem discussing third-party or
FreeBSD software specifically from the point of view of an ISP server-side
environment, we're a little at a loss as to what to suggest when it comes to
what would appear to be a strange bug in the stack somewhere. However, I
suspect the guys on -net will be able to work it out far quicker, and if you
do find the solution, you might want to follow up to this thread and let us
know (for those of us who don't track -net).
So, let's not get into a huff about this - we're as frustrated that we don't
know the answer as you are. However, on our kit it works, and on your kit it
doesn't, so the stack hackers at -net will probably look forward to hearing
from you.
Apologies if I'm sending this "out of step" or stepping on people's toes,
but I agree that I think it's about time we looked to wrap this one up over
here on -isp, with the possible exception of alexus getting back to us to
let us know what the fix was.
--
Paul Robinson ,---------------------------------------
Technical Director @ Akita | A computer lets you make more mistakes
PO Box 604, Manchester, M60 3PR | than any other invention with the
T: +44 (0) 161 228 6388 (F:6389)| possible exceptions of handguns and
| Tequila - Mitch Ratcliffe
`-----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010808163139.B29584>