2.1 shows as 2.0.3 and web configurator on wrong ip??

zerokool

so i thought i downloaded 2.1 it said it was 2.1 but it installs as 2.0.3??????????

also. seams that on these machines im using i cant get the web configurator to work on the desired nic??

10.0.0.2 is my internal/LAN ip
and i have 2 wan's of 192.168.0.3
i cant get configurator on 10. only on 192.???

i have several other pfsense units running.

zerokool

!!!!!
does this make sense!?!?!?!

![IMG_0843 (Medium).JPG](/public/imported_attachments/1/IMG_0843 (Medium).JPG)
![IMG_0843 (Medium).JPG_thumb](/public/imported_attachments/1/IMG_0843 (Medium).JPG_thumb)

zerokool

anyone???

doktornotor

No, noone at all… probably since

Ad 1/ It clearly does NOT install as 2.0.3, reading the screenshot it clearly says 2.1-RELEASE
Ad 2/ The very same screenshot very clearly says that 10.0.0.2 is NOT your LAN IP, and you have no such things as WAN on 192.168.0.3, let alone two of them.

Considering the above, it's extremely "surprising" that you cannot reach the box on 10.x.x.x ::)

Executive resume: You make zero sense, dude.

zerokool

i had to manually upgrade it to 2.1 after first landing on webconfigurator.
second. before i took that pic i changed this silly thing atleast for 3 hours!
reset it numerous times.

but i figured it out! i CANNOT use the integrated lan plug for "lan" my "laa" has to be on an expansion pci lan card?
so when integrated lan is used for wan or opt all is okay.

doktornotor

Good that you figured it out, have a nice day.

kejianshi

I see a few issues.

1st - Looks like pfsense is getting a private address via DHCP on its WAN
(If thats what you wanted, you will have to uncheck "block private" at botom of interfaces > WAN

2nd - If you were going to access the WEB GUI, it should be at the LAN address at 192.168.1.1

3rd - If, for some strange reason, you wanted to access the web gui via the WAN interface, you would have a few whoops to jump through.
(You would need to uncheck "block private" at botom of interfaces > WAN and in system > advanced disable DNS Rebind Check (check box)

Anyway - I suspect everything works hardware/software wise and that you simply have a little learning curve ahead of you. Thats all.

zerokool

@kejianshi:

I see a few issues.

1st - Looks like pfsense is getting a private address via DHCP on its WAN
(If thats what you wanted, you will have to uncheck "block private" at botom of interfaces > WAN

2nd - If you were going to access the WEB GUI, it should be at the LAN address at 192.168.1.1

3rd - If, for some strange reason, you wanted to access the web gui via the WAN interface, you would have a few whoops to jump through.
(You would need to uncheck "block private" at botom of interfaces > WAN and in system > advanced disable DNS Rebind Check (check box)

Anyway - I suspect everything works hardware/software wise and that you simply have a little learning curve ahead of you. Thats all.

1-yes i was jumping off my other pfsense box. just testing.
2-thats what i thought, and wanted.
3- NOOOO!! but thanks for telling me how!
as a side Q to your 3rd point. when im at my house and i click to my officenetwork website sometime i got to pfsense and it told me some error about dns rebind, do i make sense?

kejianshi

Sounds like you are NATing back to the same port the webconfigurator is running on.

stephenw10

Ill just add that the webgui listens on every interface, access to it is only restricted by the firewall rules. This means that you can access it on the WAN IP address from the LAN side even if your WAN rules block it. The default LAN to any rule allows it.

Steve