Jump to content

Mainfrezzer

Members
  • Posts

    372
  • Joined

  • Last visited

Posts posted by Mainfrezzer

  1. 3 minutes ago, Sacred said:

     

     

    Bei Fritz!Boxen musst du, den DNS-Rebind-Schutz für die Domain deaktivieren. 

    Ansonsten verwirft die Firewall eine Anfrage, die nach extern geht und von der Domain auf die WAN-IP zurück geworfen wird. 

     

     

    Das ist ja hier gerade etwas unrelevant. Letsencrypt und das Mobile Internet konnten ja nicht drauf zugreifen.

    Irgendwo sitzt entweder beim Dockerservice nen Furz quer oder bei der Fritzbox, Unraid öffentlich zu machen hat ja funktioniert.

    Ich würde jetzt mal einfach nen 0815 Apache Container oder so testen um zu gucken ob die Fritzbox dort die Anfragen durchlässt.

  2. oh mein Gott ich bin ein Idiot. Natürlich ist ipvlan an. Das kann mit ner Fritzbox nicht funktionieren. ARRGHHH.

    Ich gehe mal stark davon aus das 6.12.4 benutzt wird. In den Netzwerkeinstellungen die Brücke ausschalten, in den Dockereinstellungen macvlan auswählen (eventuell, wenn gebraucht wird, host access enabled) und dann bei Docker br0 zu eth0 wechseln, bei Wireguard einmal kurz ne 1 irgendwo eintragen, wieder löschen, dann speichern. 

  3. Mhmmm, dual-stack Anschluss oder ds-lite?

    Edit:

    26 minutes ago, pille said:

     

    Ping vom Rechner löst auf meine IP auf. Aus der unRaid CLI ebenfalls.

    Intern den Router zu pingen sagt nix^^

    Das ähnelt sich etwas mit dem Telefon ein anderes Telefon intern anzurufen um zu testen ob man von außerhalb angerufen werden kann.

    Wo wir bei intern sind. Die interne IP von dem NPM Container erzielt die gewünschte "Glückwunschseite"?

  4. 13 minutes ago, akhisyahmi said:

    Hi, I want to buy this 10GB card but I check back that my nvme cache can only go up to 3000MB/s which defeat the purpose of 10GB transfer rate

     

     

     

     

    I dont know where you got that one from but thats wrong

    The 10 gbit card has roughtly 1.04GB/s of throughput

    Your NVME does theoretically 40 gbit but equals in your case to around 3GB/s

  5. FUSE ist nen bisschen funky.

    Wenn man /user/ benutzen möchte dann müsste man statt "mv" "cp" nehmen und dann anschließen die original Dateien löschen.

     

    #!/bin/bash
    
    # Define the path to your BackupScript.sh on the host
    host_script_path="/mnt/user/misc/scripts/BackupMSSQLdatabases.sql"
    container_script_path="/home"
    
    # define backup locations
    host_backup_path="/mnt/user/appdata/mssql-production/backup"
    backup_share="/mnt/user/backup/backup-wawi"
    
    # Specify the name or ID of your MSSQL container
    container_name="MS-SQL-Server-Production"
    
    docker cp "$host_script_path" "$container_name":"$container_script_path"
    docker exec "$container_name" /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P xxxxx -i /home/BackupMSSQLdatabases.sql
    
    # move files to central backup share
    cp "$host_backup_path"/*.bak "$backup_share/"
    rm "$host_backup_path"/*.bak

     

  6. Benutze statt /user/ die disks direkt.

     

    #!/bin/bash
    
    # Define the path to your BackupScript.sh on the host
    host_script_path="/mnt/user/misc/scripts/BackupMSSQLdatabases.sql"
    container_script_path="/home"
    
    # define backup locations
    host_backup_path="/mnt/cache_vm_docker/appdata/mssql-production/backup"
    backup_share="/mnt/cache/backup/backup-wawi"
    
    # Specify the name or ID of your MSSQL container
    container_name="MS-SQL-Server-Production"
    
    docker cp "$host_script_path" "$container_name":"$container_script_path"
    docker exec "$container_name" /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P xxxxx -i /home/BackupMSSQLdatabases.sql
    
    # move files to central backup share
    mv "$host_backup_path"/*.bak "$backup_share/"

     

  7. 19 05:07:02 Beast kernel: igc 0000:09:00.0 eth0: PCIe link lost, device now detached
    Sep 19 05:07:02 Beast kernel: ------------[ cut here ]------------
    Sep 19 05:07:02 Beast kernel: igc: Failed to read reg 0xc030!
    Sep 19 05:07:02 Beast kernel: WARNING: CPU: 28 PID: 28060 at drivers/net/ethernet/intel/igc/igc_main.c:6472 igc_rd32+0x76/0x8b [igc]
    Sep 19 05:07:02 Beast kernel: Modules linked in: xt_connmark xt_comment iptable_raw xt_mark cmac cifs asn1_decoder cifs_arc4 cifs_md4 oid_registry dns_resolver xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc amdgpu edac_mce_amd edac_core intel_rapl_msr intel_rapl_common gpu_sched iosf_mbi drm_buddy i2c_algo_bit drm_ttm_helper ttm kvm_amd drm_display_helper drm_kms_helper kvm drm crct10dif_pclmul crc32_pclmul btusb
    Sep 19 05:07:02 Beast kernel: crc32c_intel ghash_clmulni_intel sha512_ssse3 btrtl btbcm aesni_intel btintel agpgart crypto_simd cryptd wmi_bmof bluetooth i2c_piix4 syscopyarea rapl sysfillrect sysimgblt nvme k10temp i2c_core ccp input_leds fb_sys_fops ahci ecdh_generic led_class joydev igc libahci ecc nvme_core video tpm_crb tpm_tis tpm_tis_core wmi tpm backlight acpi_cpufreq button unix
    Sep 19 05:07:02 Beast kernel: CPU: 28 PID: 28060 Comm: update_3 Tainted: P           O       6.1.49-Unraid #1
    Sep 19 05:07:02 Beast kernel: Hardware name: ASUS System Product Name/ROG STRIX X670E-E GAMING WIFI, BIOS 1416 05/16/2023
    Sep 19 05:07:02 Beast kernel: RIP: 0010:igc_rd32+0x76/0x8b [igc]
    Sep 19 05:07:02 Beast kernel: Code: 8b bb 28 ff ff ff e8 d8 e1 1a e1 84 c0 75 0d 83 c8 ff eb 1a 8b 02 ff c0 75 f5 eb bf 89 ee 48 c7 c7 db cf 2f a0 e8 97 e8 d7 e0 <0f> 0b eb e1 5b 5d 41 5c e9 7b 33 91 e1 83 c8 ff e9 73 33 91 e1 0f
    Sep 19 05:07:02 Beast kernel: RSP: 0018:ffffc9001b14fc40 EFLAGS: 00010286
    Sep 19 05:07:02 Beast kernel: RAX: 0000000000000000 RBX: ffff88812a130ba0 RCX: 0000000000000027
    Sep 19 05:07:02 Beast kernel: RDX: 0000000000000004 RSI: ffffffff820ed4af RDI: 00000000ffffffff
    Sep 19 05:07:02 Beast kernel: RBP: 000000000000c030 R08: 0000000000000000 R09: ffffffff8294e3f0
    Sep 19 05:07:02 Beast kernel: R10: 00003fffffffffff R11: ffff889057fbd32e R12: ffff88812a130000
    Sep 19 05:07:02 Beast kernel: R13: 000000000000c030 R14: ffff8881099fcc80 R15: 0000000000000000
    Sep 19 05:07:02 Beast kernel: FS:  00001472ebb5a640(0000) GS:ffff889018900000(0000) knlGS:0000000000000000
    Sep 19 05:07:02 Beast kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep 19 05:07:02 Beast kernel: CR2: 000015293274b000 CR3: 00000003006b4000 CR4: 0000000000750ee0
    Sep 19 05:07:02 Beast kernel: PKRU: 55555554
    Sep 19 05:07:02 Beast kernel: Call Trace:
    Sep 19 05:07:02 Beast kernel: <TASK>
    Sep 19 05:07:02 Beast kernel: ? __warn+0xab/0x122
    Sep 19 05:07:02 Beast kernel: ? report_bug+0x109/0x17e
    Sep 19 05:07:02 Beast kernel: ? igc_rd32+0x76/0x8b [igc]
    Sep 19 05:07:02 Beast kernel: ? handle_bug+0x41/0x6f
    Sep 19 05:07:02 Beast kernel: ? exc_invalid_op+0x13/0x60
    Sep 19 05:07:02 Beast kernel: ? asm_exc_invalid_op+0x16/0x20
    Sep 19 05:07:02 Beast kernel: ? igc_rd32+0x76/0x8b [igc]
    Sep 19 05:07:02 Beast kernel: igc_update_stats+0x70/0x6ae [igc]
    Sep 19 05:07:02 Beast kernel: igc_get_stats64+0x35/0x52 [igc]
    Sep 19 05:07:02 Beast kernel: dev_get_stats+0x39/0xcd
    Sep 19 05:07:02 Beast kernel: netstat_show.constprop.0+0x5b/0xac
    Sep 19 05:07:02 Beast kernel: dev_attr_show+0x1f/0x44
    Sep 19 05:07:02 Beast kernel: sysfs_kf_seq_show+0x7e/0xb9
    Sep 19 05:07:02 Beast kernel: seq_read_iter+0x16c/0x346
    Sep 19 05:07:02 Beast kernel: vfs_read+0x105/0x19f
    Sep 19 05:07:02 Beast kernel: ksys_read+0x76/0xc2
    Sep 19 05:07:02 Beast kernel: do_syscall_64+0x6b/0x81
    Sep 19 05:07:02 Beast kernel: entry_SYSCALL_64_after_hwframe+0x64/0xce
    Sep 19 05:07:02 Beast kernel: RIP: 0033:0x1472eec3aafd
    Sep 19 05:07:02 Beast kernel: Code: 31 c0 e9 e6 fe ff ff 50 48 8d 3d 36 a1 0a 00 e8 49 15 02 00 66 0f 1f 84 00 00 00 00 00 80 3d e1 ca 0e 00 00 74 17 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec
    Sep 19 05:07:02 Beast kernel: RSP: 002b:00007ffd62f178d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
    Sep 19 05:07:02 Beast kernel: RAX: ffffffffffffffda RBX: 00001472eb878380 RCX: 00001472eec3aafd
    Sep 19 05:07:02 Beast kernel: RDX: 0000000000003000 RSI: 00001472eb8a9018 RDI: 000000000000000a
    Sep 19 05:07:02 Beast kernel: RBP: 0000000000000000 R08: 0000000000000002 R09: 00000000000000a9
    Sep 19 05:07:02 Beast kernel: R10: 00000000000a9000 R11: 0000000000000246 R12: 0000000000003000
    Sep 19 05:07:02 Beast kernel: R13: 00001472eb8a9018 R14: 00001472eb8773c0 R15: 0000000000000000
    Sep 19 05:07:02 Beast kernel: </TASK>
    Sep 19 05:07:02 Beast kernel: ---[ end trace 0000000000000000 ]---

    Its a driver issue with icg and the intel nic you have 

    Seems to be related to https://forums.unraid.net/topic/133803-intel-ethernet-adapter-sporadically-losing-connectivity-until-reboot/




    Edit:

    OOF, ive bad news for you. It seems like this is a specific issue with Asus and this NIC

    Ive found following info about it
    https://www.reddit.com/r/buildapc/comments/xypn1m/network_card_intel_ethernet_controller_i225v_igc/?rdt=62100

    You could try to add 

    pcie_port_pm=off pcie_aspm.policy=performance

    to the syslinux configuration


    Edit #2

    Seems like the solution is working since following can be found here in the forum
    6.11.5 - igc 0000:09:00.0 eth0: PCIe link lost [Ryzen 9 7950X] [SOLVED] - General Support - Unraid

    • Like 1
×
×
  • Create New...