WRT300N v.2 syslog problem

Hi,
On the Log page of the config program, the help file suggests that there is a form where I can enter a syslog target IP address, but i can't find it anywhere. Has anyone know how to make permanent event logging on my PC. Any ideas??? I have european WRT300N v.2. and Kiwi Syslog Deamon.

You can try to adjust the wireless settings on the router...Open the setup page and under the Wireless tab,Set the Radio Band to Standard-20MHz and change the Standard channel to 11-2.462GHz...Under the Advanced Wireless Settings..Change the Beacon Interval to 75,Change the Fragmentation Threshold to 2304,Change the RTS Threshold to 2304..Under the Security tab...Uncheck Filter Anonymous Internet Requests...Now,power cycle the router and check.. 

Similar Messages

  • WRT300N & Wireless G Adapter Problem Fix!!

    I'm posting this message again with a better "message subject" because I believe it will help a lot of frustrated purchasers of the WRT300N Router.  Please excuse the double post!!
    Unbelievable.  I cannot tell you how long I had to work on getting my wireless G adapter to recognize my new WRT300N router network!!  Very frustrating.  I tried just about every suggestion from all of you wonderful forum participants (just where is linksys tech support in all of this?) and just couldn't get the thing to work until.....I did a combination of things, one suggested here, and another on the Microsoft knowledgebase support site.  Here they are.  First, Microsoft says your wireless G cannot communicate with your WRT300N because the  RTS threshold and Fragmentation threshold settings are not the same.  If you have taken Linksys' suggestion to lower your advance wireless settings so RTS and Fragmentation are "2304", you must also change your wireless G card adapter RTS and Fragmentation settings to "2304", mine were defaulted much higher at 4906.  Then you should take the WONDERFUL advice of "Shoemaker2006" who posted the following back in July of 2006:
     "...I figured out that the wide band does not really cover the G range but only the N range sort of like a donut with the hole in the middle. When the settings are in mixed mode and wide band the G range is only covered on the outermost part of the G range next to the N range. When in wide band and only N mode the G range is not even addressed. To get the G strength you jave to have it in G mode only and Short band to address the G range. Also have it on channel 11 if possible to not have wireless phone problems. With these settings my network is rock solid (WRT300N + 3 WUSB54G adapters). As far as the N desktop adapter goes it probally will have issues in mixed mode since this is a Pre-N architecture router and the range is not N only. I would not suggest the router to anybody looking for N only speeds until the next firmware update which is specific to the N range problems.
    Thank you Shoemaker2006!  Changing my channel to 11 and selecting "G mode only" gave me the range I needed to make my wireless G card communicate with my WRT300N router.  Hope this helps some of you.  I won't even bother you with the 25 other things I tried because none of those changes worked.  So, match your card and routers RTS and Fragmentation threshold numbers, change the router to channel 11 and select "G mode only".  It works!!!

    set your gateway on the second to be the IP of the 1st router.  that should take care of it.

  • Cisco ASA 5585-X SSP-20 8.4(2) - TCP Syslog problem

    Hi,
    We have a firewall service environment where logging is handled with UDP at the moment.
    Recently we have noticed that some messages get lost on the way to the server (Since the server doesnt seem to be under huge stress from syslog traffic). We decided to try sending the syslog via TCP.
    You can imagine my surprise when I enabled the "logging host <interface name> <server ip> tcp/1470" on an ASA Security context and find out that all the connections through that firewall are now being blocked. Granted, I could have checked the command reference for this specific command but I never even thought of the possibility of a logging command beeing able to stop all traffic on a firewall.
    The TCP syslog connection failing was caused by a missmatched TCP port on the server which got corrected quickly. Even though I could now view log messages from the firewall in question in real time, the only message logged was the blocking of new connections with the following syslog message:
    "%ASA-3-201008: Disallowing new connections."
    Here start my questions:
    - New connections are supposed to be blocked when the the TCP Syslog server aint reachable. How is it possible that I am seeing the TCP syslog sent to the server and the ASA Security Context is still blocking the traffic?
    - I configured the "logging permit-hostdown" after I found the command and it supposedly should prevent the above problem/situation from happening. Yet after issuing this command on the Security Context in question, connections were still being blocked with the same syslog message. Why is this?
    - Eventually I changed the logging back to UDP. This yet again caused no change to the situation. All the customer connections were still being blocked. Why is this?
    - After all the above I removed all possible logging configurations from the Security Context. This had absolutely no effect on the situation either.
    - As a last measure I changed to the system context of the ASA and totally removed the syslog interface from the Security Context. This also had absolutely no effect on the situation.
    At the end I was forced to save the configuration on the ASAs Flash -memory, remove the Security Context, create the SC again, attach the interfaces again and load the configuration from the flash into the Security Context. This in the end corrected the problem.
    Seems to me this is some sort of bug since the syslog server was receiving the syslog messages from the SC but the ASA was still blocking all new connections. Even the command "logging permit-hostdown" command didnt help or changing back to UDP.
    It seems the Security Context in question just simply got stuck and continued blocking all connections even though in the end it didnt have ANY logging configurations on.
    Seems to me that this is quite a risky configuration if you are possibly facing cutting all traffic for hundreds of customers when the syslog connection is lost or the above situation happens and isnt corrected by any of the above measures we took (like the command "logging permit-hostdown" which is supposed to avoid this situation alltogether).
    - Jouni

    Hi,
    I FINALLY had the time to look at this issue as I was testing something else in our lab too.
    In short, here is what I did:
    I configured the TCP logging in the same way as in the original post
    I configured the TCP logging giving the commands in different order
    Did some other tests related to the proble
    Device used: ASA 5585-X
    Software: 8.4(2)
    Original Device and software : ASA 5585-X running 8.4(1)9
    Heres the above scenarions and what actually happened
    Original situation
    Before doing any changes the test firewall context in question is working normally and the log sent by UDP/514 is arriving to the Syslog server as usual.
    I now change the syslog to TCP by giving a command "logging host tcp/1471" (actual port being TCP/1470)
    The firewall immediatly starts blocking all connections going through it.
    I change the configuration to the correct port TCP/1470 after which log starts appearing in my realtime view on the syslog server. The firewall context in question is still sending only the message "Disallowing new connections" even though the TCP -port on the Syslog server is clearly reachable and the connection is active.
    After this I try to do the suggest "clear local-host all" command. This has no effect on the firewall context. No connections are getting through. No connections/xlates are formed on the firewall. I can only see the firewall doing DNS queries with its outside interface (related to another configuration).
    After this I try to start correcting the situation the same way as before. I add "logging permit-hostdown" command which has no effect on the situation. I remove all logging configurations and it doesnt have any effect on the situation.
    After this I activate UDP logging and can see the logs arriving on the syslog server but again I can only see "Disallowing new connections" message.
    In the end I have no other option (to my knowledge) other than to delete the Security Context and create it again with same interfaces and with the configuration saved to the Flash -memory of the ASA.
    After this the connections work like usual. (UDP logging in the saved configuration)
    Giving the configurations in different order
    After I've created the firewall again and all is working I have another try in configuring the TCP Syslog while giving the commands in different order.
    First I add the command "logging permit-hostdown" command
    Then I add the command "logging host tcp/1470"
    After this logs start arriving on the syslog server and connections work as usual. Seems giving the "logging permit-hostdown" first before any other configurations is the right way to go.
    Removing the "logging permit-hostdown" command
    After I saw that everything was working I tried to remove the "logging permit-hostdown" command and see what happens. Everything worked fine.
    Configuring wrong TCP port to "logging host" command
    I decide to try and change the TCP port used to a wrong one and see if anything happens. (logging permit-hostdown is active). Firewall works as usual. Naturally no logs can be viewed at the syslog server.
    Configuring the TCP Syslogging without "logging permit-hostdown" but with correct port
    Finally I tried to configure the TCP Syslogging on ASA with the correct TCP port without issuing the "logging permit-hostdown" command. Everything seemed to work fine after this.
    So in conclusion it seems that IF you don't have the "logging permit-hostdown" command issued before you start configuring "logging host tcp/xxxx" , you might run into problems IF you don't have matching settings on the ASA sending the log and the Syslog server receiving the log.
    There doesnt seem to be any easy way to correct the situation (with the connections getting blocked) after you have once messed up the configurations. Seems your only option is to reconfigure the Security Context (which is easy) or if this problem exists in the same way in a single ASA you will have to reboot the device which means longer downtime than reconfiguring a context.
    There would still be a couple of things to test but at the moment I have no more time for this. I will update if there is any new information.
    - Jouni

  • WRT300N - wireless connections -- intermittent problems

    I just purchased a WRT300N router and have my desktop PC wired into one of the ports but then are running three separate laptops via wireless.  Both my IBM laptop and my Dell laptop continue to run into problems keeping the internet connection as the wireless connection is dropped periodically throughout the day (every 20-30 minutes).  Any suggestions?  

    Hi!try changing the radio band of your router to wide...wide channel to7 and standard channel to 9.Also on the advance wireless settings of the router change DTIM to 3..beacon interval to 50 and rts threshold 2305..fragmentation threshold:2304...hopefully that will solve ur problem..ciao!

  • LMS 4.0 syslog problem

    Hi,
    I am trying to setup syslog server on LMS 4.0.
    Everything seems to be working fine but I have a lot of stragne logs in my syslog.log file.
    Every single day I receive logs like :
    Mar 05 09:31:03 127.0.0.1 100: <30>   dmgt[1136]: 3007(I):Started application(1015) "e:\CSCOpx\bin\cwjava.exe -cw:jre lib/jre -cp e:\CSCOpx\MDC\tomcat\shared\lib\MICE.jar;e:\CSCOpx\MDC\tomcat\shared\lib\NATIVE.jar;e:\CSCOpx\MDC\tomcat\shared\lib\jdom.jar;e:\CSCOpx\MDC\tomcat\shared\lib\xalan.jar;e:\CSCOpx\MDC\tomcat\shared\lib\xerces.jar;e:\CSCOpx\MDC\tomcat\common\lib\servlet.jar;e:\CSCOpx\MDC\tomcat\shared\lib\castor-0.9.5.jar;e:\CSCOpx\MDC\tomcat\shared\lib\castor-0.9.5-xml.jar;e:\CSCOpx\lib\classpath;e:\CSCOpx\www\classpath;www\classpath\vbjorb.jar;MDC\tomcat\webapps\upm\WEB-INF\classes;lib\jre\lib\endorsed\jacorb.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\ctm.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\log4j.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\jep-3.2.0.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\struts.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\upmcmn.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\upmplr.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\xstream-1.1.1.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\xpp3.jar;MDC\tomcat\webapps\up
    Mar 05 09:31:03 127.0.0.1 100: <30>   dmgt[1136]: 3009(I):Application "1018" registered.
    Mar 05 09:31:03 127.0.0.1 100: <30>   dmgt[1136]: 3007(I):Started application(1018) "e:\CSCOpx\bin\cwjava.exe -cw:jre lib/jre -cp e:\CSCOpx\MDC\tomcat\shared\lib\MICE.jar;e:\CSCOpx\MDC\tomcat\shared\lib\NATIVE.jar;e:\CSCOpx\MDC\tomcat\shared\lib\jdom.jar;e:\CSCOpx\MDC\tomcat\shared\lib\xalan.jar;e:\CSCOpx\MDC\tomcat\shared\lib\xerces.jar;e:\CSCOpx\MDC\tomcat\common\lib\servlet.jar;e:\CSCOpx\MDC\tomcat\shared\lib\castor-0.9.5.jar;e:\CSCOpx\MDC\tomcat\shared\lib\castor-0.9.5-xml.jar;e:\CSCOpx\lib\classpath;e:\CSCOpx\www\classpath;www\classpath\vbjorb.jar;MDC\tomcat\webapps\upm\WEB-INF\classes;lib\jre\lib\endorsed\jacorb.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\log4j.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\jep-3.2.0.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\ags.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\xdi.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\ctm.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\deviceselector.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\mibmgr.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\upmcmn.jar;MDC\tomcat\webapps\upm\W
    Mar 05 09:31:36 127.0.0.1 100: <30>   dmgt[1136]: 3021(I):Died method called for process (1018, pid=6600).
    Mar 05 09:31:36 127.0.0.1 100: <30>   dmgt[1136]: 3011(I):Application "1018" unregistered.
    Mar 05 09:31:36 127.0.0.1 100: <30>   dmgt[1136]: 3021(I):Died method called for process (1015, pid=5632).
    Mar 05 09:31:36 127.0.0.1 100: <30>   dmgt[1136]: 3011(I):Application "1015" unregistered.
    Mar 05 10:48:01 127.0.0.1 100: <30>   dmgt[1136]: 3021(I):Died method called for process (UTMajorAcquisition, pid=10388).
    Mar 05 08:31:03 127.0.0.1 100: <30>   dmgt[1136]: 3009(I):Application "1015" registered.
    Mar 05 08:31:03 127.0.0.1 100: <30>   dmgt[1136]: 3007(I):Started application(1015) "e:\CSCOpx\bin\cwjava.exe -cw:jre lib/jre -cp e:\CSCOpx\MDC\tomcat\shared\lib\MICE.jar;e:\CSCOpx\MDC\tomcat\shared\lib\NATIVE.jar;e:\CSCOpx\MDC\tomcat\shared\lib\jdom.jar;e:\CSCOpx\MDC\tomcat\shared\lib\xalan.jar;e:\CSCOpx\MDC\tomcat\shared\lib\xerces.jar;e:\CSCOpx\MDC\tomcat\common\lib\servlet.jar;e:\CSCOpx\MDC\tomcat\shared\lib\castor-0.9.5.jar;e:\CSCOpx\MDC\tomcat\shared\lib\castor-0.9.5-xml.jar;e:\CSCOpx\lib\classpath;e:\CSCOpx\www\classpath;www\classpath\vbjorb.jar;MDC\tomcat\webapps\upm\WEB-INF\classes;lib\jre\lib\endorsed\jacorb.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\ctm.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\log4j.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\jep-3.2.0.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\struts.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\upmcmn.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\upmplr.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\xstream-1.1.1.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\xpp3.jar;MDC\tomcat\webapps\up
    Mar 05 08:31:03 127.0.0.1 100: <30>   dmgt[1136]: 3009(I):Application "1018" registered.
    Mar 05 08:31:03 127.0.0.1 100: <30>   dmgt[1136]: 3007(I):Started application(1018) "e:\CSCOpx\bin\cwjava.exe -cw:jre lib/jre -cp e:\CSCOpx\MDC\tomcat\shared\lib\MICE.jar;e:\CSCOpx\MDC\tomcat\shared\lib\NATIVE.jar;e:\CSCOpx\MDC\tomcat\shared\lib\jdom.jar;e:\CSCOpx\MDC\tomcat\shared\lib\xalan.jar;e:\CSCOpx\MDC\tomcat\shared\lib\xerces.jar;e:\CSCOpx\MDC\tomcat\common\lib\servlet.jar;e:\CSCOpx\MDC\tomcat\shared\lib\castor-0.9.5.jar;e:\CSCOpx\MDC\tomcat\shared\lib\castor-0.9.5-xml.jar;e:\CSCOpx\lib\classpath;e:\CSCOpx\www\classpath;www\classpath\vbjorb.jar;MDC\tomcat\webapps\upm\WEB-INF\classes;lib\jre\lib\endorsed\jacorb.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\log4j.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\jep-3.2.0.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\ags.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\xdi.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\ctm.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\deviceselector.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\mibmgr.jar;MDC\tomcat\webapps\upm\WEB-INF\lib\upmcmn.jar;MDC\tomcat\webapps\upm\W
    Mar 05 08:31:39 127.0.0.1 100: <30>   dmgt[1136]: 3021(I):Died method called for process (1015, pid=7600).
    Mar 05 08:31:39 127.0.0.1 100: <30>   dmgt[1136]: 3011(I):Application "1015" unregistered.
    Mar 05 08:31:39 127.0.0.1 100: <30>   dmgt[1136]: 3021(I):Died method called for process (1018, pid=6596).
    Mar 05 08:31:39 127.0.0.1 100: <30>   dmgt[1136]: 3011(I):Application "1018" unregistered.
    I dont want to get any logs from 127.0.0.1. Is it possible to filter out logs from server ?
    Thanks and best regars.

    I don't think you can easily stop LMS from logging its own starting and stopping of processes.
    Why does this bother you? It doesn't appear in you reports
    Cheers,
    Michel

  • WRT300N V1.0 - Bittorent Problems!

    When I download a lot with any torrent client, the router slows the internet connection slowly to a crawl, and then cuts it off completely as well as preventing me from accessing the router status page by taking forever to load, if it is even loading. The only solution is to reset the router by pulling out the power and replugging it which allows me to surf but hardly use bittorrent again without repeating the process again. Can't figure out why and it's really annoying that I have a secured network and when it drops, so does the security, so I have to reset that all the time when this happens. This also happened with my old WRT54G V1.1 router too.
    Fixes for any of the 2 routers are extremely helpful!!!
    Thanks!
    Message Edited by Vinny13 on 01-20-200703:06 PM

    I also had that problem, I restricted my tcp connects to 45 and I only d/l 2 files at a time now and it seems to be running smooth, I also applied a patch to one of the networking files to allow 45 tcp connections at a time instead of only 10 which is a winxp default. Seems fine now. I am still running the old firmware on my 300N also if that matters, also I am port forwarding, but this did not make a diff with this matter.

  • WRT300N and network printer problems

    I have a pc wired into the router and a printer wired into it as well, they work fine.  I have a laptop that can access the router wirelessly and it can get out to the internet.  When I use the laptop to try and find the printer using the printer setup wizard its not found on the network, all i get is the microsoft windows network option.  The Printer is an HP 7780 model and has the wireless option, went with the the cable to try and limit complications.  Any help with this would be greatly appreciated.
      Thanks.

    Depending on the operating system (Windows XP) go to the control panel and click on the Network Wizard and set up both computers and during the wizard it will give you the option to enable File and printer sharing.  After you set up your network you should be able to see the other PC and printer from each printer.  Also make sure you have TCP/IP enabled by clicking on start>control; panel>Network connections and right click on the LAN (wired or wireless depending on which one it is) and clicking on properties.  In there make sure TCP/IP is checked.  You may have to install any software on each PC that came with your printer.
    Richard Aichner (Ikester)

  • WRT300N - My home network not visible on other home machines

    I've had a WRT300N in place and problem-free for about two years; always able to have other laptops and notebook in the house view our network and able to connect.  Suddenly, the network no longer shows on the other machines.  The only thing I had done over the course of two or three days was to unplug the power cord from the back of the router (to prevent one of our children from using the wireless to access the internet late at night).  So the most recent time I reconnect the power cord, local network no longer visible on the other machines.  I have done a new set-up and a factory reset, and to no avail can I see the network on our other machines at home.  When I run a hard cable from the router to the back of my laptop, I can gain internet access that way.  I am puzzled why I can't see the wireless network any longer. The location of the router has not changed one inch, nor is there anything new posing interference.  And as far as I can tell, the settings are all proper.  I am not an expert when it comes to computer set-ups, but I was able to set-up the router and wireless on the first try two years ago; but now I have a problem.  I would be grateful if anyone has any suggestions.  Thank you.

    Follow the below mentioned settings and check.
    Open an Internet Explorer browser page on your wired computer(desktop).In the address bar type - 192.168.1.1 and press Enter...Leave Username blank & in Password use admin in lower case...
    For Wireless Settings, please do the following : -
    Click on the Wireless tab
    - Here select manual configuration...Wireless Network mode should be mixed...
    - Provide a unique name in the Wireless Network Name (SSID) box in order to differentiate your network from your neighbors network...
    - Set the Radio Band to Standard-20MHz and change the Standard channel to 11-2.462GHz...Wireless SSID broadcast should be Enabled and then click on Save Settings...
    Please make a note of Wireless Network Name (SSID) as this is the Network Identifier...
    For Wireless Security : -
    Click on the Sub tab under Wireless > Wireless Security...
    Change the Wireless security mode to WPA, For Encryption, select TKIP...For Passphrase input your desired WPA Key. For example , MySecretKey , This will serve as your network key whenever you connect to your wireless network. Do NOT give this key to anyone and remember the key.
    NOTE : Passphrase should be more that 8 characters...
    Click on Advanced Wireless Settings
    Change the Beacon Interval to 75,Change the Fragmentation Threshold to 2304,Change the RTS Threshold to 2304 and Click on Save Settings...
    Now see if you can locate your Wireless Network and attempt to connect...

  • WRT300N and Gaming?

    I have recently purchased a WRT300N and am having problems connecting to some of my computer games. I opened the ports on the router, but it doesn't seem like the ports actually opened. When playing Diablo II, I can be the server and have another computer on my LAN connect to me, but I cannot connect to another computer on my LAN. I also use a bit torrent program, it is telling me to recheck my port forwarding and make sure the proper ports are open. As far as other games like Rappelz go, I cannot connect to their servers to play. Any suggestions as to what I am doing wrong?

    Opening ports on the router only affects connections from the internet into your LAN. It does not affect LAN connections. On the LAN side the router is basically a simple ethernet switch. If you can connect in one direction but not in the other it is usually because of a firewall installed on the computer to which you cannot connect.
    Otherwise, please post the exact settings you have tried.

  • WiFi issue with MAC address

    I've been using MAC filtering as part of my home network wireless security for years. This means inputting the MAC address of every device and computer that I want to have connect to my network. So I get my new WiFi + 3G iPad on May 28th and look in Settings to find the MAC address so I can input it into my router info. The router (D-Link) says that it's not a valid MAC format, presumably because it begins with E8 instead of the 00 that all my other devices have. I ended up having to disable MAC address filtering in order to have my iPad connect to my WiFi network. Does anybody have any comments or ideas about how I can get the router to recognize a MAC that begins E8:06 etc.?
    Would appreciate any help. Thanks.
    Glenys

    I am using MAC filtering on my network using a Linksys router (WRT300N) and had no problems adding our iPad to the MAC table. Also, if I'm not mistaken, the first portion of a MAC address is unique to the manufacturer, so unless all of your wireless devices are from the same manufacturer (at least the wireless component of the device), then it isn't likely that all of your MAC addresses will start with the same digits. Make sure when you enter the MAC address that you include the colon in between each pair. My Linksys won't accept the MAC address without them. As someone else recommended, you may also want to see if there is a firmware update for your router that addresses this issue. Good Luck.

  • EEM Applet Problem With: event syslog pattern ".*" priority 2

    I went to create a EEM applet that would be invoked whenever any syslog message of priority 0-2 was invoked. I figured  the following event statement would work
           event syslog pattern ".*" priority 2
    I never really used the priority optional argument before but thought I understood from the docs that messages at or numerically lower than the specified level are matched.
    Well it doesn't seem to work as documented.  Seems to me that only messages at the specified level are beng matched and not messages numerically lower than the specified level.
    Anyway I did what I wanted differently but wanted to post this in case this is a bug in the syslog ed.

    Actually, it's a problem with the documentation.  The priority option only matches the specified severity.  What you could do is adjust pattern to do this:
    event syslog pattern "*-[012]-"

  • WRT300N - Problem Connecting With Desktop

    I recently reset my HP desktop to the factory default after experiencing a whole slew of technical issues I had neither intention nor time to deal with. As a result of the reset, I lost connectivity to my host computer which runs a WRT300N Wireless Router. This wasn't a suprise, but I then ran into a few more problems in trying to reconnect. The first issue I experienced was that on my client PC, it wouldn't detect the Wireless PCI Card I previously installed before the factory reset. This was a quick fix, as upon opening the tower, I discovered the card had become disconnected. I connected the card and ran the installation CD successfully. Since the installation program contains a service to select the wireless network you wish to connect to, I did so, and followed the on screen directions to reset my computer. Unfortunately, I was still disconnected from the intended wireless network upon opening up Internet Explorer. I ran the Wirless Zero Configuration service on my computer so I could deal with the wireless networks on more familiar ground. I was completely dumbfounded to what I saw there. It detected the wireless network, but it gives all the wrong information about it. The SSID resembles the actual SSID, but it is not the same. Also, it says that the wireless network is unsecured when, in actuality, is it secured with a WEP Key. I am stumped. A PSP and HP laptop have absolutely no problem connecting  to this network. The problem seems to soley exist with my HP desktop. Any help at all would be great. Thank you.

    Hi,
    Have you tried to install latest drivers for the wireless PCI card.
    Download those from www.linksys.com/download from a computer already online.
    Transfer those drivers to computer with the wireless PCI card, using a flash drive or by burning a disk.
    Uninstall the old drivers from desktop, reboot the desktop computer.
    Install the new drivers and again reboot the desktop computer.
    Now check for available wireless networks and try to connect to wireless network.

  • Encoding Problems with WRT300N V2

    Hello guys,
    i have following problem:
    I have a WRT300n Router and it seems to have problems with WPA2 encoding. I have 2 different deviceses (a SMC Ethernet Bridge and a PS3) trying to connect to my Linksys wireless router. No chance in WPA2 mode but when I try in WEP-Mode, both devicec can connect to it.
    Are there known encoding problems?
    Any idea what i can do?

    It is able to use. But my router always drops the connection. WEP is no problem, but ... what about low security and Wirless N is not enabled ??

  • Cisco Security manager syslog.log file problem

    Hello
    I have this problem with the CSM, the next file Syslog.log  (C:\Program Files\CSCOpx\log\Syslog.log  ), this file grows very fast to fill the hard disk and saturates the server, I have tried the log rotation of the cisco works but it doesnt work, what else can i do?
    the hard drive fills in 4 hours. tankyou

    In CSM clinet under Tools > CSM Administration > Debugging you can changing the level to something higher than debugging.
    I hope it helps.
    PK

  • Problems with WRT300n & WPC300n

    Hi guys!
    I have a problem. I am reviewing the two Linksys-thingys WRT300n & WPC300n for a pc-mag, and for the last 4 hours I have been all over the internet trying to get a clue...
    First of all both items works (not well (low range/falls out once in a while), but there is a connection after all). My main prob is, that I cant get the WPC300n to go faster then 54 Mbps... In the Linksys-control it says Wide Channel: N/A... like this is just regular G-speed...?
    I have tried to turn on all the encryptionfacilities but it doesnt help. All the drivers and firmware are the newest...
    Any of you got a clue?

    I'm having the same problem with the same equipment. I hope there is someone that can help us. PLEASE

Maybe you are looking for