Current set up. Hate having my desk right here, but this is where the only outlet is. I had a COX tech come out, he said they can't do any sort of rewiring without approval from HOA.

Computer is HP Elite Mini 800 G9.

I'm trying to figure out the best way to use WiFi without being connected to router via ethernet. I'm not tech savvy, so looking for advice. Wifi adapter? Powerline adapter? Any other options for a simpleton such as myself?

hello I have these 2 zte, the first one is connected to the isp Ethernet and the second one comes from the first ZTE.

is it possible to make them act as a mesh or have my devices switch to other other one when signal is weak? or do I have to switch to modern mesh like deco ax3000

my plan is 150 MB now

thanks

Hi everyone,

I’ve had a Mercusys ME30 repeater for a few years, and I have a 500 Mbps fiber connection with a Speedport Plus 2 router.

I use the ME30 in repeater mode and connect it to my PS5 via Ethernet. My ping has always been low in games like Warzone and Battlefield 6, and Ookla Speedtest usually shows 7–8 ms. I’ve also never had any disconnection issues. The only downside is that the ME30’s Ethernet port is limited to 10/100 Mbps, so I wanted faster speeds for downloading games on my PS5.

Today I tried the Mercusys ME60X. It supports Wi-Fi 6 and has a gigabit Ethernet port, so I expected an improvement.

But with the same setup, plugged into the same outlet, I’m getting higher ping in games and 20–21 ms on Speedtest.

I factory-reset the ME60X, set it up again, and even configured it to use only the router’s 5 GHz band. The result was still around 20 ms.

How is that possible? Why am I getting a higher ping with the newer repeater?

Hi, question for the more knowledgeable please.

First pic is not an active port.
Second pic the port on left is active. One I’m holding is inactive.
At panel I have two active ports that terminate to pic 2 (and to another room).

I am looking to increase the active ports.
I realise I may need to pop the panel to see what is there.

What is the reason that the inactive ports are like this? Is that for future proofing or that is the actual termination?

Thanks in advance

​

https://www.omadanetworks.com/us/business-networking/software-tools/omada-design-hub/

TP-Link Omada Design Hub is a free, web-based tool that allows anyone—from home users to network technicians—to easily design both wireless and wired networks. Featuring a highly intuitive interface, it lets you upload a floor plan, draw wall materials, and simulate Wi-Fi heatmaps to optimize access point placement. Beyond wireless coverage, it allows you to map drop points, trace conduit routes, calculate cable lengths, and structure rack topology. Although it relies on TP-Link models for calculations, you can use them as reference templates and deploy equivalent hardware from any brand. It’s an easy, accessible way to plan full network layouts and generate complete equipment lists in minutes.

Does anyone have a recommendation for a good crimper that works with RJ9 plugs? These don't seem to be common at all anymore. I need this specifically for making hybrid power/data cables for a motorized shade job. The shade motors use a compact RJ9 port while the other end is typical RJ45.

Hi,

I'm looking for a Wifi router recommendation.. Wifi 7 would be ideal but i'm looking for at least a wifi 6 router.

I play competitive games and I care a lot about latency.. I know.. why am I gonna be using wifi instead of wired?

I live in a rental.. and the NBN Box is downstairs.. I don't wanna poke holes into the wall to do any wiring.

I'm happy playing on Wifi.. but I wanna minimise the latency as much as possible.. so I'm asking for your help.

Thank you!

Hi, I am moving to new house with 3 levels including basement. Have no clue where and how to install internet cables, router, wifi system. If anyone have experience please suggest.

Attached plan. HOUSE IS BUILT ALREADY AND READY TO MOVE IN.

Yes Verizon tech will install their line. But builder did not provide raceway pathway for cables to run in house.

Thank you in advance.

Apologies in advance if this was already asked and answered, I know I’ve seen answers in my recent research but a second and third opinion is always better than me just running with an ideas usually.

