Home-network failures are often collapsed into “the broadband is down,” but the line, session, IP configuration, routing, and Wi-Fi are different layers. Locate the failing layer before changing configuration. This guide assumes no provider, speed, interface, or access method. Obtain accounts, VLAN, MTU, IPv4/IPv6, and device-mode requirements from the current contract and the provider's written parameters.
Table of Contents
1. Understand the terms as layers
| Term | Layer or role | What it is | What it is not |
|---|---|---|---|
| Broadband, narrowband | Service or policy description | Relative labels for access capability; thresholds change by place, policy, and time | A fixed protocol or a statement of the line medium |
| DSL, ADSL | Copper access | DSL is a digital-subscriber-line family; ADSL is designed with asymmetric directions | PPPoE or Wi-Fi |
| Fiber, PON | Optical access | A provider optical-access network; GPON systems include an OLT, ODN, and ONU/ONT | An automatic statement of authentication or routing mode |
| PPPoE | Session and encapsulation | PPP over Ethernet, with discovery, session, and optional authentication | Telephone dialing, a VPN, DSL, or a physical line |
| IPoE, DHCP, static IP | IP configuration | A provider may deliver IP with DHCP, IPv6 SLAAC/DHCPv6, or static parameters | Wi-Fi or a guarantee of a public address |
| Ethernet | Wired link | May be a home LAN or the provider handoff | Internet service merely because a cable is connected |
| Wi-Fi | Wireless LAN | The local radio link between a client and access point | The Internet, a broadband account, or a provider line |
| Cellular | Wireless wide-area access | Packet-data access through a phone, hotspot, or cellular router | A reason to reuse old GPRS dialing instructions or assume public IPv4 |
56K telephone dial-up and GPRS are historical context, not current setup paths here. Never use shared, default, or web-found ISP credentials, and do not buy an unsupported second-hand modem with no security updates to restore a legacy workflow.
2. Separate access technology from upper-layer service
ADSL is an access technology over metallic twisted pairs; ITU-T G.992.1 defines transceivers and the physical-layer interface. Fiber access uses a different system; GPON in ITU-T G.984.1 includes the provider OLT, optical distribution network, and customer ONU/ONT. Cable, fixed wireless, satellite, and cellular have their own access boundaries.
One physical access can deliver different upper-layer methods. After a DSL or fiber Ethernet handoff, the service might use PPPoE, DHCP/IPoE, static IPv4, IPv6 prefix delegation, or a combination. Conversely, PPPoE is not limited to ADSL.
Do not infer parameters from the words “fiber” or “broadband,” or from a device's appearance. Identify the provider handoff first: telephone copper, coax, optical ONT, Ethernet port, fixed-wireless terminal, or cellular SIM/eSIM device.
3. Modem, ONT, router, switch, and AP
| Device or function | Primary responsibility | Common boundary |
|---|---|---|
| Modem | Terminates a specific line signal and presents a data link locally | DSL and cable need matching line equipment; they are not interchangeable |
| ONU/ONT | Terminates the provider passive optical access | May be optical-to-Ethernet only, or integrate routing, voice, and Wi-Fi |
| Router | Forwards IP between WAN and LAN; often includes firewall, NAT, DHCP, and IPv6 prefix delegation | May terminate PPPoE or obtain an address through DHCP/static configuration |
| Switch | Forwards Ethernet frames within one layer-2 network | Does not authenticate Internet service; an unmanaged switch does not normally supply ISP VLAN configuration |
| Wireless AP | Bridges Wi-Fi clients onto the local network | May be separate or integrated into a home gateway |
| Home gateway | Combines several modem/ONT, router, switch, and AP functions | Its bridge or router mode changes the functional boundary |
The colloquial “optical modem” usually refers to a device with ONT functionality, but the product may also contain a router and AP. Check its mode and port functions, not only its label.
4. Three common topologies and session placement
A. Bridge device and own router
ISP access network --> [modem or ONT: bridge] --> [router: PPPoE or IP, firewall, DHCP] --> devices
B. Provider gateway
ISP access network --> [gateway: modem or ONT + router + switch + AP] --> devices
C. Upstream gateway and downstream AP
ISP access network --> [gateway: routing] --> [second device: AP or bridge mode] --> devicesBridge mode passes the provider service to a downstream device, so PPPoE or IP configuration usually terminates on the customer's router. In router mode, the upstream gateway terminates the WAN session and supplies LAN addresses. A second device in router mode creates another routing boundary and commonly double NAT. If both also initiate PPPoE, duplicate sessions or authentication conflicts result. Do not configure this unless the provider explicitly provisions multiple sessions.
If the upstream device must remain a router, placing the downstream device in AP/bridge mode is usually simpler than stacking NAT. Host-terminated PPPoE is only for a deliberate single-host design; that host needs a firewall and must not expose an unprotected LAN to the provider side. Before enabling bridge mode, verify whether IPTV, voice, remote management, or VLANs depend on the provider gateway.
5. IPv4, IPv6, NAT, and CGNAT
A provider may supply public IPv4, RFC 1918 private space, RFC 6598 shared 100.64.0.0/10 space, IPv6, or a combination. A private or shared WAN address usually indicates upstream NAT, but confirm with the provider. Under CGNAT, a customer router's port-forward rule cannot control the provider's upstream mapping. For inbound connectivity, ask about public/static IPv4, native IPv6, or a supported alternative instead of disabling the firewall.
IPv6 is routable without NAT, so IPv6 firewalls on the router and hosts remain important. Receiving a global IPv6 address does not mean a port is open; lacking one does not by itself prove that the provider lacks IPv6. Record the router's WAN address, IPv6 prefix, and delegated-prefix length, and test IPv4 and IPv6 separately.
Double NAT and CGNAT are different: the first usually comes from two local routing layers, while the second occurs in the provider network. Both can exist at once.
6. VLAN, MTU, and provider-specific parameters
- VLAN: A provider may require a particular 802.1Q VLAN ID and priority, and may separate Internet, IPTV, and voice. The designated device should apply the tag once; never copy another subscriber's VLAN value from the web.
- MTU: With traditional 1500-byte Ethernet carrying PPPoE, an IP MTU of 1492 is common. RFC 4638 permits 1500 when the whole path supports larger frames, but it does not make 1500 valid everywhere. Prefer the provider or device's automatic value.
- Encapsulation and binding: Confirm whether PPPoE, DHCP/IPoE, static IP, MAC binding, options, service name, or other parameters are actually required. Do not guess or clone an unknown device identifier.
- Multiple services: IPTV multicast, voice ports, and provider remote management may depend on separate VLANs or managed configuration. Ask for a preservation plan before bridging or replacing equipment.
Partial page loads, stalled VPNs, or large-packet failures can involve MTU/path MTU, but can also originate in DNS, a firewall, or the remote endpoint. Gather evidence rather than repeatedly changing MTU at random.
7. What to ask the provider without leaking secrets
| Question | Needed answer | Safe handling |
|---|---|---|
| What is the physical access and handoff? | DSL, PON, coax, fixed wireless, or cellular; handoff port and equipment ownership | Record model and support status; do not publish serial, LOID, or SIM/eSIM identifiers |
| What is the WAN method? | PPPoE, DHCP/IPoE, static IPv4, IPv6 SLAAC/DHCPv6, and prefix delegation | Record only the method; enter credentials directly in the local management interface |
| Is PPPoE required? | Username format, service name, and permitted session count | Never send a password in chat, ticket screenshots, command history, or public logs |
| What are VLAN and MTU? | VLAN ID/priority, tagging device, and WAN MTU | Request written parameters; do not try another subscriber's settings |
| What is the address boundary? | Public/private/CGNAT IPv4, IPv6 prefix and delegated length, static options | Redact IP, MAC, account, and customer number in shared diagnostics |
| How are additional services preserved? | IPTV, voice, remote management, fixed-line, and alarm requirements | Do not bridge or reset provider equipment without a rollback |
| Who updates and supports the equipment? | Ownership, firmware source, support lifetime, and replacement process | Install only official signed firmware; reject untrusted configuration backups |
Do not give a full password to support staff through an unofficial direct message. Enter secrets only on a verified provider domain/app or the local management page, store them in a password manager, and avoid screenshots.
8. Evidence and safety plan before changes
- Draw the current topology and mark the provider handoff, every device mode, WAN/LAN ports, and the PPPoE/IP termination point.
- Record link, DSL/optical status, WAN method, IPv4/IPv6, DNS, VLAN, MTU, uptime, and error times from read-only pages. Remove secrets and device identifiers before sharing.
- Preserve current configuration and photos. A router backup may contain plain or recoverable credentials; encrypt it offline and restrict access.
- Confirm with the provider and manufacturer that target hardware is supported, receives security updates, and matches the interface. Avoid an unknown or unsupported second-hand modem/ONT.
- Define a maintenance window, success criteria, and rollback point. Do not factory-reset without recovery credentials, a backup, and provider support.
- Change one layer at a time: access link, WAN session, IP/DNS, then Wi-Fi and additional services.
9. Read-only verification
Start with LEDs and local status pages: line/optical link, WAN session, IPv4 address, IPv6 address and prefix, default route, DNS, MTU, VLAN, and event log. Do not export an unredacted page to a public service.
On Linux with NetworkManager, these commands read status only; do not add --show-secrets:
nmcli --terse --fields DEVICE,TYPE,STATE,CONNECTION device status
nmcli --fields GENERAL.STATE,GENERAL.CONNECTION,IP4.ADDRESS,IP4.GATEWAY,IP4.DNS,IP6.ADDRESS,IP6.GATEWAY,IP6.DNS device show
ip route show default
ip -6 route show defaultOn Windows PowerShell, read the adapter, IP configuration, and default routes:
Get-NetAdapter | Select-Object Name, Status, LinkSpeed
Get-NetIPConfiguration
Get-NetRoute -AddressFamily IPv4 | Where-Object DestinationPrefix -EQ "0.0.0.0/0"
Get-NetRoute -AddressFamily IPv6 | Where-Object DestinationPrefix -EQ "::/0"Output can contain private/public IPs, DNS, interface names, and MAC addresses. Analyze locally and minimally redact before creating a support ticket. Do not run commands that change connections, delete profiles, reset equipment, or reveal secrets.
10. Failure matrix
| Symptom | First layer to inspect | Read-only evidence | Do not start by |
|---|---|---|---|
| DSL/optical/cellular link is down | Physical access and provisioning | LEDs, optical/DSL status, provider outage notice, cabling, power | Repeated resets or PPPoE password changes |
| Link is up but WAN is disconnected | Session, authentication, DHCP, VLAN | WAN method, PPPoE error, DHCP state, VLAN, timestamps | Dialing from multiple devices |
| WAN address exists but default route does not | IP configuration | IPv4/IPv6 address, prefix, gateway, route table | Disabling the firewall to experiment |
| IP works but names fail | DNS | Provider/router DNS and results for both families | Treating random public DNS as a root-cause repair |
| Only some sites or VPNs fail | MTU, DNS, IPv4/IPv6 path | MTU, session log, separate family tests | Randomly reducing MTU and leaving it there |
| Ethernet works but Wi-Fi is weak or drops | Local WLAN | AP state, channel, band, distance, roaming, client differences | Declaring the provider line faulty |
| Port forwarding fails | CGNAT, double NAT, firewall | WAN range, two routing layers, provider address policy | Exposing a DMZ or disabling the IPv6 firewall |
| IPTV/voice fails after bridging | Multi-service VLAN and managed configuration | Old configuration, port binding, provider parameters | Deleting more VLANs or factory-resetting |
11. Security, privacy, and remote-management boundaries
- Replace default router-admin and Wi-Fi passwords, and use supported WPA3-Personal or WPA2-Personal. Do not reuse ISP, email, or other account passwords.
- Install supported firmware only from the provider or manufacturer. Read release notes, verify the exact model, and understand rollback limits; never flash firmware for a similar model or another region.
- Disable unneeded WAN remote management, WPS, UPnP, and exposed ports by default. If a provider-managed gateway requires remote management, clarify responsibility rather than breaking provisioning or security updates.
- Prefer HTTPS or an official app for local management and confine it to a management network. If remote management is necessary, use manufacturer-supported strong authentication, MFA, or a controlled VPN, not plaintext HTTP/Telnet.
- IPv6 also needs a stateful firewall. NAT is not a firewall, and disabling NAT is not a general security diagnostic.
- Logs and backups can expose accounts, IPs, MACs, SSIDs, client names, browsing data, or serial numbers. Minimize collection, limit retention, encrypt, and redact before sharing.
Broadband Forum TR-124 specifies residential-gateway requirements for PPPoE, IPv4/IPv6, firewalls, and management, but verify whether a particular product implements them and has safe defaults in its current support material.
12. Migration from legacy copper and rollback boundaries
- Inventory the old line, telephone numbers, alarms, fax, IPTV, voice, static addresses, port forwards, and required devices. Do not assume analog-telephone functions survive an Internet-access change.
- Obtain the new provider's written handoff, WAN method, VLAN/MTU, IPv4/IPv6, equipment ownership, and additional-service plan.
- When possible, retain the old service until the new link passes wired, Wi-Fi, DNS, IPv4, IPv6, VPN, and required-service tests. Do not use advertised speed as the sole acceptance test.
- Have the provider provision and register any ONT/ONU, SIM/eSIM, or other controlled terminal. Do not clone serials, LOIDs, SIM identifiers, or unauthorized equipment identities.
- Migrate only port forwards and rules that remain necessary, documenting each one. Check double NAT, CGNAT, and the IPv6 firewall.
- Before cancelling, retain dated acceptance evidence and a provider ticket, and confirm number porting, equipment return, billing, and data-erasure requirements.
Stop and escalate to the provider if link state is abnormal, credential provenance is uncertain, VLAN/MTU is unknown, bridging affects voice/IPTV, firmware is unsupported, or the recovery path is unverified. Rollback means restoring documented cabling, modes, and configuration, not erasing the device. Provider-owned ONTs, lines, and remote configuration belong with the provider.
13. Related page and official sources
The site's historical Linux PPPoE command article (post 717, canonical HTTPS link) preserves older distribution-command context. It is not a source for current provider parameters; verify commands against current distribution documentation and the credential boundaries in this guide.
- ITU-T G.992.1: ADSL transceivers
- ITU-T G.984.1: GPON general characteristics
- RFC 2516: PPPoE
- RFC 4638: PPPoE MTU/MRU greater than 1492
- RFC 2131: DHCP
- RFC 1918: Private IPv4 address space
- RFC 6598: Shared address space
- RFC 8200: IPv6 specification
- RFC 4862: IPv6 stateless address autoconfiguration
- Broadband Forum TR-124 Issue 9: Residential gateway requirements
- IEEE 802.3-2022: Ethernet
- IEEE 802.11 Working Group: Wireless LAN
- IEEE 802.1Q-2022: Bridges and VLANs
- NetworkManager: nmcli reference
- Microsoft: Get-NetAdapter
- Microsoft: Get-NetIPConfiguration
- Microsoft: Get-NetRoute
Sources checked on 2026-09-01. Standards, provider configuration, device support, and service availability change; verify again at deployment time.
14. Original 2011 archive (provenance only)
The fence preserves the complete visible source_export body verbatim, with exactly two value-level safety substitutions: one historical public username became [historical public username redacted], and one historical public password became [historical public password redacted]. No trailing whitespace was normalized and no URL was removed; no private or tracking link required redaction. The archive contains errors, obsolete workflows, a historical dial number, prices, and unsafe advice. It is not current instructions.
~~~~markdown
Table of Contents
Toggle
上网的方式
- 使用56k MODEM网络+MODEM调制解调器拨号上网
- 使用ADSL宽带网络+MODEM调制解调器拨号上网
- 使用路由器或局域网接入
- 使用无限网卡接入无线网络
- 使用手机上网，包括以手机作为MODEM拨号上网、以手机进行GPRS上网，还有手机直接拨号上网
笔记本上网的方式
- 直接将电话线插在笔记本上进行MODEM拨号上网
- 直接插网线（双绞线）进行ADSL
- 使用路由器或局域网接入
- 直接打开无限网络设置进行无线上网
- 使用手机、手机数据线及其驱动光盘进行手机上网
ADSL（宽带）
Asymmetrical Digital Subscriber Loop, 是非对称数字用户环线（硬件），ADSL是服务网络
pppoe（虚拟拨号）
PointProtocoloverEthernet是以太网上的点对点协议（软件），PPPOE是接入类型
ADSL虚拟拨号
所谓虚拟拨号是指用ADSL接入INTERNET时同样需要输入用户名与密码（与原有的MODEM和ISDN接入相同），但ADSL连接的并不是具体的接入号码如16900，而是所谓的虚拟专网VPN的ADSL接入的IP地址。
56K MODEM（窄带）
虽然现在宽带很流行，但对于很多没有开通宽带的城市郊区或小乡镇读者而言，56K MODEM依然是其上网时的首选。
56K MODEM是将电脑通过电话线连接到另一台电脑或一个电脑网络的装置，它的作用是将电脑的数字信号转换为能够依电话线路传输的模拟信号，通过网络传递到另 外的电脑或服务器；对于接受到的模拟信号，则由它再解调为数字信号，以便电脑能够识别。
此外，目前一些调制解调器还具有传真功能，可用来接收和发送传真， 有些型号还具有语音功能，可以方便地实现语音信箱等功能。
56K指的是Modem与ISP之间建立网络连接时的速率，它是一个理论值，在实际的上网过程 中，由于电话线路质量及网络传输的忙碌程度不同，实际的传输速率在很多情况下达不到其额定值（最高能达到52K、而在边远地区最多能达到14-36K就不 错了），所以其在多数上网应用中已显得力不从心。
适合人群：已有MODEM（如笔记本电脑内置），在国庆期间偶尔上网的用户。当然，你也可买一块新MODEM或淘一块人家不用的二手猫来用，其投入也不 多，大概20-100元左右。
现在采用56K MODEM上网除了廉价的包月方式外，一般都使用的是公用通用帐号和密码（如帐号[historical public username redacted]：密码[historical public password redacted]），不需要单独的申请，这样即使你是带着笔记 本到异地去旅游，只要小旅店里有电话你就可用其上上网，收下Email，看看有没有好友QQ消息等等。
Modem（猫、调制解调器）
硬件，调制解调器，笔记本一般内置Modem，使用ADSL虚拟拨号也需要用一个外置的Modem。但笔记本的内置Modem不能够用来进行ADSL虚拟拨号。
路由器
这个我也不会解释，我们一般可以用路由器进行ADSL虚拟拨号，当然也可以路由器再接一个路由器。
~~~~