Proxmox All-in-One Guru Notes

TheGuruOfNothing — Today at 11:03 Ok, wiping the PfSense VM and building a new one (for simplicity) [11:08] Already hit the wall [11:08]

smiley:

[11:09] Being as I have never used more than one port on any of my servers, I am not sure how to set up and utilize the other ports since it defaults to whatever it defaults to

Tinker — Today at 11:09

smirk:

[11:09] Step 1... [11:09] go to the Web UI of the server... [11:10] Select the server itself... [11:10] See System/Network in the second column? [11:12]

image - sample:

TheGuruOfNothing — Today at 11:14 yep

Tinker — Today at 11:15 See at least one each of "Network Device" & "Linux Bridge"?

TheGuruOfNothing — Today at 11:15 yep

Tinker — Today at 11:15

thumbup:

[11:16] The Network Device marked as Active is the one you're talking to it through... [11:16] Same for the active bridge. [11:16] See a second (or more...) "Network Device"?

TheGuruOfNothing — Today at 11:18 Sorry... phone call [11:18] Im back

Tinker — Today at 11:18 Phone calls happen... [11:19] So, see a second Network Device?

TheGuruOfNothing — Today at 11:19

image - screencap:

Tinker — Today at 11:20 Thare ya go...

TheGuruOfNothing — Today at 11:20 vmbr0 is using eno1

Tinker — Today at 11:20 eno1 is the NIC you have connected ATM...

TheGuruOfNothing — Today at 11:20 I have cables connected to both actually

Tinker — Today at 11:20 & vmbr0 is the internal connection to it that all of the VMs see. [11:21] eno2 isn't actually doing anything tho.

TheGuruOfNothing — Today at 11:21 correct

Tinker — Today at 11:22 If it's working like I think it is... They are in the same order as the physical NIC are listed on the machine. [11:22] For the moment, I'd just unplug the cable from the second one. [11:22] Simplify life... [11:22] Yer gonna swap them later anyhow.

TheGuruOfNothing — Today at 11:23 lemme run down there

Tinker — Today at 11:23 Exercise time!

TheGuruOfNothing — Today at 11:30 I was mistaken [11:30] I have two cables going to each server ... [11:31] one to a NIC and one to iLO [11:31] So... we good

Tinker — Today at 11:31 All-Righty then... [11:31] Step 2... [11:32] See the "Create" button? [11:32] Click it.

TheGuruOfNothing — Today at 11:32 yep [11:32] yeop

Tinker — Today at 11:32 You wanna make a new "Linux Bridge" [11:33] Only thing you want to fill in is the Bridge ports box. [11:33] tell it "eno2" [11:34] Once you tell it to go ahead & create it, poke the "Apply Configuration" button.

TheGuruOfNothing — Today at 11:34 yep

Tinker — Today at 11:35 You now have 2 network ports available to your shiny new pfSense VM...

TheGuruOfNothing — Today at 11:35 SO... [11:35] I create the VM, tell it to put WAN on vmbr1 and LAN on vmbr0

Tinker — Today at 11:36 nope...

TheGuruOfNothing — Today at 11:36 lol

Tinker — Today at 11:36 WAN goes on vmbr0 during construction. [11:36] & LAN on vmbr1. [11:37] When you get to the fugly step... [11:37] https://wiki.nerdmage.ca/index.php/Proxmox_All-in-One#Taking_it_LIVE Proxmox All-in-One [11:37] You'll be swapping the bridges.

TheGuruOfNothing — Today at 11:37 Fer giggles... why can't ya build it the other way around? [11:38] A way of inserting a PfSense box into an existing server

Tinker — Today at 11:38 Coz then you'll have a VERY hard time reaching the machine through the unconfigured pfSense VM...

TheGuruOfNothing — Today at 11:38 ah, ok [11:39] forgot that ya hafta have a console to config on

Tinker — Today at 11:39 The bridge swap puts the management port of the PVE box itself behind the pfSense server & kinda hides it from the real world. [11:40] Just had a thought... [11:40] Your local network... It contains the 192.168.1.xxx range?

TheGuruOfNothing — Today at 11:40 yes [11:41] .0.xxx -.3.xxx [11:41] /22

