Error message

  • The specified file temporary://fileBDQkli could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://filezR0Uqa could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileB7brE2 could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.

Marek wonders why AS48384 is announcing 91.0.0.0/8!?

Link: Marek wonders why AS48384 is announcing 91.0.0.0/8!?

It appears as though yesterday, around 15:17 UTC, AS48384 began announcing a huge chunk of IPv4 address space and this has propagated around Europe via peering links.

In a tweet Andy Davidson suggests a possible cause: that AS48384 has missed out a word in their configuration. Quite rightly many “backbone” providers have filtered this invalid announcement, but I am a little surprised that one of AS48384’s upstreams, TransTeleCom (AS20485) has accepted and propagated this route to its peers.

Category: