In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> >> IPv4 connection via mapped address is still IPv6 connection. In this
> >> case, if ftp(1) doesn't have awareness of using mapped address, your
> >> problem will occur. And, ftp(1) seems not aware about it.
> >Yes. NetBSD did that commit just right now.
> >I guess they obtained it from you, or it's just a BIG coincidence.
> ume and I discussed it a little bit, directly.
Tested the patch on a 4.0S system against KRB5 tunnelled through VPN
(pipsecd for now) then NATed (using IP Filter at the remote side) to my
employer's network. Kerberos rlogin and KRB5 telnet now work however
KRB5 ftp still has problems.
KRB5 works nicely with or without the patch when directly connected via
PPP to my employer's network, e.g. no VPN and no NAT. (This opened up
another can of worms when I disconnected PPP from work and tried to
reestablish routes through VPN through the cable modem... but I digress
onto a tangent of something else that might be broken when IPv6 is in
the kernel and as it's late, I don't want to go there right now. Maybe
some other day.)
KRB5 works nicely through VPN and NATed without the patch without IPv6
in the kernel.
As IPv6 is not an issue for me at this time I haven't aggressively
pursued a solution, however I am willing to help out with testing and
debugging when time permits.
In summary, the patch is a huge step in the right direction. It could
very well be that KRB5 ftp may be at fault, not IPv6 in FreeBSD. I
don't know at this time.
Regards, Phone: (250)387-8437
Cy Schubert Fax: (250)387-5766
Team Leader, Sun/DEC Team Internet: [EMAIL PROTECTED]
Open Systems Group, ITSD, ISTA
Province of BC
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message