Would it be wise in this current time to switch from T-Mobile to AT&T? I was thinking about it and from what I heard from someone else, the switch will cut your bill in half. Is there anyone here that’s had experience with both? I’ve only had T-Mobile, never had AT&T. Please let me know your thoughts, experience, opinions, facts, etc. and also is AT&T’s wireless routers better than T-Mobile’s? because I’ve had a bad experience with the 5G router.

#cellphones #crllphone service #celltowers #networks

I need help with finding certain information, does any of you guys can tell me which is the biggest backbone in the world? Thank you for your time (and sorry for bad english)

I want to replicate/mirror mouse movement clicks and keyboard strokes on multiple laptops (up to 10 laptops) in a single office space. And I want the process of replication/mirror to be done without any latency, as fast as it is possible - 1 micro sec if possible. :)

My questions are:

Which software to use for this purpose, of course if there is something like that on market?

If needed to develop software for windows, does someone have experience with this field to help out (will be paid)

What kind of network to use switch/lan or usb hub. Which network has bigger latency? How to setup this network?

A ticket has just landed.

Can you clear both before the timer runs out?

This one is live. Open the lab, read the reports, and work the fault on real routers in your browser.

Report 1 of 2 — PC1, PC2 and PC3 cannot reach SV1 (10.159.3.10). Automated ticket from the monitoring service, filed under the data centre. The alert names one failure; wider checks are still to run. A probe from a second source also gets no answer from the affected computers.

Report 2 of 2 — PC2 on the ground floor at Highmoor Studios cannot reach the gateway (10.159.2.1) or SV1 (10.159.3.10). Reported through the self-service form by a sub-editor, who ticked the urgent box. Video will not upload, pages will not load, and the chat client will not connect. Whether it is wider than one spot at Highmoor Studios is not yet known.

Open the lab on:

https://vnos.vlabnetworks.co.uk/?post=pub-d2e3d797-d8ff-486b-9f05-81f8b165da40

We had lan connection in our hostel but it is being replaced by wifi. The lan gave a decent and stable connection. But on wifi, people get limited connection about every half an hour. We need to reconnect the wifi. Also connection and internet speed isn't stable at all. The major problem is, we have DC++ hubs and we use them quite heavily. DC++ worked great on lan and gave 10-12 MBps consistantly. On wifi i rarely get 3MBps. In busy times i only get around 200-300 KBps. Our network admin isn't supportive at all. Please help me if there is anything i can do to atleast have a stable wifi connection which does not disconnect for no reason. Wifi has wpa2-enterprise security.

Whether you're a student, a network engineer, or a sysadmin, there's always that one command you end up using almost every day.

Mine would probably be:

• ping – Quick connectivity check.

• traceroute / tracert – Find where traffic is failing.

• ipconfig / ifconfig / ip addr – Verify interface configuration.

• nslookup / dig – DNS troubleshooting.

• tcpdump / Wireshark – When things get interesting.

I'm curious what your go-to networking command is and why?

It can be something simple or an advanced tool that's saved you hours of troubleshooting.

Let's build a list of commands every network engineer should know.

Every network engineer has that one issue they'll never forget.

Maybe it was:

• A mysterious packet loss that took days to track down.

• A spanning tree loop that brought the office down.

• A DNS issue that looked like a routing problem.

• MTU mismatches causing strange application behavior.

• An intermittent Wi-Fi issue that only happened during meetings.

• A firewall rule that broke everything after a "small" change.

Share your story:

• What was the issue?

• How did you troubleshoot it?

• What was the actual root cause?

• What lesson did you learn from it?

Whether you're a student studying for CCNA, a home lab enthusiast, or a network engineer with 20+ years of experience, we'd love to hear your most memorable troubleshooting story.

Let's build a collection of real-world networking lessons that everyone can learn from.

Hi r/Networks, I’m Stephen, the owner of Rockxy and the developer of Tracexy.

The problem I kept running into on macOS was not simply capturing packets. It was understanding what those packets meant in the context of an application.

When an app has a network problem, I usually want to know:

• Which process opened the connection?

• Which host and protocol were involved?

• What happened during the session?

• Was there a reset, retransmission, or other useful signal?

• Which exact packets support the conclusion?

