Hi,
I can only confirm that having stripped out the blank lines from loader.rc
took care of the boot issue, exactly as it was described by the previous
poster.
Cheers,
-C
PS. I forget to say this now and then, but as always: pfSense is a really
great piece of software! Yay for good stuff!! =)
Just reporting, this problem happen to me too.
At first I installed version 74 and upgrading to 80.x
After 6 days, i try to reboot it, and reported kernel not found.
Cause it is on production network, i do not have time to trace.
So i just re-installed the iso i had (v 74) and reconfuguring it
a
On 9/15/05, Mojo Jojo <[EMAIL PROTECTED]> wrote:
So, if I am reading you right, this is something I
should mostly ignore and not worry about too much?
Mostly, don't worry about it too much. I'd keep an eye on them as
it's possible it's part of a stealth scan. But I wouldn't put too
much w
So, if I am reading you right, this is something I
should mostly ignore and not worry about too much?
Oh and if I haven't said it yet.. Thanks to all
those involved in this project, it's a GREAT piece of software!
Regards,
Todd
- Original Message -
From:
Bill
Marquette
Looks like a packet from MyIPWasHere destined for 209.86.93.236 port 25
with the flags FIN/PSH/ACK set was blocked. This happens
frequently for traffic that is out of state - most commonly because
it's a delayed packet. There are other reasons, but it usually
has something to do with timing of th
Can anyone tell me what this log entry means?
Sep 15 20:36:16 pf: 594200 rule 65/0(match): block in on dc2:
MyIPwasHere.1284 > 209.86.93.236.25: FP 0:6(6) ack 1 win 16954
I have replaced my IP with "MyIPwasHere"...
It looks to me like a packet going out from my server (MyIPwasHere) on the
dc
Hi All,
now that I got the loader.rc issue fixed, my new 80.4 (upgrade from 70.8)
boots fine, and manages to get to the point where DynDns is being updated,
and hangs indefinately (well, I hit reset after 10 minutes.)
This is on a normal PC with 3Com NICs.
I'm assuming the upgrade has issues w
Howdy,
yeah, this seems to be it.
Booted from LiveCD, mounted drive:
# pwd
/mnt/moo/boot
# grep -v '^$' loader.rc > loader.rc.new
# ls -l loader.rc*
-r--r--r-- 1 root wheel 7504 Sep 10 17:41 loader.rc
-rw-r--r-- 1 root wheel 346 Sep 15 22:17 loader.rc.new
Copying the "new" file over th
Hi,
this is exactly the problem I expericed a few days ago. See my message
http://www.mail-archive.com/support@pfsense.com/msg01022.html
It could be that the /boot/loader.rc is corrupted. Please have a look at it
and, if appropriate, grep out the non-empty lines into a new loader.rc in
order to m
The only thing that I can think of is try mounting the slice then cd
to the /boot/kernel dir and gzip -9 kernel.gz
Then reboot and see if it finds the kernel.We are still not sure
why this happens but it doesn't seem to happen when you install from a
0.80+ iso and then upgrade.
Scott
On 9/1
Howdy pfSensers,
I've been running 0.70.8 just fine on a normal PC with 3Com NICs for months
now. I did the 0.80.4
Upgrade and rebooted the box and I get:
(bootloader loads fine, fives me the option of "F1 FreeBSD" and then duly
loads):
Can't work out which disk we are booting from.
Guessed
On Sep 15, 2005, at 12:20 PM, Chris Buechler wrote:
But, now that I look back again at your comment, if you're talking
about the local PPTP user database,
Yes, precisely. The WatchGuard FireBox exported them as hashed in its
configuration export, so I'm sure it can be done.
Also, one mor
Vivek Khera wrote:
The failure was due to how 1:1 NAT rules are processed. It seems
that the NATing is done before rules are matched, so one must specify
the private IP in the allow rules for 1:1 hosts. On other firewalls
I've dealt with, one always specified the public IP as the endpo
Yesterday I replaced a WatchGuard FireBox II firewall with pfSense.
Things went pretty smoothly, as I was able to recreate all the rules
"offline", then just switch IP addresses and it *almost* just worked.
The failure was due to how 1:1 NAT rules are processed. It seems
that the NATing i
"After a day or so, the wan side seems to fail...
ewerythig else works ok... then I'm forced to do a
reboot and it works for a day and fail... :-("
There are dhclient fixes in CVS that fix this.
Scott
On 9/15/05, Mojo Jojo <[EMAIL PROTECTED]> wrote:
> Scott,
>
> Is it the GUI failing in gener
okay... good!!!
--- Scott Ullrich <[EMAIL PROTECTED]> a écrit :
> This is fixed in CVS. Look for the new version
> soon.
>
> Scott
>
>
> On 9/15/05, Damien Dupertuis <[EMAIL PROTECTED]>
> wrote:
> > Hello,
> >
> > Here I am again with my dyndns/pppoe problems :-)
> >
> > For three day my
Scott,
Is it the GUI failing in general that's fixed?
Not sure if you were referring to a specific issue with DynDNS and the GUI
or if you mean the GUI problems in general.
Thanks,
Todd
- Original Message -
From: "Scott Ullrich" <[EMAIL PROTECTED]>
To:
Cc: <[EMAIL PROTECTED]>
Sent
This is fixed in CVS. Look for the new version soon.
Scott
On 9/15/05, Damien Dupertuis <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Here I am again with my dyndns/pppoe problems :-)
>
> For three day my 0.83 seems to have strange
> comportments...
>
> After a day or so, the wan side seems to fa
Hello,
Here I am again with my dyndns/pppoe problems :-)
For three day my 0.83 seems to have strange
comportments...
After a day or so, the wan side seems to fail...
ewerythig else works ok... then I'm forced to do a
reboot and it works for a day and fail... :-(
I disabled the dyndns service an
19 matches
Mail list logo
