If I knew where this list's FAQ was housed, I would have checked it 
before sending this.  I _strongly_ suspect I'm not the first to 
check in with this particular woe.  But a perusal of the last 4 
months of the list archives at the www.linuxhq.com site affords 
neither that, nor an answer to my problem.  Neither did Usenet.  

Configuration:

    Intel VX440FX motherboard, PPro/200, running RedHat 5.1, kernel
        2.0.34 (not stock ... had to build, custom, for CD burner).
    DEC 21140-based "SMC Ether Power 10/100" ethercard on IRQ 10,
        configured (when applicable) as 192.168.0.2/255.255.255.0,
        (mjollnir), connected to a Netgear Fast Ethernet hub, itself
        connected to a __second__ local IP, 192.168.0.4 (excalibur).
    COM2/ttyS1 serial port on IRQ 3 hosting 56Kflex modem running
        intermittent ppp connection (_dynamic_ IP) to my ISP on ppp0.
        The call to establish pppd _does_ make _explicit_ use of the
        "defaultroute" keyword.  This is also present in
        /etc/ppp/options.

                                         __________
                                        /   ISP    \
                                       |(dynamic IP)|
                                        \ _________/
                                             |
                                             | <- Sick Connection
         ___________________      ___________|_______
        |                   |    |          ppp0     |
        | 192.168.0.4   eth0|----|eth0   192.168.0.2 |
        |___________________|    |___________________|


Problem:

    All attempts to use the RedHat network configuration interface,
        python /usr/lib/rhs/netcfg/netcfg.py
    to configure interface eth0 for internal ethernet traffic end up
    blocking the ppp interface, once eth0 is activated and ppp0 is 
    shut down once.  Only a reboot clears this condition.  

FixRoutes.sh script (attempt to fix problem):

    route delete default
    route add default dev ppp0

After the eth0 interface is activated, ppp connections cannot be
established past the first downing of ppp0.  _Period_.  Turning off
the interface does not help.  Only rebooting the box will restore
ppp0 functionality.

The "FixRoutes.sh" script does __NOT__ help, even after
re-establishment of the ppp0 interface.  Yes, I _did_ look this one
up on DejaNews before posting.  Too bad the proposed fix does not
work worth a curse.

/etc/sysconfig/network-scripts/ifcfg-ppp0 _does_ contain the line
    DEFROUTE=yes

/etc/sysconfig/network-scripts/ifcfg-eth0 reads (in it's entirety) ...
    PERSIST=no
    DEVICE=eth0
    IPADDR=192.168.0.2
    NETMASK=255.255.255.0
    NETWORK=192.168.0.0
    BROADCAST=192.168.0.255
    ONBOOT=no
    BOOTPROTO=none
    GATEWAY=none

I added /etc/sysconfig/network-scripts/ifup-eth0, which reads (in
it's entirety):
    route add -net ${NETWORK} netmask ${NETMASK} ${DEVICE}

/etc/ppp/options reads (in it's entirety) ...
    lock
    defaultroute

I use the following (scripted) command to bring up ppp:
    exec pppd connect \
            'chat -v -f /etc/ppp/chatscript-0777' \
            -detach crtscts modem defaultroute \
            mru 576 mtu 576 \
            user Pcroten \
            /dev/modem 115200

eth0 can remain configured .. but once it is activated _and_ ppp0 is
allowed to go down _even_ _once_, the jig is up .. It is gonna take
a reboot to restore ppp0 functionality.

Can someone _please_ tell me what gives ?  Just saying "establish
ppp0 as the default route" is __NOT__ good enough .. the FixRoutes.sh
script _does_ that, to no avail.

Thanks in advance.

Charles.

--
[EMAIL PROTECTED]       | Hideous anti-spam threat would go here ...
(Charles D. Roten)  | if this were Usenet.  :^)
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to