RE: [Leaf-user] Still Prob with INTERN_SERVERx (Indexed list) Dachstein
Hi, I take it back. When starting with INTERN_SERVER1, if I do an ipmasqadm portfw -l -n, then the entries I expect are not there. I suspect that starting at '1' just doesn't load anything at all. Thanks, BK -Original Message- From: Boyd Kelly Sent: Thu 07/03/2002 7:27 AM To: barwals; [EMAIL PROTECTED] Cc: Subject: RE: [Leaf-user] Problem with INTERN_SERVERx (Indexed list) Dachstein Thanks Sudhir, Started with INTERN_SERVER1 and sorks fine now. BK -Original Message- From: barwals [mailto:[EMAIL PROTECTED]] Sent: March 7, 2002 12:18 AM To: [EMAIL PROTECTED] Subject: Re: [Leaf-user] Problem with INTERN_SERVERx (Indexed list) Dachstein Dear Body, Please do not start with INTERN_SERVER0 instead start with INTERN_SERVER1. I hope you will not get any error. I was also getting the same error but after changing 0 (zero) to 1. And I didnot got any error. Thanks. Sudhir Boyd Kelly wrote: Hello, Making good progress on my Dachstein migration, but just had a hiccup with forwarding. The uncommented line (well they all would) from below gives me an error when starting the network: IP filters: portfw: Invalid protocol specified. The INTERN_SERVER section (not indexed) works ok, but I have too many entries. Those shown below are just some of what I have to do. As usual any help is very much appreciated. Boyd # Advanced settings: parameters passed directly to portfw and autofw # Indexed list: #INTERN_SERVER0=-a -P PROTO -L LADDR LPORT -R RADDR RPORT [-p PREF] INTERN_SERVER0=-a -P tcp -L 208.x.x.233 110 -R 192.168.1.233 110 #INTERN_SERVER1=-a -P tcp -L $PUB2_IP 143 -R $PRI2_IP 143 #INTERN_SERVER2=-a -P tcp -L $PUB2_IP 80 -R $PRI2_IP 80 #INTERN_SERVER3=-a -P tcp -L $PUB2_IP 443 -R $PRI2_IP 443 #INTERN_SERVER4=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110 #INTERN_SERVER5=-a -P tcp -L $PUB2_IP 5800 -R $PRI2_IP 5800 #INTERN_SERVER6=-a -P tcp -L $PUB2_IP 5900 -R $PRI2_IP 5900 #INTERN_SERVER7=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110 #INTERN_SERVER8=-a -P tcp -L $PUB0_IP 53 -R $PRI0_IP 53 #INTERN_SERVER9=-a -P udp -L $PUB0_IP 53 -R $PRI0_IP 53 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from http://www.planetm.co.in ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user Þiû¬z¹X§X¬´·~ë ®X¬¶Ë(º· ~àzwÛi³ÿåËl²«qç讧zßåËlþX¬¶)ߣù^iû¬z
Re: [Leaf-user] Still Prob with INTERN_SERVERx (Indexed list) Dachstein
I take it back.
When starting with INTERN_SERVER1, if I do an ipmasqadm portfw -l -n, then
the entries I expect are not there. I suspect that starting at '1' just
doesn't load anything at all.
This is what I would expect to happen...indexed lists start with zero, and
continue to the first missing number. If the zero entry is missing, no
other variables will be processes.
snip
Making good progress on my Dachstein migration, but just had a hiccup
with forwarding. The uncommented line (well they all would) from below
gives me an error when starting the network: IP filters: portfw: Invalid
protocol specified.
The INTERN_SERVER section (not indexed) works ok, but I have too many
entries. Those shown below are just some of what I have to do.
# Advanced settings: parameters passed directly to portfw and autofw #
Indexed list: #INTERN_SERVER0=-a -P PROTO -L LADDR LPORT -R RADDR
RPORT [-p PREF] INTERN_SERVER0=-a -P tcp -L 208.x.x.233 110 -R
192.168.1.233 110 #INTERN_SERVER1=-a -P tcp -L $PUB2_IP 143 -R
$PRI2_IP 143 #INTERN_SERVER2=-a -P tcp -L $PUB2_IP 80 -R $PRI2_IP 80
#INTERN_SERVER3=-a -P tcp -L $PUB2_IP 443 -R $PRI2_IP 443
#INTERN_SERVER4=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110
#INTERN_SERVER5=-a -P tcp -L $PUB2_IP 5800 -R $PRI2_IP 5800
#INTERN_SERVER6=-a -P tcp -L $PUB2_IP 5900 -R $PRI2_IP 5900
#INTERN_SERVER7=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110
#INTERN_SERVER8=-a -P tcp -L $PUB0_IP 53 -R $PRI0_IP 53
#INTERN_SERVER9=-a -P udp -L $PUB0_IP 53 -R $PRI0_IP 53
Looking through the scripts, the comments above are incorrect. From the
actual procedure doing the port-forwarding:
# A function to portforward services, setup to be called by walk_list
# $1 = Name of environment variable to use for arguments
# Arguments as they should appear in the environment variable:
# protocol Laddr Lport Raddr [ Rport [ preference ] ]
port_forward () {
So...Remove the -a, -P, -L, and -R fields from your INTERN_SERVER entries,
start with INTERN_SERVER0, and everything should work properly.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] Still Prob with INTERN_SERVERx (Indexed list) Dachstein
Thanks Charles.
I am probably missing something, but as per below this is what happens if I start at
zero.
The uncommented line (well they all would) from below
gives me an error when starting the network: IP filters: portfw: Invalid
protocol specified.
I do realize I can use the non indexed section as well.
Thanks for any help.
-Original Message-
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]]
Sent: Thu 07/03/2002 11:37 AM
To: Boyd Kelly; barwals; [EMAIL PROTECTED]
Cc:
Subject: Re: [Leaf-user] Still Prob with INTERN_SERVERx (Indexed list)
Dachstein
I take it back.
When starting with INTERN_SERVER1, if I do an ipmasqadm portfw -l -n, then
the entries I expect are not there. I suspect that starting at '1' just
doesn't load anything at all.
This is what I would expect to happen...indexed lists start with zero, and
continue to the first missing number. If the zero entry is missing, no
other variables will be processes.
snip
Making good progress on my Dachstein migration, but just had a hiccup
with forwarding. The uncommented line (well they all would) from below
gives me an error when starting the network: IP filters: portfw: Invalid
protocol specified.
The INTERN_SERVER section (not indexed) works ok, but I have too many
entries. Those shown below are just some of what I have to do.
# Advanced settings: parameters passed directly to portfw and autofw #
Indexed list: #INTERN_SERVER0=-a -P PROTO -L LADDR LPORT -R RADDR
RPORT [-p PREF] INTERN_SERVER0=-a -P tcp -L 208.x.x.233 110 -R
192.168.1.233 110 #INTERN_SERVER1=-a -P tcp -L $PUB2_IP 143 -R
$PRI2_IP 143 #INTERN_SERVER2=-a -P tcp -L $PUB2_IP 80 -R $PRI2_IP 80
#INTERN_SERVER3=-a -P tcp -L $PUB2_IP 443 -R $PRI2_IP 443
#INTERN_SERVER4=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110
#INTERN_SERVER5=-a -P tcp -L $PUB2_IP 5800 -R $PRI2_IP 5800
#INTERN_SERVER6=-a -P tcp -L $PUB2_IP 5900 -R $PRI2_IP 5900
#INTERN_SERVER7=-a -P tcp -L $PUB2_IP 110 -R $PRI2_IP 110
#INTERN_SERVER8=-a -P tcp -L $PUB0_IP 53 -R $PRI0_IP 53
#INTERN_SERVER9=-a -P udp -L $PUB0_IP 53 -R $PRI0_IP 53
Looking through the scripts, the comments above are incorrect. From the
actual procedure doing the port-forwarding:
# A function to portforward services, setup to be called by walk_list
# $1 = Name of environment variable to use for arguments
# Arguments as they should appear in the environment variable:
# protocol Laddr Lport Raddr [ Rport [ preference ] ]
port_forward () {
So...Remove the -a, -P, -L, and -R fields from your INTERN_SERVER entries,
start with INTERN_SERVER0, and everything should work properly.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
Þiû¬z¹X§X¬´·~ë ®X¬¶Ë(º· ~àzwÛi³ÿåËl²«qç讧zßåËlþX¬¶)ߣù^iû¬z