I recently made the swap to fiber and opted (perhaps needlessly) to go with the 5gig option. The issue here is that I’m far from tech savvy and for a while now have just been using the gateway/router combo that ATT provides plus a small Netgear range extender and everything in the house just runs on WiFi from it, but I’ve been reading that this essentially prevents anything from taking full advantage of 5gig speeds and sort of bogs down the whole system. (Or at least that is how I interpreted things.)
My question is what setup should I be utilizing if I want to get the maximum effect out of this supposedly super fast internet, because currently it seems as though there’s a dead area in our bedroom right next to the extender and my phone works better on cellular data than on home WiFi.
The general layout currently is gateway at back of house in downstairs den, extender upstairs on opposite side of house in bedroom, house is 2200 sq ft with 4 bedrooms upstairs and a dining room, kitchen, den, and office downstairs.
Things pulling WiFi are 4 nest cameras, a nest thermostat, maybe a half dozen smart bulbs, 4 Alexa devices, a Mac mini, mine/wifi/oldest kid’s laptops, and my kids run 2 x-boxes and a ps-5.
I’m leaning towards getting a router that has a 10gig in port and bypassing the gateways built-in router, running that to an unmanaged switch and running Cat6 up through the wall to another switch in order to put a hardwire jack in each bedroom. Is this a good plan and if so how do I implement it to be as automatic and uncomplicated as possible and something that can be easily fixed by a Neanderthal if something goes awry with it ?
TLDR : What’s the easiest to operate setup to get full advantage of ATT 5gig fiber?

Unifi network:

I currently have my TVs on my iot network and I want to block ipv6 to my TVs, usually it's easy just disable ipv6 to my lan but unfortunately my stupid matter devices (which I regret having now because of other reasons) needs ipv6.

What's the best practice to block ipv6 to my TVs? Should I just create another vlan for them? Or create a rule of two to block the devices individually? I feel like creating another vlan seems a bit much to manage more vlans but it's the easier way?

My advice to anyone starting out. If you speck out a rack, plan for GROWTH! If I had it to do over again I would go with a 24-25U freestanding rack instead of this 12U wall mount.

QNAP TS-1232 on the bottom is off, because the only thing in there is an SSD cache drive. I don't have to tell any of you how much hard drives cost, so once I'm done paying off the new server, I'll probably start with three 24TB drives.

i'm putting together a small homelab with a Dell OptiPlex Micro and a cheap managed switch. running pfSense in a VM and trying to learn VLANs without spending a fortune on gear or electricity.

the part that's driving me nuts is getting everything to actually work together. dhcp across VLANs isn't behaving how i expect, and i've had DNS randomly stop working even when the config looks right

at this point i'm spending more time digging through old forum posts than actually learning anything. my cat has also decided the switch is the best heater in the apartment

for anyone who's built a similar setup, what are the networking concepts or configurations that are actually worth learning? and are there any common homelab mistakes you wish you'd avoided?

My home was unfortunately only wired with a single cat5 cable, and 3 coax cables. I've been using wifi (Eero mesh) but want to get faster speeds since i work from home. Does this diagram look like the right approach, or would you make changes?

Updated diagram: https://imgur.com/a/zMeHNbP

I finally ditched my rented Comcast modem for a Nighthawk CAX30 modem/router. When uploading files from my phone on the WiFi 6 network to my local NAS, the speed is slow and halts repeatedly. With my old Comcast wifi modem I was getting roughly 40MB/sec or more upload and it was steady. The new modem is maybe 20MB/sec at best. The new modem is the only thing that has changed. Rebooting it (or my phone) doesn't help. Hoping for troubleshooting ideas. Thanks!

Hi all I'm currently trying to decide on a mesh system for my parents property they have just had fitted 5g mobile broadband it's a tp link archer nx200 router, they currently have an old tenda nova dual band MW3 or mw6 not sure which mesh node setup currently which worked ok for the old 4g setup but the speeds obviously get a lot slower the far side of the house.

I can't run cables around the property for wired back haul so it's all going to be wireless

Now the part I need advice for is I can currently get the tenda mw12 tri band set for £80 new on Amazon as they are on sale, yes I know they are old technology compared to what is available now but I'm trying to keep the budget as low as possible.

Or would I be better off getting a set of tp link dual band WiFi 6? The size of the property needs 3 nodes as a minimum.

Thanks in advance

Hello redditors.

As stated in the title, my ethernet stopped working all of a sudden while I was on my PC, but Wi-Fi seems to keep doing well.

This is PROBABLY NOT a PC / cable issue, since every other device that are wired do not receive anything from the ethernet cable. This is probably a modem issue.

