1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

http_id mismatch in log file

Discussion in 'Tomato Firmware' started by mpegmaster, Jun 28, 2009.

  1. mpegmaster

    mpegmaster Addicted to LI Member

    I'm new at this... ;^)

    So please be patience with me too!

    Linksys WRT54G-TM running on Tomato Firmware v1.23.8515 .5 RAF ND

    I'm getting the following in the Log File...
    Jun 27 18:07:56 Tomato daemon.warn httpd[2075]: http_id mismatch
    Jun 27 18:08:06 Tomato daemon.warn httpd[2076]: http_id mismatch
    Jun 27 18:08:16 Tomato daemon.warn httpd[2085]: http_id mismatch
    Jun 27 18:08:26 Tomato daemon.warn httpd[2086]: http_id mismatch
    Jun 27 18:08:37 Tomato daemon.warn httpd[2087]: http_id mismatch
    Jun 27 18:08:47 Tomato daemon.warn httpd[2088]: http_id mismatch
    Jun 27 18:08:57 Tomato daemon.warn httpd[2090]: http_id mismatch

    As you see it is happening every 10 seconds! It just goes on an on...

    Is there some thing wrong?

    I tired to Google this to, and no avail answer... ;^(

    Thanks in advance too!

    Cheers!
     
  2. bogderpirat

    bogderpirat Network Guru Member

    probably some program trying to access your router... download wireshark and have it capture all packets that are directed at your router, port 80, while you're not accessing the webif. have it running for 10-20 seconds to maybe have two the said packets, then look at them and see if you can configure out where they might come from.
     
  3. mpegmaster

    mpegmaster Addicted to LI Member

    bogderpirat,

    I had already had Wireshark [http://www.wireshark.org/] and could not find anything that was causing the errors. They updated Wireshark it's #1.20 - June 15, 2009.

    About 90 minutes later the errors simply disappeared in the log and all is well... ;^)

    Thanks for suggestion and help... ;^)


    Cheers!!!
     
  4. Toastman

    Toastman Super Moderator Staff Member Member

    I believe when a web browser connects to a web server it uses an ID of some kind, perhaps to do with submitting forms. If somehow the browser subsequently gets a different ID to what it is expecting, this message pops up. Perhaps someone more familiar with the protocols could comment if this is correct and if so, why it happens. Anyway, it seems to disappear when the browser page is refreshed. It could be your own browser or someone else on the network, or anything using HTTP to the router I guess. That might include UPnP for example. Anyway, it's nothing to worry about and is very common.

    Don't take this as anything definitive, but I hope it helps.
     

Share This Page