Skip Navigation
talkingpumpkin talkingpumpkin @lemmy.world
Posts 2
Comments 25
[SOLVED] Weird (to me) networking issue - can you help?
  • why is your network like this?

    Well, at the moment my network is actually flat :)

    This is an experiment I'm doing because I wanted to have all the management stuff on a different subnet (eg. adguard dns is on the "regular" subnet everyone uses, but its web interface is on the special subnet only select devices can talk to).

    Of course (like with most stuff in my homelab), it's not like I really have a super-compelling security reason to that, it's mostly that I wondered "what if?" :D

    Oh. the ping option you are referring to is -I (upper case) and takes either an interface name or an ip. I did try giving a .10/24 IP to the PC and the results were consistent with scenario 1 (pings where source and destination are on the same subnet work, pings acrrss subnets don't), so I didn't mention that in the OP

  • [SOLVED] Weird (to me) networking issue - can you help?
  • I don't think I quite explained the situation well enough: my server only has 1 ethernet port (same as my PC), otherwise I wouldn't have bothered with vlans (well, I would still have bothered, since my house still only has one "backbone" cable running through it, but I would have configured it on the switches only).

    Anyway... a few of the things you say/imply go against my understanding of networking, so one of us would better go back RTFM as you suggest :) (just kidding - most probably I just don't understand what you mean)

  • [SOLVED] Weird (to me) networking issue - can you help?
  • Thanks! Forwarding is disabled. I don't want the server to steal the router's job :)

  • [SOLVED] Weird (to me) networking issue - can you help?
  • So the request goes trough but the replies are discarded ? That could actually be it!

    I think there was an option to allow that... I'll search it and give it a try. Thanks!

  • [SOLVED] Weird (to me) networking issue - can you help?
  • I tried dropping the default routes (one at a time) and it doesn't make a difference, which isn't (I think) surprising as all traffic is local as far as the server in scenario 1 is concerned. Also IIUC only the default gateway with the lowest metric actually counts.

  • Weird (to me) networking issue - can you help?

    I have two subnets and am experiencing some pretty weird (to me) behaviour - could you help me understand what's going on?

    ----

    Scenario 1

    PC: 192.168.11.101/24 Server: 192.168.10.102/24, 192.168.11.102/24

    From my PC I can connect to .11.102, but not to .10.102:

    bash ping -c 10 192.168.11.102 # works fine ping -c 10 192.168.10.102 # 100% packet loss ----

    Scenario 2

    Now, if I disable .11.102 on the server (ip link set <dev> down) so that it only has an ip on the .10 subnet, the previously failing ping works fine.

    PC: 192.168.11.101/24 Server: 192.168.10.102/24

    From my PC:

    bash ping -c 10 192.168.10.102 # now works fine

    This is baffling to me... any idea why it might be?

    ----

    Here's some additional information:

    • The two subnets are on different vlans (.10/24 is untagged and .11/24 is tagged 11).

    • The PC and Server are connected to the same managed switch, which however does nothing "strange" (it just leaves tags as they are on all ports).

    • The router is connected to the aformentioned switch and set to forward packets between the two subnets (I'm pretty sure how I've configured it so, plus IIUC the second scenario ping wouldn't work without forwarding).

    • The router also has the same vlan setup, and I can ping both .10.1 and .11.1 with no issue in both scenarios 1 and 2.

    • In case it may matter, machine 1 has the following routes, setup by networkmanager from dhcp:

    default via 192.168.11.1 dev eth1 proto dhcp src 192.168.11.101 metric 410 192.168.11.0/24 dev eth1 proto kernel scope link src 192.168.11.101 metric 410

    • In case it may matter, Machine 2 uses systemd-networkd and the routes generated from DHCP are slightly different (after dropping the .11.102 address for scenario 2, of course the relevant routes disappear): default via 192.168.10.1 dev eth0 proto dhcp src 192.168.10.102 metric 100 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.102 metric 100 192.168.10.1 dev eth0 proto dhcp scope link src 192.168.10.102 metric 100 default via 192.168.11.1 dev eth1 proto dhcp src 192.168.11.102 metric 101 192.168.11.0/24 dev eth1 proto kernel scope link src 192.168.11.102 metric 101 192.168.11.1 dev eth1 proto dhcp scope link src 192.168.11.102 metric 101

    ----

    solution

    (please do comment if something here is wrong or needs clarifications - hopefully someone will find this discussion in the future and find it useful)

    In scenario 1, packets from the PC to the server are routed through .11.1.

    Since the server also has an .11/24 address, packets from the server to the PC (including replies) are not routed and instead just sent directly over ethernet.

    Since the PC does not expect replies from a different machine that the one it contacted, they are discarded on arrival.

    The solution to this (if one still thinks the whole thing is a good idea), is to route traffic originating from the server and directed to .11/24 via the router.

    This could be accomplished with ip route del 192.168.11.0/24, which would however break connectivity with .11/24 adresses (similar reason as above: incoming traffic would not be routed but replies would)...

    The more general solution (which, IDK, may still have drawbacks?) is to setup a secondary routing table:

    bash echo 50 mytable >> /etc/iproute2/rt_tables # this defines the routing table # (see "ip rule" and "ip route show table <table>") ip rule add from 192.168.10/24 iif lo table mytable priority 1 # "iff lo" selects only # packets originating # from the machine itself ip route add default via 192.168.10.1 dev eth0 table mytable # "dev eth0" is the interface # with the .10/24 address, # and might be superfluous

    Now, in my mind, that should break connectivity with .10/24 addresses just like ip route del above, but in practice it does not seem to (if I remember I'll come back and explain why after studying some more)

    19

    Simplest tool to maintain local mirrors of git repos?

    I want to have a local mirror/proxy for some repos I'm using.

    The idea is having something I can point my reads to so that I'm free to migrate my upstream repositories whenever I want and also so that my stuff doesn't stop working if some of the jankiest third-party repos I use disappears.

    I know the various forjego/gitea/gitlab/... (well, at least some of them - I didn't check the specifics) have pull mirroring, but I'm looking for something simpler... ideally something with a single config file where I list what to mirror and how often to update and which then allows anonymous read access over the network.

    Does anything come to mind?

    14
    Router died - Replacement/solution recommendations
  • If going the route of a backup solution, is it feasible to install OpenWRT on all of my devices, with the expectation that I can do some sort of automated backups of all settings and configurations, and restore in case of a router dying?

    My two cents: use a "full" computer as your router (with either something like OPNsense or any "regular" linux distro if you don't need the GUI) and OpenWRT on your access points.

    Unless you use the GUI and backup/restore the configuration (as you would with proprietary firmwares), OpenWRT is frankly a pain to configure and deploy. At the moment I'm building custom images for all my devices, but (next time™) I'm gonna ditch all that, get an x86 router and just manually manage OpenWRT on my wifi APs (I only have two and they both have the same relatively straightforward config).

    It’s a pain that I know can be solved with buying dedicated access points (…right?)

    Routers and access points are just computers with network interfaces (there may be level-2-only APs, but honestly I've never heard of any)... most probably your issue is that the firmware of your "routers as access points" doesn't want to be configured as a dumb AP.

  • Immutable backup for important data
  • How much data are we talking about?

    A free mega.nz account should be fine for everything except family fotos and legally obtained music/movies.

  • 8 versions of UUID and when to use them
  • Personally, I always regarded UUID as one of those overcomplicated and frankly unneded "enterprisey" standards (similar to SOAP and XSD, XSLT and various other XML techonologies). After reading this article my opinion didn't change.

    Also... do they even know what "version" means? That they choose that word over "type" or any other alternative says it all.

    UUID Version 7 (v7) is generated from a timestamp and random data.

    Use v7 if you're using the ID in a context where you want to be able to sort. For example, consider using v7 if you are using UUIDs as database keys.

    Please, do NOT rely on that and just add to your tables a field with the actual timestamp.

  • Benefits of a join table vs. array to express relations? (outside of SQL)
  • Not sure I'm getting the issue here (what does "join table" mean in the scope of JSON/XML?), but... doesn't how you lay out your data in JSON/XML file have zero impact in your application's queries? You won't be querying the JSON - you'll be loading data from it into memory and query the memory.

  • Has anyone ever used Jaspersoft?
  • I last used it a good while ago (like, 10yrs?), so you'll have to verify how what I am about to say applies to current versions (it probably does).

    Jasper is an old-school, enterprisey tool similar to Crystal Reports that attempts to give you a WYSIWYG editor for building your reports.

    All in all, I'd say that it might be good if you have a reporting department full of people that only do reports and you don't want to train as programmers. If the ones doing the reports are gonna be actual programmers, they'll be much better off generating html/latex/whatever and converting that to pdf.

  • How do you handle family requests that you disagree with?
  • I'd say a good middle ground could be making that stuff only visible from your mom's user (or even setting up a completely separate server)?

    It depends on what YOU want to do, really... personally, I would be ok hosting religious nonsense if asked, as long as it's not generally available in kids' accounts and stuff (also, porn), but I would come clean and outright refuse if it was neonazi,racist and/or conspiracy stuff. It depends on where you decide to draw the line.

    BTW: there's also the passive/aggressive, cowardly option of sayng "I'll rip them when I have time" and then sequester all the DVDs and only ever find the time to rip the ones you don't mind

  • Syncthing ... where are the users?
  • man this is getting real popular (kinda like "why not both?" a while ago)

  • Is ansible worth learning to automate setting up servers?
  • IMHO Ansible isn't much different than a bash script... it has the advantage of being "declarative" (in quotes because it's not actually declarative at all: it just has higher-level abstractions that aggregate common sysadmin CLI operations/patterns in "declarative-sounding" tasks), but it also has the disadvantage of becoming extremely convoluted the moment you need any custom logic whatsoever (yes, you can write a python extension, but you can do the same starting with a bash script too).

    Also, you basically can't use ansible unless your target system has python (technically you can, but in practice all the useful stuff needs python), meaning that if you use a distro that doesn't come with python per default (eg. alpine) you'll have to manually install it or write some sort of pythonless prelude to your ansible script that does that for you, and that if your target can't run python (eg. openwrt on your very much resource-constrained wifi APs) ansible is out of the question (technically you can use it, but it's much more complex than not using it).

    My two cents about configuration management for the homelab:

    • whatever you use, make sure it's something you re-read often: it will become complex and you will forget everything about it
    • keep in mind that you'll have to re-test/update your scripts at least everytime your distro version changes (eg. if you upgrade from ubuntu 22.04 to 24.04) and ideally every time one of your configured services changes (because the format of their config files may in theory change too)
    • if you can cope with a rolling-style distro, take a look at nix instead of "traditional" configuration management: nixos configuration is declarative and (in theory) guarantees that you won't ever need to recheck or update your config when updating (in reality, you'll occasionally have to edit your config, but the OS will tell you so it's not like you can unknowingly break stuff).

    BTW, nixos is also not beginner-friendly in the least and all in all badly documented (documentation is extensive but unfriendly and somewhat disorganized)... good luck with that :)

  • What storage manufacturer do you swear to and why?
  • With the very limited number of drives one may use at home, just get the cheapest ones (*), use RAID and assume some drive may fail.

    (*) whose performances meet your needs and from reputable enough sources

    You can look at the backblaze stats if you like stats, but if you have ten drives 3% failure rate is exactly the same as 1% or .5% (they all just mean "use RAID and assume some drive may fail").

    Also, IDK how good a reliabiliy predictor the manufacturer would be (as in every sector, reliabiliy varies from model to model), plus you would basically go by price even if you need a quantity of drives so great that stats make sense on them (wouldn't backblaze use 100% one manufacturer otherwise?)

  • Tv box recommendations?
  • IIUC you can flash LineageOS on the shield (if you try, let us know how it goes)

  • Introducing Raspberry Pi 5
  • Good catch on my megabit vs megabyte blunder!

  • Introducing Raspberry Pi 5
  • One of the most exciting additions to the Raspberry Pi 5 feature set is the single-lane PCI Express 2.0 interface.

    IIUC PCIe2.0x1 means 0.5GB/s, which is slower than USB 2 (I'm talking USB 2 specs - no idea how USB actually performs in PIs). I can't wait for people to buy that NVME hat and mount WD Blacks on that :) READ BELOW

  • ISP router wifi range
  • One thing you can try doing before throwing away the router (which is probably the exact same one your neighbor use) is checking the channel situation in your condo with an app like WiFiAnalyzer and also try moving the router around (some spots are better than others - and hi up is usually better)

    That said, ISP routers are often terrible.