I decided to buy one of these mini PCs and load Debian onto it to build my own router.
So far I have it running Debian, with PiHole installed handling DHCP, along with a Unifi server, SQM (installed, not configured) and it just will not work.
I'm pretty sure I fricked up my iptables and interfaces because PiHole sees connections but whatever device I connect to it sees nothing at all, and doesn't get a gateway.
What are some guides or books that I can read to get this thing up and running?
OpenWRT.
See if there's a build for that equipment. It's the absolute bees knees.
I need it to run Debian in order to run the Ubiquiti/Unifi server, it won't run on WRT.
But there is both Open and Friendly WRT available for the NanoPi family of mini PCs.
,,,
Trust me, I would have used it if that was an option.
run openwrt with a docker container
>OpenWRT.
>See if there's a build for that equipment. It's the absolute bees knees.
Is that you, Ben?
ok, sorry Patrick, you really sounded like Ben.
>using ubiquitrash spyware
Beyond that, sounds like you are trying to go way beyond building just a router and you may be better splitting off your needed functions to a seperate server machine. Let the router be a router. Set up the unifi server, pihole, etc in docker or through a hypervisor on a different machine.
hijacking this thread to ask something related
once you have your router running, what more do you need?
a switch, an AP? how to choose those?
Modem, switch, access points.
Pick by looking at how many moneys you have and how many moneys they want.
I did this in high school but that was like, 25 years ago. Google is surprisingly bad at help for this shit.
I'm hoping someone has an actual resource for finishing my ruleset, because I'm pretty sure everything else is up and running.
Understand what you're doing, and google this stuff first. Not trying to be a dick, it's a big can of worms, get the basics straight first
did you set net.ipv4.ip_forward=1?
Nope! Danke Herr Anon.
We ARE a router.
Where's the fun in that.
Seriously dude, many thanks, it's a network now, but my interfaces and iptables files are a mess. I can see the network but there's no internet.
But that's a fricking hell of a big step. Have a rare (You).
>installed a load of dogshit with no understanding of how anything
>it didnt work
dont run fricking debian on network devices use something stable like openbsd
dont use something moronic like pihole just write fricking proper firewall rules and learn how they work
the basic guides and books for a start are the man pages for your networking stack
you need to enable forwarding to route between two ports.
>ubiquity
>sqm
go to reddit or try reddit lite
where morons fill half cabinets with consumer gear on shelves and spend billions on ubiquishit if you want meme help from morons
>moron moron moron
>dont use this establish thing build your own shit from stick and stone instead
>dont use this thing wah wah moron
okay thanks for the help bro
>dont use this establish thing
>use "establish thing"
>doesn't work
how is that working out for you?
>moron moron moron
you are absolutely a moron if you blindly stumble into any aspect of internet exposed networking when clearly you have zero idea at all what you are doing.
frick off.
I'm OP but I clearly have a normal router, I just wanted to learn to build a headless home server, what's so fricking bad about that?
After this I'm gonna ditch Windows for my gaming PC in favor of Nobara, give that a spin.
What's the worst that could happen, I learn how to set up a virtual PC for the games that don't run?
Learning shit is fun.
are or are not? because you propose entirely different use case
packet forwarding is not trivial it is default disabled for very good reason.
nothing in this post bears any relevance to this thread
I'm OP, the
>moron moron moron
guy is not me.
Debian is just set for this, and also, I'd probably use Debian anyway. All the software and hardware is built around Debian.
I won't do bsd or Gentoo or any of that ever again unless I decide to become a warlord, which we're not ruling out at this point.
I just want to make a headless server that doubles as a router and makes the ads go away.
In that sense, these are baby steps.
That's moronic. You are building a 747 for your stealth mission. Just install an AdBlocker on your router or setup a virtual VPN and wow you want to use pihole too? Did you Google keywords and post them together?
Device-wise I'd prefer the N100-based mini PCs from Beelink/Trigkey/etc. on Amazon, you can find lots of models with dual 2.5gbps ports, and they're great basic machines if you device to retire it from router service.
Honestly if I was still a bachelor I'd just plug one one these into the modem and just share the wifi: https://www.friendlyelec.com/index.php?route=product/product&path=69&product_id=292
These machines are pretty slick for not very much money. It's been a lot of fun.
Can you post some links? Not OP but i made the openwrt comment. Interested in what you think is good in the 'value' category.
just put pfsense on it and stop being autistic.
>doesn't get a gateway
Do you mean "doesn't have a default route?" If so, your DHCP is badly configured.
BTW, I strongly suggest you break your problem up into smaller pieces. Get one computer with a static IP, static routes and static DNS. Then ping your router. Then ping 1.1.1.1. If that isn't working, then masquerade and forwarding isn't working on the router.
Yeah that's what I've come up with for this weekend. I thought I could do it all from memory but that was pretty moronic, so I broke things out for tomorrow.