On Dec 16, 2010, at 2:09 PM, Levan, Jerry wrote: > > In my opinion Dan Shoop is a high level troll.
Ah, more personal attacks. Way to go there. Really demonstrates a high level of maturity and technical prowess. > Dan initially suggested that I use dyndns and things went downhill > from there... Ghod knows why. It's a practical solution already supported by your router *directly*. All you need to do is configure it. And when you disliked that solution I suggested yet another way that returned better, more reliable and more accurate results. > [Jerry wrote] > > It turns out that it is not hard to get the Airport Extreme Base Station > external address: > > > [mbp:]$ snmpwalk -Ov -OQ -c public router ipAdEntAddr > 76.177.12.46 > 127.0.0.1 > 127.0.0.2 > 169.254.162.44 > 192.168.1.1 > > [Dan responds] > Except that this isn't the proper answer to your question at all. > Nor are you going to be able to reliably use this either. > > This isn't your WAN IP address at all, it's a list of all VNICs that the > Airport > currently has. > **************** > > It looks to me like the IP address of the router is plainly visible :) > > Who is the 'wooly' thinker here? Because it's not returning what you suggest it is. It's returning a list of VNICs on the device. That is not the same as returning the WAN IP address, aside from the obvious difference from being a list rather than a scalar. So it's also a harder way of getting the information too (it's a fact you need to do more to scrub this returned data.) > [Jerry wrote ] > skynet is the (local) domain of my lan. > > [Dan reponds ] > No it's not. > > The local domain of your LAN is .local. > > This isn't a FQDN. > ************************* > > I have a nameserver running on my home network and I use skynet as the > domain name ie mbp.skynet is the local name of one of my computers. > > I think Dan was just being his usual snarky self. No I'm pointing out that this is not a valid DNS name at all. As I said it's not a FQDN. Moreover the "local domain" of your LAN is also not this value. It may be a zone you use locally on your network(s) with split horizions (which I'll bet a dollar you've implemented wrong if you're running OS X 10.6 or higher since it has new requirements and uses DNS servers differently) but this still isn't the local zone. And it's not a domain at all in DNS parlance it would be a zone (domains equate to hosts or things which have entry records) but that's a different distinction too. > [Jerry wrote > Just out of curiosity, am I the only person who wants to send a 'scripted > email' to > a location outside of the local network? It seems like that would be a handy > notification tool. > > [Dan responds] > > No you're the only person doing it in such a silly way. > This is all woolly thinking and you really need to understand > what you're doing, and more importantly define the real problem you're not > really solving. > > This is ridiculous what you're doing and your approach. > > What are you really trying to do? > > Most no one needs to have a mail message sent to them to tell them the > address of > their IP since any sane person would use a DNS name and not an IP address. > Given dyndns solves this problem completely and for free and with next to no > effort on your part I find it silly that you're going about it this way. > ****************************** > > Dan is really pissed...I won't do it his way and he is not going to take it > anymore :) I'm not pissed, I'm pointing out that this is a complex solution to a trivial and well solved non-problem and that you're missing that for all the wool. > Later on he expresses displeasure when I assert that he is > writing 'Bull Pucky' from his parents basement. Which sounds like a personal attack if there was one. > Hey Dan if you treat people with arrogance and rudeness, expect the same > in return. Perhaps open up Dictionary.app and read what your choice of words mean. Specifically see "brusque" and read the section "Choose the Right Word" "Brusque, which comes from an Italian word meaning rude, describes an abruptness of speech or manner that is not necessarily meant to be rude (a brusque handshake ; a brusque reply). Curt is more deliberately unfriendly, suggesting brevity and coldness of manner (a curt dismissal). There's nothing wrong with being blunt, although it implies an honesty and directness that can border on tactlessness (a blunt reply to his question about where the money went). Someone who is bluff is usually more likable, possessing a frank, hearty manner that may be a little too outspoken but is seldom offensive (a bluff man who rarely minced words). Exhibiting gruff or surly behavior will not win friends, since both words suggest bad temper if not rudeness. But gruff is used to describe a rough or grouchy disposition and, like bluff, is applied more often to a man. Anyone who has had to deal with an overworked store clerk while shopping during the holidays knows the meaning of surly, which is worse than gruff. It describes not only a sour disposition but an outright hostility toward people, and it can apply to someone of either sex (that surly woman at the customer service desk)." Note I'm not trying to win friends here. This isn't Facebook or a social list, it's a technical list. I'm not inviting anyone over for beers nor am I interested in anything other than the technical discussions which is the lists purpose. > TLDR: > Jerry wrote a short shell script that sends an email notification of > his routers external IP whenever it changes. This had a side effect > of causing some people to run in tight circles and bite their tails. > > As far as I am concerned I have finished what I set out to do and plan on > moving on to a new task... > > Thank you all for your patience during this difficult time. A difficult time you chose for yourself rather than using several other options that were both more simple, well established and more reliable. But hey, I'm happy your happy. And if using me as a foil for attacks helps you feel better it's still not bothering me, it's just bad form. I don't expect everyone to be nice, but you do seem to have hard time understanding why your approach may not be as robust as you think. -d ------------------------------------------------------------------------ Dan Shoop [email protected] GoogleVoice: 1-646-402-5293 aim: iWiring twitter: @colonelmode _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
