Problems Installing or Upgrading pfSense Software

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

N

*NEWB* After Install it won't boot !

• • nathan715

48

0
Votes

48
Posts

14.7k
Views

N

I don't think I'll need to all I am using this for is taking a wired connection and making it wireless, the only thing that is on that network is my iPod, the rest of the house is separate networks and my dad's got it all figured out, so security isn't a big deal for me, well not for the specific project,

Thanks
Nathan

I'm glad I didn't kick the piece of **** lol
J

Setting up an entirely Wireless LAN? Only one Ethernet port.

• • Jamesey162

3

0
Votes

3
Posts

1.3k
Views

J

That's sounds like a plan! I'll try it out later to see if I can get it working.

Thanks for the reply :)
D

Workstations on Lan can't reach internet

• • djp1973

6

0
Votes

6
Posts

1.9k
Views

D

Yup,
Bang on the money. I had incorrectly entered the firewall rules for the network (Newbie error!). Once I corrected them, woosh it all worked.

Thanks Guys!
V

Changed self-signed certificate to one from in-house CA and now no meus!

• • Vk2hmc

2

0
Votes

2
Posts

1.1k
Views

V

FixEd

get new certificate with SAN FQDN and all is good again..
?

Swap size

• • azdps

3

0
Votes

3
Posts

3.5k
Views

?

I'll try 1gb and see how things turn out. I wanted to use snort, maybe squid and dansguardian as well. Thanks for the info.
T

I'm new. I can't log in through the WAN nic. LAN nic works ok.

• • tokerau

8

0
Votes

8
Posts

1.9k
Views

P

Yes, the screenshots are 2.1 - as you say, there are a few new fields there. The IPv4 stuff is all the same principle.
(Hmmm - I have forgotten exactly what 2.0.n screens look like!)
M

Full install on a flash drive

• • misterpat

6

0
Votes

6
Posts

2.1k
Views

M

Thanks Steve!
H

Upgrade to 2.0.1, missing implicit rules

• • hhubris

3

0
Votes

3
Posts

1.6k
Views

H

Is there a best practice suggestion for an ICMP rule?
D

ISO Image

• • designwebs

4

0
Votes

4
Posts

1.9k
Views

G

Yes you download it as .gz file.
You have to decompress it with the decompress-flavour of your liking.
M

SSH works, browser doesn't

• • MMacD

1

0
Votes

1
Posts

875
Views

No one has replied
M

PPPoE can't be set from config wizard?

• • MMacD

4

0
Votes

4
Posts

1.4k
Views

M

sigh it's a human-factors problem, not a coding one. The fields are gated by the "type" list at the top, but the non-selected ones are r/o rather than disabled as they should be. So if someone doesn't start with that top field, the page will look broken.

I recommended that they scrap that field and use javascript to disable the irrelevant fields after one of them is selected to type into. E.g., I would (and in fact tried to) start typing my account name into that PPPoE field, so javascript should immediately disable all competing choice unless and until I empty the field(s) I chose. Add some text garnish explaining what's going on, for those who aren't unix/network nerds, and Bjorn Stronginthearm's your uncle.

(Thanks for your response, btw! Just to dot the Ts and cross the Is, v2.0.1, i386, and yes, System -> Setup wiz.

It's a little disgusting, even though helpful, to know that the fBSD under pfSense isn't the same as the fBSD runnning on my toy webserver or my muscle machine)
M

Help Installing pfSense 2.0.1 on a Sata 3 SSD

• • megatronprime

12

0
Votes

12
Posts

6.3k
Views

M

pfSense could not detect my SSD when I typed '?' at the mountroot>. I followed wallaybob's advice and put the latest snapshot on my flash drive. It detected my SSD automagically, and everything looks good so far. Thanks for all of the help.
V

PfSense newbie configuration problem

• • vdecristofaro

43

0
Votes

43
Posts

14.7k
Views

V

@podilarius:

Yes. the same proxy you used with pfsense and your workstation.

Ok! Finally I have got my target ;D ;D

I have installed and enabled Squid to be a transparent proxy against internal network.
I have also enabled Squid to use an upstream proxy (the one of the network I am in).

It seems that everything is working. Thank you so much for helping
E

NanoBSD and SSD

• • esnakk

3

0
Votes

3
Posts

2.0k
Views

M

A modern SSD should wear level across the drive. It wouldn't make sense for the partition size to matter as a partition is a logical division in the formatting of data on the drive, that layer of hardware layer doesn't "understand" such things. It should simply see data coming in, mapped to a particular logical sector, and map it to physical memory locations as it sees fit. The logical sector that the OS sees looks just like a physical sector, the ambiguity comes in the hardware re-mapping, which neither the OS nor the BIOS sees, nothing outside the drive (asside from some diagnostics tools that may be able to access such data) should be able to notice the difference.

That being the case, a 4GB partition should still wear across the full accessible data range in a modern drive that does wear leveling.

