On 10-1-2011 8:04, Pim Zandbergen wrote:
>
> On 10-1-2011 5:53, Dale Dellutri wrote:
>> Please file a bugzilla. It looks like you have the info needed to pin down
>> the problem description.
> Right now, I'm checking whether this is a kernel issue or a racoon issue.
Solved it. It was neither a
On 10-1-2011 5:53, Dale Dellutri wrote:
>
> Please file a bugzilla. It looks like you have the info needed to pin down
> the problem description.
Right now, I'm checking whether this is a kernel issue or a racoon issue.
Pim
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe o
On Mon, Jan 10, 2011 at 10:09 AM, Pim Zandbergen
wrote:
> I'm seeing something possibly similar.
>
> I have upgraded a Fedora 11 box to Fedora 14. This box was succesfully
> running five
> IPSec tunnels. Four of them to a ZyXEL P-2602H, one to Fedora 13 box.
>
> After upgrading, all of the tunnels
I'm seeing something possibly similar.
I have upgraded a Fedora 11 box to Fedora 14. This box was succesfully
running five
IPSec tunnels. Four of them to a ZyXEL P-2602H, one to Fedora 13 box.
After upgrading, all of the tunnels were reestablished, but no traffic
was possible over it.
Using Wi
Hi,
I use racoon to establish an IPSEC tunnel between a fedora box and a router.
The tunnel is mounted.
Both my fedora and network behind the router can ping each other
The network behind the router can use the tunnel to ssh my fedora
But my fedora isn't able to ssh the network behind the rout