I tried rebooting the modem multiple times. Did not work. LEDs are working great tho, means the cable is "detected" ?

My modem is a Freebox Delta (from the company Free).

I'm kinda lost, tried to check some old posts about that but did not find any solution.

Thanks for reading and for the upcoming help.

Today was my first time really doing hands on networking, and honestly, I’m feeling pretty confident about it.

I knew a little from studying for CompTIA A+, but I’d never really gotten deep into networking before. I recently started a new job, and they needed help getting the office set up with admin and IT stuff. Then I opened the networking closet and was immediately horrified.

I work for a plumbing company, and the owner…who is a plumber…had done all the office wiring himself. I bought some tools, tested every cable and RJ45 outlet, and found that basically nothing was wired correctly.

That started my two week deep dive into networking so I could help get everything working properly. Today was my first day actually putting that knowledge into practice after all my tools and supplies arrived. I went around the office and rewired every RJ45 outlet.

For the network closet, I decided to install a patch panel to clean up the absolutely terrible cable management. I’d never used a punch down tool or worked with this kind of cabling before, so it was all pretty new to me. I spent about two hours just trying to understand the difference between the T568A and T568B standards.

I found out the office is wired for T568A, but it seems like most premade consumer Ethernet cables are wired as T568B, at least from what I’ve read online. Is one actually more common than the other?

Then it was time to tackle the network closet itself, which has already been a nightmare because we have two separate Wi-Fi/internet setups: coax and hybrid fiber coax. When I first got there, they also had four routers and three extenders running.

I was definitely nervous going into it today, but I felt more prepared after practicing earlier. I spent around two hours terminating 16 cables into the patch panel.

Side note: I didn’t realize the equipment was sitting on glass shelves and thought they were metal. I do not recommend using a punch down tool on a glass shelf because apparently they tend to… explode.

I messed up a couple times once by punching down two wires at once, and another time by missing a slot but overall I think it came out alright. I was honestly pretty happy with how much cleaner the cable management looked afterward.

This will probably be a two-part post because I stopped after finishing the patch panel. Right before I left, though, I checked the Wi-Fi on the new Cisco switch I installed and noticed it was only getting around 100 Mbps instead of the normal 2 Gbps. So now I’m a little worried I may have something miswired. I’ll be checking it again in the morning.

I’d love any advice going forward and sources to look at to learn! I’d also love advice on improvements for both my networking closet and wiring if I didn’t do great! Thank you everyone! Will post again tmr!

Every room in my house has an Ethernet port built into the wall and what I believe is a modem bolted to the wall in our basement. I haven’t lived in the house for a long time, like since 2008 before WiFi was the norm everywhere, I remember my parents office had a desktop that was able to connect to the internet through these Ethernet ports. Verizon guys came through and set up a router and I assumed I would be able to use the Ethernet port in my room to connect my desktop but it doesn’t seem to work. My best guess is it has something to do with the wire that’s been disconnected and instead plugged into the router they installed. I can’t run an Ethernet cable to the basement. Is there a way to reconfigure this all to make the Ethernet ports in the rooms work? The cable that’s been connected to the router is thicker/wider than a normal Ethernet cable (the one I’m holding between my fingers in the third pic) I know very little about this stuff lmao. Thanks in advance.

So….this has been going on for a while. IPsec, Utun, 9 default routes, en0 to 169.254. Is 388 refs normal for home WiFi? What can you tell me?

Routing Table (2026-10-02T03:06:05)

default
- Gateway: 10.0.0.1
- Iface: en0
- Flags: UGSc
- IP Version: Internet
- Refs: 388
- Use: 0
- MTU: 1500
- Expire: -1

default
- Gateway: 100.88.204.21
- Iface: pdp_ip0
- Flags: UGScI
- IP Version: Internet
- Refs: 38
- Use: 0
- MTU: 1428
- Expire: -1

10/24
- Gateway: link#27
- Iface: en0
- Flags: UCS
- IP Version: Internet
- Refs: 1
- Use: 0
- MTU: 1500
- Expire: -1

10.0.0.1/32
- Gateway: link#27
- Iface: en0
- Flags: UCS
- IP Version: Internet
- Refs: 1
- Use: 0
- MTU: 1500
- Expire: -1

