It appears that I've just found a problem. I'm using the default port pool for TCP on the IPv4 side (61001-65535), but I'm also trying to add a static binding for port 22065 on the IPv4 address to an IPv6 address. Jool refuses to add the mapping, probably because port 22065 is not inside the port range in the pool4 structure. This wouldn't be an issue with a second IPv4 address, of course, because Jool would have the entire port range available.
Thoughts on how to approach this? On Mon, Sep 14, 2015 at 8:42 PM, Kevin Fleming <[email protected]> wrote: > No, it went just fine. I did have to adjust MTUs on all involved > interfaces to 1460 in order to get reliable TCP connections, but I was > expecting that. > > On Mon, Sep 14, 2015 at 12:03 PM, Alberto Leiva <[email protected]> wrote: > >> Awesome! :-) >> >> Any feedback on anything that we might have done better to ease the >> installation? >> >> On Sun, Sep 13, 2015 at 11:14 AM, Kevin Fleming <[email protected]> >> wrote: >> >>> Just a note to say that I've installed the testing branch on my system >>> (which is hosting VMs using KVM/libvirt, with only IPv6 available in the >>> VMs), using a single IPv4 address to connect to the public network, and >>> everything seems to be working fine. >>> >>> Thanks for the nice work :-) >>> >>> _______________________________________________ >>> Jool-list mailing list >>> [email protected] >>> https://mail-lists.nic.mx/listas/listinfo/jool-list >>> >>> >> >
_______________________________________________ Jool-list mailing list [email protected] https://mail-lists.nic.mx/listas/listinfo/jool-list
