Clifford Hammerschmidt [EMAIL PROTECTED] wrote:
It sounds like your ISP is filtering traffic which has a source port in
the masq port range (61000-65535).
Wouldn't that possible screw up a lot of things? (Other than MASQ)
No.
I imagine MASQ must do something to prevent "regular" user
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The application is called JNOS. Now here is what I have in the
simplest terms I can come up with.
Your explanation boils down to a picture like this:
+-+
| ISP |
+-+
|
| ppp0 (205.1.1.20)
++
I have that same problem, but I don't use mirc. I have a masq'ed linux
box that can't dcc chat or dcc send. I tried editing the ip_msaq_.c
module, but it wouldn't work. Any ideas how to get ircii and deritives to
dcc right?
Craig
On Wed, 3 Feb 1999, John E. Christ III wrote:
Also, I am
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Nigel
Metheringham
Remember that this list is international.
Assumptions of bandwidth and transport costs that are valid within the US
merely have the effect of making those of us in the rest of the
On Thu, 4 Feb 1999, Craig McDaniel wrote:
Date: Thu, 4 Feb 1999 04:02:24 -0600 (CST)
From: Craig McDaniel [EMAIL PROTECTED]
To: "John E. Christ III" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [masq] [masq] [masq] VDOPHONE
I have that same problem, but I don't use mirc. I
Clifford Hammerschmidt [EMAIL PROTECTED] wrote:
#define PORT_MASQ_BEGIN 61000
#define PORT_MASQ_END(PORT_MASQ_BEGIN+4096)
I though that since it was build into the kernel it also modified the
code for creating sockets so user sockets where from 1024-61000,
rather than
At 14:42 -0600 2/4/99, Fuzzy Fox wrote:
Clifford Hammerschmidt [EMAIL PROTECTED] wrote:
I though that since it was build into the kernel it also modified the
code for creating sockets so user sockets where from 1024-61000,
rather than 1024-64k. (In theory you should be able to place MASQ in
