| Re: network discovery & selection: problem definition | <– Date –> <– Thread –> |
|
From: Michael Richardson (mcr |
|
| Date: Sun, 30 Nov 2003 15:28:47 -0600 (CST) | |
-----BEGIN PGP SIGNED MESSAGE-----
mcr> However, GammaCoffee has found a way to make money without spending
mcr> much.
mcr> They set their ESSID to "delta", and respond to EAP.
Farid> Is this a legal thing to do? That is, having two overlapping
Farid> hotspots whose ESSID values are the same. It seems that this will
Farid> create other problems ...! But, let's go on with this assumption.
It is unlicensed space. Everything is legal, as long as you don't exceed
the transmit power.
Further, multiple APs on the same ESSID - well, that's how we arrange to
cover more space. This is a feature of 802.11.
At this point, Farid's choice of non-Usenet anti-quoting loses me
completely, so he'll have to ask his question again.
(see http://www.lemis.com/email/fixing-outlook.html)
Farid> Here you losing me! Are we still talking about authentication
Farid> packets here? Who is passing the packets to DeltaCoffee's AP?
GammaCoffee's AP takes the packets from the client machine, NATs them,
and then *retransmits* them to Delta.
Farid> How do supplicant's IP packets get sent to Delta hotspot? If it
Farid> double NATed, I assume that the packets are forwarded by some
Farid> Access Router within Gamma to Delta. That means that there has to
Farid> be some business agreement between Gamma and Delta, otherwise
Farid> Delta can simply drop the packets.
Delta thinks that Gamma is just another flat-rate customer.
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr [at] xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device
driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBP8pfs4qHRg3pndX9AQFP/gP/ef/adXhP5xl7nS2jMUCuhkLA0oXpjKRk
uXnAkZNgGNb+Kho0j86dftJbbnOeUfH77H7wcxvx4PYp/fNLfTqLDlLbbg5uxf3o
0QjTqmMgCl6AMxexJBCpLROgNOo+ubxA6ARIzaDrBu9Xna/Wz5xTXDTLzfUGj47U
Ag8uaHMDiWk=
=p8ZX
-----END PGP SIGNATURE-----
- Re: network discovery & selection: problem definition, (continued)
-
Re: network discovery & selection: problem definition Alper Yegin, December 10 2003
-
Re: network discovery & selection: problem definition Jari Arkko, December 10 2003
- Re: network discovery & selection: problem definition Alper Yegin, December 11 2003
-
Re: network discovery & selection: problem definition Jari Arkko, December 10 2003
-
RE: network discovery & selection: problem definition Adrangi, Farid, November 30 2003
- Re: network discovery & selection: problem definition Michael Richardson, November 30 2003
-
Re: network discovery & selection: problem definition Alper Yegin, December 10 2003
- Re: network discovery & selection: problem definition Bernard Aboba, November 30 2003
- RE: Re: network discovery & selection: problem definition Mark Grayson (mgrayson), December 1 2003
- RE: network discovery & selection: problem definition Adrangi, Farid, December 1 2003
- RE: Re: network discovery & selection: problem definition Adrangi, Farid, December 1 2003
Results generated by Tiger Technologies using MHonArc.