Welcome
Welcome to vistafirewallcontrol

You are currently viewing our boards as a guest, which gives you limited access to view most discussions and access our other features. By joining our free community, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content, and access many other special features. In addition, registered members also see less advertisements. Registration is fast, simple, and absolutely free, so please, join our community today!

Resolved: Generation of "prev" zones with update

Resolved: Generation of "prev" zones with update

Postby PietO » Mon Apr 15, 2013 4:15 pm

Dear Sphinx support: it would be nice if an option during installation would exist that previous "build-in" zone definitions are not renamed to "<old name> (prev)" but deleted. It takes some effort to clean up the repository every time an update is made.
Last edited by PietO on Tue Apr 23, 2013 8:11 pm, edited 1 time in total.
PietO
 
Posts: 192
Joined: Wed Mar 02, 2011 12:09 pm

Re: Generation of "prev" zones with update

Postby VistaFirewallControl » Mon Apr 15, 2013 5:34 pm

The W7FC zone updater is smart enough and does not perform the zone backup-ing (creating (prev) copies) of the zones if the zones are equal. So if the newly generated zones differ from the existing ones only, W7FC creates the “(prev)” backups. Otherwise the zones are kept intact.

Regarding the option for whether the zones should be overwritten unconditionally or backup-ed.
The question is in the option default state, which would be hardly changed by typical user.
The regular user will accept the default value almost anytime. However we are not able to make the right choice as the both approaches could be useful equally.

Also there is no a technical need to clean up the (prev) zones. Moreover the zones may include important customizations made by you. W7FC should provide you with the way to recover.

Usually you can easily prevent the (prev) backups creating by avoiding the reason for generated-vs-existing zone difference. The difference is almost anytime in ipV6 related rules. Windows generates new IPv6 addresses for some virtual network interfaces. W7FC has nothing to do with such behavior, the behavior is determined by the OS core. So if you do not need ipv6, switch ipv6 off by unbinding the v6 protocol from the network interfaces and disabling v6-via-v4 tunneling (teredo etc). After that the newly generated zones will be equal to the existing ones and there will be no (prev) copies created.
VistaFirewallControl
Site Admin
 
Posts: 1479
Joined: Fri Mar 27, 2009 11:25 am

Re: Generation of "prev" zones with update

Postby PietO » Tue Apr 16, 2013 9:47 am

i was just suggesting a user option at installation time which could be defaulted to "backup existing". Did follow your interesting idea to take V6 out including Linklayer Topology Discovery items. Just V4 is left.
PietO
 
Posts: 192
Joined: Wed Mar 02, 2011 12:09 pm

Re: Generation of "prev" zones with update

Postby PietO » Wed Apr 17, 2013 4:18 pm

did today the upgrade from 5.2.18.32 to 5.2.18.33 after the IP-V6 was NOT connected anymore (check taken away) but not deinstalled. Most unfortunately, some zones were again available with "<name> (prev)". So checking on the contents of the most simplest case: "LANservice"

Rule list looks the same but:
1. LANrule is changed: IPnumber, Mask, Name
2. IPV6 rules still present but NOT changed.

Although i don't have to understand the details, i did expect something changed in the V6 rules as you indicated, but LAN-rule changed. Do i have to uninstall the V6 protokoll instead of disabling to get rid of the prev-zones? I realise that the differences could be caused by disabling the V6 protokoll instead of uninstalling.

