Openswan pretty old and problems with gawk

juk · n00b Joined: 08 Aug 2005 Posts: 24

Hallo,

openswan 2.4.x is ot now and openswan 2.3.x is still marked unstable. And openswan 2.2.x can't be compiled anymore using a recent gentoo system...

So i used openswan 2.3.1 unstable and everything worked for a wile. After several gentoo updates a update for gawk went in and broke everything in openswan. The problem seems that gawk now has "default" as a keyword and "default" is used in the openswan scripts as a variable.

I was able to fix this partialy replacing "default" by "mydefault" in the confread script, but there are still errors in ipsec__plutorun.

Could someone contribute a working patch for openswan 2.3.x or even bette introduce an openswan 2.4.x package? Openswan has fixed this gawg issue but since the last portage for gentoo is pretty old, this is still broken for gentoo...

chunderbunny · Posted: Sun Oct 02, 2005 1:06 pm Post subject:

I don't know if this will work, but it's worth a shot I guess...

What you should try is a "version bump" of openswan. First you need to create a portage overlay (apologies if you know how to do this) by editing your /etc/make.conf to include the line

juk · n00b Joined: 08 Aug 2005 Posts: 24

chunderbunny · Posted: Sun Oct 02, 2005 1:28 pm Post subject:

Hmmm... the newest version has a weird naming scheme which portage doesn't recofnise. If you replace 2.4.1dr1 with 2.4.0 it should work.

chunderbunny · Posted: Sun Oct 02, 2005 1:48 pm Post subject:

Ack! I've just tried it and you run into a patch error. The old version of openswan had a gentoo-specific patch and i don't know what it does. You can fix it either by making the patch work for openswan-2.4.0 (I'm not a coder so I can't do this) or commenting out the line

juk · n00b Joined: 08 Aug 2005 Posts: 24

hello,

after solving the naming issue "2.4.1dr1" did not work, but "2.4.0" worked, i was able to emerge openswan 2.4.0.

But there is still an issue about this gawk "default" keyword behavior... seems that openswan still did not fix this completly...

Oct 2 16:30:51 amd64 ipsec__plutorun: awk: cmd. line:52: function default(k, val) {
Oct 2 16:30:51 amd64 ipsec__plutorun: awk: cmd. line:52: ^ syntax error

As a told above in my first posting "default" is now a keyword and cant be used anymore the way it has used before... but i think this now is a openswan issue and i will ask in their support forum about this.

Thank you.

juk · n00b Joined: 08 Aug 2005 Posts: 24

Hello,

i switched now to strongswan 2.5.4. The "default" issue is fixed there. Despite of the openswan maintainer who says everything is fixed in openswan 2.4.x there are still problems with gawk.

The tunnel is up and running again now.

Thanks for your help.