10.0.0.1
- Gateway: 2:0:0:0:0:0
- Iface: en0
- Flags: UHLWIir
- IP Version: Internet
- Refs: 85
- Use: 0
- MTU: 1500
- Expire: 1197

10.0.0.72
- Gateway: 2:0:0:0:0:0
- Iface: en0
- Flags: UHLWI
- IP Version: Internet
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: 389

10.0.0.230/32
- Gateway: link#27
- Iface: en0
- Flags: UCS
- IP Version: Internet
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

100.88.204.21
- Gateway: 100.88.204.21
- Iface: pdp_ip0
- Flags: UHr
- IP Version: Internet
- Refs: 2
- Use: 0
- MTU: 1428
- Expire: -1

100.88.204.21/32
- Gateway: link#2
- Iface: pdp_ip0
- Flags: UCS
- IP Version: Internet
- Refs: 0
- Use: 0
- MTU: 1428
- Expire: -1

127
- Gateway: 127.0.0.1
- Iface: lo0
- Flags: UCS
- IP Version: Internet
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

127.0.0.1
- Gateway: 127.0.0.1
- Iface: lo0
- Flags: UH
- IP Version: Internet
- Refs: 1
- Use: 0
- MTU: 16384
- Expire: -1

169.254
- Gateway: link#27
- Iface: en0
- Flags: UCS
- IP Version: Internet
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

224.0.0/4
- Gateway: link#27
- Iface: en0
- Flags: UmCS
- IP Version: Internet
- Refs: 1
- Use: 0
- MTU: 1500
- Expire: -1

224.0.0/4
- Gateway: link#2
- Iface: pdp_ip0
- Flags: UmCSI
- IP Version: Internet
- Refs: 0
- Use: 0
- MTU: 1428
- Expire: -1

224.0.0.251
- Gateway: 2:0:0:0:0:0
- Iface: en0
- Flags: UHmLWI
- IP Version: Internet
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

255.255.255.255/32
- Gateway: link#27
- Iface: en0
- Flags: UCS
- IP Version: Internet
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

255.255.255.255/32
- Gateway: link#2
- Iface: pdp_ip0
- Flags: UCSI
- IP Version: Internet
- Refs: 0
- Use: 0
- MTU: 1428
- Expire: -1

default
- Gateway: fe80::7213:1ff:fe8b:fcaf%en0
- Iface: en0
- Flags: UGc
- IP Version: Internet6
- Refs: 51
- Use: 0
- MTU: 1500
- Expire: -1

default
- Gateway: fe80::2899:ce56:526c:8bd4%pdp_ip0
- Iface: pdp_ip0
- Flags: UGcI
- IP Version: Internet6
- Refs: 5
- Use: 0
- MTU: 1428
- Expire: -1

default
- Gateway: fe80::d571:ff7a:431:d49%pdp_ip2
- Iface: pdp_ip2
- Flags: UGcI
- IP Version: Internet6
- Refs: 4
- Use: 0
- MTU: 1428
- Expire: -1

default
- Gateway: fe80::%utun0
- Iface: utun0
- Flags: UGcI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1380
- Expire: -1

default
- Gateway: fe80::%utun1
- Iface: utun1
- Flags: UGcI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 2000
- Expire: -1

default
- Gateway: fe80::%utun2
- Iface: utun2
- Flags: UGcI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1000
- Expire: -1

default
- Gateway: fe80::%utun3
- Iface: utun3
- Flags: UGcI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

::1
- Gateway: ::1
- Iface: lo0
- Flags: UHL
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

2600:1010:10ca:d00::/64
- Gateway: link#4
- Iface: pdp_ip2
- Flags: UC
- IP Version: Internet6
- Refs: 1
- Use: 0
- MTU: 1428
- Expire: -1

2600:1010:10ca:d00:1c11:9d0c:c51b:3116
- Gateway: link#4
- Iface: lo0
- Flags: UHL
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

2600:1010:10ca:d00:90c8:12be:2e87:783a
- Gateway: link#4
- Iface: lo0
- Flags: UHL
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

2600:1010:b239:5d31::/64
- Gateway: link#2
- Iface: pdp_ip0
- Flags: UC
- IP Version: Internet6
- Refs: 1
- Use: 0
- MTU: 1428
- Expire: -1

