802.11b network

Ionian · #1 (**permalink**) 11-09-2004, 03:49 PM

I am currently conducting a project with the aim to create a wireless network for networked appliances i.e. connecting everyday appliances such as tvs, kettles, fridges etc via a WLAN.

The work in my project basically consists of creating a c++ program that can control these devices. I wont actually be connecting to tvs and fridges, I will have another program that simulates this.

So far i have created the network and it all works, however it is not wireless it uses the internet to communicate. I have used the winsock function so far.

I am looking for information as to how to make a program communicate using 802.11b. I have read that winsock can still be used but I am not sure of the changes to make in order to this e.g. do I need to use particular port numbers, do I need to use specific send functions etc.

Skink · #2 (**permalink**) 11-10-2004, 05:04 AM

it is exactly the same as the internet or ethernet... get off windows...

Ionian · #3 (**permalink**) 11-11-2004, 01:20 PM

so does that mean i dont have to make any changes? If i do would you mind describing them? Im a newb and have little knowledge of network programming but the basics.

Skink · #4 (**permalink**) 11-12-2004, 05:04 AM

listen to me. it is EXACTLY the same....

Ionian · #5 (**permalink**) 11-12-2004, 01:24 PM

I beleive you that its exactly the same, but I just cant understand it. In that case doesnt it mean that it should already be communicating wirelessly?

Skink · #6 (**permalink**) 11-12-2004, 05:11 PM

huh? what?? the hardware is different... the protocols are not... if you direct something to an internet IP it will go over the internet... if you direct it to a loccal IP of the same machine it will go over the local network.. please... be more descriptive... it is VERY hard if i cant tell and am working in the dark

whetu · #7 (**permalink**) 11-12-2004, 10:32 PM

Quote:

I beleive you that its exactly the same, but I just cant understand it. In that case doesnt it mean that it should already be communicating wirelessly?

It's TCP/IP traffic... there's absolutely no great mystery to that. Traffic over the internet is generally TCP/IP, traffic over a LAN is generally TCP/IP... The only difference is that it's going over a radio link rather than a wired link. As far as any application you make is concerned, how it physically (or not) connects should be completely transparent (or in other words, irrelevant).

I'll put it another way.
http://www.webopedia.com/quick_ref/OSI_Layers.asp
Read that.

Worry about Layers 5-7, not Layers 1-3

It also sounds like you need to pick up a networking for noobs book as well. We cant spoonfeed you on this one, you'll have to learn how to help yourself. Learn basic to intermediate networking before you try to create network applications.

Ionian · #8 (**permalink**) 11-13-2004, 05:12 PM

My bad!!! Sorry for being so dumb. I understand what you mean now. The program will communicate on whatever its given. If I have a wired ethernet card it will work wired, if I have a wireless ethernet card it will work wirelessly. Ive been so preocupied with trying to get this project working I forgot the basics of networking. Thanks for showing me the light.

whetu · #9 (**permalink**) 11-14-2004, 07:18 AM

I make it sound easier than it is.. wait till you have to tie in wireless security

ok, sorry to rain on your parade. I'll stfu now.

Ionian · #10 (**permalink**) 11-14-2004, 05:24 PM

Do you know any sites with information on creating the security features?

Skink · #11 (**permalink**) 11-15-2004, 04:12 AM

the security is built into the cards... you do not even think about putting it into ur progs...