| Westell 6100 Network Device Detection I have a Westell 6100 that I'm using with a Linksys WRT54G2 behind it. I was wondering why the name and connection type of the Linksys doesn't show up most of the time?
• No, there's nothing wrong with my connection.
• Yes, I understand that this doesn't really matter.
It's more of a curiosity if anything. I have seen it report the name and connection type before. I don't know what I changed that made it stop. Here's a screenshot of what I see.
 |
|
 nwrickertsand groperPremium,MVM
join:2004-09-04
Geneva, IL
kudos:7
 ·AT&T U-Verse
| Is the Linksys getting its WAN IP using DHCP (might be described as getting it automatically)? Or have you assigned its IP statically?
It might also depend on how the linksys is doing the DHCP.
--
AT&T Uverse; Zyxel NBG334W router (behind the 2wire gateway); openSuSE 11.3; firefox 3.6.13 |
|
| Well, here's a screenshot of the detection page with the Linksys set to DHCP.
And here it is with the Linksys set to Static (192.168.1.2).
I rebooted the router and modem before checking each time. I'm not sure why the modem still lists it as being connected through a static IP under DHCP. Any ideas on what else I could try or look into? |
|
 wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | Have you set a host name for the internet port of the linksys
When the linksys internet port is a dhcp client it will tell the dhcp what it's host name is
Most all dhcp clients do this
When the linksys internet port has a static ip address it will only check to see if it's ip address is unique
Most all static clients do this |
|
| I tried setting a host name for the WAN side of the Linksys—no change. I then tried resetting the modem and router. This is what I see when directly connected to the modem:
After disconnecting from the modem and connecting to the router (The router is set to grab an IP via DHCP):
And after rebooting the modem:
Is this something wrong with DD-WRT? or a misconfiguration? or something else entirely? |
|
nwrickertsand groperPremium,MVM
join:2004-09-04
Geneva, IL
kudos:7 Reviews:
·AT&T U-Verse
| said by Mendayen:Is this something wrong with DD-WRT? or a misconfiguration? or something else entirely?
This is the first time that you have mentioned that you were using DD-WRT.
I believe that DD-WRT is linux based.
My current router always gets a name for Windows boxes. But it doesn't always get a name for linux boxes. It does get the name of my linux desktop, which I have configured to assign an IP address the traditional way (the "ifup" method, using "ifconfig" with dhcp. It does not get the name of my laptop when booted to linux. The laptop use NetworkManager to handle the WiFi. The difference seems to be that the "ifup" method calls "dhclient" (a dhcp client) with the "-H hostname" command line option.
As you said in the OP, this doesn't really affect anything.
--
AT&T Uverse; Zyxel NBG334W router (behind the 2wire gateway); openSuSE 11.3; firefox 3.6.13 |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | reply to Mendayen
said by Mendayen:Is this something wrong with DD-WRT? or a misconfiguration? or something else entirely? I don't think there is anything wrong with ddwrt
When you connect the internet port of the ddwrt device to a lan port of the westell the westell can only detect the internet port of the ddwrt device
Any devices connected to the lan ports of the ddwrt device are hidden by nat
The westell uses dhcp and arp to detect identify devices connected to it's lan ports |
|
| reply to nwrickert
Ahh, I'm very sorry about that. Thank you very much for the information though! I really appreciate it. |
|
