Displaying 4 results from an estimated 4 matches for "tapinstall".
Did you mean:
appinstall
2015 Oct 17
2
Automated Windows installer
...taller, goes through usual pages and then installer asks
for a name of his/her future node.
It's not a problem to embed our network bootstrap configuration inside
installer.
The problem starts with Windows itself. We have tap-win{32,64}
directories. Inside them, there is a few batch files and tapinstall.exe
binary. It actually performs installation process of TAP driver and
new interface.
And that's it: I can't safely rename interface from installer batch
file. If it comes with name "Local Area Connection", then I can rename
it. But if user has many unrenamed "Local Area Co...
2015 Oct 17
1
Automated Windows installer
On Sat, 17 Oct 2015 14:54:17 +0200
Guus Sliepen <guus at tinc-vpn.org> wrote:
> On Sat, Oct 17, 2015 at 02:54:01PM +0700, ???? wrote:
>
> > The problem starts with Windows itself. We have tap-win{32,64}
> > directories. Inside them, there is a few batch files and
> > tapinstall.exe binary. It actually performs installation process of
> > TAP driver and new interface.
> >
> > And that's it: I can't safely rename interface from installer batch
> > file. If it comes with name "Local Area Connection", then I can
> > rename it....
2015 Oct 17
0
Automated Windows installer
On Sat, Oct 17, 2015 at 02:54:01PM +0700, ???? wrote:
> The problem starts with Windows itself. We have tap-win{32,64}
> directories. Inside them, there is a few batch files and tapinstall.exe
> binary. It actually performs installation process of TAP driver and
> new interface.
>
> And that's it: I can't safely rename interface from installer batch
> file. If it comes with name "Local Area Connection", then I can rename
> it. But if user has many...
2018 Oct 18
0
miniupnp support in Windows builds
...ompiling tinc with this one change for my project and UPnP seems to work very well so far on Windows nodes.
Another small minor issue with the Windows package is with the bundled tap-windows install scripts.
The batch files do not refer to the directory the scripts are in (e.g via using "%~dp0tapinstall.exe")
which means that when the batch files are ran as administrator (required for driver installs)
cmd.exe attempts to run the command from System32 rather than directory where tapinstall.exe and OemWin2k.inf files are.