25 replies
by a.gounder Accepted solution
by w2ktechman Accepted solution
the cable comes in from the coax, to the cable modem. Then it goes out in a LAN cable, hook that end up to your router.
setup your router per instructions, and connect all of the computers to the router.
If your dsl provider gives you 1 IP to use, give that IP to the router. Also, if you get a username/PW, those should be put into the router as well.
If your router (doubt it) does not have extra LAN ports, then you can purchase a hub (less than $20) to split the connection to all of the systems, or you can get a switch for a little more.
by a.gounder Accepted solution
by w2ktechman Accepted solution
by a.gounder Accepted solution
by w2ktechman Accepted solution
I do think that it may have a problem unless you are talking about the admin username/PW, in which case this is perfect.
Best to try a connection from a system that is all patched up, does the Internet come up?
by a.gounder Accepted solution
by w2ktechman Accepted solution
by a.gounder Accepted solution
by dumphrey Accepted solution
by a.gounder Accepted solution
by dumphrey Accepted solution
by cg it Accepted solution
didn't go through all the posts to see what else was said, but the Verizon Westell ADSL+2 wireless router/modem.
To get the wireless to work, you have to use the key provided by Verizon [on the documentation or on the bottom of the router] without the key, you can't connect wirelessly.
any router connected to the Westell must be on the same subnet as the LAN address of the Westell. That means the WAN port configuration is the Westell LAN [with the default gateway on the WAN port as the Westell router and ISP DNS]. Best to use a static address.
The router should be connected via straight thru ethernet [not crossover] to the Westell. For the router LAN, best to make it a different subnet that the westell subnet.
the whole configuration would look something like this.
Westell :
WAN addressing provided by ISP
LAN IP : 192.168.1.1 -254
mask : 255.255.255.0
Gateway: 192.168.1.1 [westell router address]
DNS ISP DNS
Linksys router:
WAN addressing static 192.168.1.3 or 4 or
Mask 255.255.255.0
gateway 192.168.1.1 [westell router]
DNS ISP DNS
LAN IP address 192.168.2.1 -254
mask 255.255.255.0
gateway 192.168.2.1 [linksys router]
DNS ISP DNS.
Clients behind the Linksys will get the linksys addressing and use the ISP DNS with the linksys as the default gateway.
clients behind the Westell will get the Westell addressing and use the ISP DNS with the Westell as the default gateway.
by dumphrey Accepted solution
by a.gounder Accepted solution
by dumphrey Accepted solution
them run a cable from one of the ethernet ports on the Westell to the WAN port on the linksys. You also may need to configure it all a little differently. In theory, the Westell should get an IP on its wan port from your ISP, and pass DNS info along to anything connected to its 4 ethernet ports. So, if DHCP is set up on the WEstell, it should give the linksys a dhcp address, dns info, and a default gateway. So, it follows that if you plug a computer into the linksys, it will pass dns and a new gateway to its DHCP clients. A client on the linksys would look just like the linksys to the Westell because of NAT configured in the linksys. And the Westell should support NAT out its WAN port as well, but it may not be configured. I did this at home with a cisco 870 and a linksys 5somethingG. I kmnow it can be done, but I have a feeloing I used RIP between them.
Its Friday afternoon, and Im ready to go home =) If my logic seems flawed let me know and Ill get back to you on monday. Ill try to look and see what i did at home.
by a.gounder Accepted solution
by cg it Accepted solution
before you go any further, please give us the configuration in this type of format.
Westell router
WAN address
subnet mask
default gateway
DNS
LAN address
subnet mask
default gateway
DNS
Linksys router
how did you connect it to the westell?
WAN address [static address on the westell subnet which is the actual IP address]
subnet mask
default gateway
DNS
Linksys LAN address
subnet mask
default gateway
DNS
without this information, everyone is just guessing
I will say this, the connection type on the Linksys router is wrong, you don't enter your user name and password and you don't clone the westell MAC address onto the Linksys router.
by a.gounder Accepted solution
by cg it Accepted solution
unless we know the configuration & addressing scheme you have for both routers, we're just guessing at what might be the problem.
configuration = if you changed the westell router to be just a modem, then we need to know that [least me] because the assumption is you've got 2 routers there.
when you connect 2 routers together via ethernet, you use a straight through type of cable. one end on the westell 4 port switch, the other end on the linksys WAN port [NOT LAN port].
After that, it's addressing which includes IP address, subnet mask, default gateway and DNS servers for both routers on all interfaces and also on the computer which is connected to whatever router. We also need to know what router the computer is connected to.
The Westell versalink wireless router is also the DSL modem, so it MUST be connected to the DSL line [there's really not way to switch it around because the linksys doesn't have a RJ11 port, but there are some who've tried.]
once we know the configuration and addressing, then we can look at it and make suggestions.
it's not very complicated to do, but rule # 1 if a configuration doesn't work, change it back to the default. you don't add another configuation to a configuation that doesn't work .
by a.gounder Accepted solution
Here is the configuration:
Westell Versalink DSL Modem IP Address: 192.168.1.1
Linksys IP Address: 192.168.2.1
Connection Type: PPPOE
DHCP enabled
Phone line RJ11 goes to the Westell router. I hooked up one end to Ethernet port and other end to Linksys WAN port. My computer connected through Linksys ethernet port.
This is what I configured in the Linksys router.
IP address is 192.168.2.1
I enabled PPPOE
Checked round button to keep alive connection
Enabled DHCP Server.
Under the MAC Clone, I entered Westell router MAC address.
Is this information enough? Please help me.
by cg it Accepted solution
here's the deal....
The Westell is your connection to the internet. you can set the Westell as either a modem or a router. If you want the Westell wireless function, it needs to be set as a router.
I'll assume the Westell is a router.
Westell
WAN port = public address x.x.x.x
if you have to log in to get an address or use a protocol to obtain an address you configure the Westell with the protocol they say to use and the user name and password. The router will then obtain a public address from your ISP along with a subnet mask, gateway address and DNS information. You'll need the DNS information to configure the linksys routers and client computers [if you use a static addressing scheme].
Westell LAN
you can configure whatever private addressing scheme you want. for the sake of simplicity, I'll use the standard class C
Westell router address 192.168.1.1
subnet mask 255.255.255.0
If you use DHCP then DHCP will provide clients connecting directly to the Westell router either through the 4 port switch or wireless connection an IP address, subnet mask, default gateway and DNS servers. Note: The default gateway for clients on the westell router is the westell router LAN address. DNS servers is always your ISP DNS server addresses.
Linksys Router [connected to the Westell LAN 4 port switch]
WAN port [static address only]
IP address 192.168.1.10
subnet mask 255.255.255.0
default gateway 192.168.1.1 [westell router lan address]
DNS is ISP DNS servers.
The Linksys router is on the Westell LAN so it must have a Westell LAN address and the same subnet mask.
Linksys LAN
IP address 192.168.2.1 [different subnet than the Linksys WAN port]
subnet mask 255.255.255.192 [which gives you 62 host addresses available
default gateway is the Linksys LAN address 192.168.2.1
DNS is ISP DNS server.
note: if you use DHCP on the linksys LAN then you must configure DHCP [you can not use the default values. Therefore you use the 192.168.2.1 subnet the 255.255.255.192 subnet mask, specify the Linksys LAN port [192.168.2.1 address as the default gateway and use the ISP DNS servers.
clients which then connect to the linksys router via the 4 port switch would then obtain the proper subnet addressing,default gateway and DNS servers to use.
I would reset the Linksys router to default values so that you get rid of the Westell router MAC address. The linksys does not have to have the westell MAC address if it is not being used to obtain your public address from your ISP.
If you have configured your Westell router to only be a modem [non routing fuction], then you might have to clone the Westell MAC address to the Linksys. This is only if your ISP registers the MAC address for subscribers and only allows that MAC address to obtain an address for Internet Service.
DNS is ISP DNS server
by dumphrey Accepted solution
by el.crowe.pasa Accepted solution
Sadly, jacking around with my buddies setup did not prove successful. there are many rational inherent ways to configure such a setup, most of the "IT" people mentioned ideas or solutions they read in an O'Reilly PDF for A+ Cert. One guy did mention his working setup, and how he things RIP protocol might have been involved. Well.....guess what????? yea.
OK, Im not trying to be rude to the community that extended their time and effort trying to help you. Here's a lil bit of fat I put on my head last night I'd like to share with you.
1. No two routers can both be DHCP enabled.
2. trying to config 2 routers with incompatible firmwares isnt something you want to tackle, not even macgyver should waste his time.
research RIP protool and NAT and what that lil "METRIC" checkbox does.
3. research Mesh Hopping Networks/ Mesh Connectivity Layer (MCL)
And so, dont burn up all that fat on your head trying to sort WANs and DESTINATIONS and LOCAL parameters, its really really simple crap....on the surface. But I believe that the inner conflicts created with the multiple DHCP,ACK,metric,TACCOS and all that other stuff makes this super annoying. Your solution involves simple router protocols, MCL, and umm....cisco.
Its been my pleasure-
andeanlogic
by mliang3 Accepted solution
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending