Date: Wed, 6 Jun 2012 09:26:24 -0500 From: Mark Felder <feld@feld.me> To: freebsd-questions@freebsd.org Cc: Robert Bonomi <bonomi@mail.r-bonomi.com> Subject: Re: IP -> e-mail Message-ID: <op.wfhjqaup34t2sn@tech304> In-Reply-To: <201206061411.q56EB2sf030101@mail.r-bonomi.com> References: <1338973608.78319.YahooMailNeo@web162906.mail.bf1.yahoo.com> <20120606125125.GA2043@tiny> <20431.22651.888125.876852@jerusalem.litteratus.org> <20120606134611.GA2185@tiny> <201206061411.q56EB2sf030101@mail.r-bonomi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 06 Jun 2012 09:11:02 -0500, Robert Bonomi <bonomi@mail.r-bonomi.com> wrote: > Matthias, your lynx-based 'solution' does *NOT* solve the OP's question. Incorrect; it does solve his problem. > He wants to know -when- his DHCP assigned address changes. Consider > what happens if both the expired address and the new address are behind > the _same_ NAT translation. The internal addrress changes, but the > external one does not. Please people, read carefully: His ISP is handing out his public IP via DHCP. This is normal for consumer internet connections. He doesn't care about his internal RFC 1918 IP which is handed out by his router's DHCP server; that's an easy problem to solve.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wfhjqaup34t2sn>