...and this syntax works fine with Gmail too! Thanks for the tip.

@renjithb said in Issue in Virtual box installation: Yes the same way I configured Which is how? What can not talk to what? Your host from what IP can not talk to pfsense IP on what interface in VB.. Your really going to have to give us more if you want any help.. sofar you have told the mechanic its broke..

Still better to have the public IP on the pfSense WAN directly if you can. Steve

@microkid yes that's okay, I also wrote this too, but fix the file system before you scan further the box everything must be ruled out when searching for such an error.. poor disk fragmentation, a typical cause of random crashes I know you think of the NIC because the LEDs don't flash but like I said it could be part of a process

@nafeasonto said in Can someone help me please? I can't udpate my packages on PFsense.: 2.5 of Pfsense. Ah, the bleeding edge technology. Probably not everything, but most of this page could be helpfull. edit : also : consider posting in the 2.5 Development forum.

This is a recent, clean install ? You use packages ? If so, what happens if you disable them all ?

@valentinius Yes, as i posted above the issue is resolved.

Had a moment to look in the logs more closely. I see this: miniupnpd 34231 setsockopt(udp, IPV6_RECVPKTINFO): Invalid argument It works, but... This happens on restart of miniupnpd after any config change.

Update - @Gertjan @johnpoz I think one of the problems (or the main one) was not a DNS blocking/limiting etc. but a static route to it set by pfsense because it was used as a monitoring IP etc. (read about it online). Since I'm never gonna use 4.2.2[1-6] for production DNS resolving, I decided to utilize them as monitor IPs for every gateway that is not the WAN itself or has no proper 'upstream' gateway to check against. Currently I'm happy with the solution below. I think the assumption mentioned in the screenshot is correct but we'll see what happens. [image: 1593508324504-screen-shot-2020-06-30-at-11.55.49.png] [image: 1593508333326-screen-shot-2020-06-30-at-11.56.06.png]

@rafamello If their SIP packets have the private IP encapsulated then they won't be able to stream back to you. I'm not sure which it would be but it's either ALG or the double NAT. SIP doesn't really work with either. When dealing with Cable operators in the USA (Spectrum and Comcast) there are 3 modes for the cable modems: RIP with NAT = Use when you are not providing a separate router. You would never use this with pfSense or any other customer provided firewall/router. RIP without NAT = Use when you have a static IP programmed in the router and the modem needs to be your Gateway. Bridge = Use when you don't have a static and are providing your own router. This puts the Public IP directly on your firewall.

@bmeeks I'll have to look at the packet capture to see what is going on at this point. I set everything up this morning again fresh with just the very basic default settings on the netgate box and this is what I have found. no netgate installed on my home network I can connect to my site with chrome and edge. put in the netgate and only edge will see my site. I tried to do a reinstall from the flash image and it gave me ad error not being able to read the drive. I followed the support link and used the program they suggested to image my flash drive and it did fine even it's test said it was fine. So I'm now looking for a new flash drive to retry to redo the image. I know you guys think I'm missing something simple because what I'm telling you just can't happen... Well if it can it will happen to me. I really can't tell you any more then what I have and I almost went through writing my last couple messages as I was doing it here at the house. I don't know how much more of a basic setup I can get. I'll shutup :-) once I'm able to get a new inage on my box to see if that has anything to do with something residule not being reset. But like you said, the browsers are supposed to be 100% agnostic. so something is going on here. if I can do a lookup and it comes back fine then why shouldn't both browsers act the same. Thank you for all your comments. I will do a packet capture and see what's going on. too weird.

yeah can not get nat 1:1 and ipsec with port forwards to work right.

Thought I would post an update. It has been months since I started this thread, with our friend COVID in town and everyone online, bringing the Internet down makes me very unpopular. Back on April 10, I rolled back to my old hardware. It was running v2.3.5-RELEASE-p2. From April 10 until today (June 28) it has worked perfectly. Never a glitch. Today the family went out, so I took the opportunity to try switching hardware again. I made a fresh backup of my v2.3.5-RELEASE-p2 that was running. I see there has been a new release of PFSense, so I downloaded v2.4.5-RELEASE-p1 and installed it on my new box. Restored the backup and everything is running perfectly. No packet loss every 15 minutes. I looked at the release notes for 2.4.5-p1 and don't see anything that jumps out at me. Guess I will never know what the true cause of the problem was, but glad to have my new hardward back in place without any packet loss as my old hardware could was limiting my connection speeds.

SOLVED Just a quick thank you for all your contributions but an especial thanks to netblues for this "Well, this is straight and clear. The isp is asking the client to drop and reconnect ppp so isp provisioning (most probably radius) can also assign the route for the added network." That paragraph really opened my eyes and allowed be to proceed and get the public ip routed to opt1 interface. Thanks again