Getting Ready for IPv6: When and How Should an SME Make the Move?
TL;DR: What IPv6 is, when an SME should make the move, dual-stack architecture, and a practical preparation guide.
Summary: IPv6 is the next-generation internet protocol developed in response to IPv4 address exhaustion: instead of 4 billion addresses, it offers a practically unlimited pool. In Türkiye, mobile operators and large ISPs have largely completed the IPv6 transition; corporate networks are still IPv4-dominant. For an SME, the right framing is not "full cutover now" but dual-stack readiness: IPv4 stays exactly as it is, IPv6 is enabled in parallel. Over the next five years, enabling IPv6 will gradually become a baseline requirement; early preparation pays off. This article covers IPv6 fundamentals at SME scale, dual-stack architecture, and the practical preparation steps.
For years, SMEs treated IPv6 as "an enterprise problem — we'll stay on IPv4". The reality around us has changed: most mobile devices already connect over IPv6, AWS / Azure / GCP support IPv6, and IoT devices are being designed IPv6-first. When IPv6 is disabled on an SME network, some modern applications run sub-optimally — it goes unnoticed, but performance loss and compatibility friction quietly accumulate.
In this article we cover how to approach IPv6 at SME scale — the "no full cutover, but preparation is mandatory" mindset — and the practical steps. Target audience: IT managers, network administrators, and decision-makers who want to turn "does IPv6 affect us?" into a concrete answer.
Core Differences Between IPv4 and IPv6
IPv4
- 32-bit address
- ~4 billion addresses (effectively fewer usable)
- Format: 192.168.1.1
- Private networks via NAT
- Exhausted address pool
IPv6
- 128-bit address
- ~340 undecillion addresses (effectively unlimited)
- Format: 2001:db8::1 (hexadecimal)
- NAT generally not required
- New capabilities: SLAAC autoconfiguration, built-in IPSec
Side by Side
| Feature | IPv4 | IPv6 |
|---|---|---|
| Address length | 32 bits | 128 bits |
| Address count | ~4 billion | ~340 undecillion |
| Format | 192.168.1.1 | 2001:db8::1 |
| NAT | Common | Generally unnecessary |
| DHCP | Required | DHCPv6 or SLAAC |
| Multicast | Limited | First-class |
| Auto-configuration | Needs DHCP | Automatic via SLAAC |
| IPSec | Optional | Built in (not default-on) |
Anatomy of an IPv6 Address
Typical Form
2001:db8:abcd:0012:0000:0000:0000:0001
Shortened:
2001:db8:abcd:12::1
(Consecutive zero groups can be replaced with :: — but only once.)
Address Types
- Global Unicast: routable on the internet (2000::/3)
- Link-Local: local network (fe80::/10) — automatic on every IPv6 device
- Unique Local Address (ULA): private use (fc00::/7) — the IPv6 analogue of 192.168.x.x
- Multicast: ff00::/8 — replaces broadcast
Subnet Notation
2001:db8:abcd::/48 /* Site prefix */
2001:db8:abcd:0001::/64 /* Subnet 1 */
2001:db8:abcd:0002::/64 /* Subnet 2 */
A typical SME receives a /48 prefix from its ISP and can define 65,536 sub-subnets (/64) inside it.
IPv6 Adoption in Türkiye
How IPv6 looks on the ground:
- Mobile: Turkcell, Vodafone, Türk Telekom — IPv6 widespread
- Fibre / ADSL: TT, Turkcell, TurkNet — partial support
- Corporate: generally IPv4-dominant
- Cloud: AWS Türkiye Local Zones and Azure Istanbul region both support IPv6
The trend: between 2025 and 2030, IPv6 enablement on SME networks will become progressively widespread.
"Not a Full Cutover — Dual-Stack" — The SME Approach
The pragmatic SME approach: don't turn IPv4 off; enable IPv6 in parallel.
Why Dual-Stack Works
- IPv4 services keep working
- Applications and devices that support IPv6 connect over IPv6
- The transition is risk-free
- Performance improves where IPv6 is supported
Dual-Stack Architecture
Client (IPv4 + IPv6)
↓
Switch (IPv4 + IPv6)
↓
Router / Firewall (IPv4 + IPv6 dual stack)
↓
ISP (IPv4 + IPv6)
Most devices (Windows 10+, Linux, macOS, modern switches) already support dual-stack.
Preparation Steps
A 6-step path at SME scale:
1. Inventory
- Which devices support IPv6? (A modern OS — yes.)
- Are there older devices or applications in the mix?
- Are switches, routers, firewalls IPv6-enabled?
- Does the ISP offer IPv6?
2. Request IPv6 from the ISP
Ask the ISP for IPv6 prefix delegation:
- You typically get a /56 or /48 prefix
- Static or dynamic assignment
- BGP announcement (if needed)
3. Pilot Subnet
Enable IPv6 on a single VLAN:
- A development environment or a management VLAN
- Observe for 1–2 weeks
- If clean, continue
4. Firewall and Security
IPv6 needs its own ruleset:
- Firewall IPv6 rules (default deny + explicit allow)
- ICMPv6 matters (Path MTU Discovery)
- IPv6 RA (Router Advertisement) Guard on the switch side
5. DNS
- Dual-stack DNS (A + AAAA records)
- Internal DNS server with IPv6 support
- Public DNS (Cloudflare, Google) over IPv6
6. Monitoring and Logging
- Monitor IPv6 traffic
- Anomaly detection
- Track the attack surface
SLAAC and DHCPv6
Automatic addressing works differently in IPv6.
SLAAC (Stateless Address Autoconfiguration)
- The device learns the prefix from a Router Advertisement (RA)
- It derives the host portion from its own MAC address
- No DHCP needed
- Privacy extensions (RFC 4941) randomise the host portion
DHCPv6
- DHCP-style, static assignments
- Finer-grained control
- Useful for audit and logging
Hybrid
- Address via SLAAC + DNS server info via DHCPv6
- The common approach in SMEs
IPv6 Security Notes
New security topics that come along with IPv6:
New Attack Vectors
- Rogue Router Advertisement (spoofed RA)
- NAT bypass over IPv6
- Inadequate firewall rules
Countermeasures
- RA Guard on the switch
- A defined IPv6 ruleset on the firewall
- Filter ICMPv6 correctly (turning it off entirely is a mistake)
- Logging covers IPv6 to the same level as IPv4
Common Mistakes
- "We have an IPv4 firewall — that's enough" — IPv6 traffic walks past it
- Claiming IPv6 is disabled while link-local is still active on the device
- IPv6 leak via an open DNS resolver
The Cloud and IPv6
Hyperscalers offer IPv6 as a standard option:
AWS
- IPv6 support in VPC
- Egress-only Internet Gateway
- Application Load Balancer over IPv6
- A cost angle (IPv4 Elastic IPs are billable; IPv6 isn't)
Azure
- IPv6 support in Virtual Network
- Public Load Balancer over IPv6
- Application Gateway IPv6 (verify preview / GA status)
Google Cloud
- IPv6 support in VPC
- Network Connectivity Center IPv6
When an SME invests in the cloud, IPv6 support should be on the requirements list.
Application Compatibility with IPv6
How IPv6-ready typical SME software is:
| Category | Status |
|---|---|
| Microsoft Windows 10+ | Full support |
| macOS, iOS, Android | Full support |
| Web browsers | Full support |
| Modern web servers (nginx, Apache) | Full support |
| Modern databases (PostgreSQL, MySQL) | Full support |
| Office 365, Microsoft 365 | Full support |
| Legacy Windows applications | Mixed |
| Older IoT devices | Limited |
| Some older printers | None |
To avoid surprises when IPv6 goes live in your SME network, pilot testing is essential.
SME Migration Timeline
A suggested staged plan:
Year 1: Preparation
- IPv6 inventory
- IPv6 prefix request to the ISP
- Training (the IT team)
- Pilot subnet
Year 2: Broader Dual-Stack
- Dual-stack across every subnet
- Mature firewall ruleset
- IPv6 in cloud environments
Year 3+: Trimming IPv4
- Some internal services move to IPv6-only
- Refresh older IPv4-only devices
- Keep the IPv4 NAT layer but make IPv6 dominant internally
A full IPv4 sunset is a 5–10-year horizon for an SME; dual-stack readiness should be done inside 1–2 years.
What Yamanlar Bilişim Offers
Our IPv6 support areas at SME scale:
- An IPv6-readiness audit of your existing infrastructure
- ISP coordination for IPv6 prefix delegation
- Dual-stack architecture design
- Pilot subnet rollout
- Firewall IPv6 ruleset
- Dual-stack DNS configuration
- Annual IPv6-readiness report
Frequently Asked Questions
Where can I learn IPv6 properly?
- RFC 4291 — IPv6 addressing architecture (the official source)
- He.net IPv6 Certification — free online exam, very hands-on
- Cisco IPv6 documentation
- APNIC, RIPE training materials — and TR-NIC in Türkiye
Practical path for an SME IT team: the He.net certification (2–3 weeks) plus work on a real pilot subnet.
Conclusion
For an SME, IPv6 falls into the "not urgent today, late tomorrow" category. Dual-stack preparation enables IPv6 in parallel without disturbing the existing IPv4 setup; a pilot subnet brings the risk to zero. Asking the ISP for an IPv6 prefix, defining IPv6 firewall rules, and going dual-stack on DNS — these are all steps you can finish inside 1–2 years. A full IPv4 sunset is on a distant horizon; but having a modern SME network that supports IPv6 is a realistic target as of 2025–2026.
Yamanlar Bilişim provides an IPv6-readiness audit, dual-stack design, and pilot-rollout services sized to your needs — carrying your network into the future without unwelcome surprises.
Frequently Asked Questions
Do I really need to move to IPv6 as an SME?
It isn't mandatory today, but preparation is. Within 2–5 years, modern applications and providers may require it. Moving to dual-stack now is pragmatic — you gain IPv6 support without taking any IPv4 risk. Going fully IPv6-only is a longer horizon.
Will my legacy applications still work once IPv6 is enabled?
In a dual-stack environment IPv4 keeps working exactly as before and IPv6 runs in parallel. Legacy applications continue to use IPv4. To avoid surprises: pilot test (1–2 weeks), monitor, then roll out gradually.
Do I need NAT with IPv6?
Generally no. Because IPv6 offers effectively unlimited addresses, every device can have a global address — NAT isn't needed. Some organisations still use NAT66 because they treat NAT as a security veil — but that's not best practice. A properly configured firewall provides the security benefit NAT was a proxy for.
My ISP doesn't offer IPv6 — what now?
Start by asking. Most large ISPs in Türkiye now support IPv6; requesting may be enough. If the ISP genuinely doesn't support it: a tunnel broker (Hurricane Electric's free IPv6 tunnel) is a stop-gap. Longer term, switching to an IPv6-capable ISP is worth considering.
Will performance improve once IPv6 is on?
Usually you won't notice; some scenarios do improve (mobile-network clients connect directly over IPv6, more stably). Don't expect a performance revolution; what you gain is compatibility and future-proof infrastructure.
Author
Serdar YAMAN
Yamanlar Bilişim Expert
Writes content on IT infrastructure, cybersecurity, and digital transformation at Yamanlar Bilişim. Get in touch for any questions.
Professional Support
Get help on this topic
Let's design the Network and Security solution you need together. Our experts get back to you within 1 business day.
support@yamanlarbilisim.com · Response time: 1 business day
Keep Reading
Related Articles
Branch Connectivity Redundancy: What Happens When the VPN Drops?
When the tunnel linking a branch to head office drops, ERP screens, shared folders and internal telephony stop together. Why site-to-site tunnels fail, which redundancy pattern fits which topology, and the three settings that make a tunnel heal itself.
Backup Internet for the Office: A Failover Setup Guide for SMBs
When a single-line office loses its internet, phones, card payments and every cloud application stop at once. The four components of a dual-WAN failover setup, how to choose a second line that fails independently, and what users actually experience during the switchover.
Second Fibre or 4G/5G? Choosing the Right Backup Internet Line
Two strong candidates compete for the backup-line budget: a second wired circuit or a cellular 4G/5G solution. We compare them on infrastructure independence, CGNAT and static IPs, data quotas and latency — and give a clear recommendation for three typical office profiles.