| Using the Westell 6100 with a Wireless Router This is a continuation of a past thread to which replies are no longer allowed:
»[modem/router] How do I swith my Fairpoint modem to bridge
I am trying out Fairpoint as an ISP for 30 days and have used Comcast up to now. The Comcast modem is just that - a cable modem and it works well with my Netgear WNDR3700 - a wireless router. But the Westell 6100 is a modem/router combo, whose DHCP function generates the same (conflicting) set of IP addresses (192.168.1.x etc.) and as a result, I can't use it for my wireless/wired network.
I've read other posts and solutions for this problem but haven't gotten to a real solution yet. I suppose bridging the 6100 would allow the 3700 to work in PPPoE mode, take over the DHCP function and generate the IP addresses as it always has in the past.
Wayjac, in the thread above shows how to do this but if the 6100 loses its ability to be accessed by the 192.168.1.1 address, how would I access it if I want to go back to using it in PPPoE mode?
And in the above thread, wayjac hints that there may be another way to solve this problem. I'm curious as to what this might be.
Appreciate any help from wayjac or anyone else who has solved this problem.
TIA
gemad9 |
|
 wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1
1 edit | said by gemad9:the Westell 6100 is a modem/router combo, whose DHCP function generates the same (conflicting) set of IP addresses (192.168.1.x etc.) and as a result, I can't use it for my wireless/wired network If you change the 6100 default ip address to 192.168.2.1 that will allow you to use the router as you did with cable without putting the modem in bridge modesaid by gemad9:if the 6100 loses its ability to be accessed by the 192.168.1.1 address, how would I access it if I want to go back to using it in PPPoE mode? When the modem is in bridge mode it's dhcp server is disabled to gain access the computer that is used must have a unique ip address that is within the subnet the modem uses |
|
| Thanks for the reply.
On the 6100, 192.168.2.1 is the modem's default Public IP Address. Are you saying that I should change the Private IP address to that as well?
What exactly would I type into the browser to gain access to a bridged modem? Can you give me an example?
Thanks again |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
 ·SONIC.NET
