Freddy
join:2005-05-17
Arlington, VA
 ·Verizon Online DSL
1 edit | reply to vadimtsarik
Re: New firmware for Westell 327W - version 4.4.3
vadimtsarik,
I'm running Vista Home Premium and thus couldn't find the setting for ICMP you referred to for Windows XP. It's somehow different in Vista. Instead, I turned off the Vista firewall. That act enabled the version 4.4.3 firmware to display correctly the connection type and some other network information.
However, the WEP information is still not displayed correctly. One page shows WEP as enabled, but a different page shows it as disabled. In fact, it's running and working properly.
So, it's clear that some of the information is displayed incorrectly by the new firmware in the VersaLink because of one or more settings in the firewall.
I'll do some more research on this issue and post back. In the meantime, perhaps someone else can beat me to the punch and chime in with the steps needed to fix this in Vista.
Some preliminary research on the Internet about ICMP in Vista shows the following:
"By default, incoming ICMP echo requests are allowed through the firewall, and all other ICMP messages are blocked. This is because the Ping tool is routinely used to send echo request messages for troubleshooting purposes. However, hackers can also send echo request messages to locate target hosts. You can block echo request messages (or unblock other ICMP messages if they're needed for diagnostic purposes) through the Advanced tab on the basic configuration interface."
I have no idea whether that's correct. It's what I found.
Freddy
|
|
Freddy
join:2005-05-17
Arlington, VA
·Verizon Online DSL
1 edit | All,
I found the following on the Internet:
This is from microsoft Vista TechCenter:
-----------------------------------------------
Nobody can ping my computer
A common step in troubleshooting connectivity situations is to use the Ping tool to ping the IP address of the computer to which you are trying to connect. When you ping, you send an ICMP Echo message (also known as an ICMP Echo Request message) and get an ICMP Echo Reply message in response. By default, Windows Firewall does not allow incoming ICMP Echo messages, and therefore the computer cannot send an ICMP Echo Reply in response.
Enabling incoming ICMP Echo messages will allow others to ping your computer. However, it also leaves your computer vulnerable to the types of attacks that use ICMP Echo messages. Therefore, we recommended that you enable the Allow incoming echo request setting temporarily, and then disable it when it is no longer needed.
To enable ICMP Echo messages, create new inbound custom rules to allow ICMPv4 and ICMPv6 Echo Request packets.
To enable ICMP Echo Request for ICMPv4 and ICMPv6
1. In the Windows Firewall with Advanced Security snap-in, click Inbound Rules in the tree, and click New Rule in the Actions Pane.
2. Click Custom and click Next.
3. Click All programs and click Next.
4. For Protocol type, select ICMPv4.
5. Click Customize for Internet Control Message Protocol (ICMP) settings.
6. Click Echo Request, click OK, and then click Next.
7. Under Which local IP address does this rule match? and for Which remote IP address does this rule match click either Any IP address or These IP Addresses. If you click These IP addresses, specify the IP addresses and click Add, then click Next.
8. Click Allow the connection, and then click Next.
9. Under When does this rule apply?, click the active profile, any or all profiles (Domain, Private, Public) to which you want this rule to apply, and then click Next.
10. For Name type a name for this rule and for Description an optional description. Click Finish.
11. Repeat steps for ICMPv6, selecting ICMPv6 for Protocol Type instead of ICMPv4.
---------------------------------------------------
In the screen where you click 'Echo Request', I had to go back and select all of the settings (messages) to make it work, but after it was done, WinVROC could ping the servers again, and those responding to it showed green as usual.
To open Windows Firewall with Advanced Security, use the following steps:
1. Click the Start button, and then click Control Panel.
2. In Control Panel, double-click Administrative Tools.
3. In Administrative Tools, double-click Windows Firewall with Advanced Security.
Regards,
Marko
----------------------------------------------------------
By Freddy: From that information, I think I'll leave my firewall alone. It seems that allowing incoming Echo ICMP requests can open up your computer to attack. At least that's the way I understand it. There must be a better way.
Any comments from all this information?
Freddy |
|
Pathfinder
Dazed Confused
Premium
join:2000-03-26
Mount Vernon, NY
·Verizon Online DSL
| reply to vadimtsarik
said by vadimtsarik  :said by Pathfinder :It seems to have a problem viewing the network. ... It won't even show the station's name. My findings indicate that connection type is detcted as 'Unknown' for computers with firewalled incoming Echo ICMP requests. I think Windows XP is by default set up to not allow incoming Echo requests. Here's what worked for me: 1. Login to Windows as administrator (i.e. make sure you have administrative rights) 2. Go to Control Panel -> Windows Firewall -> Advanced tab and click 'Settings' button for ICMP 3. Check 'Allow incoming echo request' and click OK couple of times to close out the dialogs. Hopefully this'll do the trick for you. At any rate, this helped me to get the new firmware see my network correctly. I noticed that if new firmware can't detect connection type it seems to assume IP allocation as 'Static IP'. The other thing is that offline devices are still displayed, but I'm guessing this is due to DHCP server lease settings (by default 1 day?). I believe that this may make you visible and vulnerable. However, in the Advanced Settings under Network Connection Settings highlight Local Area Connection and hit the Settings button to the right. Then under ICMP click Allow ICMP Echo Request which will only open it to the local network.
I think. |
|
ImaDuffer264
Premium
join:2003-11-05
Mercer, PA
|  reply to brugar
What if anything will I gain by upgrading this firmware?
I have a model A90-327W15-06 revision E "made in China" that I received from Verizon when I got VOL at my old house about 4 years ago. It has not yet let me down and I'm still using the original firmware that it was supplied with (ver 03.00.63a).
Now, I downloaded the new firmware but I'm unsure I want to install it unless someone can give me a compelling reason to. It's like my dad always used to say "if it ain't broke don't fix it"  . |
|
Jodokast96
R.I.P Bassman442
Premium
join:2005-11-23
Erial, NJ | It really doesn't add anything other than a new interface. If you are using it wirelessly, it will offer WPA in addtion to WEP. |
|
andre2
join:2005-08-24
Brookline, MA
| reply to ImaDuffer264
I experienced a significant improvement in DSL transceiver stats (higher downstream margin and/or lower downstream transmit power) with the previous version of the firmware (3.02.01). I seem to have experienced another slight improvement with the latest version as well. Of course this is only important if your stats are borderline at present. |
|
acuariano
Premium
join:2004-10-27
Woodside, NY | reply to brugar
if somebody could the previous firmware for A90 westell versalink 327W ...this new 443 is very buggy.. |
|
Freddy
join:2005-05-17
Arlington, VA
·Verizon Online DSL
2 edits | reply to Freddy
All,
I did some more google searching, and found a site that contains detailed instructions for enabling ICMP Echo Requests in Vista. It is here:
»nic.phys.ethz.ch/readme/226
Vista permits a user to allow ICMP Echo Requests for just the Local network, as well as for the Public and one other, which I don't recall. I just finished setting mine to allow ICMP for Local network only. After that setting, my VeraLink is detecting my connections correctly.
I'm assuming that setting it to allow ICMP Echo Requests only for the Local network will protect me from any attempts to hack into my system from the outside (Internet). There is no one on my Local network that has any idea about how to hack (wife, son), ha, ha ha. If this assumption is incorrect, please post that fact.
For those using Vista, take a look. You can't go wrong with those instructions.
Freddy |
|
Dehumanization
@verizon.net
| reply to brugar
I downloaded the file and it says it is an .upg file. How do i turn it into an .exe or to open it? On this forum it shows it has an icon, with mine it is just a blank folded sheet and it tells me i have to pay for a program to open it. Is there any way i can use this without paying? |
|
Bullet2k4
join:2006-02-10
New York, NY | update manually in the modem browswer.
192.168.1.1 |
|
Dehumanization
@verizon.net | reply to brugar
OK it says i need a user name and password? How do i find out what they are? |
|
BigBoyBilly
join:2003-02-12
Covina, CA | Try the defaults.. username = admin and password = password
 |
