NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

9 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    It was down for a while due to an ISP problem, but is back on line now.
  • super-poussin wrote:
    Perhaps David shut it down :(

    Send him a PM, I'm sure he will answer


    Still here... as Stephen B noted, I had some major ISP problems. Everything should be running normally as of June 4th or so.
  • Gives a database error with the following at the moment:


    Error establishing a database connection
  • Thanks... fixed now.

    I was having this really strange networking issue last night where I couldn't access one of my remote servers from any of my ReadyNAS devices [destination network unreachable], however, all of my other devices could access it perfectly fine. After a couple hours of troubleshooting [disabling bonding, jumbo frames, rebooting, etc] I noticed that the ReadyNAS Remote service (specifically the LeafNetworks adpater) has a network ID & subnet mask of 5.169.x.y/255.0.0.0 that was conflicting with my remote server (which has an IP of 5.79.x.y).

    Anyhow, I've disabled the LeafNetworks adapter, restarted mysqld and everything is now working properly.
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    dbott67 wrote:
    Thanks... fixed now.

    I was having this really strange networking issue last night where I couldn't access one of my remote servers from any of my ReadyNAS devices [destination network unreachable], however, all of my other devices could access it perfectly fine. After a couple hours of troubleshooting [disabling bonding, jumbo frames, rebooting, etc] I noticed that the ReadyNAS Remote service (specifically the LeafNetworks adpater) has a network ID & subnet mask of 5.169.x.y/255.0.0.0 that was conflicting with my remote server (which has an IP of 5.79.x.y).

    Anyhow, I've disabled the LeafNetworks adapter, restarted mysqld and everything is now working properly.
    Your remote server was assigned a real [public] 5.x.x.x address?

    I've posted on this before, the LeafNetworks adapter shouldn't be using these addresses. Netgear has had 3 years to avoid a foreseeable problem [5.x.x.x. were assigned by IANA in 2010, before that they were reserved for "experimental" use).
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    That makes sense, as the 5.x.x.x addresses went to RIPE, which handles IPv4 addresses for Europe, the Middle East, and part of Asia.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More