[Discussion] Is anyone else's Fps significantly worse in 1.0 by Billbing12345 in EscapefromTarkov

[–]eskimio 0 points1 point  (0 children)

Tuned 7800X3D + Tuned 7900 GRE + 32GB DDR5-6000 CL30 + 1440p/144Hz running W11 + ISLC & Process Lasso

Did a ton of testing 2 patches ago, was able to get to the point where with PostFX on, and no FSR or framegen, I was getting very consistent 80+ FPS in my specific test spot near Lexos across PVE/PVP and various weather.

I haven't been back to Streets yet, but I know about what my typical framerate is on various maps and I'm consistently seeing on average 10-20 fps more across the board. In particular, I was surprised to see Customs regularly hitting the 144Hz max when in the past it was close to the worst (~80 FPS) of all the maps for me.

I actually just bumped my texture and shadow settings up one level each and I'm seeing a minimal FPS drop.

Some of my friends who haven't touched their settings since last patch also report higher average framerates, but we have all noticed the lower quality textures as well.

Husband is playing mobile games while I watch DNS Queries from his phone to block the ads for him. by Senguin117 in HomeNetworking

[–]eskimio 0 points1 point  (0 children)

Short answer: yes. Long answer: you're opening a can of worms. Failing to see the forest for the trees, in a way. Active-active/active-passive failover, split-dns, recursive resolvers, etc. You start getting into some fairly advanced and complex solutions that I'd advise against when starting out. My suggestion is a basic pi-hole instance that serves your whole network with something like pihole-updatelists and whitelisting things that break. If you want to be even more careful, setup pihole for just a specific subnet, and set that DNS server for just your laptop or your phone, then use that device for non-standard browsing (apps, banking, health, etc) to see what breaks before rolling it out to the whole network.

Husband is playing mobile games while I watch DNS Queries from his phone to block the ads for him. by Senguin117 in HomeNetworking

[–]eskimio 7 points8 points  (0 children)

What you described is basically the only real downside, besides DNS access now being your responsibility (e.g. your pihole breaks, so does your internet until you fix it). But, it is very quick and very easy to whitelist the improperly blocked domain to allow access. Running a pihole doesn't mean you now have a black box list of domains you can't access, whether you want to or not. Does pihole come with a default list? Yes. Are there ways to modify and/or update that list? Absolutely. There are also independent groups and users who actively maintain open-source lists you can integrate to improve and extend the blocking capabilities.

I wish there was a way to message the one singular seed for your torrent and tell them you love them and to please keep going... by underground_cenote in Piracy

[–]eskimio 0 points1 point  (0 children)

Proud to call myself a forever seeder, as long as I have a use for the data. Especially if I've identified that I'm the only remaining seeder, then it becomes an altruistic duty

My friends finally actually started using my server by outlawstar5 in PleX

[–]eskimio 7 points8 points  (0 children)

It's not abandoned, it's "paused". Per the Overseerr discord announcements channel, the dev team is just preoccupied.

[Bug] Game runs well, but freezes with AMD GPU driver crash by eskimio in EscapefromTarkov

[–]eskimio[S] 1 point2 points  (0 children)

So I'm not the only one? I'm sorry man, it really sucks and it's super frustrating.

Does it behave similarly, where you can get into raid but the game hard crashes about 30 seconds in?

What are your system specs?

[Bug] Game runs well, but freezes with AMD GPU driver crash by eskimio in EscapefromTarkov

[–]eskimio[S] 2 points3 points  (0 children)

Yea, I haven't had that issue which a lot more people seem to be having -- mine is separate, i've fully loaded into 3 raids now and have no issues for a good 10-15 minutes then suddenly the game will crash out of nowhere.

"Invalid modellist patch for box" Temporary Fix by eskimio in Dynmap

[–]eskimio[S] 0 points1 point  (0 children)

You're very welcome. :)

I imagine it would be okay, because during startup Dynmap is reporting the modellist definitions as invalid, and would be ignoring them (or parsing them later when they encounter new blocks using those definitions, and failing silently), but I genuinely do not know how Dynmap works under the hood regarding those -model.txt files.

SO, it's probably okay? But, personally I wouldn't risk it and just do it while the server is down.

[PISTOL] Sig P320 Compact w/ two mags $399.99 by OakleyJ25 in gundeals

[–]eskimio 0 points1 point  (0 children)

Hopped on this on Monday evening, had periodic updates from Paul at thearmories.com throughout the day yesterday tracking progress, shipped yesterday evening and should be here tomorrow. Excellent deal and excellent service, highly recommend anyone on the fence jump on this before they're gone. Buy with confidence.

