"jj92_2" <(E-Mail Removed)> hath wroth:
>I'll try to describe a bit better.
You're doing very badly (seriously). I keep asking for exact version
numbers. Instead, I get truncated descriptions. You are apparently
doing an excellent job of troubleshooting (simulating the WAN
connection with another PC) but the descriptions are very vague and
confusing. I realize the English is not your native language. Your
English is quite good, but the organization and descriptions are the
problem. I'll try to illustrate the problem with my quesitions below.
Do NOT answer my questions as there are too many of them. Try to use
them as a guide for a new posting that describes the equipment and
symptoms much better.
>I have entered the network manually.
Does that mean a static IP address? LAN or WAN side? It's easy to do
those wrong. Fill in the blanks below:
LAN IP Address:
LAN netmask:
WAN IP Address:
WAN IP Netmask:
WAN Gateway Address:
If DCHP on the WAN side, look on the status page for the IP's. If you
have security concerns, do NOT post the exact WAN IP and Gateway
Address.
>In the GS54 V4 I get signal to the AP, I connect to the network (WEP
>code), wireless status shows packages sent and received.
Signal to what AP? I thought that the WRT54GS v4 is acting as an
access point or wireless router and that you're using some unspecified
client computer to connect to the WRT54GS v4. If there is more than
one access point in your system, kindly describe it. To avoid
confusion, especially when changing "modes", try describeing them as
"box #1" and "box #2".
>But seems to be that the TCP/IP part doesnt work.
The first step to solving a problem is NOT to blame something. TCP/IP
part not working is like saying "my car doesn't go". It tells us
nothing. Does your car have a flat tire or dead engine? What part of
TCP/IP is not working? What doesn't it do that you would expect it to
do.
>For me it looks like something weird is broken in hardware.
Again, please describe the symptoms, not your impression of the
symptoms. What looks weird to you way be a common problem familiar to
those with some experience.
>What happenend:
>I had DD-WRT#23 installed. It worked fine.
Try again on the version number. It's a bit tricky to find. Go to the
status page. It's in the upper right hand corner of the page. Include
the version date. Mine is at:
https://office.learnbydestroying.com:8080/
If you click on the version number, you get some more detail. Mine
says:
DD-WRT v23 SP1-RC4 (05/12/06) std
That's what I want from you.
>I unplugged and plugged power, and lost the TCP/IP part.
I started and stopped the car and it still won't go. That doesn't
tell me whether it's the engine or the flat tires. Try a better
description that does NOT include your guess as to the cause. What
part of TCP/IP does not work?
>If I run DHCP - I do not get an address from the AP (Antoher Linksys).
What other Linksys? Make, model, version, firmware? Is it acting as
an access point, client, repeater, or what? Just what are you doing
to "run DHCP"? DHCP is not a program. It's a service that is enabled
or disabled and is run by the operating system. Better description of
what you're doing.
>(If I connect with my laptop the the AP, it works great).
What laptops? Wireless or wired? What AP? Which AP (there are
apparently two)? How do you connect?
>If I run static IP on the GS54, I still dont get any connection.
Don't use static IP's on the LAN side. Use DHCP. That will tell us
if you have a connection.
>If I telnet to the 54GS and do ping to the AP, I get "host
>unreachable".
Host unreachable means that the IP addresses are not set properly.
It's difficult to tell without knowing the IP setup. See fill in the
blanks on the IP's above and add the 2nd AP to the list of IP's. If
you're using DHCP to set the IP addresses on the 2nd AP, then supply
what IP's are returned, even if it's 0.0.0.0 or 169.254.xxx.xxx.
>If I do it from the laptop, I get OK ping.
What laptop? Maker, model, wireless client maker, model, version,
operating system.
Do what from the laptop? What is "it"? What are you doing when you
try "it"?
>Then I tried to setup my 54GS as AP, and connect to it from the laptop.
>It worked fine.
I thought it was acting as an AP all this time? An AP is nothing more
than a wireless AP connected to an ethernet router. In this case,
it's all in one box but can be in two seperate boxes. How are you
using the WRT54GS v4 as an AP? How is the connection made via
wireless? Do you get a valid IP address from the AP? If so, you've
apparently still have the DHCP server enabled in the router section.
That means that you may have two DHCP servers running at the same
time. Bad idea. If you're going to convert the WRT54GS v4 into an AP
only, please disable the DCHP server.
>As I do not have my own internet backbone, I have not tried setting the
>54 up as AP, with Internet connectivity, and check that that works.
I don't think anyone in this newsgroup owns an internet backbone. They
cost millions of dollars to build and tend to more than what the
average user can afford. You could invest in an ISP, but that would
still be overkill. What do you mean by your "own internet backbone"?
>From my analysis, it seems to me that something inside the 54 is
>broken, so it cannot create the connection to the WAN. This I still
>have to find a way to test.
From my analysis, I have only partial clues as to what you're trying
to accomplish and what you have to work with. There doesn't seem to
be much of a problem with your troubleshooting abilities. What's
lacking is your abilities to describe the problem, the equipment, the
symptoms, and the testing. My questions above are to illustrate the
questions I'm asking myself when I read you posting. I suggest you
*NOT* try to answer them. Instead, start over with a description of:
1. What are you trying to accomplish. This is totally missing. A
one sentence description will suffice.
2. What do you have to work with? That means hardware, software,
versions, etc. Numbers, not partial truncated descriptions.
3. What have you done so far and what happened? That means describe
your test setup and what actually happened, even if you know the
results are "weird".
>Any ideas on how I can diagnosis this further with commandline commands
>inside the 54?
Pardon my warped sense of humor but I noticed that we started with
WRT54GS, then shrank to 54GS, and now are down to 54. I don't really
care what designations you use to describe a single box, but since you
apparently have two access points, it would very handy if you would
consistently use the same designation or abrev.
>I have tried running a ifconfig - and it show me a lot of info I dont
>understand, but I cant see anything about errors in there.
Wait. Let me check my crytal ball. Ah, I can almost see the results
of ifconfig.... drats, you cleared the screen.
>Any ideas on how I can test this further - before I go out and buy
>another router (which is hard to find - especially the Linksys routers
>here in Denmark are all much newer than those that can run DD-WRT.)
I still can't determine what you're using for equipment and software.
I also can't determine what is not working.
It might be helpful if I recommended the exact DD-WRT version. Try:
|
http://www.dd-wrt.com/dd-wrtv2/down....23_wrt54gs.bin
This is v23 SP1 standard for the WRT54GS May 16, 2006.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558