Symfony Profiler

{
    "@context": [
        "https:\/\/join-lemmy.org\/context.json",
        "https:\/\/www.w3.org\/ns\/activitystreams"
    ],
    "actor": "https:\/\/lemmy.world\/c\/selfhosted",
    "to": [
        "https:\/\/www.w3.org\/ns\/activitystreams#Public"
    ],
    "object": {
        "id": "https:\/\/lemm.ee\/activities\/create\/e9cd4f01-8e3a-42d3-908c-355622d48558",
        "actor": "https:\/\/lemm.ee\/u\/tiramichu",
        "@context": [
            "https:\/\/join-lemmy.org\/context.json",
            "https:\/\/www.w3.org\/ns\/activitystreams"
        ],
        "to": [
            "https:\/\/www.w3.org\/ns\/activitystreams#Public"
        ],
        "object": {
            "type": "Note",
            "id": "https:\/\/lemm.ee\/comment\/20831723",
            "attributedTo": "https:\/\/lemm.ee\/u\/tiramichu",
            "to": [
                "https:\/\/www.w3.org\/ns\/activitystreams#Public"
            ],
            "cc": [
                "https:\/\/lemmy.world\/c\/selfhosted",
                "https:\/\/lemmy.world\/u\/nix98"
            ],
            "content": "<p>Wireguard doesn\u2019t necessarily need to have those limitations, but it will depend in part how your VPN profile is set up.<\/p>\n<p>If you configured your wireguard profile to always route all traffic over the VPN then yeah, you won\u2019t be able to access local networks. And maybe that\u2019s what you want, in which case fine :)<\/p>\n<p>But you can also set the profile to only route traffic that is destined for an address on the target network (I.e your home network) and the rest will route as normal.<\/p>\n<p>This second type of routing only works properly however when there are no address conflicts between the network you are on (i.e. someone else\u2019s WiFi) and your home network.<\/p>\n<p>For this reason if you want to do this  it\u2019s best to avoid on your <em>own<\/em> home network the common ranges almost everyone uses as default, i.e. 192.168.0.* and 10.0.0.*<\/p>\n<p>I reconfigured  my home network to 192.168.22.* for that reason and now I never hit conflicts and VPN can stay on all the time but only traversed when needed.<\/p>\n",
            "inReplyTo": "https:\/\/lemmy.world\/comment\/17374875",
            "mediaType": "text\/html",
            "source": {
                "content": "Wireguard doesn't necessarily need to have those limitations, but it will depend in part how your VPN profile is set up.\n\nIf you configured your wireguard profile to always route all traffic over the VPN then yeah, you won't be able to access local networks. And maybe that's what you want, in which case fine :)\n\nBut you can also set the profile to only route traffic that is destined for an address on the target network (I.e your home network) and the rest will route as normal.\n\nThis second type of routing only works properly however when there are no address conflicts between the network you are on (i.e. someone else's WiFi) and your home network.\n\nFor this reason if you want to do this  it's best to avoid on your _own_ home network the common ranges almost everyone uses as default, i.e. 192.168.0.* and 10.0.0.*\n\nI reconfigured  my home network to 192.168.22.* for that reason and now I never hit conflicts and VPN can stay on all the time but only traversed when needed.\n",
                "mediaType": "text\/markdown"
            },
            "published": "2025-05-31T08:34:22.500Z",
            "tag": [
                {
                    "href": "https:\/\/lemmy.world\/u\/nix98",
                    "name": "@nix98@lemmy.world",
                    "type": "Mention"
                }
            ],
            "distinguished": false,
            "language": {
                "identifier": "en",
                "name": "English"
            },
            "audience": "https:\/\/lemmy.world\/c\/selfhosted",
            "attachment": []
        },
        "cc": [
            "https:\/\/lemmy.world\/c\/selfhosted",
            "https:\/\/lemmy.world\/u\/nix98"
        ],
        "tag": [
            {
                "href": "https:\/\/lemmy.world\/u\/nix98",
                "name": "@nix98@lemmy.world",
                "type": "Mention"
            }
        ],
        "type": "Create",
        "audience": "https:\/\/lemmy.world\/c\/selfhosted"
    },
    "cc": [
        "https:\/\/lemmy.world\/c\/selfhosted\/followers"
    ],
    "type": "Announce",
    "id": "https:\/\/lemmy.world\/activities\/announce\/create\/b854cb0a-62f5-4ea4-9ef9-36a1fbf480bc"
}

