[nycwireless] Fwd: All frequencies hailing!!! Berlin's c-base fighting for survival.
c-base needs your help and attention for its continued existence. to my knowledge, no other independent group in europe has done more for research and inspiration into the field of open wireless networking. from promotion of German designed and acclaimed meshcubes, to promoting research and experimentation with wardriving, wireless mapping, wireless meshing, OLSR, and more recently a possible successor B.A.T.M.A.N. weekly events including wireless antenna building workshops have been held there regularly for years. 3d artists, musicians, gaming freaks, wireless networkers, embedded hackers, caffeine freaks and more have all regularly used the c-base and the cross-disciplinary cooperation and cross-talk is unique to c- base. From the initial BerLon (Berlin/London) meeting that spawned the Picopeering agreement framework (that inspired the FNPA), to being critical in the formation of "freifunk.net" the on-going importance of incubating ideas that eminates from c-base cannot easily be overestimated. If you've ever visited c-base and experienced their extraordinary hospitality, please consider a symbol of gratitude in terms of a donation, as they really need it now. If you haven't, then please consider taking a little time to research the real impact that c-base has made on community wireless networking globally for many years, and consider a small token of thanks to help support their continued operations. thanks & shine, .vortex Begin forwarded message: From: Sven Wagner <[EMAIL PROTECTED]> Date: 3 July 2007 18:04:17 BDT To: Discuss list on the World Summit on Free Information Infrastructure <[EMAIL PROTECTED]> Subject: All frequencies hailing!!! hi wsfii "c-base space station", which is a vital part of Berlin's governmentally unfunded subculture, is under pressing threat of closure. Until July, 31th 2007 we have to come up with several months' worth of outstanding rent, otherwise we'll be evicted and the space station will have to close. If that happens an important and fertile ground for ideas and projects (e.g. berlin's free wavelan networks "freifunk.net" and the wikipedia regulars' table ), event location (e.g. exhibitions, concerts, open stage sessions) and space for open knowledge transfer and last but not least a home for creatives, utopians and space cadets will dissapear from berlin's cultural landscape. YOU can help to avoid this, by getting engaged and involved: drop by at our facilities in Rungestrasse and participate, become a member or just go online and hit the donation button on http://c-base.org thx cven ___ wsfii-discuss mailing list [EMAIL PROTECTED] http://lists.okfn.org/mailman/listinfo/wsfii-discuss -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] Kit followup: which setup?
[EMAIL PROTECTED] wrote: My question: for optimal reception, is it better to have a highpowered card with a basic antenna (senao) or a lower powered card with an excellent antenna (orinoco)? i assume you want to use kismet or variant to passively scan and map the local network ecosystem. most cards are rated for *transmission* power (because that's what's regulated by FCC/ETSI). the antenna will be your best ally rather than transmission strength. each anetenna sculpts it's own reception volume of space. for your usage, consider an omni-directional that creates a "donut" shaped reception zone, maybe specced at about 8-10dBi.. if you've got a team of participants, it will definitely be easier to calibrate and share results to map if everyone uses identical set-ups (same cards, length of pigtails, antennae - even car mount point for antenna). and cruising speed will affect results as well. also, scanning software does eactly that - jumps and scans all channels. when you're listening to one channel, you can't listen to all the rest. programs such as kismet allow for multiple wlan devices to cut down on missed activity. mind you, that's gonna hit your budget. if you do manage a setup with a laptop, usb hubs & 14 wlans, pigtails and antennae mounted in one car, i want the photos!!! :-) hope this helps! shine brightly, .vortex -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] Wireless over-crowding in your apt? Join our wireless over-crowding study.
what does your diagnostic kit consist of? On 13 Sep 2005, at 16:11, Dustin Goodwin wrote: NYCwireless is looking for NYC residents that think they are receiving interference from neighboring wireless access points. We are going to bring over diagnostic equipment. and see what the situation really is. We hear this complaint often enough that we want to get solid answers on what is happening in NYC. Please shoot me an email with the description of your problem and I will let you know if we are going to include your location in the effort. One way to "see" interference is to bring up the list of wireless networks your computer can detect. If your getting a list of 5 or more wireless networks then *maybe* your suffering interference. Although there is no way to know for sure until we test on-site. - Dustin - -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/ nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/ -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] Multimodal applications?
On Wed, 2004-09-08 at 17:42, Jon Baer wrote: > By Nancy Gohring > Special to Wi-Fi Networking News > Permanently archived item <http://wifinetnews.com/archives/004119.html> > > [1] As expected, the Wi-Fi Alliance is now certifying products to an > interim standard called Wi-Fi Multimedia, or WMM: The standard, which is > a precursor to 802.11e, is meant to improve audio, video, and voice > applications over Wi-Fi. A handful of products from vendors including > Atheros, Cisco, Broadcom, and Intel have already been certified for WMM. > The 802.11e standard will include quality of service mechanisms, which > will allow network administrators to give priority to traffic such as > voice that suffers from delays. given that most serious wifi operators already, within limitations, do this. This will affect who? shine ;-P .vortex -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] WiFi for real people
On Tue, 2004-09-07 at 05:06, Sameer Verma wrote: > Gabe Sawhney wrote: > > > (apologies for cross-posting) > > > > I'm writing an article for Spacing magazine (spacing.ca) about the > > real-life impact of WiFi availability; specifically, its (immediate, > > tangible) potential to transform the way people work. So many of us > > complain that our work requires us to be in front of a networked > > computer almost all day; WiFi seemed to promise some kind of > > liberation. I personally haven't yet been able to experience this > > benefit (but I'm still hopeful)... are there people out there who have? > > > > > > I'd like to hear about: > > * people who use public (ie. parks) or pseudo-public (ie. cafes) spaces > > as their primary work environments > > * the positive or negative impact of the presence of these "wireless > > workers" have on these spaces > > * people's reactions to the idea of working outside of an office: a bad > > idea? if not, why aren't you doing it? is it only appropriate for a > > very particular kind of worker? > > > > > > If you have any relevant thoughts/experiences/stories/references, I'd > > love to hear from you. While my interest in this subject extends beyond > > simply writing this article, my deadline requires that I get research & > > interviews done this week. Thanks! > > > > Gabe Sawhney > > > This might be of some interest... > While it does not show what people explicitly do with their Wi-Fi > networks, it goes to show what people may do without knowing. > > I *hope* this e-mail is going over my Wi-Fi connection :-) > Sameer Even if it didn't - I read it and replied over someone else's. With prior permission! shine, .vortex -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] [Another App Idea] Wireless Port
On Thu, 2004-08-19 at 02:50, AdamVazquez wrote: > Hi there. Two points re: port knocking. > > If you have a mobile AP or Wifi point of interest, it makes for a neat > way not to advertise until your resource is needed. Great if you have a > iPod and/or PC mp3 player and continually want to vary your collection > for example. It's not "neat", it's irrelevant. Authentication is Authentication. You either make certain resources available anonymously, or you don't. If you don't, then even "port knocking" is just a delivery mechanism (vector) for username/password, public key, whatever. And an unreliable one at that. Possession of an iPod and varied collection is also irrelevant. > 2nd is that aren,t you creating a hidden transmiiter problem if you have > a point of interest with low range and you start up in a environment > with one or more APs with greater RF footprints. OUCH if someone is > streaming Shoutcast or something like that. Again, irrelevant. Port knocking does not change your "RF footprint", nor can it in any way impact on 802.11 ad-hoc mode hidden node issues. Has anyone done the demographics? Perhaps the meme of port knocking is appealing to people who own or desire iPods purely on their image despite price and functionality of similar devices. And because their friends think they're cool. ;-P shine, .vortex -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] [Another App Idea] Wireless Port
On Thu, 2004-08-19 at 06:35, Yury G wrote: > Wireless Port Knocking for mobile access points. that's convenient. > This would be good way for wireless bicycle messengers to relativity > securely pass valuable packets and documents. No it would not. It's highly unreliable. With limited time while you're (perhaps only sometimes) in AP range on a bike, it would blow goats. shine, .vortex -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] Re: nycwireless Digest, Vol 18, Issue 5
Hi Kenneth, IANAL. Radio emanations and IP routing are not labelled with human intent. I believe there lies both the risks and freenet opportunities. On Thu, 2004-08-12 at 00:36, Kenneth Gutierrez wrote: [snip] > Since my neighbor could prevent me from using his > bandwidth with a simple push of a button, I'll assume > he doesn't mind and keep using it. In the meantime I > will shop around for an antenna in the hopes of > connecting to a legitimate community access point from > my home. Since the laws of your country have not yet prevented you from using his bandwidth/resources with a simple arrest and incarceration, you can assume that what you are doing is risk free. [snip] > As far as security goes, I get the feeling that there > are infinite levels of paranoia one can get swallowed > up in, so I might as well just try to trust people. And you might as well continue to just try to use people to your personal benefit without a modicum of effort on your part to communicate effectively over how to share a resource that costs. As long as it doesn't cost you. This seems to me to be a one-way reflection of trust. shine, .vortex PS [EMAIL PROTECTED] is a mailing list dedicated to active analysis of the socio-political and legal frameworks that affect open public networks (the network commons). This on-going research is vital in coming to terms with understanding what legal and social risks owners, operators and care-takers make when establishing and managing such a network. To subscribe: http://lists.free2air.org/mailman/listinfo/legal-issues -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
[Fwd: Re: [nycwireless] [Another App Idea] Wireless Port Knocking]
resent because this list currently bounces gpg email signing content types. -Forwarded Message- From: vortex <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [nycwireless] [Another App Idea] Wireless Port Knocking Date: Wed, 18 Aug 2004 09:30:54 +0100 hi jon, On Mon, 2004-08-16 at 08:29, Jon Baer wrote: > Im including a short readme from something Ive been tearing apart from > different projects and trying to glue together. Feedback always good :-) I've been watching at the sidelines over the recent port knocking groundswell, and I *really* have to admit - I don't get it. I want to, but I don't. Why do this? And doubly so for "hiding" wireless beacon frames. Even if the port knocking sequence is cryptographically strong, how will it help? And how will it help with wifi? Once one or more clients have associated, wifi frames are broadcast, and thus receivable by a third party. It seems to be an unnecessary (obscure) but interesting (obscure) facility (non-standard hack). Yes, I've read Krzywinski's protestations over obscurity, but they just don't cut the mustard. He fails to address exactly what risk port knocking mitigates. Wait a minute ... unless ... of course! ... send your second public key over the IP packet TOS bits while you knock ... ;-) shine, .vortex > -snip- > WKNOCK 0.1 alpha "Knock, knock" "Who's there?" > Wireless Port Knocking > + Proof of Concept > + Jon Baer ([EMAIL PROTECTED]) > > What is wknock? > > Wknock is a port knocking scheme for wireless networks. A daemon listens > for a sequence in monitor mode and when the right sequence is established > it will place itself into master mode and act as the AP. Once the > disassociation occurs or the session (DHCP) has timed out, the link is > closed and must be established with a new knock sequence. > > This is a proof of concept and is not intended to be used in a production > environment or even deployed. It is just an idea I had when reading about > portknocking for TCP/UDP sequences and thought it could be also used for > 802.11 management. > > It allows you to "hide" an AP which broadcasts no beacons or probe > responses until the correct packet sequence is heard by the AP. > > Usage: > > On the AP: > > wknockd -c wknockd.conf > > On the client STA: > > wknock -essid [essid] (or -bssid [mac]) (-f binary file) (-s hex sequence) > > This currently only works with HostAP drivers on Linux. > > For more info on port knocking in general see http://www.portknocking.org > > This primary testbed for this project was a Thinkpad T20 running RedHat 9 > with HostAP drivers and a WRT54G access point. > -snip- > -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] Confessions of a War Driver
ah, this old chestnut again. can anyone provide a direct link to any such us state legislature? it could be argued that any wireless network that offers open dhcp services (ie no filtering, crypto, or authentication - no *discrimination*) is, in effect, explicitly authorizing anonymous and random connectivity to that network. any network activity beyond that point may well be open to interpretation... but also remember that dhcp gives a default route, which could also be interpreted as giving authorization to transit beyond the local wireless subnet. to my knowledge the first such case to come before us courts was two years ago: http://www.theregister.co.uk/2002/07/26/ethical_hacker_faces_war_driving/ http://www.free2air.org/?op=displaystory;sid=2002/7/27/105013/369 the legal case against stephan puffer in houston, tx was dropped many months later. shine, .vortex On Thu, 2004-07-01 at 03:26, [EMAIL PROTECTED] wrote: > Jim Henry wrote: > > > I disagree with thew author of that article in that it is not a crime to > > just connect to an unsecured wireless network (in the U.S.A. anyway) if you > > do not use the connection in a malicious way. If I'm mistaken I'd sure like > > to see the specific section of the law being violated. > > Many States have Computer Crime Laws on the books that make it a crime to > connect to unsecured networks. > Play if you want to but you will end up a guest of the "Gray Bar" hotel. I'm > seeing more and more requests for RF Engineers to track these guys down using RF > finger printing. > > - > War driver pleads guilty in Lowes WiFi hacks > By Kevin Poulsen, SecurityFocus Jun 4 2004 1:04PM > > The remaining defendant, 23-year-old Paul Timmins, is scheduled for arraignment > on June 28th. In 2000, as a juvenile, Salcedo was one of the first to be > charged under Michigan's state computer crime law, for allegedly hacking a local > ISP. According to statements provided by Timmins and Botbyl following their > arrest, as recounted in an FBI affidavit filed in the case, the pair first > stumbled across an unsecured wireless network at the Southfield, Michigan Lowe's > last spring, while "driving around with laptop computers looking for wireless > Internet connections," i.e., wardriving. The two said they did nothing malicious > with the network at that time. > > http://www.securityfocus.com/news/8835 > > > -- > NYCwireless - http://www.nycwireless.net/ > Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ > Archives: http://lists.nycwireless.net/pipermail/nycwireless/ -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: Re[2]: [nycwireless] Need help - troubleshooting new public WAP @ Center for Architecture
exactly why your should 'map' your local area regularly. a bit like flossing your teeth in network terms ... ;-) shine, .vortex On Tue, 2003-12-02 at 13:40, John Howell wrote: > Thanks for the good advice, Glenn. I think that they are automatically > on separate channels - at least that's what NetStumbler would > indicate. I'll check and make sure, though. JOHN > > Tuesday, December 2, 2003, 8:27:20 AM, [EMAIL PROTECTED] wrote: > > > One thing I noticed in setting up a multiple node network for a friend is > > that any access points on the same channel will cause problems with each > > other. You may want to put the three nodes on seperate channels. > > > Glenn > > > -- > NYCwireless - http://www.nycwireless.net/ > Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ > Archives: http://lists.nycwireless.net/pipermail/nycwireless/ -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] Listing your wireless node on the NYCw map
hi dustin, i'm aware of evilbunny's efforts in nodedb, but i think you may have missed the main points of my post. for one, why impress on ppl the apparent importance of *not* mapping? shine, .v On Wed, 2003-11-26 at 14:37, Dustin wrote: > Vortex, > Nodedb is a web application that allows a node owner to advertise > their desire to share it with the public. NYCw has always tried to > advocate responsible sharing. There are many other groups working on > detection and mapping of wireless nodes. It's just not our main focus > although many of our members are actively involved in these activities > via other organizations. > > - Dustin - -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/
Re: [nycwireless] Listing your wireless node on the NYCw map
is this documented formal mycwireless policy? if so, why? why is it so *important* for a recommendation for ppl not to publish RF emanation data in public spaces? passive GIS detection of of 802.11* transmissions in public spaces is both of cwn and general public interest. publication of this can only help in the self-forming of further wireless network links, and planning and deployment of any and all new wireless networks (whether public or private) in the local RF environment. handballing to nodedb is, in part, avoiding or even exacerbating the issue. wait until someone enters AP details on nodedb claiming to be an open nycwireless node but does in fact point to someone else's private but unprotected AP. essid naming conventions are irrelevent here. actually, recommending the use of nodedb may well increase nycwireless liability risk because it may imply that nycw in some way is endorsing the accuracy and integrity of this db (IANAL). an email on a mailing list or a node listing on a web site declaring ownership of an AP and authorizing open usage of that resource is far more problematic than just passively mapping RF emanations of wireless AP's and impartially publishing the results. what level of identity, ownership and usage permission verification do you require for a 'node' to become a 'public access' or indeed formal 'nycwireless' node and why? and have you applied this policy to existing participants? i sincerely believe that this mapping concern is unwarranted, and the recommendation not to map and publish in order to mitigate any concerns is misguided. it's a messy wireless world we're in ... shine brightly, .vortex On Tue, 2003-11-25 at 14:09, dgoody wrote: > NYCwireless does not do wardriving or any other sort of access point > mapping to find nodes. If you want your free public wireless node to be > useful let your fellow New Yorkers know about it. Also if you know of a > coffee shop or other public place offering free access please ask the > owner to get listed. Feel free to forward this email as needed. > > *IMPORTANT* NYCwireless does *NOT* recommend you ever publish data about > another persons access point online without their permission. > > NYCwireless currently uses a project called nodedb run out of Australia. > It is a non-commercial projects that survives because of the hacker > ethic and donations (http://www.nodedb.com/donate.php). > > To list your node follows these some what none-intuitive steps: > 1. If your node in going to be in Manhattan or nearby follow this link > http://www.nodedb.com/unitedstates/ny/newyork/? > or if your node location cannot be seen in the map view above use this > link for nodes further out: > http://www.nodedb.com/unitedstates/nj/newjersey-newyorkarea/? > 2. Click "Register" fill in the information (please enter a valid & > working email addresss) which will lead you back to the New York Region > view when your done. You have to click "Click Here" to return to the NY > region view. > 3. Click "Login" enter your information which will lead you back to the > New York Region view. You have to click "Click Here" to return to the NY > region view. > 4. Now you can click "Create a new node entry" as it will appear as an > option on the region view after you complete registration and login. > > A few notes on creating your node entry. > * Short Name * > If you look at all the other short names in the NY region you can see > "Short Name" has adopted a life of it's own to help describe the > location of a node. This field was intended to list the SSID of the node > but it didn't work out that way. > > Some examples of current entries: > Manhattan: Park - Tompkins Square Park - NYCwireless > Queens: Forest Hills - Yellowstone & Austin > Manhattan: Cornelia Street - NYCwireless > Manhattan: 92nd Street btwn. Colombus and Amsterdam, 21st fl. - NYCwireless > > My recommendations is like so: > For NYC > borough : area : street > like Manhattan : Greenwich Village : Cornelia St > > for a park a little different > borough : parkname > Manhattan : Bryant Park > > For non-NYC > City, ST : Street > like Hoboken, NJ : 1st & Clinton > > I question the need to encode so much information in the short name > maybe we should just use it as the ssid as nodedb intended. > > * Node Status * > The data suggests confusion reigns when it comes to choosing the correct > entry for this field. If your AP is working and broadcasting the > www.nycwireless.net SSID please list it as "Fully Operational AP" not > because this is the best choice but because it is the most popular > choice based on the current list of nodes. > >
