[pfSense Support] Wan-side problem...
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 and it seems to work...but I don't know if there is a real connection... next time it hangs, what do you want me to spot in the logs??? regards... ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Wan-side problem...
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 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 and it seems to > work...but I don't know if there is a real > connection... > > next time it hangs, what do you want me to spot in the > logs??? > > regards... > > > > > > > ___ > Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger > Téléchargez cette version sur http://fr.messenger.yahoo.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Wan-side problem...
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: Thursday, September 15, 2005 10:00 AM Subject: Re: [pfSense Support] Wan-side problem... 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 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 and it seems to work...but I don't know if there is a real connection... next time it hangs, what do you want me to spot in the logs??? regards... ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Wan-side problem...
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 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 and it seems to > > work...but I don't know if there is a real > > connection... > > > > next time it hangs, what do you want me to spot in > the > > logs??? > > > > regards... > > > > > > > > > > > > > > > ___ > > Appel audio GRATUIT partout dans le monde avec le > nouveau Yahoo! Messenger > > Téléchargez cette version sur > http://fr.messenger.yahoo.com > > > > > - > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Wan-side problem...
"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 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: Thursday, September 15, 2005 10:00 AM
> Subject: Re: [pfSense Support] Wan-side problem...
>
>
> 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 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 and it seems to
> > work...but I don't know if there is a real
> > connection...
> >
> > next time it hangs, what do you want me to spot in the
> > logs???
> >
> > regards...
> >
> >
> >
> >
> >
> >
> > ___
> > Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
> > Téléchargez cette version sur http://fr.messenger.yahoo.com
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] successful new installation notes
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 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 endpoint for rules. This should either be fixed or well documented. The only other issue of significance I had was setting up IPsec tunnel to a remote office. IPsec config of tunnels with shared key stores the shared key using IP address as the identifier even if "ID" is not set to IP in IPsec config. Thus, no shared key is found for the tunnel to complete negotiation since it is looking for a key based on the wrong ID type (in my case domain name). It only works if you use IP address as the "ID" for the connection. Took me almost 30 minutes to figure this out, otherwise it would have fired up on my first try! Here are some other minor issues I noticed: 1. export of config leaves PPTP passwords as cleartext. they should be hashed or something. 2. the status menu item for "services" doesn't show DHCP and SNMP services. 3. in Safari web browser, the status menu last two items' labels are cut-off. You see Services System System Traffic rather than the complete text. In Firefox it looks just fine. 4. when logged into the console, and you run the option 10 Traffic Logs program, there is no way to break out of it. Ctrl-C is ignored, Ctrl-\ is ignored. My only recourse was reboot. It works fine when connected remotely via ssh. 5. I'd like to see a few more pre-defined ports in the rules configuration page: ident/auth at 113/tcp imaps at 993/tcp NTP at 123/tcp+udp Overall, I'm extremely impressed with the system. It is running installed to disk on a Dell PE420 with a CERC raid card under the amr0 driver, and hyperthreaded dual CPU. Way cool. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] successful new installation notes
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 endpoint for rules. This should either be fixed or well documented. That's correct. That's just how it works, and working around it would be a major pain. It will be documented. 1. export of config leaves PPTP passwords as cleartext. they should be hashed or something. We don't hash things that must be available in clear text at some point, to avoid the perception that the passwords are secure when they wouldn't be. Same reason Manuel does it that way in m0n0wall, and he explains it well: http://m0n0.ch/wall/docbook/faq-plaintextpass.html But, now that I look back again at your comment, if you're talking about the local PPTP user database, we probably could leave those as hashes in the config as they should never be required in plain text (though I'm not intimately familiar with how that works so I might be wrong). I'll have to leave the rest for Scott or somebody to comment on. -cmb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] successful new installation notes
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 more feature enhancement: on the IPsec status page, the "create" and "last" times of the current connections would be helpful. Right now I have to run the command setkey -D and look them up the hard way (I have a remote network flapping and see many repeat connections). Vivek Khera, Ph.D. +1-301-869-4449 x806 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Upgrade to 80.4 causes problems finding kernel
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 BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' lsdev: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and everything looks fine in the filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. So I don't know what happened. I am a Linux guy, so I don't enough to figure out what FreeBSD decided to magically not find my drive anymore. The Hardware must be okay, or else I wouldn't have been able to mount it from the Live CD. Any ideas? Many thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
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/15/05, Xtian <[EMAIL PROTECTED]> wrote: > > 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 BIOS device 0x not found by probes, defaulting to disk0: > > can't load 'kernel' > > lsdev: > disk devices: > disk0: BIOS drive A: > disk1: BIOS drive C: > > Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and > everything looks fine in the > filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. > > So I don't know what happened. > > I am a Linux guy, so I don't enough to figure out what FreeBSD decided to > magically not find my drive > anymore. The Hardware must be okay, or else I wouldn't have been able to > mount it from the Live CD. > > Any ideas? > > Many thanks, > > Christian > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
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 make it boot again. Oliver -Original Message- From: Xtian [mailto:[EMAIL PROTECTED] Sent: September 15, 2005 4:54 PM Cc: support@pfsense.com Subject: [pfSense Support] Upgrade to 80.4 causes problems finding kernel 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 BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' lsdev: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and everything looks fine in the filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. So I don't know what happened. I am a Linux guy, so I don't enough to figure out what FreeBSD decided to magically not find my drive anymore. The Hardware must be okay, or else I wouldn't have been able to mount it from the Live CD. Any ideas? Many thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
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 the old one and rebooting took care of the boot up issue. Thanks! -C On Thu, 15 Sep 2005, Oliver Stark wrote: 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 make it boot again. Oliver -Original Message- From: Xtian [mailto:[EMAIL PROTECTED] Sent: September 15, 2005 4:54 PM Cc: support@pfsense.com Subject: [pfSense Support] Upgrade to 80.4 causes problems finding kernel 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 BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' lsdev: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and everything looks fine in the filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. So I don't know what happened. I am a Linux guy, so I don't enough to figure out what FreeBSD decided to magically not find my drive anymore. The Hardware must be okay, or else I wouldn't have been able to mount it from the Live CD. Any ideas? Many thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- devo dot com - "Where the future is only a memory." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Startup hangs at DynDNS Update
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 with the config that comes from the previous (70.8) version. I have seen numerous posts regarding DynDns issues, but did not see this one mentioned. Sorry if its a repeat. Thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Understand log entry
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 dc2 interface (my DMZ interface) to 209.86.93.236 on port 25 was blocked by PfSense. Is this all correct? If so, I am not sure why because I have a rule setup to specifically allow this. In fact, if the rule wasn't working I would have serious phone calls at this point because customers wouldn't be getting their mail. I don't see a ton of these but I do see enough to make me wonder why things are being rejected on port 25 out from my DMZ on occassion. Thanks in advance for any help. Todd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Understand log entry
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 the packet involved. --BillOn 9/15/05, Mojo Jojo <[EMAIL PROTECTED]> wrote: 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 16954I have replaced my IP with "MyIPwasHere"... It looks to me like a packet going out from my server (MyIPwasHere) on thedc2 interface (my DMZ interface) to 209.86.93.236 on port 25 was blocked byPfSense.Is this all correct? If so, I am not sure why because I have a rule setup to specifically allow this.In fact, if the rule wasn't working I would have serious phone calls at thispoint because customers wouldn't be getting their mail.I don't see a ton of these but I do see enough to make me wonder why things are being rejected on port 25 out from my DMZ on occassion.Thanks in advance for any help.Todd-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Understand log entry
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 To: support@pfsense.com Sent: Thursday, September 15, 2005 9:30 PM Subject: Re: [pfSense Support] Understand log entry 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 the packet involved.--Bill On 9/15/05, Mojo Jojo <[EMAIL PROTECTED]> wrote: 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 16954I have replaced my IP with "MyIPwasHere"... It looks to me like a packet going out from my server (MyIPwasHere) on thedc2 interface (my DMZ interface) to 209.86.93.236 on port 25 was blocked byPfSense.Is this all correct? If so, I am not sure why because I have a rule setup to specifically allow this.In fact, if the rule wasn't working I would have serious phone calls at thispoint because customers wouldn't be getting their mail.I don't see a ton of these but I do see enough to make me wonder why things are being rejected on port 25 out from my DMZ on occassion.Thanks in advance for any help.Todd-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Understand log entry
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 weight in them if it's just onesy-twosy type stuff. --Bill
Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
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 all manually. I tried the configuration.xml I downloaded 1 day before, it could not work. After all work properly, I upgraded it to 83.2 and now the /boot/loader.rc is in size 784 i just tried: # grep -v '^$' loader.rc > loader.rc.new and have loader.rc.new is in size 346 So I think it is dangerous to reboot the gateway right now, unless the problem is well known to be solved. Xtian wrote: 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 the old one and rebooting took care of the boot up issue. Thanks! -C On Thu, 15 Sep 2005, Oliver Stark wrote: 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 make it boot again. Oliver -Original Message- From: Xtian [mailto:[EMAIL PROTECTED] Sent: September 15, 2005 4:54 PM Cc: support@pfsense.com Subject: [pfSense Support] Upgrade to 80.4 causes problems finding kernel 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 BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' lsdev: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and everything looks fine in the filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. So I don't know what happened. I am a Linux guy, so I don't enough to figure out what FreeBSD decided to magically not find my drive anymore. The Hardware must be okay, or else I wouldn't have been able to mount it from the Live CD. Any ideas? Many thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
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!! =) On Fri, 16 Sep 2005, Paulus Edwin Prasetya wrote: 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 all manually. I tried the configuration.xml I downloaded 1 day before, it could not work. After all work properly, I upgraded it to 83.2 and now the /boot/loader.rc is in size 784 i just tried: # grep -v '^$' loader.rc > loader.rc.new and have loader.rc.new is in size 346 So I think it is dangerous to reboot the gateway right now, unless the problem is well known to be solved. Xtian wrote: 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 the old one and rebooting took care of the boot up issue. Thanks! -C On Thu, 15 Sep 2005, Oliver Stark wrote: 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 make it boot again. Oliver -Original Message- From: Xtian [mailto:[EMAIL PROTECTED] Sent: September 15, 2005 4:54 PM Cc: support@pfsense.com Subject: [pfSense Support] Upgrade to 80.4 causes problems finding kernel 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 BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' lsdev: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and everything looks fine in the filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. So I don't know what happened. I am a Linux guy, so I don't enough to figure out what FreeBSD decided to magically not find my drive anymore. The Hardware must be okay, or else I wouldn't have been able to mount it from the Live CD. Any ideas? Many thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- devo dot com - "Where the future is only a memory." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