|
AB
Premium
join:2006-04-04
Leesburg, VA
| reply to Bullet2k4
Thanks much for this info!
I'm currently running a 'Transciever Revision 4.2.0.11' for the Westell 6100, C90-6100-15-06, from this link:
»netservices.verizon.net/portal/l···aLinkFix
(Installed maybe a little over a year ago.)
Is the '.upg' file from the quoted westell.com link newer than what I'm running, can anyone tell me?
I can't see where I can make a specific determination as to what exactly revision version number that is.
Though as I recall from a prior experience, if the version is no newer I'll get a warning message of some type when trying to install it, is that correct?
Thanks. |
|
Dehumanization
@verizon.net | reply to brugar
The user name admin and password password does not work. So how do i find out what the user password is now?  |
|
kevinfritz
join:2000-08-06
Bel Air, MD
| You must have changed it when you set it up for the first time, or perhaps later. Your only option at this point would likely be to do a hardware reset (button on the back of the modem), which should erase all user configured settings, including your custom password - the login and password should go back to the defaults. Note that you'll have to reconfigure your modem with Verizon also, which means entering your user login and password for the Verizon service itself (at least if you're on PPoE, don't think DHCP needs that).
Is it possible you changed your modem login and password ot match your Verizon login and password? I worked on someone 327W and the defaults did not work to get to the firmware, but his Verizon login/password did... |
|
bluepoint
join:2001-03-24
| reply to AB
Is the '.upg' file from the quoted westell.com link newer than what I'm running, can anyone tell me?
Yes, the version in the westell link Bullet2k4 posted for 6100 firmware is 4.04.03.00 and the transceiver version is 7 something. |
|
AB
Premium
join:2006-04-04
Leesburg, VA
| said by bluepoint :Is the '.upg' file from the quoted westell.com link newer than what I'm running, can anyone tell me?
Yes, the version in the westell link Bullet2k4 posted for 6100 firmware is 4.04.03.00 and the transceiver version is 7 something. Thank you very much! |
|
bluepoint
join:2001-03-24
| said by AB :said by bluepoint :Is the '.upg' file from the quoted westell.com link newer than what I'm running, can anyone tell me?
Yes, the version in the westell link Bullet2k4 posted for 6100 firmware is 4.04.03.00 and the transceiver version is 7 something. Thank you very much! You're welcome! Did it blew on you yet?  |
|
AB
Premium
join:2006-04-04
Leesburg, VA
| said by bluepoint :Did it blew on you yet? I haven't installed it yet. Is there possibly going to be a problem?
I don't wanna hear that . . . . |
|
bluepoint
join:2001-03-24
| said by AB :said by bluepoint :Did it blew on you yet? I haven't installed it yet. Is there possibly going to be a problem? I don't wanna hear that . . . . Nah, just let'r rip! It's been 4 days since I upgraded the firmware and it's operating smoothly. According to the pdf, the firmware is MS certified.
Certifications
• EMC FCC, Part 15 Class B
• CAN/CSA 22.2 60950
• UL 60950, 3rd Edition
• UL
• CSA
• ACTA 968-A
• Industry Canada CS03
• CE
• WHQL |
|
