Hi again, after trying several times, differen USB sticks and so on I had to chose another terminal than the default. Welcome to pfSense! Please choose the appropriate terminal type for your system. Common console types are: ansi Standard ANSI terminal vt100 VT100 or compatible terminal xterm xterm terminal emulator (or compatible) cons25w cons25w terminal Console type [vt100]: cons25w No I could run through the installer process

@Derelict Yep, that is what I'm going to have to do. Especially since the I can't reach the HTTP or SSH interfaces anymore. Just waiting for a USB to female serial cable to arrive.

@KOM said in Cannot log into 192.168.1.1: Good catch. I never would have figured that one out in a million years. Thanks again for your help.

@Jonathan-Elias said in Do not carry packets!: The DNS has already put the private and the public... Restore the original, default DNS settings : let the Resolver do the work. "Availabe Packages" will populate.

Thank you that worked.... got past this error anyways, and i dont expect any more problems as this exact machine has ran pfsense before, but not in my ownership. case closed.

What do you want to know dude, if your isp is locked down to prevent inbound traffic, there is nothing pfsense can do to fix that.. Run a vpn that supports inbound traffic if that is what your after.

If it's a moderate size disk then RAM isn't a huge concern. I don't have any specific disk size vs RAM consumption recommendations, but I've gotten away with ZFS even on some really low-RAM VMs when testing.

@kevin9033 said in Migrate Sophos XG/UTM to PFSense: Sophos UTM/XG I was also thinking to install pfSense on some old Watchdog hardware installation may be possible on some of them with a little hack but thought those hardware are too old to run the latest pfSense OS so decided to go with netgate certified / approved devices. I found a link regarding Sophos https://forum.netgate.com/topic/133355/installing-pfsense-on-sophos-xg-105-rev-2

@Derelict okay? The bug is restarting interface assignment after doing so

Actually I've learnt a lot form the guidance given here. But it has to be infuriating to deal with the problems of numpties who don't really understand how stuff works but non the less want to set up something which is beyond them. Cables are bought and changed about to check for errors tho not got a connection checker here. What I meant to be saying in my final note on the problem was that a good deal of time was wasted because I hadn't realised Id got a problem with dhcp on the client and restarting linux didnt flush the network if that’s even the correct phrase. sudo ip route flush table main – after which it got better -or maybe I just imagined it ;) Anyways, its doing what it should now - Thanks

Appears to be UPnP AV. So all multicast discovery shenanigans.

You can import the old configuration. When you restore it will prompt you to remap the interfaces, but that should be all it needs. You might want to remove any <package> ... </package> sections, restore that modified config, and reinstall packages after you restore. That would make it smoother.

So /32 is not correct.. Should be using the mask of your netblock [image: 1556532580703-vipmask.png] Then also run through the troubleshooting guide. https://docs.netgate.com/pfsense/en/latest/nat/port-forward-troubleshooting.html First thing I would do is actually validate traffic is hitting your wan with dest to that IP, with a packet capture. edit: Oh you got it working - you deleted your last post saying you were still having issues. Glad to hear.

Yeah so this got solved with a power cycle of the modem. That I SWEAR i'd done 1000 times in myriad different orders of operation. I did refresh and renew the dhcp under Interfaces->WAN before the the refresh/renew had seemingly done nothing (still had 0.0.0.0). So I'm up for now at least...

@JeGr said in New installation strange behavior - I can access web interface. however, I can't ping to the device: no ping" to "ping" that's your case: Thanks and it does explain everything .... You are a star.

Hi, The numbers I got were posted earlier. The changes I made to the loader/sysctl for the most part do not seem to have changed much. The speed increase happened once I turned off the option to insert a stronger ID. For reference here are the system tunables page (sysctl) and boot/loader.conf.local file. Most of which is now commented out and/or for the built in interface card and not the chelsio. :p #Improve Cache size hw.ix.rxd="4096" hw.ix.txd="4096" #Change processing limit -1 is unlimited hw.ix.tx_process_limit="-1" hw.ix.rx_process_limit="-1" #Set the queues to cores #hw.ix.num_queues="16" #force flow control settings 0 to disable. hw.ix.flow_control="0" dev.ix.0.fc=0 dev.ix.1.fc=0 dev.ix.2.fc=0 dev.ix.3.fc=0 #disable cache connection detail #net.inet.tcp.hostcache.cachelimit="0" #ensure HT is disabled machdep.hyperthreading_allowed="0" #enable optimized version of soreceive #net.inet.tcp.soreceive_stream="1" #unlimited isr threads to maximize all core use #net.isr.maxthreads="-1" #net.isr.bindthreads="1" #use msix instead #hw.ix.enable_msix="1" #use aim to improve efficency on network stack #hw.ix.enable_aim="1" #hw.ix.max_interrupt_rate="16000" #increase max interrupts #hw.intr_storm_threshold="9000" [image: 1556238943170-sysctl-resized.png] Hope that helps. Cheers!

Yes it does. It is listed as "default". That's what 0.0.0.0/0 is all about anyway! [image: 1556193675221-aaa657c2-01ae-4e73-a32c-a5dfaf21a1a8-image.png]