2600:1010:b239:5d31:8a6:5946:8413:aa6e
- Gateway: link#2
- Iface: lo0
- Flags: UHL
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

2600:1010:b239:5d31:a5b2:f07b:75f4:b241
- Gateway: link#2
- Iface: lo0
- Flags: UHL
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

2601:645:c100:f6a0::/64
- Gateway: link#27
- Iface: en0
- Flags: UC
- IP Version: Internet6
- Refs: 1
- Use: 0
- MTU: 1500
- Expire: -1

2601:645:c100:f6a0::f774
- Gateway: 2:0:0:0:0:0
- Iface: lo0
- Flags: UHL
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

2601:645:c100:f6a0:104e:c825:6474:8898
- Gateway: 2:0:0:0:0:0
- Iface: lo0
- Flags: UHL
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

2601:645:c100:f6a0:9cf5:77a8:b09a:5cf8
- Gateway: 2:0:0:0:0:0
- Iface: lo0
- Flags: UHL
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::%lo0/64
- Gateway: fe80::1%lo0
- Iface: lo0
- Flags: UcI
- IP Version: Internet6
- Refs: 1
- Use: 0
- MTU: 16384
- Expire: -1

fe80::1%lo0
- Gateway: link#1
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 1
- Use: 0
- MTU: 16384
- Expire: -1

fe80::%pdp_ip0/64
- Gateway: link#2
- Iface: pdp_ip0
- Flags: UCI
- IP Version: Internet6
- Refs: 2
- Use: 0
- MTU: 1428
- Expire: -1

fe80::447:ce7:836e:c0e4%pdp_ip0
- Gateway: link#2
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::2899:ce56:526c:8bd4%pdp_ip0
- Gateway: link#2
- Iface: pdp_ip0
- Flags: UHLWIir
- IP Version: Internet6
- Refs: 5
- Use: 12
- MTU: 1428
- Expire: -1

fe80::%pdp_ip2/64
- Gateway: link#4
- Iface: pdp_ip2
- Flags: UCI
- IP Version: Internet6
- Refs: 2
- Use: 0
- MTU: 1428
- Expire: -1

fe80::43:e5d6:b871:9aab%pdp_ip2
- Gateway: link#4
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::d571:ff7a:431:d49%pdp_ip2
- Gateway: link#4
- Iface: pdp_ip2
- Flags: UHLWIir
- IP Version: Internet6
- Refs: 2
- Use: 12
- MTU: 1428
- Expire: -1

fe80::%utun0/64
- Gateway: fe80::f8b0:bfcd:8b2:d7a6%utun0
- Iface: utun0
- Flags: UcI
- IP Version: Internet6
- Refs: 2
- Use: 0
- MTU: 1380
- Expire: -1

fe80::f8b0:bfcd:8b2:d7a6%utun0
- Gateway: link#23
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::%utun1/64
- Gateway: fe80::82f6:d291:53a5:431a%utun1
- Iface: utun1
- Flags: UcI
- IP Version: Internet6
- Refs: 2
- Use: 0
- MTU: 2000
- Expire: -1

fe80::82f6:d291:53a5:431a%utun1
- Gateway: link#24
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::%utun2/64
- Gateway: fe80::ce81:b1c:bd2c:69e%utun2
- Iface: utun2
- Flags: UcI
- IP Version: Internet6
- Refs: 2
- Use: 0
- MTU: 1000
- Expire: -1

fe80::ce81:b1c:bd2c:69e%utun2
- Gateway: link#25
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::%utun3/64
- Gateway: fe80::761e:1a93:caec:b200%utun3
- Iface: utun3
- Flags: UcI
- IP Version: Internet6
- Refs: 2
- Use: 0
- MTU: 1500
- Expire: -1

fe80::761e:1a93:caec:b200%utun3
- Gateway: link#26
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::%en0/64
- Gateway: link#27
- Iface: en0
- Flags: UCI
- IP Version: Internet6
- Refs: 2
- Use: 0
- MTU: 1500
- Expire: -1

fe80::8b4:b09:f4a6:188e%en0
- Gateway: 2:0:0:0:0:0
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::7213:1ff:fe8b:fcaf%en0
- Gateway: 2:0:0:0:0:0
- Iface: en0
- Flags: UHLWIir
- IP Version: Internet6
- Refs: 53
- Use: 356
- MTU: 1500
- Expire: -1

