| reply to vito
Re: fvs318- beta firmware Hey my router won't take it, when i click upload nothing happens what to Doooooooooooooooooo ????????
Jj
--
Anything Possible |
|
 vito
join:2001-11-28
Gilbertsville, PA | That’s weird; I have not had issues with flashing the firmware.
Poss. bad file maybe?
How about flashing it with 1.0 then the new firmware. (beta) |
|
 JimThePCGuyFormerly known as schja01.Premium,MVM
join:2000-04-27
Morton Grove, IL
| reply to jj_in_mood
said by jj_in_mood:
Hey my router won't take it, when i click upload nothing happens what to Doooooooooooooooooo ????????
Jj
My bin file is EXACTLY:
455 KB (466,576 bytes) and it loads.
Is yours ??
James
--
Damn the Torpedoes, Full Speed Ahead !
[text was edited by author 2002-08-08 15:52:37] |
|
| reply to jj_in_mood
I had the same problem. Try enabling remote management, and doing the upgrade from another computer over the internet. I know it's ugly, and awkward if you don't have a seperate internet connection available, but it's the only thing that worked for me.
And the beta firmware didn't fix that :P
- CyberShoe |
|
|
|
JimThePCGuyFormerly known as schja01.Premium,MVM
join:2000-04-27
Morton Grove, IL | reply to jj_in_mood
said by jj_in_mood:
Hey my router won't take it, when i click upload nothing happens what to Doooooooooooooooooo ????????
Jj
What browser and version are you using. IE needs to be fairly up to date to be able to do uploads. If you have Netscape try using that browser instead ??
--
Damn the Torpedoes, Full Speed Ahead ! |
|
 Link LoggerPremium,MVM
join:2001-03-29
Calgary, AB
kudos:3
 ·Shaw
| Now that the FVS318 firmware supports syslog could someone please send us some samples of the syslog logging output for evaluation of building a version of Link Logger which supports the FVS318?
Please email the samples to mcneillb@LinkLogger.com and of course the samples will be kept in strictest confidence.
What we are especially interested in seeing is how it handles different protocols (TCP, UDP, ICMP, IGMP, etc), traffic and non-traffic messages.
If needed we can send you a very simple syslog sniffer which will record the traffic received on your syslog port such that you can copy and paste it in an email to us.
Thanks
Blake
mcneillb@LinkLogger.com
»www.LinkLogger.com |
|
sga534741Premium
join:2002-07-22
Virginia Beach, VA | Broken syslog output At this point, the syslog output is not very useful. (1) It only records successful connections; (2) it only records the source IP address, source port, and destination IP address; and (3) it records incoming connections backwards. This is for the j1.01 beta firmware. Here is an excerpt from the message I sent to betabugs@netgear.com...
The router appears to syslog all connections as if they were outbound. Incoming connections show the source port number and IP address in the destination fields. However, the internal log and notification e-mails show the information correctly. Here is an example of an incoming SMTP connection:
- internal: Wed, 08/07/2002 22:24:47 - Ports Allow: SMTP - Source:65.120.48.2, 45600, WAN - Destination:68.15.147.130, 25, LAN
- syslog: Aug 7 22:24:47 router router [156]:TCP(45600) Dest IP: 65.120.48.2 Src IP :192.168.0.102
As you can see, the syslog entry has the source and destination backwards. |
|
