Brilliant xkcd recently, number 1337: Hack - xkcd.
Hackers (1995) - imdb movie database
: Look at the linked results and find out "your" is not the correct term in the title of the article. The author of the original code reads about 10-12 smart meters clearly from neighbouring houses.
I expect three things out of this:
- "Read your own meter" software which doesn't work until you put in the ID of your meter (and silently ignores all other signals)
- "Compare my usage to the neighbours" software which doesn't ignore but uses those measurements to compare usage.
- "Which house is probably empty" software, using a gps to triangulate meters.
Found via http://www.kb6nu.com/from-my-twitter-feed-clear-top-boxes-sdr-hsmm/
Misschien komt er ooit een upgrade naar glasvezel of VDSL, en dan is het heel prettig om te lezen dat andere mensen al de details hebben uitgezocht, bijvoorbeeld voor de combinatie van een Draytek Vigor 130 VDSL2-modem en een MikroTik 2011UiAS-2HnD router achter een XS4ALL VDSL aansluiting wat Harold Schoemaker keurig heeft beschreven. De volledige lijst VLAN tags:
- vlan 4: IPTV, untagged aanbieden aan de settopbox
- vlan 5: VoIP bij KPN (XS4ALL biedt dit aan als onderdeel van de IP dienst)
- vlan 6: IP (IPv4/IPv6) via een PPPoE sessie
Vandaag is het precies 34 jaar geleden dat 27 MHz communicatie in Nederland werd geintroduceerd, 27 MC artikel op de nederlandse wikipedia. Ik luister wel eens met een scanner naar 27 MHz verkeer, erg vermakelijk.
: Hmm.. for me the answer is "IRC", github is way too new ;)
Sharing my earlier experiences with the hidden telnet interface on the Netgear GS716T switch was appreciated by someone else with a Netgear GS110p switch: "Hidden" CLI interface on Netgear GS110TP. So I guess this is a feature on multiple netgear switches. And that article made me look at the firmware version, finding in the release notes for the newer version:New Features:I like that feature a lot! And indeed, after upgrade and setting the IPv6 management address:
* Add IPv6 management, IPv6 ACL, and IPv6 DiffServ support.$ telnet .... 60000 Trying ..:1234... Connected to ..:1234 Escape character is '^]'. (Broadcom FASTPATH Switching) Applying Interface configuration, please wait ...admin Password:******** (Broadcom FASTPATH Switching) >enable Password: (Broadcom FASTPATH Switching) #show ver Switch: 1 System Description............................. GS716Tv2 Machine Type................................... GS716Tv2 Machine Model.................................. GS716T smartSwitch Serial Number.................................. [..] FRU Number..................................... Part Number.................................... BCM53313 Maintenance Level.............................. A Manufacturer................................... 0xbc00 Burned In MAC Address.......................... [..] Software Version............................... 188.8.131.52 Operating System............................... ecos-2.0 Network Processing Device...................... BCM53313_B0 --More-- or (q)uit Additional Packages............................ FASTPATH QOS FASTPATH IPv6 ManagementKudos to netgear for making this switch IPv6 enabled! Update 2014-03-02 And.. back to the previous firmware. Plugging in a cable on a port that was long idle wasn't detected at all. That's not what I have a switch for at home, it should detect it when I plug in a device at the living room table. Disabling the 'green' option (power-saving when idle) on the switch did not change this behaviour. Now running:Software Version............................... 184.108.40.206 Operating System............................... ecos-2.0One upside: I can have two firmware versions in the switch and make one or the other active. So I switched back to the previous one easily: set the other as active and initiate a reset. There are other 5.4 firmwares available from netgear but 220.127.116.11 is the first version with IPv6 management.
: Log of a cubesat launch from ISS, interesting for this community. Spotted by .
: One of our cats enjoying the warmth of the dishwasher.
I noticed in the logs of the weather station computer ritchie:[770336.506717] cfg80211: Calling CRDA to update world regulatory domain [770336.906545] cfg80211: World regulatory domain updated: [770336.906567] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [770336.906585] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [770336.906602] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [770336.906619] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [770336.906635] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [770336.906652] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)But I'm in a specific country (the Netherlands) although the access-point is old enough to not transmit the regulatory domain information. I found out I can update the default in the client using:root@ritchie:~# iw reg get country 00: DFS-UNSET (2402 - 2472 @ 40), (3, 20) (2457 - 2482 @ 40), (3, 20), NO-IR (2474 - 2494 @ 20), (3, 20), NO-OFDM, NO-IR (5170 - 5250 @ 40), (3, 20), NO-IR (5735 - 5835 @ 40), (3, 20), NO-IR root@ritchie:~# iw reg set NL root@ritchie:~# iw reg get country NL: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5330 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5490 - 5710 @ 40), (N/A, 27), DFS (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOORThis changes maximum power, bandwidth and frequency ranges. And indeed in dmesg:[770977.623611] cfg80211: Calling CRDA for country: NL [770977.715887] cfg80211: Regulatory domain changed to country: NL [770977.715909] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [770977.715926] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [770977.715941] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [770977.715957] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [770977.715972] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [770977.715988] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)Now I wonder about the flags... NO-IR = no initiating radiation the device may not transmit on a frequency until it has received beacons on the frequency. DFS = Dynamic Frequency Selection which is mainly avoiding collision on the 5 GHz wireless band with weather radars. More information about this subject at Regulatory - Linux Wireless.
: I really like the size difference between the dumb terminal and the host computer. And the RaspberryPi is probably a lot more powerful than what a dinosaur pen was filled with in the days an ADM3A was the standard.
I almost started to digres in my last post getting an APRS report out using an android device, aprsdroid and a wouxun radio about the privacy implications but decided to separate that issue. It works, and I am not going to invest in it. APRS is nice, but for me it has privacy implications: it reports my position in real-time which is more than I want to share with the world, even as an amateur radio experiment. I know there are people who will post their bicycling tours or runs on-line as they happen but I don't like publishing my wereabouts, especially not in (near) real-time. Enough people can browse the mobile telecom location registers as it is. So I think I'll leave the APRS location experiments at this and I'll go look at other amateur radio stuff. There is enough to play with! I know APRS is bigger than just reporting location. Getting my weatherstation in Utrecht Overvecht to report weather to the APRS citizen weather observer program is on my wishlist.
Again playing a bit with APRS and aprsdroid. No luck with using a 3.5mm to 3.5mm audio cable, the vox on the wouxun KG-UVD1P does not trigger at all. I did test with the audio from aprsdroid near the microphone of my laptop and decoding it with multimon, and that works:AFSK1200: fm PD4KH-7 to APDR12-0 via WIDE1-1 UI^ pid=F0 =5206. N/00507. E$/A=000162 http://pd4kh.idefix.net/The 'audio through the air' method works with the radio right next to the internal speaker of the android device: with some fiddling of audio settings on the android device and vox settings on the wouxun I can send out a position report and it shows up on the aprs network! Wouxon vox level at 5, audio output type "music", audio level medium. The pink square is because I don't give out a very precise location on purpose.
After getting the gps running in the shed I noticed a bit of variation in the output location as logged from the NMEA $GPGGA strings in the clockstats file. And reading Tom van Baak testing the MG1613S GPS Receiver noting the variation in location made me decide to do a bit of plotting of location on my own. As Tom notes, plotting distance in meters gives a better idea of scale. So I wrote a bit of perl to massage the lat/long pairs into X/Y meters from a starting point. I was lazy: I used the first measurement as starting point. The resulting X/Y pairs are graphed using gnuplot.
Update: I'm a security specialist, not a programmer: I found some errors in the routines that convert output from the GPS to degrees to meters. Fixed them, so the first graph has been redrawn using data from 17 and 18 Februari.
- holux gr-213 in the shed wanderings, 2 days Interesting first results with the GPS module inside the shed so the roof adds extra signal loss and reflections.
- holux gr-213 with the antenna on the shed roof wanderings, 2 days The better reception seems to help a lot, notice the difference in scale.
- holux gr-213 with the antenna on the shed roof wanderings, 6 days the range does not change much over 6 days.
Since the old gpskit gps was showing problems in ntp tests earlier I decided now that the weatherstation computer is up and running on the alix.1c board to try a different gps unit: The Holux GR-213 GPS I still have from earlier wardriving. Not much of a succes sofar. First the GPS did not get a lock at all. I was expecting a delay in acquiring a lock since it hadn't been used in over a year but after a day and a half it still wasn't locking. So I moved it a bit which led to a lock (blinking led). But ntpd was still not using the GPS_NMEA driver. When I had time to have more of a look than just the graphs at NTP server ritchie.idefix.net stats I noticed ntpd was still seeing GPS_NMEA as a falseticker. Which is about right, when I look at the peer stats the GPS_NMEA clock has an offset of about 500 milliseconds(!!) compared to the rest. To my best knowledge I can find the right offset with 'enable calibrate'. But documentation is very minimal on this matter: Reference clock drivers - ntp 4.0.99k documentation has:The recommended procedure is to enable the function, let it run for an hour or so, then edit the configuration file using the time1 values displayed by the ntpq utility and clockvar command.With 'enable calibrate' on I see after a long run:ntpq> peer remote refid st t when poll reach delay offset jitter ============================================================================== +greenblatt.idef 18.104.22.168 2 u 137 512 377 1.012 1.780 87.722 *metronoom.dmz.c .PPS. 1 u 166 512 377 18.297 -1.207 46.401 +auth1.xs4all.nl 22.214.171.124 2 u 119 512 377 16.604 -1.104 27.267 xGPS_NMEA(0) .GPS. 0 l 4 16 377 0.000 -529.94 3.286 ntpq> clockvar associd=0 status=0000 , no events, clk_unspec, device="NMEA GPS Clock", timecode="$GPGGA,210752.000,5206.6230,N,00507.0976,E,1,06,1.5,-0.1,M,47.1,M,,0000*7F", poll=762, noreply=0, badformat=0, baddata=0, fudgetime1=0.000, stratum=0, refid=GPS, flags=0So even after running for a long time with clearly an offset between the other clocks and the reference clock there is no change in the suggestion for the time1 factor, still showing 0.000. Remarks in [ntp:questions] enable calibrate? suggest 'enable calibrate' will only work when there is a PPS signal available, and confirm the lack of documentation and samples I found. The Holux GR-213 also does not have a PPS signal to the outside at all, so I can't use a PPS signal anyway. Update: Some sleep, thinking and reading later: first of all, time1 is the PPS time offset and time2 is the gps message offset, found by reading ntpd documentation Generic NMEA GPS driver. So I started looking for the right offset with the 127.127.20.0 driver in noselect mode. After some testing I found a reasonable answer with:# GPS as time source without pps server 127.127.20.0 minpoll 1 maxpoll 4 fudge 127.127.20.0 time2 +0.544And now things look better:ntpq> peer remote refid st t when poll reach delay offset jitter ============================================================================== +greenblatt.idef 126.96.36.199 2 u 2 64 77 0.956 -2.252 41.400 *metronoom.dmz.c .PPS. 1 u 5 64 77 17.921 -2.236 1.190 -auth1.xs4all.nl 188.8.131.52 2 u 3 64 77 16.254 -2.750 0.880 +GPS_NMEA(0) .GPS. 0 l 2 8 377 0.000 -5.916 1.100
I decided to try aprsdroid on my android device. First and easiest should be to select the option AFSK via Speaker/Mic and I hoped it would work when the speaker and microphone of the portable radio are near the microphone and speaker of the android device. No luck: no transmitted APRS packet was found via aprs.fi call PD4KH and no incoming packet was decoded. I guess there was too much distortion and interference. I looked at the aprsdroid settings a lot since I noticed outgoing audio seems to be fixed at the highest volume, which can also be an issue. In the video Get Started with APRS for only $30! - youtube.com video a simple cable from the android device to the radio is used, so it can be done. Going for a solution like an Mobilinkd is more expensive, but maybe interesting in the long run when I want to do more with APRS. For now, an interim solution would be nice: building the right cable to get audio from the radio to the android device and back. I found the specs for such a cable at iPhone / Baofeng interface bouw en schema - PA4TW which can be adjusted for the android device and Wouxun. And PA4TW has used it for APRS in Aprs via porto en iPhone - PA4TW. Old analog telephone equipment can be a source of 600 ohm 1:1 transformers, so I guess some old equipment will have to donate those when I go for such a cable.
: Interesting article found by