Re: [pfSense Support] Test-Upgrade from 1.2.3 to 2.0RC3 Alix
On 26.06.2011 13:26 Klaus Lichtenwalder wrote: > Can you show headers? I definitely sent it only once No problem here. I received it only once. Regards, Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] COM-port Watchguard Firebox X500 with 2.0-RC1
On 08.05.2011 02:48 Dimitri Rodis wrote: > Even if you get the console to work, you are still going to get > watchdog timeouts on the NICs of this unit, which is something that I > have been working with the driver maintainer on for quite some time > in order to try and fix. Do you know if this is a special Firebox problem or a more general one? AFAIR FreeBSD supports the Realtek 8139C+ since version 5.2 or so. Should this driver still have problems with this chip or is this a problem only on this special machine? Thanks Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] COM-port Watchguard Firebox X500 with 2.0-RC1
On 08.05.2011 00:30 Jim Cheetham wrote: >>> Bootup complete >> >> ... and now we should see the login command shell. > > And what happens if you press return a couple of times at this point? I already tried this but nothing happens. Regards, Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] COM-port Watchguard Firebox X500 with 2.0-RC1
On 08.05.2011 00:12 Jim Cheetham wrote: > So your problem is a more serious one, the console login shell isn't > running. > > I'd recommend booting your pfSense image in a virtual machine to see > what happens there. If the same thing occurs, it will be easier to hunt > for log file entries than from your real hardware I guess. OK, Thanks for the informations. I'll try to find out why the login shell isn't running. Kind regards, Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] COM-port Watchguard Firebox X500 with 2.0-RC1
Jim, thank you very much for your reply. On Fri, 06 May 2011 at 08:43:33AM +1200, Jim Cheetham wrote: > However that doesn't sound quite like the original report, especially as > his Firebox worked on 1.2.3. Markus, what output do you get? See below. In between and according to some docus I found I also tried to make changes to /boot/loader.conf - added: boot_multicons="YES" boot_serial="YES" comconsole_speed="9600" console="comconsole,vidconsole" /boot.config - replaced -h with: -S9600 /etc/ttys - added: ttyu0 "/usr/libexec/getty std.9600" cons25 on secure But these changes have no effect. As I wrote: Web access works, SSH also. But I want to have a chance to reach the firewall on a serial port, if network access is not available. Regards Markus The boot log: --- snip --- 1 pfSense 2 pfSense F6 PXE Boot: 1 /boot/kernel/kernel text=0x89a214 data=0x3c9c54+0x9b6a0 syms=[0x4+0x93b80+0x4+0xca87e] / Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RELEASE-p3 #0: Thu May 5 18:57:32 EDT 2011 sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(TM) CPU1200MHz (1202.73-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b4 Family = 6 Model = b Stepping = 4 Features=0x383f9ff real memory = 268435456 (256 MB) avail memory = 243433472 (232 MB) wlan: mac acl policy registered ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0708960, 0) error 1 ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc0708a00, 0) error 1 wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/. wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (wpi_fw, 0xc087b6b0, 0) error 1 ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc0708aa0, 0) error 1 ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309) ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. cryptosoft0: on motherboard padlock0: No ACE support. pcib0: pcibus 0 on motherboard pir0: on motherboard $PIR: Using invalid BIOS IRQ 9 from 2.13.INTA for link 0x63 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 30.0 on pci0 pci2: on pcib2 safe0 mem 0xe7bfe000-0xe7bf irq 3 at device 6.0 on pci2 safe0: [ITHREAD] safe0: SafeNet SafeXcel-1141 rng des/3des aes md5 sha1 null re0: port 0xd500-0xd5ff mem 0xefefa000-0xefefa1ff irq 10 at device 9.0 on pci2 re0: Chip rev. 0x7480 re0: MAC rev. 0x miibus0: on re0 rlphy0: PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: [FILTER] re1: port 0xd600-0xd6ff mem 0xefefb000-0xefefb1ff irq 5 at device 10.0 on pci2 re1: Chip rev. 0x7480 re1: MAC rev. 0x miibus1: on re1 rlphy1: PHY 0 on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re1: [FILTER] re2: port 0xd900-0xd9ff mem 0xefefc000-0xefefc1ff irq 11 at device 11.0 on pci2 re2: Chip rev. 0x7480 re2: MAC rev. 0x miibus2: on re2 rlphy2: PHY 0 on miibus2 rlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re2: [FILTER] re3: port 0xda00-0xdaff mem 0xefefd000-0xefefd1ff irq 12 at device 12.0 on pci2 re3: Chip rev. 0x7480 re3: MAC rev. 0x miibus3: on re3 rlphy3: PHY 0 on miibus3 rlphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re3: [FILTER] re4: port 0xdd00-0xddff mem 0xefefe000-0xefefe1ff irq 9 at device 13.0 on pci2 re4: Chip rev. 0x7480 re4: MAC rev. 0x miibus4: on re4 rlphy4: PHY 0 on miibus4 rlphy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re4: [FILTER] re5: port 0xde00-0xdeff mem 0xefeff000-0xefeff1ff irq 6 at device 14.0 on pci2 re5: Chip rev. 0x7480 re5: MAC rev. 0x miibus5: on re5 rlphy5: PHY 0 on miibus5 rlphy5: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re5: [FILTER] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHRE
Re: [pfSense Support] COM-port Watchguard Firebox X500 with 2.0-RC1
Hi Frank, On Thu, 05 May 2011 at 05:15:42PM +0200, Frank Heydlauf wrote: > My console speed changes during the boot from 9600 to 38400 > (alix.2d13 board). Maybe same problem in your case. thanks for the hint. Unfortunately it doesn't help. I already tried some usual speeds (among them 38400), but none of them worked. Regards, Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] COM-port Watchguard Firebox X500 with 2.0-RC1
Hi, I have some Firebox X500 running with pfSense 1.2.3 without any problem. No I tried 2.0-RC1 (nanobsd) on such a box. The systems boots and allows initial setup via console cable. But after reporting that the boot is complete, no more output is showing via serial console (the GUI via Web is accessible). I searched around but only found that some users have similar problems. In some cases it helped to change the speed and/or flow control of the terminal program (PuTTY in my case). But with my Firebox nothing works. I don't get any output on the com port. Does anybody had such a problem and an idea what else I could try? Thanks and kind regards, Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] List Posting Etiquette
Sorry for the wrong subject line in my first reply - sent without checking it first. Obviously my MUA tried to "repair" Yehuda's subject (parenthesis <-> square brackets). Hmm. Regards, Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] Re: Intel Gigabit - em0: Watchdog Timeout
On 08.03.2011 16:02 Yehuda Katz wrote: > >> Been there, done that. This is a drive problem. Here is how to fix > > Is it too much to request that when you post to this list about a > new issue, that you use a descriptive subject line? IMHO it isn't a new topic as the last posts talked about possible hardware/drive problems. And additionally Ozan posted a link to a web forum regarding the driver issue. And so he was on topic in any case. But here: > please keep in mind that many people on this list ask that you do not > "top-post") you're right. Regards, Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] embedded devices
On 13.02.2010 13:45 Dominik Schips wrote: > > So I think if you can handle the NanoBSD booting problem you should try > it before buying new hardware. > It is well documentet at > http://doc.pfsense.org/index.php/NanoBSD_on_WRAP Yes, I already read this. But as I wrote to Gary I think in the end ALIX is the better way. I'll let the few WRAP's as spare parts for my running m0n0wall devices and buy a new ALIX. I want to play with such a new board anyway. ;-) Thanks and regards, Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] embedded devices
On 13.02.2010 21:41 Gary Buckmaster wrote: > The limitations you're referring to are exclusive to the WRAP. OK. > PCEngines ended support for the device and so they haven't released a > firmware to support packetmode, which is necessary for the newer Yep, and that's my main concern: EOL. They will do nothing new with that old platform. > Your ALIX boards will work just fine with the newer versions of > pfSense. I have several of them and they work perfectly. Fine. Then I think I'll go with ALIX. Thank you very much! :) Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] embedded devices
Hi, I'm new here and would like to ask you something about the use of pfSense on embedded devices, especially on PC Engines WRAP/ALIX boards. In the wiki I read that there are a) some functional limitations and b) a special handling of booting necessary when using WRAP boards (which I used a long time together with m0n0wall and still have some unused ones). My question: will I have the same "problems" when using the newer ALIX boards or does this platform working without the WRAP limitations? If running on ALIX is possible without these issues then I rather would buy new boards than using the old WRAPs. Thanks and kind regards, Markus - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org