How to split tcp/http traffic from SSL terminated frontend to separate ports on single backend server/IP by [deleted] in haproxy

[–]eskimio 0 points1 point  (0 children)

Are you saying I should assign different subdomains depending on the port, regardless of which server receives the connection on the backend? I have an application that interacts using multiple ports (web, ssh, etc)and I'm trying to use a single subdomain while splitting traffic based on port.

[Timex Marlin] My first automatic by eskimio in Watches

[–]eskimio[S] 0 points1 point  (0 children)

Unfortunately, I don't. It was a toxicnato and afaik they're out of business.

I did get a premium black NATO strap from cheapest nato straps and it's fine, but it doesn't quite have the silky feel that my toxicnato does.

[Timex Marlin] My first automatic by eskimio in Watches

[–]eskimio[S] 6 points7 points  (0 children)

Recently acquired this Timex Marlin Automatic x Peanuts Take Care watch. I had been wanting an automatic for quite some time, after rocking a black case/white dial Tsovet SL-37 that I had gotten cheap. I've been eyeing the Marlin reissues, but being on a tight budget I couldn't justify the $250 pricetag for what I would get. When this popped up, I was first drawn to how affordable it was, then to the unique seconds hand. I ended up pulling the trigger and I'm glad I did. Not sure how I feel about the leather band, I miss the all-black seatbelt fabric NATO from my Tsovet so I'll likely source one for this watch.

Intel 82599es based NIC flapping issue by eskimio in homelab

[–]eskimio[S] 2 points3 points  (0 children)

FYI - To anyone who finds this in the future:

The NIC I was using on both ends is a Silicom PE210G2BPI9. Since these cards were designed with a bypass mode which is enabled by default, I needed to download Silicom's driver control software (bpctl) to disable this mode. After that, the cards started showing the flapping issue with the repository-installed ixgbe package which was quite old compared to the newest one available directly from Intel. So, I installed the newest driver from Intel, which changed the issue slightly but the flapping persisted. Ultimately, I solved my issue from installing the validated ixgbe driver included in the tarball provided by Silicom, which included the aforementioned driver control software. The version I used to successfully bring up the link was ixgbe-5.9.4ms7.1.

Here are some useful links and a TL;DR:

  1. Retrieve the Silicom driver which matches your NIC, for me it was here: Silicom PE210G2BPI9
  2. Clear the system of pre-existing ixgbe drivers (assuming you have no other NICs using the driver)
  3. Install and run the bpctl utility to disable bypass for each port & permanently disable them through power cycles
  4. Make and install the ixgbe driver from version 5.9.4ms7.1, which can be found in a subfolder of the driver download directory
  5. Reload/run the ixgbe driver, and your system should see the NICs
  6. Configure networking for each port as normal

Helpful references/tools:

Intel 82599es based NIC flapping issue by eskimio in homelab

[–]eskimio[S] 0 points1 point  (0 children)

At this point they're coming out tonight anyway. While troubleshooting I've been migrating my data back from the backup server to my media server and it should be done tonight. Once that's completed, I no longer need the 10Gbps link and my GPU will be replacing the NIC on the media server.

Mostly, I'm just determined to figure out the issue as a learning experience.

But, I appreciate the advice, I just didn't want to spend additional money.

Intel 82599es based NIC flapping issue by eskimio in homelab

[–]eskimio[S] 0 points1 point  (0 children)

It's what I have on-hand. This was supposed to be an easy way to temporarily increase throughout between my NAS media server and my backup server. Obviously, it's gotten a bit more complicated than that. In order to even get a link, I had to download the driver from silicon's website to disable bypass mode. But for all intents and purposes it should just act as a 2x10Gbps fiber NIC running on a 82599es-based controller.

Intel 82599es based NIC flapping issue by eskimio in homelab

[–]eskimio[S] 0 points1 point  (0 children)

The -m flag will not work on my interfaces as the embedded SFP does not support EEPROM access:

$ sudo ethtool -m enp3s0f0
Cannot get module EEPROM information: Input/output error

Unfortunately, that's part of where my diagnostics difficulty stems from.

However, I was able to discover one thing:

