The IP on the M10 is 210.55.116.42
The Ip being presented to the web sites in question was
203.96.111.199
the implication is that the machine that is 203.96.111.199 is
taking the
packets and doing something akin to NAT on them. Or possible
some other sort
of Proxy service. The server at the far end is seeing the
packets as if they are coming from the 203.96.111.199 machine.

As an aside the 'magic' that allows the dynamic dns servers to
see the IP you want to use without you explicitly telling them is
that they look at the IP address that the update request is
coming from. This may be an issue for those of us who have a
script that has parts that don't work as they ought. I seem to
recall there being a couple of issues of that nature.
Particularly lynx under a cron environment on FreeBSD. It was a
problem I had which is why I startd playing with Telnet and SNMP
given that fetch totaly trashed the M10. If people are using
scripts/ programs that assume that there are no proxies between
them and there dynamic dns provider they may run into 'issues'
<mode = "minor cynic"> of course that might be the point</mode>

--kit

HAMISH MACEWAN wrote:
>
> Kit <kit@hypostasis.com> wrote:
>
> > Hi Guys
> > Does anyone have any idea why I am showing up to the outside
> > world as 203.96.111.199 ?
>
> I can only imagine it's because that's the IP you've been non-statically
> allocated?
>
> > dig /nslookup tell me
> > 199.111.96.203.in-addr.arpa. 52m46s IN PTR IPNAK1-C5.xtra.co.nz
>
> Hmmm, perhaps the reverse mapping is merely out of date?
>
> > What is going on here ?
>
> What is curious to you about what is happening here?
>
> > --kit
>
> Hamish.
>
> To unsubscribe: send mail to majordomo@freebsddiary.cx
> with "unsubscribe adsl" in the body of the message

To unsubscribe: send mail to majordomo@freebsddiary.cx
with "unsubscribe adsl" in the body of the message
Received on Sun Aug 15 17:07:41 1999