>> It maybe interesting to know that aol installs a special ``adapter''
>> that is purported to behave similarly to an hardware nic. In fact, on
>> win9x, at least, it is next to the nic in network neighborhood
>> properties and is near identically configured.
>from Charles Steinkuehler
>
>As me
> I'm not that familiar with the MS networking stack, and how
> windows systems handle routing, forwarding, etc.
With the Win9x/ME family, the stack is all proxy...ISC or some other
proxy.
> As mentioned elsewhere, apparently the AOL traffic is creating a
> tunnel through your firewall for it'
> It maybe interesting to know that aol installs a special ``adapter''
> that is purported to behave similarly to an hardware nic. In fact, on
> win9x, at least, it is next to the nic in network neighborhood
> properties and is near identically configured.
As mentioned in other replies, and stre
Mike Noyes wrote:
>
> At 2002-03-09 14:01 -0600, Michael D. Schleif wrote:
> >Also, since I do not know everything there is to know about networks
> >and quantifying everything quantifiable about same, regarding your
> >sniffer questions, can you describe a simple, open source process to
> >acco
At 2002-03-09 14:01 -0600, Michael D. Schleif wrote:
>Also, since I do not know everything there is to know about networks
>and quantifying everything quantifiable about same, regarding your
>sniffer questions, can you describe a simple, open source process to
>accomplish these tasks?
Michael,
Th
guitarlynn wrote:
>
> I don't know if this will approach the problem being asked to
> help much, but I did reverse engineer the AOL software
> many years ago to connect with Linux.
>
> You can only connect to AOL via a special proxy adapter
> that is integrated with their software. The martian
I don't know if this will approach the problem being asked to
help much, but I did reverse engineer the AOL software
many years ago to connect with Linux.
You can only connect to AOL via a special proxy adapter
that is integrated with their software. The martian errors are
due to the built in
A selective reply ...
At 02:01 PM 3/9/02 -0600, Michael D. Schleif wrote:
[...]
>> The difference is that holes caused by dialout workstations are old news,
>> and there is really no way to address this problem at the firewall (except
>> by blocking traffic routed through it with the martians rul
Ray Olszewski wrote:
>
> This would probably be a good topic to explore further, either here or on
> the -devel list, and that is why I am bothering to reply at all. It is (or
> may be) a concrete, and potentially widespread, instance of a general
> problem with firewalling ... what is the differ
Thank you.
Although, I can be pretty daft on occasion, I am trying to ``do the
right thing.'' It is not always easy knowing what that maybe in a
variety of contexts.
For me, from my humble experience, when I do not know something, it
works best to try to summarize what it is that I know, espec
Michael -- It is unlikely that there is a lot of AOL expertise here on this
list (others, please correct me if I am wrong), so the most valuable
information to provide here would be a better description of what "users
logging into AOL over our high speed internet connections" means ...
particularl
Jeff Newmiller wrote:
>
> On Fri, 8 Mar 2002, Michael D. Schleif wrote:
>
> > Jeff Newmiller wrote:
> > >
> > > On Fri, 8 Mar 2002, Michael D. Schleif wrote:
> > >
> > > > We are seeing martians on internal networks on a regular basis.
> > > >
> > > > Usually, it is traceable to users logging i
I am sorry for offending everyone. I will proffer no excuses. I was in
one of my bullheaded moods and acted inappropriately. Again, I am
sorry.
Is it possible to ask a generic question?
In general, is it possible to answer my original questions? Since I
don't see this as a setup question --
Michael D. Schleif wrote:
> Jeff Newmiller wrote:
Jeff I'm sorry you ended up with that reply. Please don't
take it home with you, so to speak. We highly value your
contributions to LEAF, and we appreciate your willingness
to help Michael.
>>On Fri, 8 Mar 2002, Michael D. Schleif wrote:
>>
On Fri, 8 Mar 2002, Michael D. Schleif wrote:
>
> Jeff Newmiller wrote:
> >
> > On Fri, 8 Mar 2002, Michael D. Schleif wrote:
> >
> > > We are seeing martians on internal networks on a regular basis.
> > >
> > > Usually, it is traceable to users logging into AOL over our high speed
> > > inter
Jeff Newmiller wrote:
>
> On Fri, 8 Mar 2002, Michael D. Schleif wrote:
>
> > We are seeing martians on internal networks on a regular basis.
> >
> > Usually, it is traceable to users logging into AOL over our high speed
> > internet connections:
> >
> > 172.128.0.0 - 172.191.255.255
> >
On Fri, 8 Mar 2002, Michael D. Schleif wrote:
>
> We are seeing martians on internal networks on a regular basis.
>
> Usually, it is traceable to users logging into AOL over our high speed
> internet connections:
>
> 172.128.0.0 - 172.191.255.255
>
> Today, we saw one from United Airlin
We are seeing martians on internal networks on a regular basis.
Usually, it is traceable to users logging into AOL over our high speed
internet connections:
172.128.0.0 - 172.191.255.255
Today, we saw one from United Airlines:
205.174.16.0 - 205.174.23.255
[1] How does this h
18 matches
Mail list logo
