<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Networking on homelab89</title>
    <link>https://blog.homelab89.com/tags/networking/</link>
    <description>Recent content in Networking on homelab89</description>
    <generator>Hugo</generator>
    <language>ko-KR</language>
    <lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.homelab89.com/tags/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP Tunneling</title>
      <link>https://blog.homelab89.com/docs/networking/http-tunneling-basics/</link>
      <pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.homelab89.com/docs/networking/http-tunneling-basics/</guid>
      <description>&lt;h2 id=&#34;http-tunneling이란&#34;&gt;HTTP Tunneling이란?&lt;/h2&gt;
&lt;p&gt;HTTP Tunneling은 &lt;strong&gt;HTTP 프로토콜을 통로(터널)로 사용하여, 원래 HTTP가 아닌 트래픽을 전달하는 기법&lt;/strong&gt;이다.&lt;/p&gt;
&lt;p&gt;많은 기업 네트워크/방화벽은 HTTP(80)와 HTTPS(443) 포트만 허용한다. HTTP tunneling을 사용하면 이 제한된 환경에서도 다른 프로토콜의 트래픽을 주고받을 수 있다.&lt;/p&gt;</description>
    </item>
    <item>
      <title>k8s-cp1 VM 네트워크 접속 불가 트러블슈팅</title>
      <link>https://blog.homelab89.com/docs/k8s/cp1-vm-network-troubleshooting/</link>
      <pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.homelab89.com/docs/k8s/cp1-vm-network-troubleshooting/</guid>
      <description>&lt;blockquote&gt;&lt;p&gt;작성일: 2026-03-05&lt;/p&gt;
&lt;/blockquote&gt;&lt;h2 id=&#34;증상&#34;&gt;증상&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;virsh domifaddr k8s-cp1&lt;/code&gt; 결과에 IP가 표시되지 않음&lt;/li&gt;
&lt;li&gt;VM에 SSH 접속 불가&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;원인-분석&#34;&gt;원인 분석&lt;/h2&gt;
&lt;h3 id=&#34;원인-1-네트워크-대역-불일치&#34;&gt;원인 1: 네트워크 대역 불일치&lt;/h3&gt;
&lt;p&gt;VM은 &lt;code&gt;virbr0&lt;/code&gt; (libvirt 기본 NAT 네트워크, &lt;strong&gt;198.51.100.0/24&lt;/strong&gt;)에 연결되어 있었지만,
cloud-init network-config에서는 &lt;strong&gt;203.0.113.70/24&lt;/strong&gt;를 할당하고 있었다.&lt;/p&gt;</description>
    </item>
    <item>
      <title>TLS 1.3 over HTTP Tunneling via Squid — 무엇이 문제인가</title>
      <link>https://blog.homelab89.com/docs/networking/tls13-over-squid-tunnel/</link>
      <pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.homelab89.com/docs/networking/tls13-over-squid-tunnel/</guid>
      <description>&lt;h2 id=&#34;배경&#34;&gt;배경&lt;/h2&gt;
&lt;p&gt;기업 환경에서 Squid 같은 Forward Proxy는 보안·감사·캐싱 목적으로 HTTPS 트래픽을 관찰하거나 검사한다.
그런데 TLS 1.3이 도입되면서, 기존에 프록시가 의존하던 여러 관찰 포인트가 사라졌다.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
