[01:15] <Sven_vB> I'm trying port forwarding with iptables. According to my old notes and https://kerneltalks.com/networking/how-to-forward-port-using-iptables-in-linux/ , I think this should work: https://paste.debian.net/plainh/d3285256 but the natbox doesn't accept my connection to :307. netcat in a shell on the natbox can talk to the target perfectly.
[01:15] <Sven_vB> some other NAT tutorials use additional state-based conntrack rules or SNAT, do I need any of those maybe?
[01:26] <Sven_vB> ??? and then I found #Netfilter . I'll ask there.
[01:47] <Sven_vB> indeed, SNAT was missing.
[14:58] <IngCr3at1on> updated idrac and bios last night but still has issues with ubuntu installer failing when setting the boot mode... tried debian and it worked just fine
[14:58] <IngCr3at1on> shame though, I would have preferred to run ubuntu
[15:08] <Ussat> On what system, I have Ubuntu on several Dell systems
[15:11] <IngCr3at1on> R720XD
[15:14] <IngCr3at1on> Ussat: it's weird I came on here yesterday to see if anyone had seen it. I went to do a clean install from 19.10 to 20.04 (single SSD for the OS (there are other drives for zpools but not part of the install process)) and it would run through the install then fail during grub saying Invalid Argument when trying to set the boot mode.
[15:15] <IngCr3at1on> updated everything after someone's recommendation here but to no avail. they had recommended an in-place upgrade but I couldn't even get 18.04 to reinstall
[15:26] <teward> IngCr3at1on: are you sure your ISO is clean?
[15:26] <teward> and what errors does it fail with when you try and use the ISO/installer?
[16:08] <IngCr3at1on> teward: yes tried multiple ISOs they all do the same thing... The error was `Could not set BootOrder: Invalid argument` but at this point I'm kind of done troubleshooting that and just going to use debian anyway lol
[16:09] <teward> mmkay, just wanted to make sure.
[16:09] <IngCr3at1on> yeah I appreciate it I just need to get this thing back up and working and the host os I interact with the least anyway so you know
[16:10] <mason> IngCr3at1on: That sounds like an efibootmgr error. What was the invocation, if so?
[16:10] <mason> IngCr3at1on: should look like: efibootmgr -o 1,2,3,b,4   as an example
[16:10] <IngCr3at1on> honestly mason I can't tell you at this point but otherwise you're correct it is/was
[16:11] <IngCr3at1on> oh actually I do have it
[16:13] <IngCr3at1on> `unshare --fork --pid -- chroot /target efibootmgr -o 0006,0001,0002,0003,0004,0000`
[16:14] <IngCr3at1on> seemed like something related to the installer so I just kind of moved on /shrug
[16:15] <mason> Two things jump out: 1) the extras zeroes aren't really needed, and 2) that looks fine, so maybe executing it in a shell normally might be interesting. I guess 3) make sure all those options exist, as there isn't a set number of boot variables.
[16:16] <mason> IngCr3at1on: Did you see this during a regular install, where you didn't expect to see anything of the sort?
[16:16] <mason> If so, it'd be worth filing a bug for it.
[16:23] <IngCr3at1on> mason yes it occurred during a clean install of ubuntu server (multiple versions)
[16:23] <mason> IngCr3at1on: Ah, sorry to hear it. I never use the installers so I'm always driving that stuff by hand. Definitely worth a bug report.