[newbe] Fist install: Can't reach web GUI (can't ping OPNs)

Started by MarieSophieSG, September 16, 2024, 12:47:06 PM

Previous topic - Next topic
Quote from: newsense on September 17, 2024, 03:00:03 AM
Only the first/default  LAN will have rules that will allow you to access the FW and go online, the others will need rules to achieve that. In your case it could be LAN1
Yes, I got that, that's why I'm only trying with the LAN (which I call LAN1, while LAN2 is actually OPT1, and LAN3 is actually OPT2)
What I said in my previous is about the physicall ETH, as there is no label on it, so out of the doubt I tryied with plugging my RJ45 to each, but I'm pretty sure it's the second from left
Anyway, LAN is icg1, which I gave 192.168.111.101 at install (installer/opnsense) option 2: Attribute IP
, after which I got the confirmation messge: "Your GUI can now be accessed via IP 192.168.111.101"
Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p

September 17, 2024, 07:37:50 PM #16 Last Edit: September 17, 2024, 09:54:31 PM by MarieSophieSG
Quote from: cookiemonster on September 17, 2024, 10:30:44 AM
Also. For simplicity the interface designated as LAN during setup, say LAN1 will have a DHCP service enabled (I think it is an option given at setup) so when you plug your laptop, it gets an ip and they can talk.
If for any reason that wasn't enabled, check the ip aff of your laptop. If is not in the range ie. 192.168.111.0/24 then change it manually on the laptop so they're both in the same network that way and can talk.

Yes, I've been thinking about it since bedtime yesterday, and now connected from work as I can't wait ...
I don't get any IP even though I enabled the DHCP option on LAN (on all three actually but it doesn't matter here)
So DHCP enabled on LAN 192.168.111.101 with first address 192.168.111.102 and last 192.168.111.133 so I should get an IP ... but I remember my network spinning and not getting any
So that explain why I can't reach the GUI
But that doesn't solve my problem, I still can't communicate with my box :(

As I -obviously- didn't configure anything on the box, except for:
WAN = icg0 = DHCP in, no DHCP out;
  LAN = icg1 = LAN1 = 192.168.111.101 DHCP enabled 192.168.111.102-133
OPT1 = icg2 = LAN2 = 192.168.112.101, DHCP enabled 192.168.112.102-133
OPT2 = icg3 = LAN3 = 192.168.113.101, DHCP enabled 192.168.113.102-133
Anything else was skipped (y/N)
Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p

Back to the test table, keyboard and screen

Would it change anything if I start with the live environment, tweak a few things (suggestions ?)  and only then do the install ?

Or does the install take only the image and not the (modified) live environment ?

Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p

Just install, boot, connect a PC to the single LAN port and check if you get an address and if you can login to https://192.168.1.1.

If successful you can add the other two interfaces from the UI, add DHCP and firewall rules, check if you can login to the firewall on one of them, and then change the IP address and the DHCP of the original LAN.

Sounds like a plan?

A newly installed OPNsense with default configuration "just works". If it doesn't, there's a more fundamental problem, so start with that "known good" configuration.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Quote from: Patrick M. Hausen on September 17, 2024, 10:45:22 PM
Just install, boot, connect a PC to the single LAN port and check if you get an address and if you can login to https://192.168.1.1.

If successful you can add the other two interfaces from the UI, add DHCP and firewall rules, check if you can login to the firewall on one of them, and then change the IP address and the DHCP of the original LAN.

Sounds like a plan?

A newly installed OPNsense with default configuration "just works". If it doesn't, there's a more fundamental problem, so start with that "known good" configuration.

Yes sir, I'm on it !
There is an option during install about DHCP:
- For WAN, enter the new LAN IPv4 upstream gateway address
- For LAN, press <ENTER> for none:

As I'm on LAN (icg1) I simply type enter, right ?
Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p

Don't go through any of these dialogs. Just install and let it boot. It will work.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Tadaaaahhh !
It works !
I'm accessing the box via 192.168.111.101 (yes, I know, I wasn't supposed to)
I'm now doing the full update

The only difference is ... I'm accessing through Win10 laptop, not the Linux one

As the access is through browser, it shouldn't make a difference, but ...
Oh! and I found that ETH0 is on the far right (I thought it was on the left)
Oh ! and as suggested, I didn't configure the LAN2/LAN3

So yeah, that's that, I'm in now .... time to messup with the option (and probably reinstall a few times before getting back to serious)

Thank you all for your patience (my autism doesn't make it easy) and advice, you took my frustration away and made me happy !

MSSG

Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p

September 18, 2024, 01:13:55 AM #22 Last Edit: September 18, 2024, 01:43:03 AM by MarieSophieSG
Is it normal that the system is in
- "The upgrade has finished and your device is being rebooted at the moment, please wait..."
for like 30+ minutes ?

EDIT: 1 hour ...
Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p

Depends on the power of the processor. An old one, say from 10 years ago, maybe. Anything from the last 5 years minutes. These are very broad statements, the real answer is based on more scientific numbers.
But in short it should only take a few mins. 30 mins sounds either a dinosaur of a cpu or it has booted and you just aren't connected network-wise correctly to it yet. i.e. you are on network A and the machine only listening on B.

simplest way to verify: connect physical monitor and keyboard.

Quote from: cookiemonster on September 18, 2024, 10:40:26 AM
Depends on the power of the processor. An old one, say from 10 years ago, maybe. Anything from the last 5 years minutes. These are very broad statements, the real answer is based on more scientific numbers.
But in short it should only take a few mins. 30 mins sounds either a dinosaur of a cpu or it has booted and you just aren't connected network-wise correctly to it yet. i.e. you are on network A and the machine only listening on B.
It' a 5105 JakerLake
But I found the problem ... The password for BIOS, if both root and user password are set, is also a boot password, so the machine did reboot but has been stuck at password prompt all night  ::)
I've removed the user password in BIOS and now it boots just fine unattended ...
Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p

Quote from: cookiemonster on September 18, 2024, 10:41:14 AM
simplest way to verify: connect physical monitor and keyboard.

Yes, exactly what I did when I woke up :)
Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p

September 19, 2024, 12:19:32 AM #27 Last Edit: September 19, 2024, 12:23:35 AM by MarieSophieSG
Suggestion for those who need it:
The OPNsense guide is reach and very thorough,
But if you need a visual:
Complete beginner guide to setup OPNsense

PS: This is my first post while behind OPNsense :)
Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p

September 19, 2024, 12:20:37 AM #28 Last Edit: September 22, 2024, 06:04:03 PM by MarieSophieSG
how do I delete a post I did by mistake (I clicked quote instead of modify) ?

And how do I set this post as "Solved" ? is there a button somewhere or do I have to manually edit the title ?
Hunsn RS39 (N5105, 4x i225) 24.7.5_0 testing
LAN1 = swtch1 Laptop1 MX23, NAS, Laptop2 Win10
LAN2 = WiFi router AP, Laptop2, tablet, phone, printer, IoT, etc.
LAN3 = Swtch2 Laptop3 Suse; Laptop4 Qube-OS/Win10, printer
Pretending to be tech Savvy with a HomeLab :-p