1. TROUBLESHOOTING
    1. Telnet login problems.
    2. Unable to ping.
    3. Freesco won't boot the floppy.
    4. DHCPD start problems.
    5. NIC-Troubleshooting

     


    1. Telnet login problems.
      • Telnet sessions that *hang* during login attempts are usually related to DNS problems. If the DNS servers are not within the local subnet, and you are not online, then the reverse lookup must timeout, rather than just being denied. This problem can be resolved by turning the Freesco DNS server to (s) mode.
         
    2. Unable to ping.
      • If you want to ping, then you need to enable this feature.
      • Run *setup*, (a)dvanced section, option #11, question #112. Enable PING responses (y)
      • Save changes, exit setup, and run
        rc_masq restart
         
    3. Freesco won't boot the floppy.
      • Freesco v0.3.0 is extremely picky about floppies and drives. Even more so then v0.2.7. The reason is that there is a lot more compression used in v0.3.0.
      • If you can, try a floppy in several different machines and see if it boots. Then that will eliminate the actual floppy as the problem.
         
    4. DHCPD start problems.
      • If your router seems to hang at the *Starting dhcpd...* start process, then it may be directly related to having the LOGDHCP feature enabled.
      • Correct this problem as follows:
        --- setup, (a)dvanced
        --- 18. On/Off Debugging
        --- 186. Enable DHCP client message logging = (n)
         
    5. NIC-Troubleshooting
      • Sometimes you might have problems determining whether your network cards are working or not, so the following may be of use.

        ISA Cards

        If the card is an early one with jumpers, you need to use those jumpers to configure the io and irq. Most later cards are software set using a dos configuration utility which comes on a disk with the card. You need to run this utility and choose "jumperless" mode - plug and play will not work. Additionally, on some types of cards you might have to manually select the media type in the setup program (10base-T or thinnet/coax) and not rely on auto media sense.

        Of special note is the 3c509 and 3c509B cards - To disable PNP before using them with freesco you need a recent etherdisk (driver disk) from the 3com website, and boot up with one 3c509(B) fitted at a time, if you have more than one card - and run the pnpdsabl.bat file, shut down, boot up again, and then enter the 3c5x9cfg utilty and configure an io and irq setting. Repeat for a second and third 3c509. Note: contrary to most ISA cards, the 3c509(B) is autodetected in freesco, and the io and irq settings you enter in freesco setup are ignored.

        The newest version of the 3c5x9cfg utilty has been reported to be able to do multiple cards. While this option may be available, it is recommended to install the cards one at a time.

        PCI Cards

        Unlike ISA cards where the io and irq are configured by jumpers or a soft-set utility, PCI cards are configured by your motherboard BIOS, and if the settings in the BIOS are incorrect freesco cant access the card. Because there are so many different types of BIOS out there, the following advise is only general. If there is a PNP setting, (called "PNP OS" with an option of yes or no in an Award BIOS) you *must* set it to No. Other BIOS's may have different wording, so you may have to experiment. Symptoms of this setting being wrong are the card isnt detected at all, or its found on an invalid irq like 0 or 255.

        Even if you dont have the correct driver installed for a PCI card, you should be able to see it listed in the PCI device table with

        cat /proc/pci

        And you should see a valid irq being assigned. If you dont, go back to your BIOS and check things. If it looks ok here but freesco doesnt seem to be finding the card, you then need to look at finding the correct driver and installing it.

        For both PCI and ISA cards the following commands are also useful:

        cat /proc/ioports
        cat /proc/interrupts

        (Shows io and irq assignments of successfully loaded drivers)

        dmesg | grep eth

        (Shows messages related to the network cards filtered from dmesg. This will show you which card received what eth name.)

        Important note

        It's not possible to guarentee that cards will be detected in the order you entered them in setup, depending on the types and combinations of network cards you have. Dont be surprised if you find the cards in a different order to what you expected. The first card to be detected is labeled eth0, the second eth1, and so on. In advanced settings you can specify the interface names for each network. For example in ethernet router mode, "1st network" must be the one going to the internet, normally eth0, but if the network card you want to use to connect to the internet stubbornly insists on being detected as eth1, you can change the interface name for 1st network to eth1, and second network to eth0, which achieves the same functional result.