Tinker — Today at 11:41 If so... You may have to do an extra step while setting up pfSense. [11:41] Basically, you'll need to tell it to use a range that's not on your local LAN. [11:42] It might figure it out itself, but I'm not sure.

TheGuruOfNothing — Today at 11:42 Not thinking so [11:42] Ok, so I am not mucking this about... [11:43] I just had a thought........... [11:43] hold on

Tinker — Today at 11:45 Yer workin on a trick question... aren't you...

TheGuruOfNothing — Today at 11:45 Well, I was [11:45] then I found my own flaw [11:46] Ya can't access PfSense from the WAN side of the setup

Tinker — Today at 11:46 nope... [11:47] But telling your Management VM to use vmbr1 means you can go to its console & play... [11:47] Another reason you need PVE to stay accessible during the build.

TheGuruOfNothing — Today at 11:47 I can build the VM and tell it to use vmbr1 as it's WAN port and vmbr0 as the LAN and use the console to access it.... right up until I save the config then EVERYTHING on it will go dead stick because LAN will be dicked as long as it is connected to my network [11:48] I might be able to connect vmbr0 to a seperate switch and use a laptop to access it at that point however [11:48] it would then be a standalone server but I don't know if I can access PVE again though

Tinker — Today at 11:49 WAN has to stay on vmbr0 until pfSense is ready to take over.

TheGuruOfNothing — Today at 11:49 yeah... was spitballing [11:49] wrapping my head around all the option

Tinker — Today at 11:50 I spent many hours & much stress trying to avoid the whole "Swap everything" step... [11:50] Damn near gave up on it... [11:50] Then, suddenly, decided to abuse it a bit & it worked. [11:51] Now both the servers I've done this on look like they're hooked up backwards if you pay too much attention to the port numbers on the back. :| [11:52] But I have a label maker & I'm not afraid to use it. [11:53] Damn! Bloody coffee cup has a big hole in the top... BRB

TheGuruOfNothing — Today at 11:57 Ok, what the literal hell is fucking going on? [11:57] I have the PfSense ISO on Datastore1 and that is the ONLY place it is... [11:57] I selected it for use for the building of the new VM... [11:58] and it fucking boot loops saying that the media is not present [11:58] I used it to build a VM on this box already so I know it worked [11:59] I deleted that VM so there should be no conflict if there was such a thing (edited)

Tinker — Today at 11:59 Did you "Remove" the original VM & start from scratch? Or just try to tell it to buut from the image?

TheGuruOfNothing — Today at 11:59 I deleted the original VM [11:59] then started from scratch [12:00] buut? Canadian? [12:00]

P

Tinker — Today at 12:01 Canadian?

TheGuruOfNothing — Today at 12:01 yanno... like aBOOt

Tinker — Today at 12:01

face_palm:

TheGuruOfNothing — Today at 12:01 hehe [12:01] ok... I am done [12:01] for now [12:02] I might pull that one back out in a week or two [12:02] (it did feel kinda good though)

Tinker — Today at 12:02 Need a :slap: emoticon

TheGuruOfNothing — Today at 12:02 indeed

Tinker — Today at 12:03 musta been some simple error setting up the vm...

TheGuruOfNothing — Today at 12:03 lemme keel it and do it again

Tinker — Today at 12:07 Did you remember to tell it OS Type = OTHER?

TheGuruOfNothing — Today at 12:11 no [12:11] was Linux 5x

Tinker — Today at 12:12 pfSense ain't Linux... Just sayin' NEW

TheGuruOfNothing — Today at 12:12 it didn't even try to install, said media not present [12:12] I deleted the ISO and downloading new copy directly to server [12:12] will use OTHER

Tinker — Today at 12:21

|

Just realized why running through the steps on a test server is fighting me... Doing it on the silly little Celery machine...

TheGuruOfNothing — Today at 12:22 Still boot looping

Tinker — Today at 12:22 It doesn't have hardware virtualisation OR more than 1 core OR more than 2GB of RAM...

TheGuruOfNothing — Today at 12:22 Trying to use the PF sense aiso and it doesn't even acknowledge it is [12:23] Single core 4 gigs of ram and I don't know about hardware virtualization [12:23] I gotta go take wifey to a doctor's appointment so I will get back on this when I get back home in a few hours

Tinker — Today at 12:24 I'll see if I can reproduce the bootloop (or find out why it might happen...)