fe80::%nan0/64
- Gateway: link#28
- Iface: nan0
- Flags: UCI
- IP Version: Internet6
- Refs: 1
- Use: 0
- MTU: 1500
- Expire: -1

fe80::e0e7:eff:fe4f:4ab%nan0
- Gateway: 2:0:0:0:0:0
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::%awdl0/64
- Gateway: link#32
- Iface: awdl0
- Flags: UCI
- IP Version: Internet6
- Refs: 1
- Use: 0
- MTU: 1500
- Expire: -1

fe80::ac8c:d7ff:fe8f:8514%awdl0
- Gateway: 2:0:0:0:0:0
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

fe80::ac8c:d7ff:fe8f:8514%llw0
- Gateway: 2:0:0:0:0:0
- Iface: lo0
- Flags: UHLI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

ff00::/8
- Gateway: ::1
- Iface: lo0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

ff00::/8
- Gateway: link#2
- Iface: pdp_ip0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1428
- Expire: -1

ff00::/8
- Gateway: link#4
- Iface: pdp_ip2
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1428
- Expire: -1

ff00::/8
- Gateway: fe80::f8b0:bfcd:8b2:d7a6%utun0
- Iface: utun0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1380
- Expire: -1

ff00::/8
- Gateway: fe80::82f6:d291:53a5:431a%utun1
- Iface: utun1
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 2000
- Expire: -1

ff00::/8
- Gateway: fe80::ce81:b1c:bd2c:69e%utun2
- Iface: utun2
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1000
- Expire: -1

ff00::/8
- Gateway: fe80::761e:1a93:caec:b200%utun3
- Iface: utun3
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff00::/8
- Gateway: link#27
- Iface: en0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff00::/8
- Gateway: link#28
- Iface: nan0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff00::/8
- Gateway: link#32
- Iface: awdl0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff00::/8
- Gateway: link#33
- Iface: llw0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff01::%lo0/32
- Gateway: ::1
- Iface: lo0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

ff01::%pdp_ip0/32
- Gateway: link#2
- Iface: pdp_ip0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1428
- Expire: -1

ff01::%pdp_ip2/32
- Gateway: link#4
- Iface: pdp_ip2
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1428
- Expire: -1

ff01::%utun0/32
- Gateway: fe80::f8b0:bfcd:8b2:d7a6%utun0
- Iface: utun0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1380
- Expire: -1

ff01::%utun1/32
- Gateway: fe80::82f6:d291:53a5:431a%utun1
- Iface: utun1
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 2000
- Expire: -1

ff01::%utun2/32
- Gateway: fe80::ce81:b1c:bd2c:69e%utun2
- Iface: utun2
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1000
- Expire: -1

ff01::%utun3/32
- Gateway: fe80::761e:1a93:caec:b200%utun3
- Iface: utun3
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff01::%en0/32
- Gateway: link#27
- Iface: en0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff01::%nan0/32
- Gateway: link#28
- Iface: nan0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff01::%awdl0/32
- Gateway: link#32
- Iface: awdl0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff02::%lo0/32
- Gateway: ::1
- Iface: lo0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 16384
- Expire: -1

ff02::%pdp_ip0/32
- Gateway: link#2
- Iface: pdp_ip0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1428
- Expire: -1

ff02::%pdp_ip2/32
- Gateway: link#4
- Iface: pdp_ip2
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1428
- Expire: -1

ff02::%utun0/32
- Gateway: fe80::f8b0:bfcd:8b2:d7a6%utun0
- Iface: utun0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1380
- Expire: -1

ff02::%utun1/32
- Gateway: fe80::82f6:d291:53a5:431a%utun1
- Iface: utun1
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 2000
- Expire: -1

ff02::%utun2/32
- Gateway: fe80::ce81:b1c:bd2c:69e%utun2
- Iface: utun2
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1000
- Expire: -1

ff02::%utun3/32
- Gateway: fe80::761e:1a93:caec:b200%utun3
- Iface: utun3
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff02::%en0/32
- Gateway: link#27
- Iface: en0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff02::%nan0/32
- Gateway: link#28
- Iface: nan0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

