LRP Trouble Shooting Guide:

If you have "software firewall" installed on internal PC, it should allow port 53 DHCP to go
through so that it can obtain an IP address from the LRP box.

Boot up LRP, login as root, then type q to drop to the command prompt.

Type lrpkg -l  and you should see something like this.

Type  ps ax  and you should see something like this.

Type  lsmod  and look near the bottom of the display, you should see
something like this. In the third column, there is a number,
0 means the driver cannot see the card, 1 means the driver sees one card,
2 means the driver sees 2 cards.

If you use ISA cards, have you set them to non-PnP (or jumper-less) mode ?
Did you set the IO address on the ISA cards correctly ?
Did you set the IRQ address on the ISA cards so they do not crash into something else ?

Type  cat /proc/interrupts ,you should see something like this,
there should be some numbers. If it shows 0, then your network card has an IRQ conflict
with something obscure in the motherboard.
(Thanks to Jon Higgs for sharing this hint, it can save you hours of troubleshooting)

Type ifconfig eth0  and you should see something like this.
You should see a inet address.
If it says NONE, re-connect your original Windows machine and release the IP address
to the cable modem/ADSL company and try again.

Some cable modems (e.g. Terayon cable modems) can only talk to a Ethernet cards at 10 Mbps
in half-duplex mode. This can be a problem for the newer, faster, 10/100 Mbps full-duplex cards.
The solution to that problem is:
* use an older network card for eth0 (your geeky friends or eBay has many low-cost legacy cards), or
* insert an old , abandoned, 10 Mbps hub between the Terayon cable modem and LRP, see this diagram.

Type ip route and you should see something like this.
The third line, "default" must exist or else you will not be able to access the Internet.

Note: some ISPs filter out all pings, so that the following 2 steps will fail even if the LRP is working.

Type ping  64.202.188.201 and you should see something like this. 
Ctrl-C to stop the pings.
If you cannot get replies, type seawall clear and try ping 64.202.188.201 again.

Type ping  www.godaddy.com and you should see something like this: 
Ctrl-C to stop the pings.

icon E-mail troubles:
If you can surf the web but having trouble with email behind LRP, that is most likely because you did not
use the fully qualified hostname for your email server. For example, Shaw tells you that their email server
is "shawmail", what they meant is "shawmail.cg.shawcable.net", where the
"cg.shawcable.net" portion is their "domain suffix".
If you follow step (11) on the main page carefully, you would have configured the DHCP server on LRP to
use the correct domain suffix and your internal PC, during boot up, would naturally acquired the correct
domain suffix.
The best solution is to follow step (11), or call your ISP to find out what are the correct
domain suffix and DNS servers in your location and do step (11).
Or, edit your email client POP and SMTP hostname, change the "simplified" hostname to the
"fully qualified" hostname. Below are examples of "simplified" versus "fully qualified" hostnames:
 

 simplified hostname bad  domain suffix  fully qualified hostname good
 mail  cg.shawcable.net  mail.cg.shawcable.net
 mail  radiant.net  mail.radiant.net
 shawmail  vc.shawcable.net  shawmail.vc.shawcable.net
 smtp  telus.net  smtp.telus.net
 pop  telus.net  pop.telus.net

good fully qualified hostname = simplified hostname + . + domain suffix at your location

 

Click here to return to the main LRP page

Last revised: August 10, 2006