evan/ewpratten.com
1
Fork 0
Code Actions

more blog

Browse Source
This commit is contained in:
Evan Pratten 2022-06-08 16:26:42 -04:00
parent f08c3828a5
commit 6dfa2fbc60
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/blog/2022-06-08-bell-ipv6.md
View File

@ -44,6 +44,10 @@ Both tunneling protocols use IP [Encapsulation](https://en.wikipedia.org/wiki/En
I chose 6in4, mostly because I felt like it :laughing:. I'm sure Teredo would have brought me on an equally interesting journey, and maybe I'll see what its all about some other day. I chose 6in4, mostly because I felt like it :laughing:. I'm sure Teredo would have brought me on an equally interesting journey, and maybe I'll see what its all about some other day.
Below is a diagram of a typical 6in4 packet:
<img src="/images/posts/bell-ipv6/sit.png" loading="lazy" >
### Tunnel brokerage ### Tunnel brokerage
When creating a 6in4 tunnel, you must have a server on the other end of the tunnel with: When creating a 6in4 tunnel, you must have a server on the other end of the tunnel with:
@ -101,4 +105,8 @@ Assuming you correctly set up PPPoE using the instructions above, your router sh
## Tunnel server setup ## Tunnel server setup
At this point, everything on the local network side is ready for a [SIT tunnel](https://developers.redhat.com/blog/2019/05/17/an-introduction-to-linux-virtual-interfaces-tunnels#ipip_tunnel), and we need to set up the server side.
Even though the HH4K is bypassed, Bell will still not allow pings through to the UDM-PRO, so Tunnel Broker will not quite work yet.
## Router setup ## Router setup

BIN
static/images/posts/bell-ipv6/sit.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 12 KiB