part of the export:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
<regkey name="LANService">
<regvalue name="Advised" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Name" data="LANService"/>
<regvalue name="Result" data="0x00000001 (1)" type="REG_DWORD"/>
<regkey name="RuleList">
<regkey name="0">
<regvalue name="Direction" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0xc0a80100 (-1062731520)" type="REG_DWORD"/>
<regvalue name="IpV6" data="00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0xffffff00 (-256)" type="REG_DWORD"/>
<regvalue name="Name" data="LAN 1 Local Area Connection"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
<regkey name="1">
<regvalue name="Direction" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0x7f000001 (2130706433)" type="REG_DWORD"/>
<regvalue name="IpV6" data="00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0xffffffff (-1)" type="REG_DWORD"/>
<regvalue name="Name" data="LocalHost"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
<regkey name="2">
<regvalue name="Direction" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0xa9fe0000 (-1442971648)" type="REG_DWORD"/>
<regvalue name="IpV6" data="00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0xffff0000 (-65536)" type="REG_DWORD"/>
<regvalue name="Name" data="APIPA"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
<regkey name="3">
<regvalue name="Direction" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="IpV6" data="00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000080 (128)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Name" data="LocalHost V6"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
<regkey name="4">
<regvalue name="Direction" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="IpV6" data="fe 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000040 (64)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Name" data="Link-Local v6"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
</regkey>
</regkey>
<regkey name="LANService (prev)">
<regvalue name="Advised" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Name" data="LANService (prev)"/>
<regvalue name="Result" data="0x00000001 (1)" type="REG_DWORD"/>
<regkey name="RuleList">
<regkey name="0">
<regvalue name="Direction" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0x0affffff (184549375)" type="REG_DWORD"/>
<regvalue name="IpV6" data="00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0xffffffff (-1)" type="REG_DWORD"/>
<regvalue name="Name" data="LAN placeholder"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
<regkey name="1">
<regvalue name="Direction" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0x7f000001 (2130706433)" type="REG_DWORD"/>
<regvalue name="IpV6" data="00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0xffffffff (-1)" type="REG_DWORD"/>
<regvalue name="Name" data="LocalHost"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
<regkey name="2">
<regvalue name="Direction" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0xa9fe0000 (-1442971648)" type="REG_DWORD"/>
<regvalue name="IpV6" data="00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0xffff0000 (-65536)" type="REG_DWORD"/>
<regvalue name="Name" data="APIPA"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
<regkey name="3">
<regvalue name="Direction" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="IpV6" data="00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000080 (128)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Name" data="LocalHost V6"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
<regkey name="4">
<regvalue name="Direction" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Enabled" data="0x00000001 (1)" type="REG_DWORD"/>
<regvalue name="ExtPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Ip" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="IpV6" data="fe 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00" type="REG_BINARY"/>
<regvalue name="IpV6Prefix" data="0x00000040 (64)" type="REG_DWORD"/>
<regvalue name="LocalPort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Mask" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Name" data="Link-Local v6"/>
<regvalue name="Protocol" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="RemotePort" data="0x00000000 (0)" type="REG_DWORD"/>
<regvalue name="Result" data="0x00000000 (0)" type="REG_DWORD"/>
</regkey>
</regkey>
</regkey>
PietO
 
Posts: 192
Joined: Wed Mar 02, 2011 12:09 pm

Re: Generation of "prev" zones with update

Postby VistaFirewallControl » Thu Apr 18, 2013 11:25 am

Actually the zones are different, the difference is important and make enough reasons for backup.
For the previous installation you had the “Local Area Connection” interface (192.168.1.0/24)
However after the upgrade the interface disappeared and W7FC generates a dummy placeholder.
Could you please provide us with more details in connection with the interface? Is it a wireless interface that could be not found right after the system start or switched off during the upgrade?
VistaFirewallControl
Site Admin
 
Posts: 1479
Joined: Fri Mar 27, 2009 11:25 am

Re: Generation of "prev" zones with update

Postby PietO » Thu Apr 18, 2013 3:55 pm

Thanks for the investigation. This particular PC with W7FC has WIN7 64 bit with just ONE network interface: hardwired LAN which was NOT disconnected!

Settings of this LAN-interface:
fixed-IP: 192.168.1.1
mask: 255.255.255.0
DSN: 2 fixed V4-addresses
GTWY: 192.168.1.254

only one protokol active:
IP-V4
all other protokolls deactivated (unbinded but not uninstalled):
client for MS network
QoS
file/print share
ip v6
link layer mapper + responder

Really can't be any simpler than this; network was active and stable during the upgrade (as always). All together reason for me to start this thread to get an explanation of the prev-zones for my configuration.

Note again: the V6 and link-layer protokolls were deactivated after the upgrade to V.5.2.18.32 in the past, which may have an unknown impact to the zones to me.

VistaFirewallControl wrote:For the previous installation you had the “Local Area Connection” interface (192.168.1.0/24)
However after the upgrade the interface disappeared and W7FC generates a dummy placeholder.

It looks more to me that before/during the upgrade there was a dummy placeholder, and after the upgrade there is a normal LAN
PietO
 
