security and peer-to-peer networking

[Munchkin]

OK, if you use an Access Point, you can use IP address filtering and stuff to keep your network secure, but what do you recommend to secure a peer-to-peer network?

To provide more information, I have a small wired network at home with an internet gateway running on W2k, the rest on XP. I want to add a USB wireless client from Avaya to the gatway, so I can use my laptop to browse the web from anywhere at home.

I have already read the two articles below for the ad-hoc setting, but could not understand enough to help me solve my problem.

How does the ad-hoc mode differ from the peer-to-peer mode?
How should I configure my WLAN devices?
Would you recommend a VPN software and if so, which one?


Thanks for your reply

[Jim Lin]

Ad-Hoc mode is Peer-to-Peer mode.
When two WLAN cards setting to Adhoc mode, they can transmit files to each other directly.
But please note that WLAN card can only choose either Adhoc mode or infrastructure mode. Both modes can't exist at the same time.

[Ted]

I have used Ad-hoc networking at home. My configuration is:

A Linksys cable router for Internet, with wired LAN to a stationary PC running WinXP. I have attached an USB WLAN adapter from LinkSys to it, and configured bridging between LAN and WLAN.

My laptop runs WinXP, and has an Orinoco card.

I have enabled WEP to get a minimum level of security.

Because the settings on WinXP, I have selected that it connects only to Ad-hoc networks. When I take my laptop out and want to use a "real" network, I have to switch the Windows settings to accept Infrastructure networks. No big deal, done in a few seconds.

I am reasonably happy with my quick-and-cheap WLAN solution, and feel it is good enough for time being. The security level of WEP alone is not enough for Corporate Standards, but I have a VPN client in my laptop, and thus can safely network with company systems, too.

[Jim Lin]

Hi Ted,

Glad to hear that you enjoy between ad-hoc mode & infrastructure mode.:)

But most comsumers are lazy and stupid.:D
If driver can help user to auto-detect conection situation and judge the optimized conection and switch to it automatically, that will be better.:p

[Ted]

To say that I "enjoy" the reconfiguration is to stretch it too far. But I can live with it, exactly the same way I can live with several other of WinXP "features."

The nuisance is partial automation, with a missing feature, in WinXP -- you can select either:

* Automatic, but if Infrastructure network is present, it is preferred, and Ad-hoc ignored.
* Infrastructure only
* Ad-hoc only

In my case I would like to have the fourth, missing, option:
* Automatic, but Ad-hoc is preferred.

Then I would need no manual reconfiguration while changing my location.

I wonder why Microsoft has omitted the last alternative.... But if I would make a complete list of other similar half-well-made features, I would run out of disk space on my 80GB data volume ;)

[fritzel67]

So if I understand correctly, I could purchase two 802.11b NIC's, and run them in ad-hoc mode without an access point or gateway?

This would accomplish my goal of getting on the Internet with my laptop downstairs by using the DHCP Internet connection sharing set up on my XP box.

Thanks for any help.

Tracy Miller
Network Tech

[Jim Lin]

Hi Tracy,

I'm afraid that the answer is negative if you want to share internet connection.

Hi Ted,

I hate partial automation too.
So isn't it better if some device's driver can provide full automation?
Besides, only XP provide partial automation. If I was in 98, me...?
So most comsumer still need powerful driver with full auto configuration. How so you think?

[Ted]

I have to disagree with Jim Lin, my setup works pretty well: I share the Internet connection without any pains in Ad-Hoc network. I have a cable router with NAT and DHCP, and my internal IP addresses are those typical "192.168.x.x" for a closed network.

I am using WinXP at my "central" computer, which has both high-speed Internet and an USB 802.11b adapter from Linksys. These two network interfaces may be bridged, and my Internet cable router serves DHCP for my lap-top through that bridge. (Btw. I use a fixed IP address on my main computer due to some remote accessible services in it)

To get some basic security I use WEP, it works nicely with Ad-hoc connection, too.

If the "central" machine with Internet+WLAN would have any older version of Windows, the setup is different, and likely more complex. But NT and Win2000 could have a router function - however, so far I know, it is a pain to set up. On Linux this kind of networking should be also pretty simple.

Tracy, you are a network tech, so I believe you should no trouble in setting up that WinXP bridge. However, if you do not have a router with NAT and DHCP server on your Internet connection, it will be much more complex. You need then more services in your "central" computer for routing and sharing that Intenet IP address (Router with NAT), and maybe also a DHCPd. Likely a mess to set up...

About automation: I think there are some client software for other Windows versions giving similar automation than XP. In my case I need the manual setup because my neighbor has a AP and WinXP--if allowed--will attach itself to that network instead my Ad-hoc one... In case of roaming between Access Points, Windows XP provides full automation, but for AP <-> Ad-Hoc it is not too good.

I would not recommend my manual switching method to any average home user. For me it is a moderate nuisance, but for somebody else it could be a real hassle. I have to agree with you, Jim Lin, that partial automation is not for an average home user.

[Jim Lin]

Hi Ted,

I'm glad you partially agree with me.:D
Up to 2005, 40% of WLAN market will be enterprise.
40% of WLAN market will be home user.
Home market is potential for WLAN market.
But there is no MIS people at home except you are the one.
User friendly without complex configuration is important here.
I think it need some help from software before operation system is completed in this application.