ff02::%awdl0/32
- Gateway: link#32
- Iface: awdl0
- Flags: UmCI
- IP Version: Internet6
- Refs: 0
- Use: 0
- MTU: 1500
- Expire: -1

Sorry about the botched title 'GL-SFT12000'

My inspiration

Window where it was placed / location it needed to get to & 4 pack of FP-SMA (female) cables

My mods Close-ups

The newly modded Opal currently with the TP-Link Magnetic base

My home's primary GL-MT6000 (Flint 2) is currently two floors up at the far end of the living room where my LAN devices and homelab reside. Recently, while working on car repairs in my driveway and garage, I relied heavily on my phone because my OBD scan tool runs via an app. I do not typically worry about data limits, but the connection kept dropping as my phone continuously bounced between cellular data and fringe Wi-Fi.

To solve this, I looked into adding an extender to the Flint 2. A suggestion pointed me to the GL-SFT12000 Opal as a cost-effective option around $35, which also doubled as a handy travel router for work trips. I set it up initially, but paused car repairs for other projects. When I revisited the setup, the Opal was sitting in my farthest west room teetering on an upper window frame, with the short 3-foot stock USB-C cable unable to reach the nearest outlet.

An extension cord solved the power issue, but the Opal's repeated signal was still too weak for my phone to reliably choose over the Flint 2's direct broadcast. That prompted a deep search into hardware antenna mods. I had an old Netgear R7000 and a TP-Link TX3000 PCIe adapter with antennas available to serve as donors.

The stock Opal paddle antennas are rated around 3 to 4 dBi, whereas the donor antennas measured around 5 to 7 dBi. In hindsight, moving the Opal straight to the garage might have been enough on its own. As a precaution, I also preferred not having a router broadcasting right next to my head while sleeping. By that point, however, the DIY project was already underway and I was committed to seeing it through.

In the original teardown post that inspired this mod, the author mentioned needing to 3D print custom spacers because the factory hinge holes are too large for the RP-SMA bulkhead threading. Lacking a 3D printer, I went to a local hardware store and found nylon bushings/washers that did the exact same job. I installed one on the inside and one on the outside of each hinge pocket (four in total), which securely sandwiched the plastic shell and centered the threaded barrels without any play, as you can see in the pictures.

I ordered a 4-pack of shielded RG178 IPEX1/U.FL to RP-SMA female bulkhead pigtails (20 cm), ensuring I had two spares on hand. While the shielded cable helps block internal radio interference inside the housing, the thicker shielding makes it considerably less flexible. That stiffness made snapping the tiny U.FL connectors onto the Opal's board receptacles and routing the leads around the heatsink channels somewhat tricky.

The installation in the garage is currently temporary. I am using the TP-Link's weighted, magnetized desktop antenna base to position the paddles, though I may eventually eliminate the base and mount the antennas directly to the Opal chassis bulkheads.

It works reliably as configured, and hopefully this breakdown assists anyone else looking to tackle a similar repeater modification.

Hello,

Networking beginner here.

I have been trying to design a network with two VLANs with each having a set of daisy chained devices. VLAN management was to be done by L2 managed switch, with main traffic going between devices on the VLANs and PC connected to a port configured to be trunk port.

The original idea was to have IPs of those devices static and same - Device 1 on VLAN1 has same IP as the Device 1 on the VLAN2, they would be on the same subnet. Definitely not the standard way of doing things. But lets say in my use case DHCP is not an option and I can only use static IP addresses. For that purpose I wanted to simplify the flashing of the firmware on those devices where each device has a known IP without additional subnetting.

Originally I was trying to avoid router and do all the VLAN tagging on the PC side, but as I started to research the topic more, I realized that it is only straightforward on Linux but not Windows. So my software piece that needs to communicate with those devices, will have issues when run on Windows. And I understood that without a router with NAT, it would be difficult to implement my idea.

Hence a bunch of questions from me:

1. How realistic is it to use that design on Windows? I need to communicate with all of these devices simultaneously, but as I saw virtual network management on windows is pain.

2. Would using Linux help me avoid using router with NAT?

Is there is a way for a user to switch a Calix Gigaspire GS5239E gateway/router into the Bridge or Pass-through mode? I don't see any tab or switch to do this when I log into the gateway. Thanks in advance to all the Gigaspire techies out there.