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

Errors in log......

Discussion in 'Tomato Firmware' started by FattysGoneWild, Aug 31, 2009.

  1. FattysGoneWild

    FattysGoneWild LI Guru Member

    They are in bold. Any cause for concern? Never had them before until recently......

    Aug 30 05:00:01 unknown syslog.info root: -- MARK --
    Aug 30 06:00:02 unknown syslog.info root: -- MARK --
    Aug 30 07:00:01 unknown syslog.info root: -- MARK --
    Aug 30 08:00:01 unknown syslog.info root: -- MARK --
    Aug 30 09:00:01 unknown syslog.info root: -- MARK --
    Aug 30 10:00:01 unknown syslog.info root: -- MARK --
    Aug 30 11:00:02 unknown syslog.info root: -- MARK --
    Aug 30 12:00:01 unknown syslog.info root: -- MARK --
    Aug 30 13:00:01 unknown syslog.info root: -- MARK --
    Aug 30 14:00:01 unknown syslog.info root: -- MARK --
    Aug 30 15:00:01 unknown syslog.info root: -- MARK --
    Aug 30 15:32:40 unknown daemon.warn miniupnpd[147]: HTTP Connection closed inexpectedly
    Aug 30 16:00:02 unknown syslog.info root: -- MARK --
    Aug 30 16:10:49 unknown daemon.warn miniupnpd[147]: HTTP Connection closed inexpectedly
    Aug 30 17:00:01 unknown syslog.info root: -- MARK --
    Aug 30 18:00:01 unknown syslog.info root: -- MARK --
    Aug 30 19:00:01 unknown syslog.info root: -- MARK --
    Aug 30 19:35:37 unknown daemon.warn miniupnpd[147]: HTTP Connection closed inexpectedly
    Aug 30 20:00:01 unknown syslog.info root: -- MARK --
    Aug 30 21:00:02 unknown syslog.info root: -- MARK --
    Aug 30 22:00:01 unknown syslog.info root: -- MARK --
    Aug 30 22:20:51 unknown daemon.warn miniupnpd[147]: HTTP Connection closed inexpectedly
    Aug 30 23:00:01 unknown syslog.info root: -- MARK --
    Aug 31 00:00:01 unknown syslog.info root: -- MARK --
    Aug 31 01:00:01 unknown syslog.info root: -- MARK --
     
  2. Toastman

    Toastman Super Moderator Staff Member Member

    MARK is just a mark for ID purposes, you set the time period in ADMIN/LOGGING/Generate marker - so nothing to worry about. You have yours set to generate a marker every hour, it appears. Just turn it off.

    Miniupnpd seems to have some client attempting a upnp forward or maybe disconnect, but for some reason the transaction is closing. I get that message occasionally here, but never had any complaints from users so I guess it resolves itself subsequently. When it happens it seems to be associated with one or two particular clients using Vista, but it's hard to be sure.
     
  3. FattysGoneWild

    FattysGoneWild LI Guru Member

    Thanks Toast. I am actually using pretty much the default settings. So, I never really turned it on. Guess it is the default choice. Going a bit off topic. Reading up on DNS in general. Came across a program by grc.com that is a dns performance test program. Got the results and wondering if you or some one else can explain this a bit more and if it matters?

    System has only ONE (router based) nameserver configured.
    It appears that only one local (router gateway) DNS nameserver, with the IP address of [192.168.1.1], is currently providing all DNS name resolution services to this system. This configuration is not recommended because most consumer-grade routers provide inefficient and under-powered DNS resolution services.

    Unless the DNS resolvers your router is using is under your control, it may not be providing the best or complete name resolution services. For example, is it using multiple redundant DNS nameservers?

    Users of GRC's DNS Spoofability system have determined that consumer-grade routers can be crashed by the receipt of specific DNS reply packets from the Internet. This opens the possibility that Internet-based criminals could acquire access to your router from the Internet as well as to the private network in controls.

    Many consumer-grade routers fail to provide the full range of DNS lookup services. This may have been detected by the benchmark and noted below.

    Recommended Actions:

    Unless you have some specific reason not to, you should give serious thought to disabling your router's provisioning of DNS services (which it is providing for all computers on your local network). After this is done, a fresh reboot of your computers will likely reveal the multiple DNS nameservers provided by your ISP. This is a superior configuration, without an under-powered router acting as a incompetent middleman and impeding all DNS access.

    Note that if you can determine the IP addresses of your ISP-provided nameservers (which may be visible in your router's web configuration) you could manually add them to the nameservers being tested by this benchmark, while also leaving your router providing DNS. This would allow you to compare the performance when running through your router versus "going direct".
     
  4. mstombs

    mstombs Network Guru Member

    More FUD from GRC - It is rubbish, wrong, alarmist etc, just ignore!
     
  5. Toastman

    Toastman Super Moderator Staff Member Member

    I agree totally. THIS WEBSITE IS DANGEROUS. So may people have been scammed by it and the software it sells, which usually ends up trashing your hard disk.

    Did you run any software of theirs? You should immediately run some virus checkers and get rid of the malware they have probably put on your PC.
     

Share This Page