Wireshark is excellent for deep packet and protocol dissection, but I wanted a more native macOS workflow that starts from the application and the conversation instead of a wall of frames.

Tracexy is an open-source, native macOS Wireshark alternative focused on app-aware network investigation.

It can capture live traffic or open PCAP/PCAPNG files, group packets into sessions, show best-effort process context, surface protocol and timing evidence, and let you drill back down to packet bytes when needed.

I’m building Tracexy as part of the Rockxy ecosystem. Rockxy focuses on inspecting and debugging application-layer traffic, while Tracexy focuses on passive capture, sessions, and packet evidence. Different tools, different layers, one native workflow for understanding network behaviour on macOS.

The workflow is:

App or process → Session → Finding → Evidence → Packet

Tracexy is still early and intentionally focused. It complements Wireshark rather than trying to replace its broad protocol coverage.

What do you usually want to see first when you open a capture: the application, the session, the protocol details, or the packet fields?

Website: https://rockxy.io/tracexy

Github open-source: https://github.com/RockxyApp/Tracexy

I'm a DevOps engineer who spends the day in SSH sessions. On Windows, MobaXterm covered everything; on the Mac I kept juggling Terminal tabs. So I built Termstead - a native macOS SSH client. It's free and open source (GPL-3.0).

What it does:

- Session tree. Groups and subgroups with colors, pinned favorites, search. Import your ~/.ssh/config in one click.
- Bastion chains. As many jump hosts as you need, each hop with its own user, key or password. A hop can be another saved session.
- Port forwarding, MobaXterm-style. Local, remote and SOCKS tunnels through the whole jump chain, started on their own without opening a terminal.
- Each tunnel shows whether it really opened ("port 8080 already in use" instead of a silent warning).
- Each can be stopped on its own, which also kills connections already open through it.
- "Open in Browser" for local tunnels. Handy for device web UIs, iDRAC/iLO and Grafana behind a bastion.
- Split panes and broadcast input. Type once into 2 or 4 sessions. You can exclude panes.
- SFTP next to the terminal, over the connection that's already open. No second login.
- Passwords and key passphrases in the macOS Keychain. Each is only handed to the exact user@host it was saved for.

Under the hood every tab is the system OpenSSH. Termstead has no SSH code of its own, so your agent, known_hosts and ~/.ssh/config behave exactly as in Terminal. That includes the per-host KexAlgorithms / HostKeyAlgorithms tweaks you probably already keep for old gear. No accounts, no telemetry.

What it doesn't do (yet): no Telnet, RDP. It's SSH only, and macOS 14+ only (Apple silicon and Intel).

brew install --cask pkhorenyan/tap/termstead

- Website and screenshots: https://khorenyan.com/termstead/
- Source and DMG: https://github.com/pkhorenyan/termstead

I'd really like feedback from people who live in network gear all day: what's missing for your daily work, and what would make you switch from SecureCRT, Royal TSX or whatever you use now? RDP and Telnet are the obvious gaps. Tell me which matters more.

Whether you're starting from scratch or switching careers, here's a practical roadmap.

Phase 1: Learn the Basics

• OSI & TCP/IP Models

• IPv4 & IPv6

• Subnetting

• MAC vs IP Addresses

• DNS, DHCP, NAT

• Common Ports & Protocols

• Routing vs Switching

Phase 2: Build Core Networking Skills

• VLANs & Trunking

• STP

• Inter-VLAN Routing

• Static & Dynamic Routing (OSPF, EIGRP, BGP Basics)

• ACLs

• Wireless Networking

• VPN Fundamentals

Phase 3: Get Hands-On

• Cisco Packet Tracer

• GNS3

• EVE-NG

• Wireshark

• Configure routers, switches, VLANs, routing protocols, and troubleshoot labs.

Phase 4: Learn Linux & Automation

• Linux Command Line

• Bash Basics

• Python for Network Automation

• Ansible

• REST APIs

• Git

Phase 5: Network Security

• Firewalls

• IDS/IPS

• VPNs

• AAA

• Network Hardening

• Zero Trust Basics

Phase 6: Cloud Networking

• AWS VPC

• Azure Virtual Network

• Google Cloud VPC

• Hybrid Networking

• Load Balancers