·Pacific Bell - SBC
| said by gemad9:On the 6100, 192.168.2.1 is the modem's default Public IP Address. Are you saying that I should change the Private IP address to that as well?
The "public" IP address is what is assigned to the device acting as the PPPoE agent; assuming you have a PPPoE connection. If the modem is assigning 192.168.2.1 to the router, there should be no conflict of the sort which Netgear routers are known to balk at.
What exactly would I type into the browser to gain access to a bridged modem? Can you give me an example?
Alas, I have a router which, though set up for DHCP (my ISP does not use PPPoE DSL), does not pass private range IP addresses across the gateway. In my case, I have found a trick that allows me to access the bridged modem, at the expense of breaking the Internet connection. Normally not a problem because I am only accessing the modem for diagnostic purposes. And, while I lose the ability to access the Internet, I don't lose my ADSL2+ link to the DSLAM.
I change my router setting from DHCP (obtain IP address from the ISP) to Static. I set the computer NIC to an IP address within the range of the modem IP subnet, and restart everything. As I said, this will allow access to the modem GUI at the expense of killing the Internet access. I am up past bedtime; but I can give a blow-by-blow description of how I do it later, if you are interested.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| The "public" IP address is what is assigned to the device acting as the PPPoE agent; assuming you have a PPPoE connection. If the modem is assigning 192.168.2.1 to the router, there should be no conflict of the sort which Netgear routers are known to balk at.
There are ways to access the modem interface which require additional hardware to allow you to bypass the PPPoE tunnel, which is the part that makes contact with a bridged modem impossible.
How about a reset (reset button on the back of the modem)? Wouldn't that bring the modem back to factory settings as a PPPoE DSL modem?
I can give a blow-by-blow description of how I do it later, if you are interested.
Thanks
gemad9 |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | said by gemad9:The modem generates two IP address groups. One is called a "Private LAN" and the DHCP function generates addresses from 192.168.15 through 47. The other is a "Public LAN" and the generated address is a single one - 192.168.2.1. I was asking whether I should try to edit the Private LAN series to generate 192.168.2.xxx....? The public lan page is used with static public addresses
Below is a picture of the westell page where the modem ip address can be changed
|
|
|
|
| The Netgear defaults to 10.0.0.X IP addresses no matter what modem IP address I use. I've decided to turn off DHCP in the Netgear router and use it as an access point/switch. That solves my networking problem.
Thanks again for the help. I appreciate it.
gemad9 |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
1 edit | reply to gemad9
said by gemad9:Are you sure that additional hardware is needed to access a bridged Westell 6100? If you are, do you know what hardware is needed?
There are a couple of FAQs at DSLR outlining the necessary steps:
»SBC DSL FAQ »How do I access the modem GUI thru a router - advanced methods?
»SBC DSL FAQ »How do I access the modem GUI thru a router - advanced methods?
As noted, some of the methods will require additional hardware.
I can give a blow-by-blow description of how I do it later, if you are interested. I am. Please do explain it if you don't mind.
The router configured for nomal operation.
For some reason, this router won't go to the modem, as older routers, with bridged modems in the loop (as in cable Internet service). So I change the router to Static IP, and give it 192.168.1.64; should be an IP address in the subnet range of the modem IP address. I set the subnet mask to match the modem subnet mask: 255.255.0.0, and I set the Gateway IP address to the modem IP address:
The router configured to access the modem.
Then I reboot the router. I don't have to change anything on the computer. When the router is back, I just point it to the modem IP address.
For reasons that aren't clear to me, I have to reset the TCP/IP stack when I restore the router settings. I think it is a bug in the router firmware; it is dicey when acting as a DNS Proxy, as well. Maybe the firmware bug is what keeps me from reaching the modem in DHCP. Mode. This method should work just as well for PPPoE connections, because the router is in static IP mode on the WAN port while doing this.
Hmmm. Should have included a screen shot of the modem page:
My DSL modem statistics.
The DNS issue appears to only affect the computer which makes the configuration changes to the router; as long as you wait for the restoration of the normal state before mucking around with other computers on the LAN.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | reply to gemad9
said by gemad9:The Netgear defaults to 10.0.0.X IP addresses no matter what modem IP address I use The n series netgear routers use 192.168.1.1 as the default ip address
The netgear will automatically change it's lan ip address if it's wan port is allocated a ip address that is within the netgear's default lan subnet
The netgear will also perform a browser redirect to a page that will display what the new ip address is
said by gemad9:I've decided to turn off DHCP in the Netgear router and use it as an access point/switch You should change the lan ip address of the netgear to a unique ip in the modems subnet doing this will allow easy access to the netgear's configuration pages
Below is a picture of the netgear page where the netgear ip address can be changed
|
|
1 edit | Changed the lan ip address to 192.168.3.1. That worked well.
One more question - are there any disadvantages to changing the ip address in the Netgear router (as I've done) rather than bridging the Westell modem/router?
Thanks
gemad9 |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | said by gemad9:are there any disadvantages to changing the ip address in the Netgear router (as I've done) There are no disadvantages that I'm aware of
If I'm not mistaken you have reconfigured the router so that it can be used as a access point
The lan ip address of the netgear should be a unique ip that is in the modems subnet if you want easy access to the netgear's configuration pagessaid by gemad9:rather than bridging the Westell modem/router? Bridging the westell is a completely different configuration
Trying to compare bits and pieces of one configuration with a different configuration is pointless in my opinion |
|
| In the end, I tried your original suggestion and am allowing the Netgear's DHCP function to assign the IP addresses and also to function as a wireless transmitter. It works! No conflicts. The key was changing the Router IP address to a unique IP (192.168.3.1) as you suggested and the rest fell into place. The router thinks that 192.168.1.1 coming from the Westell 6100, is a valid WAN IP address. Thanks again. I'm all set.
gemad9 |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | said by gemad9:In the end, I tried your original suggestion and am allowing the Netgear's DHCP function to assign the IP addresses and also to function as a wireless transmitter This configuration will work just fine
If you ever need to forward ports you must forward the ports on the westell and the netgearsaid by gemad9:The key was changing the Router IP address to a unique IP (192.168.3.1) as you suggested and the rest fell into place. The router thinks that 192.168.1.1 coming from the Westell 6100, is a valid WAN IP address. Thanks again. I'm all set. You should create a bookmark/favorite in your web browser for the westell and the netgear unless you are certain that you will not forget the westell/netgear ip address |
|
