Help! Can't connect after following tutorial.

[Steamly]

Hello all,

Been trying to get better at networking environments so I can set up my own lab to practice things in. I was following this tutorial a couple weeks back.
https://www.remotelycurious.net/post/homelab/#network

Everything worked great and I was able to follow it completely damn near to the last instruction. I was worried about a problem like this since its out of date, but Im hoping its something simple and stupid so I can get back to what I was doing but I cannot figure out whats going on. I cant ping gateway, I cant connect to the web interface. I thought the NIC was bad for a moment because none of this was happening before and we have had thunderstorms.

Here is the topology created via the tutorial:



Here is the results of my ip addr and /etc/network/interfaces, I haven't set up ssh so I can't remote in and copy the text. Go ahead and roast me for the screen pictures. Hopefully compression doesnt render them unreadable.

I set up a firewall in a pfsense vm but its stopped on boot so it couldn't be that. The hosts file is editted to include 192.168.7.99. Im connected via ethernet. The strange thing is that the device isn't even showing up on my routers devices page. I set it up with a static IP and everything and now when I turn it on, its no longer even there.

Id appreciate any help. Thank you.

 

[Hannes Laimer]

Hey,

so your home network is 192.168.4.0/24 with your router being 192.168.4.1, right? Usually post-up and post-down are part an interface configuration, so here those should be in the block for vmbr0. What does ifreload -avvv say? The ... state DOWN ... in both the physical NIC and the bridge seem to indicate something went wrong in configuring those, and they where not brought up correctly.

Physical connection looks fine given LOWER_UP.

 

[Steamly]

Hey,

so your home network is 192.168.4.0/24 with your router being 192.168.4.1, right? Usually post-up and post-down are part an interface configuration, so here those should be in the block for vmbr0. What does ifreload -avvv say? The ... state DOWN ... in both the physical NIC and the bridge seem to indicate something went wrong in configuring those, and they where not brought up correctly.

Physical connection looks fine given LOWER_UP.

The home network is technically 192.168.4.0/22, since thats the way Eero set up the DHCP and I can't change it. But the proxmox server does have a static one thats within that scope. I thought I messed up by putting it in the scope, but none of the devices are close to 7.

But yes the router is 192.168.4.1.

When running ifreload -avvv the last thing is "executing iptables -t nat -A POSTROUTING -s '192.168.8.0/24' -o vmbr0 -j MASQUERADE"
then "exit status 0"

Which makes me think its a NAT issue and I put the wrong ip in there or something. But I dont know why the NIC and bridge would both say down though, and the server doesnt appear on my eero's devices page either.

Thank you for the help. Ive attached the rest of ifreload -avvv.

 

[Hannes Laimer]

exit 0 is good. Could you remove the post up and down entries(just add # to the start of the line), then run ifreload -avvv again and check if the PVE host itself is reachable, or can reach anything on the network(also ip a, still state DOWN?). This should help narrowing down where the problem is.

 

[Steamly]

exit 0 is good. Could you remove the post up and down entries(just add # to the start of the line), then run ifreload -avvv again and check if the PVE host itself is reachable, or can reach anything on the network(also ip a, still state DOWN?). This should help narrowing down where the problem is.

Commented out the post lines, rebooted just to be sure, and ran

ifreload -avvv

, which finished with

exit status 0

. Ive attached the new

ifreload -avvv

just incase.

ip a

still shows

state DOWN

for both the NIC and the bridge.

 

[Steamly]

Sorry for the formatting, didn't see the inline code option right next to it. oh well

 

[fba]

Try ip link set enp0s31f6 up
If it helps: Add a line with auto enp0s31f6 right above of iface enp0s31f6 inet manual in the /etc/network/interfaces file and try again with the ifreload command

 

[Steamly]

Try ip link set enp0s31f6 up
If it helps: Add a line with auto enp0s31f6 right above of iface enp0s31f6 inet manual in the /etc/network/interfaces file and try again with the ifreload command

This worked! Thank you so much!

Can you tell me more about this? The NIC was set to be down by default? Was this something that had changed because of the changes I made? It had never happened any other time I booted the server.