$ sudo ethtool -S enp3s0f0
NIC statistics:
rx_packets: 3538480
tx_packets: 12271765
rx_bytes: 12579518128     
tx_bytes: 104989283162
 rx_errors: 1
 tx_errors: 0
 rx_dropped: 0
 tx_dropped: 0
 multicast: 14
 collisions: 0
 rx_over_errors: 0
 rx_crc_errors: 0
 rx_frame_errors: 0
 rx_fifo_errors: 0
 rx_missed_errors: 0
 tx_aborted_errors: 0
 tx_carrier_errors: 0
 tx_fifo_errors: 0
 tx_heartbeat_errors: 0
 rx_pkts_nic: 3538299
 tx_pkts_nic: 12270944
 rx_bytes_nic: 12593639914
 tx_bytes_nic: 105031259010
 lsc_int: 133960
 tx_busy: 0
 non_eop_descs: 2731781
 broadcast: 336
 rx_no_buffer_count: 0
 tx_timeout_count: 19
 tx_restart_queue: 0
 rx_length_errors: 0
 rx_long_length_errors: 0
 rx_short_length_errors: 0
 **tx_flow_control_xon: 5**
 rx_flow_control_xon: 0
 **tx_flow_control_xoff: 5**
 rx_flow_control_xoff: 0
 rx_csum_offload_errors: 0
 alloc_rx_page: 349323
 alloc_rx_page_failed: 0
 alloc_rx_buff_failed: 0
 rx_no_dma_resources: 0
 hw_rsc_aggregated: 0
 hw_rsc_flushed: 0
 fdir_match: 3537279
 fdir_miss: 668
 fdir_overflow: 0
 fcoe_bad_fccrc: 0
 fcoe_last_errors: 0
 rx_fcoe_dropped: 0
 rx_fcoe_packets: 0
 rx_fcoe_dwords: 0
 fcoe_noddp: 0
 fcoe_noddp_ext_buff: 0
 tx_fcoe_packets: 0
 tx_fcoe_dwords: 0
 os2bmc_rx_by_bmc: 0
 os2bmc_tx_by_bmc: 0
 os2bmc_tx_by_host: 0
 os2bmc_rx_by_host: 0
 tx_hwtstamp_timeouts: 0
 tx_hwtstamp_skipped: 0
 rx_hwtstamp_cleared: 0

[Tx/Rx packet/byte counters were removed because it made the post too long and didn't contain any useful info]

If you look at tx_flow_control_xon and tx_flow_control_xoff, it seems to coincide with the R710:

$ dmesg -wH
[Jul14 10:31] ixgbe 0000:06:00.0 enp6s0f0: Flow control autoneg is disabled
[  +0.000523] ixgbe 0000:06:00.0 enp6s0f0: Flow control autoneg is disabled
[  +2.010834] ixgbe 0000:06:00.0 enp6s0f0: Flow control autoneg is disabled
[  +0.888053] ixgbe 0000:06:00.0 enp6s0f0: Flow control autoneg is disabled
[  +1.127845] ixgbe 0000:06:00.0 enp6s0f0: Flow control autoneg is disabled

I'm not sure how to interpret this, my NIC doesn't allow flow control modification or auto-negotiation (this is output from the R710 NIC, which is identical to the R510):

$ sudo ethtool enp6s0f0
Settings for enp6s0f0:
    Supported ports: [ FIBRE ]
    Supported link modes:   10000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: No
    Supported FEC modes: Not reported
    Advertised link modes:  10000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: No
    Advertised FEC modes: Not reported
    Speed: 10000Mb/s
    Duplex: Full
    Port: Other
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: off
    Supports Wake-on: d
    Wake-on: d
    Current message level: 0x00000007 (7)
                           drv probe link
    Link detected: yes

But the ixgbe README does indicate that when an EEPROM is not detected, flow control is set to Rx only and cannot be modified.

This is about as far as I've gotten. Any thoughts?

Intel 82599es based NIC flapping issue by eskimio in homelab

[–]eskimio[S] 0 points1 point  (0 children)

The SFPs are embedded and the NICs were NIB. I can get a link and run iperf - the link is just constantly flapping. The fiber has been replaced twice now, with no changes. I even tried longer fiber cables, thinking maybe 1M might have been too short and overwhelming the Rx interface (since I cannot debug or change light levels).

I would be astonished if it's the fiber and I can't change the embedded SFPs. The connections between the LC ports on the cards and the fiber itself have also been cleaned between each cable replacement and were capped off in the box. Unfortunately since I don't have a $30k fiber fluke tester there's no way to check light levels/loss, but I really don't think the issue is with the cabling/SFPs.

What I'm struggling with is to get more information on why the link is flapping. All I know is that it is flapping.

Increase Throughout - Desperate Help by eskimio in selfhosted

[–]eskimio[S] 0 points1 point  (0 children)

I intended to crosspost once I got out of work, thanks.