| reply to sashwa
Re: Verizon Westell 7500 - How do I set it to bridge mode? Yup, Verizon DSL. I just thought I would get more help out of the Westell Forum since the issue is really a hardware one instead of an ISP issue. |
|
|
|
 sashwaPixie Cat Crunchin' n Foldin'Premium,Mod
join:2001-01-29
Alcatraz
kudos:14
2 edits | Either forum (Vz DSL or Westell) would have been okay. Let's see if we can get you some help in Verizon.
Moved in from Westell. |
|
JohnAPremium
join:2003-09-16
Pittsburgh, PA
3 edits | reply to seeingwhite
You can always access the modem/routers, while in bridge mode, by direct connecting a PC to them that is set to a static IP in the modem's subnet. Say 192.168.1.21, 255.255.255.0, 192.168.1.1. The hangup comes from the DHCP server not running in the 7500, so even a direct connected PC doesn't get an IP. It's a pain in the neck, but much easier than changing the settings on multiple pieces of equipment.
For the PC you access the modem with:
You can always create a new connection, in network connections, with the static IP, and keep it in the disabled state. When you need modem access, disable the regular connection, enable the static connection, change the wire from your router to the modem. Done in the modem, just reverse it. |
|
| said by JohnA:You can always access the modem/routers, while in bridge mode, by direct connecting a PC to them that is set to a static IP in the modem's subnet. Say 192.168.1.21, 255.255.255.0, 192.168.1.1. The hangup comes from the DHCP server not running in the 7500, so even a direct connected PC doesn't get an IP. It's a pain in the neck, but much easier than changing the settings on multiple pieces of equipment. For the PC you access the modem with:
You can always create a new connection, in network connections, with the static IP, and keep it in the disabled state. When you need modem access, disable the regular connection, enable the static connection, change the wire from your router to the modem. Done in the modem, just reverse it. JohnA, thanks for taking the time to reply. As far as your suggestion, I had been doing essentially the same thing that you suggested. But doing this every time I want to check the modem's transceiver statistics got old very fast.
The bigger issue seems to be that it should be possible to access the modem even in bridged mode, by simply navigating to the modems LAN IP. Unfortunately, I haven't figured out how, yet. |
|
 mb
join:2000-07-23
Washington, NJ
 ·Verizon Online DSL
 ·Callcentric
| said by seeingwhite:The bigger issue seems to be that it should be possible to access the modem even in bridged mode, by simply navigating to the modems LAN IP. Unfortunately, I haven't figured out how, yet. When the modem is in the bridge mode, it cannot have an IP address. |
|
JohnAPremium
join:2003-09-16
Pittsburgh, PA |
I think he means the interface IP, which is still available.
I am confused as to what he's doing, as he first said he was resetting the modem and changing his router to go through it. Then he claimed he was doing what I said, which is completely different. Oh, well.
|
|
| said by JohnA:I think he means the interface IP, which is still available. I am confused as to what he's doing, as he first said he was resetting the modem and changing his router to go through it. Then he claimed he was doing what I said, which is completely different. Oh, well. This thread was split off from the orginial by a MOD. Let me clarify:
1) I prefer to run the modem in bridge mode and allow my pfsense firewall/router do the PPPoE. This works fine, however, I can no longer access the modem's web interface from my LAN. The only way I have been able to do it is through the suggestion by JohnA. This is not a long-term solution for me, though.
2) Since I could not figure out how to access the web interface from my LAN while in bridged mode, I ended up changing my network setup back to the modem doing PPPoE and pfsense getting a DHCP address from the modem. The allows me to still access the modem's web interface (obviously) from the LAN. The problem with this setup is that I lose some functionality in pfsense such as DDNS.
Summary, I want to be able to bridge the mode to my pfsense firewall as mentioned in #1, but I am currently setup like #2 until I can find out what is keeping me from accessing the modem's web interface when setup like #1 (bridge).
I hope that clears it up. And thanks for the replies guys.
--
nTelos Portable Broadand user's forum: »ntelosusers.freeforums.org |
|
JohnAPremium
join:2003-09-16
Pittsburgh, PA
3 edits | As for me only, I understand. I personally wouldn't cripple the pfsense, just to be able to look through it, rather then just swap a PC connection to look around it.
There was 1 method of doing what you want, posted here in the past. I can't recall how it was done, or the poster that presented it. Maybe someone else has it book/site marked, but I don't.
.
edit: Here it is. ChrisDAT's post in this thread. Search to locate it was: modem stats router
»Get Modem Stats while Hooked Up to Router?
He hasn't posted in over 6 months, so I hope you can make heads or tails out of what you find from him. He posted it several times so looking farther into the search results may produce a second iteration of the same information, stated in a different way. I stopped at the first instance.
His profile shows a recent log in here. If you get stuck try IM to him.
The premise, as I understand it is: You make the PPPoE connection out of the router backwards into the switch of the router/ out of the switch into the LAN port of the modem. That makes the modem's interface available on the switch to the connected PCs. The PCs look directly at the interface to see the modem, while all their other traffic goes through the router, where they get their IPs.
Let us know how it works out. |
|
| JohnA,
Thanks for that link. It looks like he was trying to use the same subnet for the modem and router. I am using different subnets, which according to the thread, should work without further configuration.
My modem: 192.168.1.X
my pfsense firewall: 192.168.2.X
So it looks like I'm back to square one, especially since I should be able to access 192.168.1.1 without any adjustments. In other words, it should "just" work. *sigh*
--
nTelos Portable Broadand user's forum: »ntelosusers.freeforums.org |
|
