On Thu, 8 Sep 2005, Leonard Isham wrote:
I plan to treat the "TO" (topology-supporting) branch as a beta series
until the 2.1 beta series formally begins -- that means it will be
updated, changes from the 2.0.x branch will get merged in, and when I make
releases, there will always be a .tar.gz,
On 9/8/05, James Yonan wrote:
> On Thu, 8 Sep 2005, Leonard Isham wrote:
>
> > On 9/8/05, James Yonan wrote:
> > >
> > > On Thu, 8 Sep 2005, Leonard Isham wrote:
> > >
> > > > On 9/8/05, James Yonan wrote:
> > > > >
[snip]
> >
> > Please bear with a network geek's rambling for a minute.
> >
>
On Thu, 8 Sep 2005, Leonard Isham wrote:
> On 9/8/05, James Yonan wrote:
> >
> > On Thu, 8 Sep 2005, Leonard Isham wrote:
> >
> > > On 9/8/05, James Yonan wrote:
> > > >
> > > > OpenVPN Addressing Topology
> > > > ---
> > > >
> > >
> > > > Merging Schedule
> > > > -
On 9/8/05, James Yonan wrote:
>
> On Thu, 8 Sep 2005, Leonard Isham wrote:
>
> > On 9/8/05, James Yonan wrote:
> > >
> > > OpenVPN Addressing Topology
> > > ---
> > >
> >
> > > Merging Schedule
> > >
> > >
> > > With sufficient testing, this code will be
On Thu, 8 Sep 2005, Leonard Isham wrote:
> On 9/8/05, James Yonan wrote:
> >
> > OpenVPN Addressing Topology
> > ---
> >
>
> > Merging Schedule
> >
> >
> > With sufficient testing, this code will be a candidate for inclusion in
> > 2.1 or higher, and w
On 9/8/05, James Yonan wrote:
>
> OpenVPN Addressing Topology
> ---
>
> Merging Schedule
>
>
> With sufficient testing, this code will be a candidate for inclusion in
> 2.1 or higher, and will be applicable to the 2.0.x branch via manual
> merging. Whi
OpenVPN Addressing Topology
---
OpenVPN addressing topology has been the subject of considerable debate,
specifically the /30 addressing scheme, where each tun client is allocated
a dynamic /30 subnet, so as to play nicely with the limitations of the
TAP-Win32 driver.
Nei
