Veins-4a2与SUMO-0.22.0仿真报错求助：无法解析sumo.dlr.de地址

Let's break down your two errors and work through fixes step by step:

1. SUMO: "SUMO_HOME not set" Warning + Host Resolution Error #

Even though you confirmed SUMO_HOME is configured, there are a few common gotchas here:

• Your active session isn't loading the environment variable:
  • On Linux/macOS: Run echo $SUMO_HOME in the terminal where you launch OMNeT++. If it returns nothing or an incorrect path, re-source your shell config (e.g., source ~/.bashrc or source ~/.zshrc) to load the updated variable. Double-check your export line is accurate:

    export SUMO_HOME=/path/to/your/sumo-0.22.0
    

  • On Windows: Open Command Prompt and run echo %SUMO_HOME%. If it's missing, verify the system environment variable is set correctly (Control Panel → System → Advanced System Settings → Environment Variables) then restart OMNeT++/your terminal.
• Outdated SUMO schema dependency: SUMO 0.22.0 is quite old. When SUMO_HOME isn't detected, it tries to pull schema files from sumo.dlr.de—but this remote resource may be unreachable or incompatible with such an old version. Fixing the SUMO_HOME variable will force it to use local schema files instead, eliminating this error entirely.

2. Veins: "Attempted to read past end of byte buffer" Error #

This error almost always relates to TraCI data parsing mismatches. Since Veins-4a2 is explicitly compatible with SUMO-0.22.0, the issue is likely with your myFile.poly.xml:

• Validate the poly file with SUMO tools:
  Use SUMO's built-in checker to catch XML syntax or schema issues. Run this command in your terminal (replace myNet.net.xml with your actual network file if you have one):

  $SUMO_HOME/bin/sumo --check-only -n myNet.net.xml -p myFile.poly.xml
  

  This will flag invalid tags, missing required attributes, or formatting mistakes in your poly file.
• Check SUMO 0.22.0 compatibility:
  Newer SUMO versions added poly attributes that 0.22.0 doesn't recognize. Ensure your myFile.poly.xml only uses tags/attributes supported by this old version:
  • Confirm all <poly> tags have mandatory attributes like id, type, and shape
  • Avoid modern attributes like layer or fill that weren't present in 0.22.0
  • Make sure all XML tags are properly closed (no unopened/unclosed elements)
• Test with a minimal working scenario:
  Temporarily replace myFile.poly.xml with the poly file from Veins' default RSUExampleScenario. If the simulation runs without errors, you know the problem is isolated to your custom poly file.

内容的提问来源于stack exchange，提问作者Joe