The main case against that would be if the drive previously had been full of data, simply re-partitioned, and the newly free space not wiped. But, I think the same thing would happen if the partition was the full size and no trim / garbage collection had been done on that partitioned, but free (to the OS) space. Remember, the hardware layer itself (SSD) needs to be "told" in some way that the space the OS has deemed as free is actually free. I would think that your best case scenario would be to use whatever tools your SSD manufacturer provides to run a full wipe on the drive before you install NanoBSD.
K

Can't write to config.xml | Using ESXi

• • Kingkoopa

8

0
Votes

8
Posts

3.2k
Views

K

I did do a fsdk, but I didn't put any of those extra commands behind it. The fsdk came and said the file system was ok, but i still have the problem with not being able to change any settings.

If someone wants to, we can set up a time for you to teamview into my computer so you can check out the settings. PM me if you want to. I'm really stumped.
S

Caching proxy/squid with pfsense ?

• • superbaim

2

0
Votes

2
Posts

1.1k
Views

S

Yes. Since 2.0 you can install pfSense with one interface. When you do so the interface is automatically named WAN which can be confusing.

Steve
P

PFsense & HP T5710 Thin Client

• • Phenominal

2

0
Votes

2
Posts

1.7k
Views

P

Well guy's, i fixed it.

after trying several usb sticks from various brands and sizes, i took my 2.5" sata usb drive, and made a seperate partition on it.
wrote the stick image on it, and it's installing as we speek
B

Does the nanobsd IMG supports XEN Paravirt ?

• • Bahaika

1

0
Votes

1
Posts

1.0k
Views

No one has replied
N

Static Configuration won't work - Ideas where to look?

• • natelabo

36

0
Votes

36
Posts

9.9k
Views

N

