Thanks man. Just got there. Gunna close this.

Cheers.

Thanks everyone for the responses. Everything works now. Something in an older config backup had the wrong username.

@jdeloach said in CD (ISO) installer for 2.4.5-p1 is too large to write to a cd:

I use a DVD to write the ISO to instead of a CD. Seems to work just fine. I use Windows, don't know if there are issues with using a Mac.

I think most folks on here use a USB memory stick but I prefer to stay with DVDs.

It worked. Thanks much

Thank you for your response, I actually got it working. it was actually 65 error. How I got fixed it by putting 1500 into the MTU and set WAN interface hard code to 1 gig auto. It is working great now and I did a quick backup! I am actually running static IP that was assign to me by Comcast.

Thanks

Hi @Derelict thanks for your help.

I will test your recommendation soon, I had a trouble with hosting, the system crashing and I will have to reset and reinstall

When I can set all good, I will test your recommendation, and I will to continue with this thread.

Thanks you very much

I would suggest contact support - when I asked for an image, I had link in like 1 minute.. There is zero reason to searching around the archives of the internet.. Just contact them - you do not need a support contract for such a question

And yeah its good idea to have current image, don't get me wrong... But the time for that is like when you first install it.. Just keep a copy ;) Reason I contact them is wanted factory version of lastest image for my sg4860. And then for the 3100. You use to be able to download them off the portal.. But now you can not get factory version without contacting them for new versions that come out.

Is this netgate appliance, or you just using the CE version?

everything worked well and then suddenly stopped working, I am puzzled over this question which is disturbing me more than anything else, i see that i not only me encountered such a challenge but i am unlike others not. I had to be able to disable it from Console too otherwise i would need to make reinstallation..

It looks like a larger amount of RAM is taken up for paging, couild this be ZFS file system?

SYSTEM MEMORY INFORMATION: mem_wire: 1198047232 ( 1142MB) [ 63%] Wired: disabled for paging out mem_active: + 76308480 ( 72MB) [ 4%] Active: recently referenced mem_inactive:+ 127647744 ( 121MB) [ 6%] Inactive: recently not referenced mem_cache: + 0 ( 0MB) [ 0%] Cached: almost avail. for allocation mem_free: + 497741824 ( 474MB) [ 26%] Free: fully available for allocation mem_gap_vm: + -258048 ( 0MB) [ 0%] Memory gap: UNKNOWN -------------- ------------ ----------- ------ mem_all: = 1899487232 ( 1811MB) [100%] Total real memory managed mem_gap_sys: + 50384896 ( 48MB) Memory gap: Kernel?! -------------- ------------ ----------- mem_phys: = 1949872128 ( 1859MB) Total real memory available mem_gap_hw: + 197611520 ( 188MB) Memory gap: Segment Mappings?! -------------- ------------ ----------- mem_hw: = 2147483648 ( 2048MB) Total real memory installed SYSTEM MEMORY SUMMARY: mem_used: 1522094080 ( 1451MB) [ 70%] Logically used memory mem_avail: + 625389568 ( 596MB) [ 29%] Logically available memory -------------- ------------ ----------- ------ mem_total: = 2147483648 ( 2048MB) [100%] Logically total memory

Hi all, apologies for the delay. Took me awhile to find another identical gigabit card to test with since cleaning the riser and card connector with isopropyl didn't work unfortunately. I also had to get a new modem from ISP since mine was way out of support.

It is now working fine with DHCP, appears to have been hardware gremlins in the gigabit card and the old modem being clunky with DHCP.

@videogamingtown said in First time install - Web interface not loading?:

Got it working after changing the subnet, thanks.

👍. Glad you got it sorted out.

My PC is in network 172.23.134.0 and i can ping normally in this network. I don't know if this are being a problemm

You can ping 8.8.8.8 from this network? If so then what is the problem?

I cannot help if you are only going to provide little pieces of information each time you think it may or may not help. Provide a full diagram of your network and all LANs, servers (squid?), smart switches. For example, in that diagram show LAN A is able to ping 8.8.8.8 but not access a website, LAN B cannot ping and so on. Are all 3 LANs different interfaces on pfsense? Show that in the diagram.

Awesome, thanks @viktor_g :)

I'm pretty new to BSD so was hoping there might be a workaround. Appreciate you taking the time to set it out 👍

@calical
So enabling the DNS forwarder resolved the issue for you as well?

@jrhatigan

hi

So you have modem... ok
what can be seen here:

6be12df5-263e-4c7d-9586-63a46c38ffb3-image.png

9afbcd1c-2ff2-45b5-ab0d-3561ae522762-image.png

++++edit:

-WAN is set to DHCP
so far (previous config / router), have you got the WAN IP address with DHCP?

-I've reset my modem, 10 min unplugged (not a combo router)
it doesn't "reset" - just a cold start 😉
10 min? it may be little, everyone here suggests more time, but it can be ISP dependent (DHCP lease)

-ping through pfsense diag from WAN to 8.8.8.8 is coming up as all packets lost
this is normal if you don't have a WAN connection the ping can't work outwards 8.8.8.8

OK, it seem this is not working after all and I am really struggling to understand why.

The issue exists under 2.4.5 and 2.4.5-1. But not 2.4.4-3.

the LAN interface is a bridge comprising vtnet0 and vtnet1.10. vtnet1.10 currently carries traffic, via managed switch, from an Asus access point (both Wireless and wired). pfSense is a Proxmox VM with vtnet0 & vtnet1 on Proxmox bridges. Latter bridge is set 'VLAN aware'. All devices on the bridge are in the same subnet 192.168.0.0/24. pfSense's IP on LAN (bridge) interface is 192.168.0.1.

Under pfSense 2.4.4-3, hosts connected to vtnet0 (eg proxy, pihole) see the real IP of incoming connections from clients on vtnet1.10. No problem.

Under pfSense 2.4.5+, this is also true. Other than for DNS traffic: Hosts on vtnet0 will always see the pfsense LAN IP 192.168.0.1 as the remote device. The DNS replies are still successfully received. The effect is something akin to NAT between the two component interfaces of the bridge, but only for DNS traffic.

I have dumped the nat & firewall rules from the command line and do not see anything that might target DNS specifically in this situation. As I say, it worked OK under pfSense 2.4.4-3. The pihole could discern the ip addresses of all the clients. Now it only sees those on vtnet0 and for those on vtnet1.10, it only ses the pfsense LAN IP.

Ok.

Your nearly there.
Contact the admin of your pfSense. Ask him why he installed bind - and why he didn't terminate the setup.
Explain him it's impossible to have tow web servers on the same server or two mail servers or two DNS caches/resolvers/forwarders that listen to the same ports : 953 in this case.
Let him make up his choice, an relocate port 953 of the two process : unbound or bind.
Port 953 is the 'control' port. Fr bind, it's the rndc program that use this port to control the bind while it's running.

Thank you guys, I will talk to netgate.