[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dshield
Subject:    Re: [Dshield] Wireless networks and corporate Lans
From:       "Chuck Rothauser" <chuckr () keywestkeys ! com>
Date:       2004-02-29 21:25:18
Message-ID: 014301c3ff0a$88039d80$6701a8c0 () bobbie
[Download RAW message or body]

Greetings Don,

If the laptop has ip forward enbabled then the laptop will forward ip
packets in both directions.  This means that users on either network can
knock on the doors (ip socket numbers) of computers in either direction.
They would not have to hack into the laptop!  Having ip forward on also
means that multi-cast packets will be forwarded in either direction also.

Generally speaking a laptop should have only one network interface active at
any given time!

Regards,

-----> Chuck

"Tomorrow is a new day and you never know what the tide will bring"

http://www.keywestkeys.com

----- Original Message -----
From: "Don Peasley" <dPeasley@epix.net>
To: <list@dshield.org>
Sent: Friday, February 27, 2004 10:40 PM
Subject: [Dshield] Wireless networks and corporate Lans


> I have not yet used wireless myself, but am curious about the following
> situation:
>
> A laptop is connected to a corporate LAN via ethernet or a docking
> station.  The laptop also has a wireless card installed.  A public
> wireless access point is within range.  Will the laptop connect both
> interfaces?  What will be the default route?  Chances are the laptop
> will be running Win2K.
>
> What are the vulnerabilities?  Can the laptop be attacked from the
> wireless port and therefore access data on the corporate LAN?
>
> Or am I being too paranoid?
>
> Thanks in advance for any response,
> Don
>
>
>
>
>
> _______________________________________________
> list mailing list
> list@dshield.org
> To change your subscription options (or unsubscribe), see:
http://www.dshield.org/mailman/listinfo/list

_______________________________________________
list mailing list
list@dshield.org
To change your subscription options (or unsubscribe), see: http://www.dshield.org/mailman/listinfo/list
[prev in list] [next in list] [prev in thread] [next in thread]