{"@context":["https://join-lemmy.org/context.json","https://www.w3.org/ns/activitystreams"],"actor":"https://lemmy.world/c/selfhosted","to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"id":"https://lemm.ee/activities/create/e9cd4f01-8e3a-42d3-908c-355622d48558","actor":"https://lemm.ee/u/tiramichu","@context":["https://join-lemmy.org/context.json","https://www.w3.org/ns/activitystreams"],"to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"type":"Note","id":"https://lemm.ee/comment/20831723","attributedTo":"https://lemm.ee/u/tiramichu","to":["https://www.w3.org/ns/activitystreams#Public"],"cc":["https://lemmy.world/c/selfhosted","https://lemmy.world/u/nix98"],"content":"<p>Wireguard doesn’t necessarily need to have those limitations, but it will depend in part how your VPN profile is set up.</p>\n<p>If you configured your wireguard profile to always route all traffic over the VPN then yeah, you won’t be able to access local networks. And maybe that’s what you want, in which case fine :)</p>\n<p>But you can also set the profile to only route traffic that is destined for an address on the target network (I.e your home network) and the rest will route as normal.</p>\n<p>This second type of routing only works properly however when there are no address conflicts between the network you are on (i.e. someone else’s WiFi) and your home network.</p>\n<p>For this reason if you want to do this  it’s best to avoid on your <em>own</em> home network the common ranges almost everyone uses as default, i.e. 192.168.0.* and 10.0.0.*</p>\n<p>I reconfigured  my home network to 192.168.22.* for that reason and now I never hit conflicts and VPN can stay on all the time but only traversed when needed.</p>\n","inReplyTo":"https://lemmy.world/comment/17374875","mediaType":"text/html","source":{"content":"Wireguard doesn't necessarily need to have those limitations, but it will depend in part how your VPN profile is set up.\n\nIf you configured your wireguard profile to always route all traffic over the VPN then yeah, you won't be able to access local networks. And maybe that's what you want, in which case fine :)\n\nBut you can also set the profile to only route traffic that is destined for an address on the target network (I.e your home network) and the rest will route as normal.\n\nThis second type of routing only works properly however when there are no address conflicts between the network you are on (i.e. someone else's WiFi) and your home network.\n\nFor this reason if you want to do this  it's best to avoid on your _own_ home network the common ranges almost everyone uses as default, i.e. 192.168.0.* and 10.0.0.*\n\nI reconfigured  my home network to 192.168.22.* for that reason and now I never hit conflicts and VPN can stay on all the time but only traversed when needed.\n","mediaType":"text/markdown"},"published":"2025-05-31T08:34:22.500Z","tag":[{"href":"https://lemmy.world/u/nix98","name":"@nix98@lemmy.world","type":"Mention"}],"distinguished":false,"language":{"identifier":"en","name":"English"},"audience":"https://lemmy.world/c/selfhosted","attachment":[]},"cc":["https://lemmy.world/c/selfhosted","https://lemmy.world/u/nix98"],"tag":[{"href":"https://lemmy.world/u/nix98","name":"@nix98@lemmy.world","type":"Mention"}],"type":"Create","audience":"https://lemmy.world/c/selfhosted"},"cc":["https://lemmy.world/c/selfhosted/followers"],"type":"Announce","id":"https://lemmy.world/activities/announce/create/b854cb0a-62f5-4ea4-9ef9-36a1fbf480bc"}