Bandwidth test= fine, browsing unusable (HYPER-V)
-
I'm just at the gym right now but when I get home, I'll do what I've been delaying forever: make a proper visio diagram.
-
I'm just bummed that it works on a crappy physical computer, works great on a VMWare host, but fails catastrophically on Hyper-V
-
Well I will certainly study it, but have no idea if I'll understand how its working. Should be fun.
-
http://imgur.com/hl2Xo77,VYt3Hts,a2W3uXi
This is the current pfsense setup for the physical pfsense implementation and it worked very well. The ISP gives me all different IPs with all different subnets and all different gateways.
-
crap
the first image is incorrect and is for the virtual and is a wrong screenshot. Disregard it.This is the correct one: http://imgur.com/XbBg4ii,PdsrAoT,2D4ps89
-
This is the one I was waiting for.
Question. Was this modem you are using now, it was connected to the physical machines before?
But your links in the main status page show correctly as up correct? -
What are you DNS servers?
Are they being served by numbers forwarded from your WAN connection?
Could you try changing them to something like:
127.0.0.1
8.8.8.8
8.8.4.4?????
-
to note: in the second image under gateway, it says dynamic for one. This is the one I've disconnected for the virtual pfsense to use, so it is seen as down for the moment (I've removed the connection to VLAN 5 from the physical pfsense and applied it to the virtual to use).
-
http://imgur.com/GaydetJ,BRkUTaK is a simplified network diagram
the first image is the functional view while the second image is the physical view
-
What are you DNS servers?
Are they being served by numbers forwarded from your WAN connection?
Could you try changing them to something like:
127.0.0.1
8.8.8.8
8.8.4.4?????
I use an internal DNS on the Domain Controller for internal name resolution. It forwards to the ISP's primary and secondary DNS as well as 8.8.8.8 and 8.8.4.4.
-
One second, trying out your suggestion
-
I like your suggestion because the internal DNS hadn't changed the gateway.
I tried external DNS both 8.8.8.8/8.8.4.4 as well as my ISP's DNS servers and it was still slow (flushed DNS before the test as well as cleared the browser caches)
-
OK - Now…. Maybe its the return path thats a problem.
Try unplugging WAN cable from one modem.
Test.Then other modem...
Test...Is it more reliable on one modem than two?
-
Crap. You only have one. Right?
OK. Can you drop 1 IP for WAN and test?
-
Just dropped everything on Modem1 except for a single connection/IP to virtualize pfSense and it still has same issues
Weird things though…...google loads quickly and has no issues, so does speedtest.net......youtube takes a while to load all the thumbs but the videos buffer at full speed
-
I can't load a single thing on forum.pfsense.org when I change to the virtualized pfsense
Also I am seeing a ton of denials on the pfsense firewall from internal IPV6 addresses (probably broadcasts) even though I disabled IPv6….......how do I kill that off?
Edit: Here are the firewall logs: http://imgur.com/1cgaMr5
-
Unless you have some need of IPV6 today, why not:
System > Advanced > networking
Un-click all the IPV6 on both your PFsense boxes?
Turn it all off.
-
Yeah I did just that. The logs are still getting filled with IPv6 denials…...weird.
-
Can you also remove the "allow" IPV6 reference in your LANs (and maybe WANS) firewall rules?
Unless you need it for something? Everywhere… -
Can you also remove the "allow" IPV6 reference in your LANs (and maybe WANS) firewall rules?
Unless you need it for something? Everywhere…hmmm I don't think this is the problem, though….....I should get some sleep on this.
Let me know if you think of anything else that I may have missed.
Edit: I have removed the references from everywhere, still showing.......hmm