We’ve been pretty good around keeping politics off this alias for the past 10 years, let’s keep it that way. :)
From: [email protected] [mailto:[email protected]] On Behalf Of mike smith Sent: Sunday, July 29, 2012 1:07 AM To: ozDotNet Subject: Re: [OT] Detect ADSL modem in use Just remember which party enabled[1] NBN, and which opposed it, and still hasn't committed to it, when we get to next election. <space left for u know who to respond> Mike [1] no, I wont say 'paid for it' :) On Sat, Jul 28, 2012 at 7:51 PM, Ian Thomas <[email protected]<mailto:[email protected]>> wrote: I don’t know what reminded me of this, but a means of reading the default gateway modem’s MAC address was needed because one common ADSL modem would not behave with one widely-used service only. Recently (6 weeks ago?), a firmware upgrade to that modem made the problem go away. Anyway (months ago now), I took the combined suggestions of Les Hughes and David Connors – see below - which gave rise to a very simple .NET DLL that called on the Windows system file, iphlpapi.dll That component is available in all 32/64 bit Windows since Windows 2000 I think. And pInvoke info was helpful. It will lovely to get the NBN here in the next 12 months and hopefully to do away with cantankerous copper connections. I have a neighbour in the same rollout FSA 6VIC-02 with a max ADSL speed of about 2x dial-up. ________________________________ Ian Thomas Victoria Park, Western Australia ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of David Connors Sent: Wednesday, May 02, 2012 6:10 AM To: ozDotNet Subject: Re: [OT] Detect ADSL modem in use On Wed, May 2, 2012 at 7:56 AM, Les Hughes <[email protected]<mailto:[email protected]>> wrote: ------------------------------------- Step 2: Send the machine a message so it's details are in your local arp table. [ ... ] This will do: "ping IP.AD.DR.ESS -n 1" Step 3: Check your ARP table. [ ... ] This can be done by doing a "arp -a" in windows. Your output will be something like: There are a few other ways you can do this with several dlls around, which avoids the 'hacky-type' process calls, but this should work, and ping.exe and arp.exe have been around and worked for a long time. Both of those steps are pretty ugly. Forking a process to send 20 bytes as a by-product of its intended function is pretty epic. :) You really want the app to make the arp request directly. Did a quick Google and found this: http://msdn.microsoft.com/en-us/library/windows/desktop/aa366358(v=vs.85).aspx C++ sample code at the end that compiles to a command line app. I'd gut that sample and turn it into a .dll you can call from .net. Nice and neat to be used with your step 1 above. -- David Connors | [email protected]<mailto:[email protected]> | www.codify.com<http://www.codify.com> Codify Pty Ltd Phone: +61 (7) 3210 6268<tel:%2B61%20%287%29%203210%206268> | Facsimile: +61 (7) 3210 6269<tel:%2B61%20%287%29%203210%206269> | Mobile: +61 417 189 363<tel:%2B61%20417%20189%20363> V-Card: https://www.codify.com/cards/davidconnors Address Info: https://www.codify.com/contact -- Meski http://courteous.ly/aAOZcv "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
