2008/9/2 Miika Komu <miika.komu@xxxxxxx> > Robert Moskowitz wrote: > > Hi Robert, > > Miika Komu wrote: >> >>> Robert Moskowitz wrote: >>> >>> Hi, >>> >>> I have been fighting the wrong battle via-a-vis IPv6 app availablity. >>>> Instead of trying every possible app for something for IPv6 functionality, >>>> if the 'main' app does do IPv6, what are LSIs for anyway???? >>>> >>>> Question is only how to get the connectivity to work write, and does the >>>> code base support this. >>>> >>> >>> HIP daemon and hipfw support both LSIs and HITs. >>> >>> The server only has an IPv6 address, so the resolver will return this >>>> address (from /etc/hosts or AAAA record in DNS). But the app only >>>> understands IPv4 addresses, so HIP needs to insert itself and return the >>>> LSI. The app happily then connects to the server; HIP does its exchange, >>>> etc. >>>> >>> >>> "hipconf run normal <app>" supports LSI resolution. >>> >> >> What does 'supports LSI resolution' mean? >> > > It means support for mapping a hostname to a LSI. > > Dns proxy does not support it. Antti promised to implement it, but did not >>> give any time estimate yet. >>> >>> There seems almost to be some magic here. I know it is not working >>>> 'simply', as VNC only supports IPv4. The server is bound to 0.0.0.0(should >>>> I change it to bind to the LSI?). The app is run by: >>>> >>> >>> No need to bind to an LSI unless you want to make sure that only >>> HIP-based connections are allowed. >>> >>> Server side LSI processing is supported in the hipfw. Notice that the LSI >>> support has to be invoked explicitly (-l) on userspace branch. >>> >> >> That option is not listed when I do an hipfw --help >> > > Seems like you are running old code, missing compilation or "make install". > > hipconf run normal vncviewer server.test:5902 >>>> >>>> All I see in the tcpdump is an I1 and I2. No R1. Why? This should work, >>>> right???? >>>> >>> >>> Yes. Did you specify both the HIT and LSI of server.test in >>> /etc/hip/hosts? >>> >> >> No. How do I include the server's LSI in the client's /etc/hip/host when >> both systems have the same LSI of 10.0.0.1? >> > > Remember that LSIs are local to the host. Select e.g. 10.0.0.10 for the > peer. > > LSIs have prefix 1, so e.g. it must be 1.0.0.10 ! -- Tere