Re: IPv6 in tmda-ofmipd

On 6 Feb 2011, at 19:27, Kevin Goodsell wrote:
> On Sun, Feb 6, 2011 at 11:16 AM, Sabahattin Gucukoglu
> <[email protected]> wrote:
>> On 4 Feb 2011, at 06:42, Kevin Goodsell wrote:
>>> You'll need to use -p with a ":" in the address for this to work. I
>>> don't know if that's really sufficient to detect IPv6. I tested with
>>> ::1.
>> 
>> Thanks for the patch, however am I understanding right that I will be
>> specifying the port number also?  It doesn't look like you have any
>> way to distinguish between bare address and address:port (Postfix does
>> it using square brackets [] around v6 addresses).
> 
> -p requires a port and I believe it always has. The last : is the port
> separator. There's no ambiguity in this case, but there are still
> ambiguous cases in the code.

Sorry, I misunderstood you to mean you didn't specify it; yes, it's always used with a port number, and is anyway on the server in question.

Anyway, as you may note from the headers of this email, this message is brought to you with IPv6 power from end to end.  Thanks very much, works fine, and very impressed it took such a small change!  (Must rethink my attitude to Python ...)

To get your own IPv6, sign up at (1) your ISP, or (2) a tunnel broker like tunnelbroker.net or sixxs.org, or use transitional techniques like Teredo, AYIYA or 6to4 (less recommended).  Or, if you just want to test with something other than localhost, turn IPv6 on in machines on the same subnet, and use the link-local addresses (fe80:*) for communication among nodes.

> Also, I'll be replacing this on a Debian box, is there a clean way to
>> get the output of the program into a log file so I can test it in
>> place, or do I hack the initscript?
> 
> You can always run tmda-ofmipd on the command line. I even included a
> script for running it in the foreground with debug output in my Debian
> package: /usr/share/tmda-smtp/run-tmda-ofmipd

Nice, thanks!  I took this script and modified it for use with daemontools.  Now, tmda-ofmipd is uncrashable, and writes its output to a pipe whose read end is logger(1), so now I can read the messages through syslog.  All very sweet.  Even so, it'd be nice if the init script were updated in a later version to support writing a log file for users of the -L switch, so tmda-ofmipd has some accountability.

Cheers,
Sabahattin

------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
tmda-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tmda-users