vpnc & cryptmount broken after installing updates

I have been running openSUSE 11.0 for a couple of months and decided it was time to install updates. I have been running openSUSE (current and earlier versions) for about 1.5 years but still consider myself somewhat green when it comes to system admin. I used the Updater to install security updates this morning (11/10/08). I know there were 47 updates installed but at the time I didn’t capture (didn’t know I needed to or how to easily do it) what the updates were. After installing the updates I notices that two packages that I use regularly, vpnc and cryptmount, no longer work. I currently have vpnc 0.5.1-30.1-i586 installed and cryptmount 3.0-1-i586 installed.

When I try to run cryptmount from a console I get these message:
device-mapper: reload ioctl failed: Invalid argument
device-mapper task failed

When I try to run vpnc from a console (logged in a root), I get these message:
vpnc: can’t open /dev/net/tun, check that it is either device char 10 200 or (with DevFS) a symlink to …/misc/net/tun (not misc/net/tun): No such device
vpnc: can’t initialise tunnel interface: No such device

It is obvious that both problems were caused by one or more of the updates that were installed because both packages were working fine before the update. I tried to figure out if there was a way to back out the updates but was unable to figure this out. Then I tried figure out which updates had been installed. Reading another post in this forum caused me to issue this command:
sudo zypper pch
The command produced a list of patches currently installed on my computer by there were more than 47 of them. I looked through the list to try to figure out if any of them were causing the problems.

Now I’m stuck. I don’t know how to figure out what updates were installed today, or what update might be causing these specific problems. At this point, I just want a solution without further breaking my system. So any help that anyone can provide would be wonderful. Thanks.

it-man

Both of these problems have been solved. It turns out that I had to do was reboot. I have no idea what caused the problem or why they are both solved but I am extremely relieved.

it-man