Re: RedHat 7.2 not binding correctly

[Richard Singer <richards,AT,kingfish,DOT,corp,DOT,rainbowfish,DOT,com>]

Quoting Andy Grimberg (tykeal,AT,bardicgrove,DOT,org) on Wed, May 01, 2002 at 
10:05:40PM -0700:
> Greetings folks,
> 
> I was trying to find an answer to this quandry and didn't turn anything
> up so I thought I would post here.
> 
> I've got two RedHat 7.2 machines that have no problems bringing a CIPE
> 1.4.5 tunnel up just fine if I have both machines set with both ends of
> the tunnel defined.  My problem is when I try and set the machine that
> has a static address up in "server" mode with a PEER of 0.0.0.0 it binds
> itself to 127.0.0.1 instead of my external interface and the tunnel
> never completely establishes.
> 
> Here are my ifcfg-cipcb0 scripts which work:
> 
> Machine 1 (static address)
> USERCTL=no
> DEVICE=cipcb0
> IPADDR=192.168.2.1
> TYPE=CIPE
> ONBOOT=yes
> MYPORT=6060
> PTPADDR=192.168.1.1
> PEER=x.x.x.x:6060
> PEERDNS=no
> 
> Machine 2 (dynamic address)
> USERCTL=no
> DEVICE=cipcb0
> IPADDR=192.168.1.1
> TYPE=CIPE
> ONBOOT=yes
> MYPORT=6060
> PTPADDR=192.168.2.1
> PEER=y.y.y.y:6060
> PEERDNS=no
> 
> To which netstat -ln gives (relevant line only)
> Machine 1 (static address)
> udp        0      0 y.y.y.y:6060     0.0.0.0:*               ESTABLISHED
> 
> Machine 2 (dynamic address)
> udp        0      0 x.x.x.x:6060     0.0.0.0:*               ESTABLISHED
> 
> 
> Here's what I want:
> 
> Machine 1 (static address)
> USERCTL=no
> DEVICE=cipcb0
> IPADDR=192.168.2.1
> TYPE=CIPE
> ONBOOT=yes
> MYPORT=6060
> PTPADDR=192.168.1.1
> PEER=0.0.0.0
> PEERDNS=no
> 
> Machine 2 (dynamic address)
> USERCTL=no
> DEVICE=cipcb0
> IPADDR=192.168.1.1
> TYPE=CIPE
> ONBOOT=yes
> MYPORT=6060
> PTPADDR=192.168.2.1
> PEER=y.y.y.y:6060
> PEERDNS=no
> 
> To which netstat -ln currently gives (relevant line only)
> Machine 1 (static address)
> udp        0      0 127.0.0.1:6060     0.0.0.0:*              
> ESTABLISHED
> 
> Machine 2 (dynamic address)
> udp        0      0 x.x.x.x:6060     0.0.0.0:*               ESTABLISHED
> 
> Am I missing something here or in the documentation?
> 
> This is a bit of an issue to me as Machine 2 is a road warrior machine
> and constantly changing the server configuration isn't an option for
> me.  It's going to be even more of an issue as I'm going to be adding in
> more road warrior machines into the mix once I have this working.
> 
> TIA,
> -Andy Grimberg-
> 

Instead of using the MYPORT= option try using ME=x.x.x.x:6060 and see if that
works.  That is how I have used it in the past for the server end and it has
worked.

-- 
Richard Singer
True World Foods, Inc.
richards,AT,kingfish,DOT,corp,DOT,rainbowfish,DOT,com
richards,AT,trueworldfoods,DOT,com