Still no luck.  ifcfg-ctc file is now:

DEVICE=ctc0
BOOTPROTO=static
IPADDR=172.16.18.130
NETMASK=255.255.255.128
ONBOOT=yes
REMIP=172.16.18.129
GATEWAY=172.16.18.129
MTU=1500

network was whittled down back to the three lines...

on reboot ifconfig ctc0 still shows that netmask is 255.255.255.255 and
mtu is 32767.


oh well,
Daniel

[EMAIL PROTECTED] wrote:

>Daniel,
>
>Ah, I missed something.  You need a "REMIP" value in your ifcfg-ctc0 file:
>REMIP=192.168.0.10
>This is the IP address of the "other end" of your CTC link.  Here's _my_
>complete file:
>DEVICE=ctc0
>BOOTPROTO=static
>IPADDR=192.168.0.20
>REMIP=192.168.0.10
>GATEWAY=192.168.0.10
>ONBOOT=yes
>MTU=1500
>
>I don't know if Peter Bishop's suggestion to change BOOTPROTO to static is
>necessary, but since we both have it in our files, it isn't going to hurt.
>
>You should remove the additional stuff you put in /etc/sysconfig/network.
>
>Mark Post
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, January 31, 2002 3:07 PM
>To: [EMAIL PROTECTED]
>Subject: Re: CTC - linux newbie - should be an easy one
>
>
>I tried renaming the file, and that wasn't enough for things to work
>correctly.  On reboot MTU is 32767 and netmask 255.255.255.255 for ctc0
>
>ifup-ctc is executing to the end (route add default gw ${GATEWAY} is
>being performed), so that seems okay.
>
>Two noteworthies:
>earlier in the script, the ifconfig line is called with ${opts} being
>empty, instead of "mtu 1500" or something.
>$NETWORK also seems to be empty during execution
>
>here's some informational stuff
># cat /etc/modules.conf
>alias parport_lowlevel parport_pc
>alias ctc0 ctc
>(parport was there from the beginning, just added the alias ctc0)
>
>#cat /etc/sysconfig/network
>NETWORKING=yes
>HOSTNAME=tcsl.tcs.timeinc.com
>GATEWAY=172.16.18.129
>NETMASK=255.255.255.128
>MTU=1500
>NETWORK=172.16.18.129
>(this used to be just the top three, but I keep on throwing more stuff
>in here in hopes that something'll catch)
>
># cat /etc/sysconfig/networking/ifcfg-ctc0
>DEVICE=ctc0
>IPADDR=172.16.18.130
>NETMASK=255.255.255.128
>ONBOOT=yes
>GATEWAY=172.16.18.129
>USERCTL=no
>MTU=1500
>BOOTPROTO=none
>NETWORK=172.16.18.129
>(in the beginning the file didn't exist, i keep throwing in stuff hoping
>something'll catch)
>
>
>RH 7.2, LPAR installation.
>I used to have at least the netmask part correct on reboot, but haven't
>ever had the mtu to work correctly.
>But now neither of them are working.
>
>
>See anything glaring?
>Thanks,
>Daniel
>
>
>[EMAIL PROTECTED] wrote:
>
>
>>Daniel,
>>
>>I believe that if you rename ifcfg-ctc to ifcfg-ctc0 that things will start
>>happening for you.  Those files are created for each interface, not a class
>>of interfaces.
>>
>>Mark Post
>>
>>-----Original Message-----
>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>>Sent: Thursday, January 31, 2002 10:05 AM
>>To: [EMAIL PROTECTED]
>>Subject: CTC - linux newbie - should be an easy one
>>
>>
>>I really hate to ask, because I had it working before, but after a fresh
>>reinstall I couldn't get it working again.
>>RH 7.2 on an LPAR.  Everytime I reboot I have to
>>
>>ifconfig ctc0 mtu 1500 netmask 255.255.255.128
>>and
>>route add default gw blah.blah.blah.blah
>>
>>(and vary tcpip on the gateway lpar)
>>
>>I'd like to avoid doing this, and am not about to hardcode values in the
>>network-scripts.  I've added alias ctc0 ctc
>>to my modules.conf so now it reads:
>>alias parport_lowlevel parport_pc
>>alias ctc0 ctc
>>
>>
>>I've also created /etc/sysconfig/networking/ifcfg-ctc and threw in some
>>values (which didn't do much)
>>
>>in /etc/sysconfig/network I have NETWORKING, HOSTNAME, and GATEWAY set
>>correctly.
>>
>>I've been tinkering with this for some time and it's just not working.
>>Previously I had gotten the configuration files to the point where
>>rebooting would get the netmask and default gateway correct (not MTU),
>>but I didn't make backups of config files I changed before I
>>reinstalled, and now I can't re-figure out what to do where.  What am I
>>doing wrong?
>>
>>
>>Thanks,
>>Daniel
>>

Reply via email to