Can't access pfsense web GUI from VLANs [Solved]

PFbest

Not sure what you thought that article had to do with a layer 3 switch.. That idiot was running 2 different networks on the same layer 2 with just trying to put a vip on the interface in the other network..

Ok you sure your just not having a problem accessing the web gui from this client, something wrong with its browser, the cert you have on the gui, you runnint it on some odd port? You using a proxy on this client? Do you have transparent proxy setup on psfense?

Ok, forget about the link haha ;D
Um, client should be fine I think, previously I tried on physical laptop, now I'm using windows in my VM workstation in my laptop.
(I passed the same module of USB nic directly to this VM, so eliminate bridge/NAT etc.)
But same results anyway. Can't access to web gui but no problem to ping.
Actually I do have proxy on 192.168.0.102 (I promise I eliminated proxy), but I did not use the proxy for testing web gui. (BTW, 192.168.3.1 can't access proxy as well, but it can access 192.168.101, I guess it's the iptable's problem) (Again, browsers are setted to not using proxy, not even auto proxy) (It's not transparent as well, so should be fine I think)
Now the pfsense cert part, it's the default one comes with pfsense, so it's invalid, I used it for 2 years, just click ignore in browser you know. (Will that be problem?? :o)
Odd port? Um, shouldn't be I think. all things should be normal I guess.
No transparent proxy, and in pfsense there's no proxy at all :P (squid is not installed on pfsense and pfsense is not using proxy from 192.168.0.102)

PFbest

Also this is what I get when I hit enter key in browser url input filed.
(url is https://192.168.3.1)
(Two times)

wire.png_thumb

wire_error2.png_thumb

PFbest

from 192.168.0.74
(ignore cert error already clicked)

wire_.0.74.png
wire_.0.74.png_thumb

johnpoz

looks like your seeing dup.. I would turn off https for testing.. And then can you post up the actual pcap so I can open it in wireshark.

PFbest

Not a problem.
I'm on it.
Heaps thanks man!!!!

PFbest

This is the pcap from PC on port 7.
(The icon on browser tab just turning and turning, no pfsense page title showing, weird thing is it's not like when we don't have internet, it will show you error page directly.)
Eventually the browser will show ERR_TIMED_OUT.
(For this pcap, I didn't wait untill the browser come up with that error, it's going to be long)
I I just start wireshark, put address in browser hit enter, wait 5/10 seconds, then save the pcap.
If wait until the error shows up will help I can do that, just say it.
(Also I tried to connect to 192.168.3.1, and 192.168.0.1)
(Last thing, https turned off in this pcap)
Thank you!!!

[PC on port 7, 192.168.3.10.pcap](/public/imported_attachments/1/PC on port 7, 192.168.3.10.pcap)

johnpoz

ok just started looking at it, but why your browser try so many connections at the same time?? to 443?

What browser are you using?

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

whyyourbrowser.png_thumb

PFbest

Thanks man!
It's chrome, google chrome :o
And yes, that's exactly the user-agent string for chrome 50.0.2661.102 m

PFbest

It's late night here, I need to go to bed, sorry :-.
I will back here tomorrow, many thanks to you!!!!

PFbest

Oh, another weird thing is
If I do nslookup google.com 192.168.0.1 or nslookup google.com 192.168.3.1 nslookup google.com 192.168.0.101
They all work.

PFbest

Another finding:
On the pc on port 7
If I do telnet 192.168.0.1 80 or telnet 192.168.3.1 80
as you see in p1, it seems I can get reply.
If I do telnet 192.168.100.1 80, it will fail, of course 192.168.100.1 does not exist on my network.

p1.png_thumb

p2.png_thumb

PFbest

More finding
If I set rules in firewall for GUEST_AP_VL like this.

reject GUEST_AP_VL net to any destination any port.

I try to open 192.168.0.1 and 192.168.3.1 in PC on port 7, the browser returns ERR_CONNECTION_REFUSED, which is right.

Any ideas? ??? ??? ???

PFbest

Interesting, I think I've found problem.
I changed the MTU for vlan 12 to 1492. (My adsl MTU is 1492, but I don't understand why vlan MTU is related to gateway/ADSL MTU) (By default MTU it set to 1500)
But it works now. As long as I change the MTU to 1492, pc on part 7 can go to 192.168.0.1, 192.168.3.1, 192.168.2.1, eben with https on for pfsense web gui, it works.
Would you mind to confirm your MTU on vlans and your gateway for me and other on this forum please? So other won't get stuck like me ;D
Now I can move on on other rules etc. :P

Your effort, help and time is appreciated!!

Thank you johnpoz!!!

kpa

I bet this has something to with the USB nics you're using, there's a reason why pros avoid them at all costs.

PFbest

@kpa:

I bet this has something to with the USB nics you're using, there's a reason why pros avoid them at all costs.

You mean the MTU issue is caused by USB NIC?
Well, pros would have proper server, rack, UPS etc. don't they 8)
I'm still study though, but I would go PRO stuff if I have the money to buy and can afford bills etc. for sure :D
That's the dream of every or at least most of the tech savvies isn't it ;)

johnpoz

My mtu is 1500.. on all devices.

There clearly was something going on in your trace.. Its like you just lost connection packets, possible it could of been large packet that got fragged..

USB interfaces are utter crap, why would you use them, you can pick up normal nics for like $10 that would be better than some usb nic.

Glad you got it sorted, for sure it was strange. But you can see in your sniff that your client is talking, you have a good handshake but when then its like something was missing.. And that packet you did get was not the next one..

PFbest

@johnpoz:

My mtu is 1500.. on all devices.

There clearly was something going on in your trace.. Its like you just lost connection packets, possible it could of been large packet that got fragged..

USB interfaces are utter crap, why would you use them, you can pick up normal nics for like $10 that would be better than some usb nic.

Glad you got it sorted, for sure it was strange. But you can see in your sniff that your client is talking, you have a good handshake but when then its like something was missing.. And that packet you did get was not the next one..

Cool, so there must be something wrong with my stuff.
Oh, did I mention the server/host of pfsense virtual machine resides in is a laptop? ;D
It's a retired laptop, and yes again, it's been like this for 2 years.
Otherwise I'd go with proper NIC for absolutely sure
I know you will be like this :o haha

(BTW, all of my other devices are all running with 1500 MTU as well, but ADLS is PPPoE so been forced to MTU 1492 for adsl gateway)

Thanks anyway ;D

PFbest

@johnpoz:

My mtu is 1500.. on all devices.

There clearly was something going on in your trace.. Its like you just lost connection packets, possible it could of been large packet that got fragged..

USB interfaces are utter crap, why would you use them, you can pick up normal nics for like $10 that would be better than some usb nic.

Glad you got it sorted, for sure it was strange. But you can see in your sniff that your client is talking, you have a good handshake but when then its like something was missing.. And that packet you did get was not the next one..

Well, heaps of trial and error + some luck, finally it's working now :P

johnpoz

Why don't you just run vlans on your physical nic vs damn usb nics?

You can get a 8 port gig switch that does vlans for like $30…

PFbest

@johnpoz:

Why don't you just run vlans on your physical nic vs damn usb nics?

You can get a 8 port gig switch that does vlans for like $30…

The physical nic is been used for DNS/email/file sharing stuff from windows server haha ;D
Oh, the switch has 24 ports (gig), I bought it when it was on discount ;D, currently ports are enough I think