Skip to content

Instantly share code, notes, and snippets.

@xirixiz

xirixiz/OpenWRT TTL manipulation on a travel router explained.md

Last active July 10, 2024 03:52
Show Gist options
  • Save xirixiz/13c81490e611947ad11471995cc8c842 to your computer and use it in GitHub Desktop.
Save xirixiz/13c81490e611947ad11471995cc8c842 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. Bram van Dartel revised this gist Jul 10, 2024. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions OpenWRT TTL manipulation on a travel router explained.md
    View file
    Original file line number Diff line number Diff line change
    @@ -9,13 +9,13 @@ Here’s an explanation of the key reasons:
    Captive portals typically recognize and manage devices based on their MAC addresses and IP addresses. When you connect a device (like a laptop or phone) directly to the hotel's network, the captive portal captures the MAC address of that device and redirects it to a login page.
    <br><br>
    However, when you use a travel router (like one running OpenWRT) to connect multiple devices to the hotel's network, all the traffic from those devices appears to come from the travel router's MAC address. The captive portal might only authenticate the travel router itself, causing issues when individual devices behind the router try to access the internet.
    <br><br>
    <br><br><br>
    <b>TTL Manipulation</b>
    <br>
    The TTL value is decremented by 1 each time a packet passes through a router. Devices connected directly to a network typically have packets with an initial TTL of 64. When a packet from such a device passes through the travel router, the TTL is reduced to 63 by the time it reaches the hotel network.
    <br><br>
    Some captive portals use the TTL value as part of their method for identifying traffic that should be redirected to the login page. A TTL of 63 can signal to the captive portal that the traffic is coming through a secondary router, which might prompt the portal to redirect this traffic differently or block it altogether.
    <br><br>
    <br><br><br>
    <b>Setting TTL to 65</b>
    <br>
    By setting the TTL to 65 on the travel router, packets reaching the hotel's network will have a TTL of 64. This makes the packets appear as though they are coming directly from a device connected to the hotel's network, rather than through a secondary router. As a result, the captive portal treats the packets as if they are from a directly connected device, allowing them to pass through normally after the initial login.
  2. Bram van Dartel revised this gist Jul 10, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion OpenWRT TTL manipulation on a travel router explained.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,5 +1,5 @@
    <h3>OpenWRT TTL manipulation on a travel router explained</h3>
    <br><br>
    <br>
    Setting the TTL to 65 can help solve OpenWRT hotel captive portal issues on a travel router because of the way captive portals often track and manage connected devices.
    <br><br>
    Here’s an explanation of the key reasons:
  3. Bram van Dartel revised this gist Jul 10, 2024. 1 changed file with 8 additions and 12 deletions.
    20 changes: 8 additions & 12 deletions OpenWRT TTL manipulation on a travel router explained.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,26 +1,22 @@
    <h3>OpenWRT TTL manipulation on a travel router explained</h3>
    <br>
    <br><br>
    Setting the TTL to 65 can help solve OpenWRT hotel captive portal issues on a travel router because of the way captive portals often track and manage connected devices.
    <br>
    <br>
    <br><br>
    Here’s an explanation of the key reasons:
    <br>
    <br>
    <br><br>
    <b>Device Differentiation:</b>
    <br>
    Captive portals typically recognize and manage devices based on their MAC addresses and IP addresses. When you connect a device (like a laptop or phone) directly to the hotel's network, the captive portal captures the MAC address of that device and redirects it to a login page.
    <br>
    <br><br>
    However, when you use a travel router (like one running OpenWRT) to connect multiple devices to the hotel's network, all the traffic from those devices appears to come from the travel router's MAC address. The captive portal might only authenticate the travel router itself, causing issues when individual devices behind the router try to access the internet.
    <br>
    <br>
    <br><br>
    <b>TTL Manipulation</b>
    <br>
    The TTL value is decremented by 1 each time a packet passes through a router. Devices connected directly to a network typically have packets with an initial TTL of 64. When a packet from such a device passes through the travel router, the TTL is reduced to 63 by the time it reaches the hotel network.
    <br>
    <br><br>
    Some captive portals use the TTL value as part of their method for identifying traffic that should be redirected to the login page. A TTL of 63 can signal to the captive portal that the traffic is coming through a secondary router, which might prompt the portal to redirect this traffic differently or block it altogether.
    <br>
    <br>
    <br><br>
    <b>Setting TTL to 65</b>
    <br>
    By setting the TTL to 65 on the travel router, packets reaching the hotel's network will have a TTL of 64. This makes the packets appear as though they are coming directly from a device connected to the hotel's network, rather than through a secondary router. As a result, the captive portal treats the packets as if they are from a directly connected device, allowing them to pass through normally after the initial login.
    <br>
    <br><br>
  4. Bram van Dartel revised this gist Jul 10, 2024. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion OpenWRT TTL manipulation on a travel router explained.md
    View file
    Original file line number Diff line number Diff line change
    @@ -2,6 +2,7 @@
    <br>
    Setting the TTL to 65 can help solve OpenWRT hotel captive portal issues on a travel router because of the way captive portals often track and manage connected devices.
    <br>
    <br>
    Here’s an explanation of the key reasons:
    <br>
    <br>
    @@ -22,4 +23,4 @@ Some captive portals use the TTL value as part of their method for identifying t
    <b>Setting TTL to 65</b>
    <br>
    By setting the TTL to 65 on the travel router, packets reaching the hotel's network will have a TTL of 64. This makes the packets appear as though they are coming directly from a device connected to the hotel's network, rather than through a secondary router. As a result, the captive portal treats the packets as if they are from a directly connected device, allowing them to pass through normally after the initial login.
    <br>
    <br>
  5. Bram van Dartel revised this gist Jul 10, 2024. 1 changed file with 4 additions and 3 deletions.
    7 changes: 4 additions & 3 deletions OpenWRT TTL manipulation on a travel router explained.md
    View file
    Original file line number Diff line number Diff line change
    @@ -4,21 +4,22 @@ Setting the TTL to 65 can help solve OpenWRT hotel captive portal issues on a tr
    <br>
    Here’s an explanation of the key reasons:
    <br>
    **Device Differentiation:**
    <br>
    <b>Device Differentiation:</b>
    <br>
    Captive portals typically recognize and manage devices based on their MAC addresses and IP addresses. When you connect a device (like a laptop or phone) directly to the hotel's network, the captive portal captures the MAC address of that device and redirects it to a login page.
    <br>
    However, when you use a travel router (like one running OpenWRT) to connect multiple devices to the hotel's network, all the traffic from those devices appears to come from the travel router's MAC address. The captive portal might only authenticate the travel router itself, causing issues when individual devices behind the router try to access the internet.
    <br>
    <br>
    **TTL Manipulation**
    <b>TTL Manipulation</b>
    <br>
    The TTL value is decremented by 1 each time a packet passes through a router. Devices connected directly to a network typically have packets with an initial TTL of 64. When a packet from such a device passes through the travel router, the TTL is reduced to 63 by the time it reaches the hotel network.
    <br>
    Some captive portals use the TTL value as part of their method for identifying traffic that should be redirected to the login page. A TTL of 63 can signal to the captive portal that the traffic is coming through a secondary router, which might prompt the portal to redirect this traffic differently or block it altogether.
    <br>
    <br>
    **Setting TTL to 65**
    <b>Setting TTL to 65</b>
    <br>
    By setting the TTL to 65 on the travel router, packets reaching the hotel's network will have a TTL of 64. This makes the packets appear as though they are coming directly from a device connected to the hotel's network, rather than through a secondary router. As a result, the captive portal treats the packets as if they are from a directly connected device, allowing them to pass through normally after the initial login.
    <br>
  6. Bram van Dartel revised this gist Jul 10, 2024. 1 changed file with 15 additions and 7 deletions.
    22 changes: 15 additions & 7 deletions OpenWRT TTL manipulation on a travel router explained.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,16 +1,24 @@
    <h3>OpenWRT TTL manipulation on a travel router explained</h3>
    <br>
    Setting the TTL to 65 can help solve OpenWRT hotel captive portal issues on a travel router because of the way captive portals often track and manage connected devices.

    <br>
    Here’s an explanation of the key reasons:

    <br>
    **Device Differentiation:**
    <br>
    Captive portals typically recognize and manage devices based on their MAC addresses and IP addresses. When you connect a device (like a laptop or phone) directly to the hotel's network, the captive portal captures the MAC address of that device and redirects it to a login page.

    <br>
    However, when you use a travel router (like one running OpenWRT) to connect multiple devices to the hotel's network, all the traffic from those devices appears to come from the travel router's MAC address. The captive portal might only authenticate the travel router itself, causing issues when individual devices behind the router try to access the internet.

    <br>
    <br>
    **TTL Manipulation**
    <br>
    The TTL value is decremented by 1 each time a packet passes through a router. Devices connected directly to a network typically have packets with an initial TTL of 64. When a packet from such a device passes through the travel router, the TTL is reduced to 63 by the time it reaches the hotel network.

    <br>
    Some captive portals use the TTL value as part of their method for identifying traffic that should be redirected to the login page. A TTL of 63 can signal to the captive portal that the traffic is coming through a secondary router, which might prompt the portal to redirect this traffic differently or block it altogether.

    <br>
    <br>
    **Setting TTL to 65**
    By setting the TTL to 65 on the travel router, packets reaching the hotel's network will have a TTL of 64. This makes the packets appear as though they are coming directly from a device connected to the hotel's network, rather than through a secondary router. As a result, the captive portal treats the packets as if they are from a directly connected device, allowing them to pass through normally after the initial login.
    <br>
    By setting the TTL to 65 on the travel router, packets reaching the hotel's network will have a TTL of 64. This makes the packets appear as though they are coming directly from a device connected to the hotel's network, rather than through a secondary router. As a result, the captive portal treats the packets as if they are from a directly connected device, allowing them to pass through normally after the initial login.
    <br>
  7. Bram van Dartel revised this gist Jul 10, 2024. 1 changed file with 3 additions and 3 deletions.
    6 changes: 3 additions & 3 deletions OpenWRT TTL manipulation on a travel router explained.md
    View file
    Original file line number Diff line number Diff line change
    @@ -2,15 +2,15 @@ Setting the TTL to 65 can help solve OpenWRT hotel captive portal issues on a tr

    Here’s an explanation of the key reasons:

    1. Device Differentiation
    **Device Differentiation:**
    Captive portals typically recognize and manage devices based on their MAC addresses and IP addresses. When you connect a device (like a laptop or phone) directly to the hotel's network, the captive portal captures the MAC address of that device and redirects it to a login page.

    However, when you use a travel router (like one running OpenWRT) to connect multiple devices to the hotel's network, all the traffic from those devices appears to come from the travel router's MAC address. The captive portal might only authenticate the travel router itself, causing issues when individual devices behind the router try to access the internet.

    2. TTL Manipulation
    **TTL Manipulation**
    The TTL value is decremented by 1 each time a packet passes through a router. Devices connected directly to a network typically have packets with an initial TTL of 64. When a packet from such a device passes through the travel router, the TTL is reduced to 63 by the time it reaches the hotel network.

    Some captive portals use the TTL value as part of their method for identifying traffic that should be redirected to the login page. A TTL of 63 can signal to the captive portal that the traffic is coming through a secondary router, which might prompt the portal to redirect this traffic differently or block it altogether.

    3. Setting TTL to 65
    **Setting TTL to 65**
    By setting the TTL to 65 on the travel router, packets reaching the hotel's network will have a TTL of 64. This makes the packets appear as though they are coming directly from a device connected to the hotel's network, rather than through a secondary router. As a result, the captive portal treats the packets as if they are from a directly connected device, allowing them to pass through normally after the initial login.
  8. Bram van Dartel renamed this gist Jul 10, 2024. 1 changed file with 0 additions and 0 deletions.
    0 gistfile1.txt → ...ipulation on a travel router explained.md
    View file
    File renamed without changes.
  9. Bram van Dartel created this gist Jul 10, 2024.
    16 changes: 16 additions & 0 deletions gistfile1.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,16 @@
    Setting the TTL to 65 can help solve OpenWRT hotel captive portal issues on a travel router because of the way captive portals often track and manage connected devices.

    Here’s an explanation of the key reasons:

    1. Device Differentiation
    Captive portals typically recognize and manage devices based on their MAC addresses and IP addresses. When you connect a device (like a laptop or phone) directly to the hotel's network, the captive portal captures the MAC address of that device and redirects it to a login page.

    However, when you use a travel router (like one running OpenWRT) to connect multiple devices to the hotel's network, all the traffic from those devices appears to come from the travel router's MAC address. The captive portal might only authenticate the travel router itself, causing issues when individual devices behind the router try to access the internet.

    2. TTL Manipulation
    The TTL value is decremented by 1 each time a packet passes through a router. Devices connected directly to a network typically have packets with an initial TTL of 64. When a packet from such a device passes through the travel router, the TTL is reduced to 63 by the time it reaches the hotel network.

    Some captive portals use the TTL value as part of their method for identifying traffic that should be redirected to the login page. A TTL of 63 can signal to the captive portal that the traffic is coming through a secondary router, which might prompt the portal to redirect this traffic differently or block it altogether.

    3. Setting TTL to 65
    By setting the TTL to 65 on the travel router, packets reaching the hotel's network will have a TTL of 64. This makes the packets appear as though they are coming directly from a device connected to the hotel's network, rather than through a secondary router. As a result, the captive portal treats the packets as if they are from a directly connected device, allowing them to pass through normally after the initial login.