Could someone take a look at these logs from the packet capture (I picked an interface and then on a local device attempted to go to google.com):
WAN Interface 16:57:41.101959 IP 75.144.79.144.13192 > 74.125.225.78.443: tcp 0 16:57:41.108078 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 23150, length 44 16:57:41.125294 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:41.144520 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 23150, length 44 16:57:41.455705 IP 10.0.0.0 > 224.0.0.1: igmp 16:57:41.580017 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:41.664690 IP 75.144.79.144.3756 > 74.125.225.78.443: tcp 0 16:57:41.685577 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:42.039584 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:42.118017 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 23406, length 44 16:57:42.149849 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 23406, length 44 16:57:42.180303 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:42.638573 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:43.128024 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 23662, length 44 16:57:43.161202 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 23662, length 44 16:57:43.380435 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:43.838306 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:43.995745 IP 75.144.79.144.39147 > 74.125.225.70.443: tcp 0 16:57:44.017177 IP 74.125.225.70.443 > 75.144.79.144.39147: tcp 0 16:57:44.098672 IP 75.144.79.144.13192 > 74.125.225.78.443: tcp 0 16:57:44.120593 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:44.137956 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 23918, length 44 16:57:44.170392 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 23918, length 44 16:57:44.383626 IP 74.125.225.70.443 > 75.144.79.144.39147: tcp 0 16:57:44.664647 IP 75.144.79.144.3756 > 74.125.225.78.443: tcp 0 16:57:44.685868 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:44.699328 IP 75.144.79.144.36950 > 74.125.225.68.443: tcp 0 16:57:44.722696 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:44.728673 IP 75.144.79.144.4217 > 74.125.225.70.443: tcp 0 16:57:44.749215 IP 74.125.225.70.443 > 75.144.79.144.4217: tcp 0 16:57:44.966891 IP 75.144.79.144.32177 > 74.125.225.68.443: tcp 0 16:57:44.988638 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:45.147931 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 24174, length 44 16:57:45.180448 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 24174, length 44 16:57:45.182179 IP 74.125.225.70.443 > 75.144.79.144.4217: tcp 0 16:57:45.184711 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:45.410414 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:45.781167 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:45.783714 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:46.010282 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:46.157899 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 24430, length 44 16:57:46.190517 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 24430, length 44 16:57:46.237759 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:46.691304 IP 75.144.79.144.38380 > 173.194.68.125.443: tcp 0 16:57:46.734180 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:46.941749 IP 75.144.79.144.33876 > 173.194.68.125.443: tcp 0 16:57:46.982674 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:46.983864 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:47.128039 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:47.167852 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 24686, length 44 16:57:47.202763 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 24686, length 44 16:57:47.210433 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:47.282514 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:47.700973 IP 75.144.79.144.36950 > 74.125.225.68.443: tcp 0 16:57:47.723263 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:47.729600 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:47.882395 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:47.961005 IP 75.144.79.144.32177 > 74.125.225.68.443: tcp 0 16:57:47.982889 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:48.116661 IP 75.144.79.144.26289 > 75.75.76.76.53: UDP, length 28 16:57:48.116694 IP 75.144.79.144.26289 > 8.8.8.8.53: UDP, length 28 16:57:48.116721 IP 75.144.79.144.26289 > 8.8.4.4.53: UDP, length 28 16:57:48.116746 IP 75.144.79.144.26289 > 75.75.75.75.53: UDP, length 28 16:57:48.132922 IP 75.75.76.76.53 > 75.144.79.144.26289: UDP, length 204 16:57:48.136766 IP 75.144.79.144.17085 > 74.125.225.130.80: tcp 0 16:57:48.153083 IP 8.8.4.4.53 > 75.144.79.144.26289: UDP, length 204 16:57:48.153130 IP 8.8.8.8.53 > 75.144.79.144.26289: UDP, length 204 16:57:48.164292 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:48.167216 IP 75.75.75.75.53 > 75.144.79.144.26289: UDP, length 204 16:57:48.177827 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 24942, length 44 16:57:48.209769 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 24942, length 44 16:57:48.456216 IP 10.0.0.0 > 224.0.0.1: igmp 16:57:48.549640 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:48.930197 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:49.084248 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:49.149509 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:49.187781 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 25198, length 44 16:57:49.221121 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 25198, length 44 16:57:49.385864 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:49.611598 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:49.695145 IP 75.144.79.144.38380 > 173.194.68.125.443: tcp 0 16:57:49.741328 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:49.945167 IP 75.144.79.144.33876 > 173.194.68.125.443: tcp 0 16:57:49.987475 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:50.108172 IP 75.144.79.144.13192 > 74.125.225.78.443: tcp 0 16:57:50.135905 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:50.197745 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 25454, length 44 16:57:50.229454 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 25454, length 44 16:57:50.351753 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:50.583027 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:50.668264 IP 75.144.79.144.3756 > 74.125.225.78.443: tcp 0 16:57:50.691144 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:51.040863 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:51.139318 IP 75.144.79.144.17085 > 74.125.225.130.80: tcp 0 16:57:51.160980 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:51.207707 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 25710, length 44 16:57:51.242954 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 25710, length 44 16:57:51.332369 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:51.484095 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:52.217676 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 25966, length 44 ------------------------------------------------------------------ LAN Interface 16:58:53.524036 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.664922 IP 192.168.0.200.64336 > 74.125.225.134.443: tcp 0 16:58:53.723976 IP 192.168.0.200.64343 > 192.168.0.99.80: tcp 0 16:58:53.724061 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724063 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724594 IP 192.168.0.200.64343 > 192.168.0.99.80: tcp 0 16:58:53.724628 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724630 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724632 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724634 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.725108 IP 192.168.0.200.64343 > 192.168.0.99.80: tcp 0 16:58:53.725146 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.725148 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.725150 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.725152 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 495 16:58:53.725640 IP 192.168.0.200.64343 > 192.168.0.99.80: tcp 0 16:58:53.733891 IP 192.168.0.200.64337 > 74.125.142.125.443: tcp 0 16:58:53.983895 IP 192.168.0.200.64338 > 74.125.142.125.443: tcp 0 16:58:54.229110 IP 192.168.0.200.50855 > 192.168.0.99.53: UDP, length 33 16:58:54.246739 IP 192.168.0.99.53 > 192.168.0.200.50855: UDP, length 49 16:58:54.455911 IP 10.0.0.0 > 224.0.0.1: igmp 16:58:54.907004 IP 192.168.0.200.64339 > 74.125.225.32.443: tcp 0 16:58:55.137092 IP 192.168.0.200.64340 > 74.125.225.32.443: tcp 0 16:58:56.767269 IP 192.168.0.200.64341 > 74.125.225.131.443: tcp 0 16:58:56.987238 IP 192.168.0.200.64342 > 74.125.225.131.443: tcp 0 16:58:57.843056 IP 192.168.0.200.64350 > 74.125.225.130.80: tcp 0 16:58:58.612801 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:58:59.014081 IP 192.168.0.200.64351 > 74.125.225.134.443: tcp 0 16:58:59.363421 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:58:59.773368 IP 192.168.0.200.64352 > 74.125.225.134.443: tcp 0 16:59:00.113507 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:59:00.843563 IP 192.168.0.200.64350 > 74.125.225.130.80: tcp 0 16:59:00.910479 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:59:01.455647 IP 10.0.0.0 > 224.0.0.1: igmp 16:59:01.660603 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:59:02.013532 IP 192.168.0.200.64351 > 74.125.225.134.443: tcp 0 16:59:02.410700 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:59:02.773546 IP 192.168.0.200.64352 > 74.125.225.134.443: tcp 0 16:59:03.163869 IP 192.168.0.200.52811 > 192.168.0.99.53: UDP, length 37 16:59:03.182386 IP 192.168.0.99.53 > 192.168.0.200.52811: UDP, length 106 16:59:03.187650 IP 192.168.0.200.64354 > 207.46.206.137.80: tcp 0
I don't care about hiding the external IP anymore…. I'm not going to be using it for long.
K

1.2.3 to 2.0.1 problem on upgrading to new hardware

• • kosh

5

0
Votes

5
Posts

2.3k
Views

C

That's what happens when the firewalls can't talk to each other on the WAN, or at least can't pass multicast between them on the WAN though usually it's that they can't talk at all.

356 / 474