On Dec 15, 2010, at 7:05 PM, Nat! wrote: > > Am 15.12.2010 um 02:07 schrieb Dan Shoop: > >> >> On Dec 14, 2010, at 5:52 PM, Nat! wrote: >> >>> >>> Am 14.12.2010 um 22:28 schrieb Dan Shoop: >>> >>>> >>>>> >>>>> I think it's fairly clever to use snmpwalk, with the result piped through >>>>> >>>>> egrep -v >>>>> '^127\.0\.0.|^169\.254\.|^172\.3[0-1]\.|^172\.2[0-9]\.|^172\.1[6-9]\.|^192\.168\.|^224\.|^2[45][0-9]\.|^10\.' >>>>> >>>> >>>> All you're doing is filtering out what may not be the WAN IP and it >>>> doesn't account for duplicates returned if the router has any additional >>>> VLANs that operate or VPNs. That could lead to additional false positives. >>> >>> True, though aren't these also usually of the 172.31.xxx.xx variety ? At >>> least, in my experience they are. >> >> Not at all. They could be RFC1918 addresses or public, depends in the >> network and CIDR blocks involved. > > Yes, but then, academically speaking, it isn't guaranteed, that > whatismyip.com is picking up the correct address
Yes, I suppose that could be true, but presumably when you're hitting these services you're not doing so from a proxy. Does curl respect a proxy data not specifically invoked? -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