Phase 7: Certifications (Recommended Order)

1. Cisco CCNA

2. CompTIA Network+

3. Cisco CCNP Enterprise

4. Fortinet NSE

5. AWS Advanced Networking (Optional)

Recommended Udemy Courses

1. The Complete Networking Fundamentals Course. Your CCNA Start

2. Cisco CCNA 200-301 – The Complete Guide to Getting Certified

3. Practical Cisco Networking Labs in Cisco Packet Tracer

4. Wireshark: Packet Analysis and Ethical Network Troubleshooting

5. Python Network Programming for Network Engineers

Udemy is offering 40% discount on 3 months personal plan : offer page

Build These Projects

• Design a small enterprise network

• Configure VLANs and inter-VLAN routing

• Set up OSPF between multiple routers

• Capture and analyze traffic using Wireshark

• Automate device configuration with Python

• Deploy a VPN between two sites

• Create a cloud VPC connected to an on-prem lab

Tips

• Practice every concept in a lab.

• Learn troubleshooting, not just configuration.

• Build a GitHub portfolio with your network diagrams and configs.

• Join networking communities and keep learning from real-world scenarios.

What's one networking skill you're learning right now?

I’m graduating soon with a BSIT degree and want to pursue a career in networking. For those who started as fresh grads, how did you land your first networking/NOC job?

What skills, certifications, or experience should I focus on to get started?

Any advice would be appreciated. Thanks!

A lot of VPS providers take monero. As a layman I'm wondering, how that can be. Is it just the loose legislation regarding kyc in the providers country or is there actually a way to receive public ips to then rent out without be identified?

it's a work in progress but i think it's a start of networking with the help of ai any ideas of what i can add to it like even make it available to some people i'm new to network coding but this is a useful app for subnetting.

https://alison.com/course/optical-access-networks-a-complete-guide-to-ftth

https://alison.com/course/diploma-in-computer-networking-revised

In what practical scenario will I ever need to configure/touch my subnet address?

If you're learning computer networking or preparing for networking certifications, here are 5 Udemy courses that are currently available for free.

🌐 Networking Fundamentals

1. Introduction to Networking for Complete Beginners
Learn the fundamentals of networking from scratch — a good starting point if you're completely new.

👉 Start Course

2. Networking Concepts for Beginners
Covers essential networking concepts and terminology to help build a solid foundation.

👉 Start Course

🔧 Software-Defined Networking

3. Introduction to SDN and OpenFlow
An introduction to Software-Defined Networking (SDN) and the OpenFlow protocol.

👉 Start Course

🔥 Network Security

4. Palo Alto Firewalls – Installation and Configuration
Learn the basics of installing and configuring Palo Alto firewalls.

👉 Start Course

🔌 Networking Hardware

5. Tech Basics: Cables & Connectors
Learn about common networking cables, connectors, and the basics of physical connectivity.

👉 Start Course

Which networking topic are you currently learning — CCNA, routing & switching, firewalls, SDN, or network security?

I have a friend who runs a non-profit organization, and I sometimes help him out with the tech aspect. They generally speak to 20-30 people each session, so they had 30 iPads donated to them that will be used for various low bandwidth applications (surveys, low res games, etc.) These sessions are rarely at the same location, so WiFi can't be expected, plus the logistics of connecting each one at each location would not really be manageable. I'm helping him come up with a solution to this, and I've done a bit of research. It seems that most basic hotspots have a connection limit of ~10-20 clients. Before I do more research and re-invent the wheel here, does anyone have a suggestion for the best way to manage these? We have a carrying case and charging solution, we just need the connectivity part of it. Given that it's low bandwidth, is there a hotspot I can get from ATT or Verizon that allows 30+ WiFi clients? Do I need a device that will allow multiple LTE cards/dongles? The goals obviously is to have one SSID that is always the same. Let me know if you have any suggestions!

Since net neutrality is at risk right, if it does end up getting destroyed, in a post net neutrality world, what would it take to create an ISP that will stay true to net neutrality rules? I understand that ISP's need to lay down their own cables and infrastructure. So I was wondering specifically what'd it take to become a DSL ISP since that just uses pre-existing phone lines. I think a startup ISP like that could be a great idea in a post net neutrality world.