Router not routing

Ric Moore wayward4now
Mon Dec 11 08:11:15 PST 2006


On Mon, 2006-12-11 at 09:29 -0600, Alma J Wetzker wrote:
> Ric Moore wrote:
> > On Mon, 2006-12-11 at 15:29 +1100, James McDonald wrote:
> >> Alma J Wetzker wrote:
> >>> This is not quite a linux question, but it is close.
> >>>
> >>> I have cable internet service to the house.  I use a linksys cable modem
> >>> and a linksys wireless G router running sveasoft 1.1 talisman basic.  We
> >>> had a power outage and the sveasoft router no longer picks up a WAN ip
> >>> address.  No problem, I have a spare linksys WRT54GS v.5.  That one
> >>> picks up the WAN address and assigns LAN DHCP addresses.  It even
> >>> resolves DNS lookups.  It does not seem to route any other traffic
> >>> between the LAN and WAN.  I can get on by attaching directly to the
> >>> modem (obviously), but I can't get the router to work.  Anything I
> >>> should be looking for?  Any ideas?  Both sides are working, but only DNS
> >>> seems to get through.
> >>>
> >>>     -- Alma
> >>>   
> >> I had to reconfigure one of these the other day and found that "packet 
> >> filtering" was on and it was blocking traffic.
> > 
> > Can you open a web browser and use http://192.168.0.2 to hit the router?
> > (assuming the modem is 192.168.0.1) The password for it is listed on the
> > linksys site. Usually blank user name and "admin" for the passwd. Then
> > you can check the settings. Ric
> 
> I can get to the router just fine (sorry I didn't mention that
> explicitly.)  What I am not certain about is what setting to check.
<cackles> Sorry, I feel ya! My stinking little PIII that I updated to
FC5 refuses to see the network card, isapnp doesn't seem to be doing
it's job and like you, it has to be some obscure setting some place in
there. My "big monster" computer can't see it although it's two feet
away plugged into the same huh. So, it's trouble shooting with a shotgun
time. I hate when that happens. Ric






More information about the Linux-users mailing list