Posts: 192
Joined: Wed Mar 02, 2011 12:09 pm

Re: Generation of "prev" zones with update

Postby VistaFirewallControl » Fri Apr 19, 2013 3:19 pm

We just tried to explain the (prev) zone appearance.
The appearance was caused in accidentally missed LAN v4 interface, no ipV6 was involved in that case.

Anyway the placeholder can be substituted with actual LAN interface anytime with Settings/LANs.

Here is the short explanation of the placeholder.
On the upgrade W7FC iterates through all the network interfaces to create new zones with reflection of all possible changes. After the zones are created, W7FC compares existing zones against the newly generated ones and decides whether there is a need to backup.
The process is pretty straightforward.
The curious (for us) thing is there was no active network adapters found at the upgrade moment.
A temporarily one-time missed adapter (actually temporary connectivity fault) is not a problem, just an accident.

If you would like us to investigate the placeholder appeared mistakenly (the interface skipped mistakenly), please let us know
VistaFirewallControl
Site Admin
 
Posts: 1479
Joined: Fri Mar 27, 2009 11:25 am

Re: Generation of "prev" zones with update

Postby PietO » Sun Apr 21, 2013 8:11 pm

VistaFirewallControl wrote:The curious (for us) thing is there was no active network adapters found at the upgrade moment.
A temporarily one-time missed adapter (actually temporary connectivity fault) is not a problem, just an accident. If you would like us to investigate the placeholder appeared mistakenly (the interface skipped mistakenly), please let us know


It's curious for me as well as my network interface is stable as said. I noted this behavior before, the reason why i started this thread. Please inform me what i can to verify the behavior. Just to test, would it work to downgrade to the official-release and upgrade to the pre-release 5.2.18.33 again?
PietO
 
Posts: 192
Joined: Wed Mar 02, 2011 12:09 pm

Re: Generation of "prev" zones with update

Postby VistaFirewallControl » Mon Apr 22, 2013 10:58 am

You can delete the
HKEY_LOCAL_MACHINE\SOFTWARE\sphinx-soft\Vista-Wall\1.0\GUI\1.0 UpdateZones key.
The key stores the version installed, the installer verifies the key against the version you are installing and decides whether to upgrade the zones accordingly.
Without the key you can install any version on-the-top, the installer will "think" the zone upgrade is required.
Please keep us informed.
We are ready to provide with a logging version if required anytime.
VistaFirewallControl
Site Admin
 
Posts: 1479
Joined: Fri Mar 27, 2009 11:25 am

Re: Generation of "prev" zones with update

Postby PietO » Mon Apr 22, 2013 6:02 pm

VistaFirewallControl wrote:You can delete the
HKEY_LOCAL_MACHINE\SOFTWARE\sphinx-soft\Vista-Wall\1.0\GUI\1.0 UpdateZones key.
We are ready to provide with a logging version if required anytime.


Did as suggested; deleted the key and "upgraded" to the installed, latest prerelease. The Prev-zones are again present, but this time i noted that after the requested restart, my network was yet "not running" although starting a webbrowser, the network came up and was immediately present without any further user action.

I'll study first exactly how my system behaves after restart, post this and possibly we need a logging version to further analyse.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit 1: cross checked and indeed there is something strange in this particular system; after a restart -also without upgrading-
- the network adapter is up-and-running oke (device manager)
- no IPv4 and IPv6 connectivity (local area network status)
- incoming packets stays at 120
- no network reported but . . . . .

user is not aware as any network access is immediately possible and the network is up-and-running thus no user problem directly visible. Did not notice this before.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit2: cross checked with deinstalled W7FC
- although the deinstallation took quite some time (black-windows popping-up) it completed oke.
- system behavior same as before
- installed again (all program-settings zones lost; oke).

Do not know what the actual "problem" is and if this is related to the prev-zones. I assume so and maybe not the network adapter but network access causes problems to W7FC. All applications (e.f. FTP-client, Email) do not have a problem to "initialise" the network access

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks for your attention
PietO
 
Posts: 192
Joined: Wed Mar 02, 2011 12:09 pm

Next

Return to Installation/Deinstallation

Who is online

Users browsing this forum: No registered users and 0 guests

cron
suspicion-preferred