Re: Bad frame pointer crash again
There is no such thing as a bad frame pointer crash. That's a
diagnostic message from ddb that it can't find anything further up the
stack trace, which is correct, since the function sched_sync is on top
of the stack.
Now, what the kernel tells you is that your kernel didn't panic, so
I'm not entirely sure how you end up in ddb, since there is no panic
or fault in the traceback. What does the traceback on other cpus show?
machine ddbcpu 0 will switch to cpu0, make a trace on each of them.
//art
On Mon, May 23, 2011 at 5:42 PM, Jeff Ross jr...@openvistas.net wrote:
Hi all,
I have a server that I'm trying to get on-line that continues to drop into
ddb with a bad frame pointer crash. Right now it is only running an hourly
rsync from the server it is to replace on an hourly basis. The server will
run for no more than a week without this happening but sometimes it will
crash after only a day.
I filed a PR 6593 on Apr 26 on this. Right now it is running i386 -current
from Apr 27, upgraded after I filed the PR.
The message I get at the ddb prompt is virtually identical to the one
below.
If anyone has any ideas on how I can further debug this, I'd like to know.
I was hoping to use the upcoming 3 day weekend to make the final switch to
this new server but I can't see how that will happen if I can't keep it
running.
Trace, ps and dmesg below.
Thanks,
Jeff Ross
jross@mail:/home/jross $ sudo cu -l /dev/cua00
Password:
Connected
ddb{2} show panic
the kernel did not panic
ddb{2} trace
handle_workitem_freeblocks(d9d2ee78,e2ac1860,e0352f2c,d03e1c95) at
handle_worki
tem_freeblocks+0x2b
process_worklist_item(0,0,e0352f5c,d03e1eff,e0352f44) at
process_worklist_item+
0x171
softdep_process_worklist(0,28,d08c4bbb,0,d03d2ec3) at
softdep_process_worklist+
0x13f
sched_sync(daea43b8) at sched_sync+0xe5
Bad frame pointer: 0xd0ba9e88
The Airport Show is just a week away
The Airport Show 2011 is just a week away! == From May 31 - June 2, 2011 at the Airport Expo in Dubai , the Airport Show will provide a platform for airport suppliers and buyers to network and leverage the opportunities the region offers. Over 170 industry leading companies from over 30 countries are exhibiting. The event is dedicated to airport development and management and offers a holistic range of services and products addressing the construction, operations, technology, and the service needs of airports. Visitors of the show can interact with an elite group of decision-makers from the corporate and public sector in the region through networking events such as Airport Leaders Summit, Innovation and Project seminars and the successful Hosted Buyer program. To learn more, visit www.theairportshow.com ONLINE REGISTRATION Click here: http://www.theairportshow.com/visitors/registration.aspx Online entries close Sunday 29th May. - Event Schedule: Expo Hours: Tuesday - Thursday 10 a.m. to 6 p.m. Seminar Hours: Tuesday 2.30 p.m. to 5.00 p.m. Wednesday 10.30 a.m. to 4.30 p.m. Thursday 10.30 a.m to 1.00 p.m Opening ceremony: Tuesday 11:00 a.m. (Central hall reception) ,
New Blog
Carissimi Amici, Vi comunico che h attivo da circa 3 mesi il nuovo blog di ambiente Italia, raggiungibile su: http://ambienteitalia.altervista.org/blog/ Li potete postare quello che vi pare, sono ben accetti anche amministratori. A tutti Vi auguro una buona giornata. Ettore
Re: Order Filter mesh,filter tube 23-05-2
Dear Sir, Thank you very much for taking the time to read this letter . This is Mr Joshua Here would like to take this opportunity to introduce Boli wire mesh Co.,LTD. as one of leaing Manufacture and Exporter of the following items. 1.Shaped Filters,Filter mesh ,Filter nets,Wire mesh filter discs, filter tube . 2.Filter mesh cylinders ,Stainless Steel Mesh Filter ,Filter cartridge, 3.Filter baskets, Medical basket, Metal turnover box,Mesh cages,Metal crafts. Warmly welcome you reply us with your details requirements of the above Items .The Best quotation would reply you soon.Sincerely hoping can do business coopeate with you in the near future. Thank you have a nice day. Best regards. Joshua.Yang BOLI WIRE MESH CO., Tel: +86-311-87789982Fax: +86-311-87769982 Mob:+0086-150-8110-4408 www.bolifilter.com b...@bolifilter.com i...@bolifilter.com www.boliwiremesh.com
pfsync over IPsec kernel panic when syncdev is not enc0
Hi While testing pfsync over IPsec I have spotted a bug. While it is documented in man pfsync that enc0 should be used as syncdev when using pfsync over ipsec IMHO the system should not crash when the physical interface is used. This bug can be spotted on 4.8/i386, 4.9/i386 and Current/i386. I have not tested any other architectures. I have noticed it when I tried to secure (with IPSEC) already configured pfsync environment. It is very easy to reproduce. You need to have two physical interfaces. One with some traffic and on the second you need to configure pfsync over ipsec like this: FW1: ifconfig xl0 10.0.0.2/24 ping 10.0.0.1 (in background) ifconfig bge0 192.168.1.1/24 up /etc/ipsec.conf: ike esp from 192.168.1.1 to 192.168.1.2 peer 192.168.1.2 psk test isakmpd -4 -v -K ipsecctl -f /etc/ipsec.conf ifconfig pfsync0 create ifconfig pfsync0 syncpeer 192.168.1.2 syncdev bge0 up ifconfig pfsync0 down ifconfig pfsync0 up crash within seconds On the second machine you need: ifconfig em0 192.168.1.2/24 up /etc/ipsec.conf: ike esp from 192.168.1.2 to 192.168.1.1 peer 192.168.1.1 psk test isakmpd -4 -v -K ipsecctl -f /etc/ipsec.conf Sometimes my system freezes sometimes it crashes sometimes kernel panics. uvm_fault(0xd0a34340, 0x100, 0,1) - e kernel: page fault trap, code=0 Stopped at m_cluncount+0x1a: movzwl 0x12(%edx),%eax ddb trace m_cluncount(d6d75600,1,d6d59d00,dc006e74,d0400252) at m_cluncount_0x1a ether_input(d1dc904c,0,d6d75600,200,a) at ether_input+0x2b xl_rxeof(d1dc9000,9000,e,6c01,d0202490) at xl_rxeof+0x121 xl_intr(d1dc9000) at xl_intr+0xd5 Xintr_ioapic0() at Xintr_ioapic0+0x70 --- interrupt --- cpu_idle_cycle(d0af0e20) at cpu_idle_cycle+0xf Bad frame pointer: 0xd0ba8e48 Dmesg below: OpenBSD 4.9-current (GENERIC) #2: Sun May 22 22:31:55 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) D CPU 2.80GHz (GenuineIntel 686-class) 2.82 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR real mem = 1064824832 (1015MB) avail mem = 1036578816 (988MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 09/26/05, BIOS32 rev. 0 @ 0xfb390, SMBIOS rev. 2.3 @ 0xf0100 (39 entries) bios0: vendor Award Software International, Inc. version F8 date 09/26/2005 bios0: Gigabyte Technology Co., Ltd. 8I945G Pro acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP MCFG APIC acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) PEX5(S5) HUB0(S5) USB0(S1) USB1(S1) USB2(S1) USB3(S1) USBE(S1) AC97(S5) MC97(S5) AZAL(S5) PCI0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xf000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 200MHz cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEX0) acpiprt2 at acpi0: bus -1 (PEX1) acpiprt3 at acpi0: bus 2 (PEX2) acpiprt4 at acpi0: bus -1 (PEX3) acpiprt5 at acpi0: bus -1 (PEX4) acpiprt6 at acpi0: bus -1 (PEX5) acpiprt7 at acpi0: bus 3 (HUB0) acpicpu0 at acpi0 acpibtn0 at acpi0: PWRB bios0: ROM list: 0xc/0xa800! 0xcc000/0x8000! pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945G Host rev 0x02 vga1 at pci0 dev 2 function 0 Intel 82945G Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1: apic 2 int 16 drm0 at inteldrm0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 2 int 16 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x01: apic 2 int 18 pci2 at ppb1 bus 2 bge0 at pci2 dev 0 function 0 Broadcom BCM5789 rev 0x11, BCM5750 B1 (0x4101): apic 2 int 18, address 00:14:85:e1:d7:51 brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 2 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 2 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 2 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 2 int 16 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 2 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb2 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xe1 pci3 at ppb2 bus 3 xl0 at pci3 dev 0 function 0 3Com 3c905C 100Base-TX rev 0x78: apic 2 int 20, address 00:04:75:dc:57:48 exphy0 at xl0 phy 24: 3Com internal media interface Creative Labs SoundBlaster Audigy LS rev 0x00 at pci3 dev 1 function 0 not configured pciide0 at pci3 dev 6 function 0 ITExpress IT8212F rev 0x13:
Re: dmesg for notebooks useful?
On Sat, 21 May 2011, Stuart Henderson wrote:
On 2011-05-21, Dave Anderson d...@daveanderson.com wrote:
On Sat, 21 May 2011, Paul M wrote:
On 20/05/2011, at 12:27 PM, Dave Anderson wrote:
FWIW I've encountered several ASUS notebooks which panic during boot
(in aml_parse or parse_aml, I can't remember which is correct); since
aml_xparse
these are store demo machines I don't have any good way to capture the
detailed information (I'm booting from a USB stick and saving the dmseg
to the stick.) If there's some small amount of information that can be
gotten without any additional hardware, etc, and would help diagnose
these problems, I'll write it down and report it if someone tells me
exactly how to get it. The panic info is long enough that some of it
scrolls off the screen.
I've tried such a laptop, booting from usb stick does indeed fail as
you describe, however booting from the install cd (4.9 release) works
just fine.
Disabling acpi will allow the system to boot from the usb stick.
Thanks for the info. I'll try disabling ACPI the next time I encounter
one of these.
You need the information in the panic message and trace.
If you want to help get the problems with those machines tracked
down, you need to get that information, maybe take a photo and
type it in from there.
If the panic message itself has scrolled off show panic
should show it again.
The only way disabling ACPI is helpful, is if the machine saves the
dmesg buffer between boots, then you may be able to get the panic,
boot -c, disable acpi, and save the information.
ACPI should not be disabled on modern machines, they are not
meant to work that way.
Got a chance to try an ASUS system (k53e-xb1) and it did save the dmesg
over the reboot -- so here's the info. I don't have the AML since there
was no obvious way to list it from ddb and I was in a bit of a hurry and
didn't think to try e.g. acpidump after the reboot with acpi disabled.
If someone tells me the exact command to produce the needed AML info
I'll make sure to try it next time.
Dave
OpenBSD 4.9-current (GENERIC) #65: Fri Apr 29 16:17:01 MDT 2011
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz (GenuineIntel 686-class) 2.30
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX
real mem = 2996805632 (2857MB)
avail mem = 2937638912 (2801MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/03/10, SMBIOS rev. 2.6 @ 0xeb9b0 (79
entries)
bios0: vendor American Megatrends Inc. version K53E.206 date 02/22/2011
bios0: ASUSTeK Computer Inc. K53E
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC DBGP ECDT SLIC HPET MCFG SSDT SSDT ASF!
acpi0: wakeup devices PEG0(S4) PEG1(S4) PEG2(S4) PEG3(S4) B0D4(S4) P0P1(S4)
HDEF(S4) GLAN(S4) EHC1(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EHC2(S3)
USB5(S3) USB6(S3) USB7(S3) RP01(S4) RP02(S4) WLAN(S3) RP03(S4) RP04(S4)
XHCI(S3) RP05(S4) RP06(S4) GLAN(S4) RP07(S4) RP08(S4) SLPB(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 99MHz
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiec0 at acpi0
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus -1 (PEG3)
acpiprt5 at acpi0: bus -1 (P0P1)
acpiprt6 at acpi0: bus 1 (RP01)
acpiprt7 at acpi0: bus 2 (RP02)
acpiprt8 at acpi0: bus -1 (RP03)
acpiprt9 at acpi0: bus -1 (RP04)
acpiprt10 at acpi0: bus -1 (RP05)
acpiprt11 at acpi0: bus 3 (RP06)
acpiprt12 at acpi0: bus -1 (RP07)
acpiprt13 at acpi0: bus -1 (RP08)
acpicpu0 at acpi0: C3, C1, PSS
acpitz0 at acpi0acpitz0: THRM: failed to read _CRT
: no critical temperature defined
acpiac0 at acpi0: AC unit in unknown state
acpibat0 at acpi0: BAT0 not present
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpivideo0 at acpi0: GFX0
acpivideo1 at acpi0: GFX0
acpivout0 at acpivideo1: LCDD
[\\_SB_.PCI0.SBRG.EC0_.PWAC] 0xd3bf5bc4 cnt:02 stk:00 buffer: 40 {33, 40, 4d,
5a, 67, 73, 80, 8d, a7, cd, ff, ff, ff, ff, ff, ff, 21, 2e, 3b, 48, 55, 61, 6e,
7b, 9a, c5, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff,
ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff,
ff}
Index out of bounds 3818/64
61b1 Called: \\_SB_.PCI0.GFX0.LCDD._BCL
local0: 0xd3c0f3c4 cnt:01 stk:60 integer: 0
local3: 0xd3c11c44 cnt:02 stk:63 integer: eea
local4: 0xd3c0fa84 cnt:01 stk:64 integer: ee0
617e Called: \\_SB_.PCI0.GFX0.LCDD._BCL
local0:
Re: tcpdump shows packets going from 0.0.0.0.0 0.0.0.0.0, what does this mean?
On Sun, 22 May 2011 12:10:24 +0200 Andreas Bartelt wrote: Hello Brett, On 05/22/11 09:02, Brett Mahar wrote: Hi misc, I have been playing around with pf lately, and have noticed a bunch of packets going from 0.0.0.0.0 to 0.0.0.0.0. I know 0.0.0.0 sometimes means the network address, but am not sure why these packets are getting through the firewall, or even if they are. Also, when tcpdump says (for example) rule 8 does that mean the 8th line in the output of pfctl -sr? I cannot find an explanation on website or man pages. I'm also seeing this for my pass in log (all to pflog0) ... rules. If you remove the all keyword, you'll see the the correct IP addresses at session initialization in the logs. Best regards Andreas Surely that just hides them. Does this happen with current or is it expected to allow the new logging functionality?
Re: ospfd/ospf6d causing denial of service(?)
On Mon, May 23, 2011 at 9:59 AM, Chris Wopat m...@falz.net wrote: Had a strange issue overnight. In short I had two OpenBSD boxes acting as routers denial of service my network with OSPFv3 multicast packets. This happened again today. This time it was on a third OpenBSD box. The last time it happened it was happening what appeared to be simultaneously from two freshly installed 4.9 AMD64 boxes. This box is the same install and similar configuration as before. This time we were able to capture a sniff as well as a ktrace. http://falz.net/static/openbsd/ktrace-openbsd-49-2011-05-24.out (~170mb) http://falz.net/static/openbsd/sniff-openbsd-49-2011-05-24.pcap (~50mb) The pcap file above shows 604941 packets in a period of 9.4 seconds(!). All of the packets are: 66.170.7.139 224.0.0.5: OSPFv2-ls_upd 28: rtrid 66.170.0.14 backbone [tos 0xc0] [ttl 1] 66.170.7.139 is one of two IPs on the problematic OpenBSD box. 0.14 is the loopback (lo1) on that box. If you want to see a screen cap of the interesting parts of the packets here's a screenshot from wireshark: http://falz.net/static/openbsd/wireshark-packet-screenshot.png These are the first two packets. They're all OSPF type 4 Link State updates. During a part of the timeperiod where we had the issue we thought it may have been soem sort of spanning tree issue since it jumped back and forth between the two VLANs that this server is attached to. You can see in the dump that the OSPF Auth Crypto Sequence Number increments and the Auth data changes in each packet so they definitely appear to be unique packets. Here's packet counts from the switch it uplinks to. blue is out, so originating from the device: http://falz.net/static/openbsd/openbsd-em0-pps-graph.png http://falz.net/static/openbsd/openbsd-em1-pps-graph.png This shows what we saw, it originates on em0 and moved to em1. I'd love to hear from Claudio/Esben or any OpenOSPFD users, especially those running 4.9 since it appears that there were several ospfd updates in 4.9. While things are stable at the moment I'm going to potentially disable ospfd tonight and switch BGP to a less redundant manner. If I can confirm there's something wrong in 4.9 I'll just go to 4.8 instead. --Chris
Re: Theo's Birthday, have you done anything?
Nope. Can't.I live below the poverty level.
Re: ospfd/ospf6d causing denial of service(?)
On Tue, May 24, 2011 at 01:12:10PM -0500, Chris Wopat wrote: On Mon, May 23, 2011 at 9:59 AM, Chris Wopat m...@falz.net wrote: Had a strange issue overnight. In short I had two OpenBSD boxes acting as routers denial of service my network with OSPFv3 multicast packets. This happened again today. This time it was on a third OpenBSD box. The last time it happened it was happening what appeared to be simultaneously from two freshly installed 4.9 AMD64 boxes. This box is the same install and similar configuration as before. This time we were able to capture a sniff as well as a ktrace. http://falz.net/static/openbsd/ktrace-openbsd-49-2011-05-24.out (~170mb) http://falz.net/static/openbsd/sniff-openbsd-49-2011-05-24.pcap (~50mb) The pcap file above shows 604941 packets in a period of 9.4 seconds(!). All of the packets are: 66.170.7.139 224.0.0.5: OSPFv2-ls_upd 28: rtrid 66.170.0.14 backbone [tos 0xc0] [ttl 1] Are you running 4.9 or -current? Up until the code generating the LSA update packets (and sending them) did not change between 4.8 and 4.9. In -current this code got rewritten to fix a issue. IIRC the problem was that an LS Update got so big that it did not fit into a MTU sized packet. If my memory serves me right then the result was this kind of packet storm. You should try and compile a -current ospfd on your 4.9 system. I think it should run without any problems. -- :wq Claudio
Re: ospfd/ospf6d causing denial of service(?)
On Tue, May 24, 2011 at 3:11 PM, Claudio Jeker cje...@diehard.n-r-g.com wrote: Are you running 4.9 or -current? Up until the code generating the LSA update packets (and sending them) did not change between 4.8 and 4.9. In -current this code got rewritten to fix a issue. IIRC the problem was that an LS Update got so big that it did not fit into a MTU sized packet. If my memory serves me right then the result was this kind of packet storm. You should try and compile a -current ospfd on your 4.9 system. I think it should run without any problems. I'm running 4.9, not -current. I didn't see anything about people having this issue in the mailing lists. I see that there was a patch applied only about 15 minutes ago to something else related to ospfd, I'm not sure what new issues will occur if I go to -current here since this box is in production. My current workaround plan is to eliminate OpenOSPFD from my network. Fortunately it's just one box for now but I was hoping to add several others in the next few weeks. * Can a reliability fix errata be created for this? * Is the same bug in ospf6d? --Chris
Dell Rack Rails
Hello, I have a few Dell Servers that are 1U and 2U. Problem is that Colocation's rails are 30. The rails that came with the servers where only about 28 or 27. Anyone know of a good company to get universals that will go the full 30? Thanks Ben --- http://www.SpryMed.com/
Re: ospfd/ospf6d causing denial of service(?)
Claudio, It was not possible to send out LS updates larger then the MTU. Change the code in such a way that single huge LSA get fragmented but avoid IP fragmentation when packing multiple ones. Problem found and fix tested by Benjamin Papillon. If I understand this correctly, there was an issue with the IP packets getting fragmented themselves -- would scrubbing with pf have prevented this issue? Regards, Mark
Re: dmesg for notebooks useful?
On 25/05/2011, at 4:48 AM, Dave Anderson wrote:
On Sat, 21 May 2011, Stuart Henderson wrote:
On 2011-05-21, Dave Anderson d...@daveanderson.com wrote:
On Sat, 21 May 2011, Paul M wrote:
On 20/05/2011, at 12:27 PM, Dave Anderson wrote:
FWIW I've encountered several ASUS notebooks which panic during
boot
(in aml_parse or parse_aml, I can't remember which is correct);
since
aml_xparse
these are store demo machines I don't have any good way to capture
the
detailed information (I'm booting from a USB stick and saving the
dmseg
to the stick.) If there's some small amount of information that
can be
gotten without any additional hardware, etc, and would help
diagnose
these problems, I'll write it down and report it if someone tells
me
exactly how to get it. The panic info is long enough that some of
it
scrolls off the screen.
I've tried such a laptop, booting from usb stick does indeed fail as
you describe, however booting from the install cd (4.9 release)
works
just fine.
Disabling acpi will allow the system to boot from the usb stick.
Thanks for the info. I'll try disabling ACPI the next time I
encounter
one of these.
You need the information in the panic message and trace.
If you want to help get the problems with those machines tracked
down, you need to get that information, maybe take a photo and
type it in from there.
If the panic message itself has scrolled off show panic
should show it again.
The only way disabling ACPI is helpful, is if the machine saves the
dmesg buffer between boots, then you may be able to get the panic,
boot -c, disable acpi, and save the information.
ACPI should not be disabled on modern machines, they are not
meant to work that way.
Got a chance to try an ASUS system (k53e-xb1) and it did save the dmesg
over the reboot -- so here's the info. I don't have the AML since
there
was no obvious way to list it from ddb and I was in a bit of a hurry
and
didn't think to try e.g. acpidump after the reboot with acpi disabled.
If someone tells me the exact command to produce the needed AML info
I'll make sure to try it next time.
Dave
OpenBSD 4.9-current (GENERIC) #65: Fri Apr 29 16:17:01 MDT 2011
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz (GenuineIntel
686-class) 2.30 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36
,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-
CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,
AVX
real mem = 2996805632 (2857MB)
avail mem = 2937638912 (2801MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/03/10, SMBIOS rev. 2.6 @
0xeb9b0 (79 entries)
bios0: vendor American Megatrends Inc. version K53E.206 date
02/22/2011
bios0: ASUSTeK Computer Inc. K53E
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC DBGP ECDT SLIC HPET MCFG SSDT SSDT ASF!
acpi0: wakeup devices PEG0(S4) PEG1(S4) PEG2(S4) PEG3(S4) B0D4(S4)
P0P1(S4) HDEF(S4) GLAN(S4) EHC1(S3) USB1(S3) USB2(S3) USB3(S3)
USB4(S3) EHC2(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) RP02(S4)
WLAN(S3) RP03(S4) RP04(S4) XHCI(S3) RP05(S4) RP06(S4) GLAN(S4)
RP07(S4) RP08(S4) SLPB(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 99MHz
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiec0 at acpi0
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus -1 (PEG3)
acpiprt5 at acpi0: bus -1 (P0P1)
acpiprt6 at acpi0: bus 1 (RP01)
acpiprt7 at acpi0: bus 2 (RP02)
acpiprt8 at acpi0: bus -1 (RP03)
acpiprt9 at acpi0: bus -1 (RP04)
acpiprt10 at acpi0: bus -1 (RP05)
acpiprt11 at acpi0: bus 3 (RP06)
acpiprt12 at acpi0: bus -1 (RP07)
acpiprt13 at acpi0: bus -1 (RP08)
acpicpu0 at acpi0: C3, C1, PSS
acpitz0 at acpi0acpitz0: THRM: failed to read _CRT
: no critical temperature defined
acpiac0 at acpi0: AC unit in unknown state
acpibat0 at acpi0: BAT0 not present
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpivideo0 at acpi0: GFX0
acpivideo1 at acpi0: GFX0
acpivout0 at acpivideo1: LCDD
[\\_SB_.PCI0.SBRG.EC0_.PWAC] 0xd3bf5bc4 cnt:02 stk:00 buffer: 40 {33,
40, 4d, 5a, 67, 73, 80, 8d, a7, cd, ff, ff, ff, ff, ff, ff, 21, 2e,
3b, 48, 55, 61, 6e, 7b, 9a, c5, ff, ff, ff, ff, ff, ff, ff, ff, ff,
ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff,
ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff}
Index out of bounds 3818/64
61b1 Called: \\_SB_.PCI0.GFX0.LCDD._BCL
local0: 0xd3c0f3c4 cnt:01 stk:60 integer: 0
local3: 0xd3c11c44 cnt:02 stk:63 integer: eea
local4:
Necesario: Actualización de Adquisiciones, Manual y Reglamento 20-21 de Junio 2011
[IMAGE] Pms Capacitacisn Efectiva de Mixico presenta: Actualizacisn Nacional de Adquisiciones, Manual de Aplicacisn y su Reglamento 20-21 de Junio, Mixico D.F. Nos acompaqan 2 Expertos en la materia: Mtro. Gerardo Coronado y Mtro. Alberto Ledesma Empresa Registrada ante la STPS Reg. COLG640205CP30005 Smguenos en Twitter@pmscapacitacion o bien en Facebook PMS de Mixico Solicite Mayores informes responda este correo electrsnico con los siguientes datos. Empresa: Nombre: Telifono: Email: Nzmero de Interesados: Y en breve le haremos llegar la informacisn completa del evento. O bien comunmquense a nuestros telifonos un ejecutivo con gusto le atendera Tels. (33) 8851-2365, (33)8851-2741. Copyright (C) 2010, PMS Capacitacisn Efectiva de Mixico S.C. Derechos Reservados. PMS de Mixico, El logo de PMS de Mixico son marcas registradas. ADVERTENCIA PMS de Mixico no cuenta con alianzas estratigicas de ningzn tipo dentro de la Republica Mexicana. NO SE DEJE ENGAQAR - DIGA NO A LA PIRATERIA. Todos los logotipos, marcas comerciales e imagenes son propiedad de sus respectivas corporaciones y se utilizan con fines informativos solamente. Este Mensaje ha sido enviado a misc@openbsd.org como usuario de Pms de Mixico o bien un usuario le refiris para recibir este boletmn. Como usuario de Pms de Mixico, en este acto autoriza de manera expresa que Pms de Mixico le puede contactar vma correo electrsnico u otros medios. Si usted ha recibido este mensaje por error, haga caso omiso de el y reporte su cuenta respondiendo este correo con el subject BAJAADQUISICION Unsubscribe to this mailing list, reply a blank message with the subject UNSUBSCRIBE BAJAADQUISICION Tenga en cuenta que la gestisn de nuestras bases de datos es de suma importancia y no es intencisn de la empresa la inconformidad del receptor [demime 1.01d removed an attachment of type image/jpeg which had a name of actualizacion adquisiciones.jpg]
mount can't find fstab entry
Hello, $ grep sd0k /etc/fstab /dev/sd0k /home/luca/ext2fs ext2fs rdonly,nodev,nosuid 0 0 $ sudo mount /dev/sd0k mount: can't find fstab entry for /dev/sd0k. but $ sudo mount_ext2fs -o rdonly,nodev,nosuid /dev/sd0k /home/luca/ext2fs/ $ mount|grep sd0k /dev/sd0k on /home/luca/ext2fs type ext2fs (local, nodev, nosuid, read-only) $ dmesg OpenBSD 4.9-current (GENERIC.MP) #3: Sun May 22 12:57:57 MDT 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3218931712 (3069MB) avail mem = 3111038976 (2966MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries) bios0: vendor LENOVO version 79ETE6WW (2.26 ) date 04/01/2010 bios0: LENOVO 2007E79 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.29 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG cpu0: 4MB 64b/line 16-way L2 cache cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG cpu1: 4MB 64b/line 16-way L2 cache ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS acpitz0 at acpi0: critical temperature 127 degC acpitz1 at acpi0: critical temperature 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 08K8193 serial 279 type LION oem LDL acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2000, 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03 ppb0 at pci0 dev 1 function 0 Intel 82945GM PCIE rev 0x03: apic 1 int 16 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon Mobility X1400 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 1 int 16 drm0 at radeondrm0 azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: apic 1 int 17 azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog Devices AD1981HD audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 1 int 20 pci2 at ppb1 bus 2 em0 at pci2 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: apic 1 int 16, address 00:15:58:83:a5:0e ppb2 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 1 int 21 pci3 at ppb2 bus 3 wpi0 at pci3 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: apic 1 int 17, MoW1, address 00:1b:77:02:dc:c5 ppb3 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: apic 1 int 22 pci4 at ppb3 bus 4 ppb4 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02: apic 1 int 23 pci5 at ppb4 bus 12 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 1 int 16 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 1 int 17 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 1 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 1 int 19 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 1 int 19 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb5 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci6 at ppb5 bus 21 cbb0 at pci6 dev 0 function 0 TI PCI1510 CardBus rev 0x00: apic 1 int 16 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 22 device 0 cacheline 0x8, lattimer 0xb0 pcmcia0 at cardslot0 pcib0 at pci0 dev 31 function 0 Intel 82801GBM LPC rev 0x02 pciide0 at pci0 dev 31 function 1 Intel 82801GB IDE rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, DVDRAM
Re: mount can't find fstab entry
$ grep sd0k /etc/fstab /dev/sd0k /home/luca/ext2fs ext2fs rdonly,nodev,nosuid 0 0 ^^ There is no such keyword in a fstab file. $ sudo mount /dev/sd0k mount: can't find fstab entry for /dev/sd0k.
Re: dmesg for notebooks useful?
On Wed, 25 May 2011, Paul M wrote:
On 25/05/2011, at 4:48 AM, Dave Anderson wrote:
On Sat, 21 May 2011, Stuart Henderson wrote:
On 2011-05-21, Dave Anderson d...@daveanderson.com wrote:
On Sat, 21 May 2011, Paul M wrote:
On 20/05/2011, at 12:27 PM, Dave Anderson wrote:
FWIW I've encountered several ASUS notebooks which panic during
boot
(in aml_parse or parse_aml, I can't remember which is correct);
since
aml_xparse
these are store demo machines I don't have any good way to capture
the
detailed information (I'm booting from a USB stick and saving the
dmseg
to the stick.) If there's some small amount of information that
can be
gotten without any additional hardware, etc, and would help
diagnose
these problems, I'll write it down and report it if someone tells
me
exactly how to get it. The panic info is long enough that some of
it
scrolls off the screen.
I've tried such a laptop, booting from usb stick does indeed fail as
you describe, however booting from the install cd (4.9 release)
works
just fine.
Disabling acpi will allow the system to boot from the usb stick.
Thanks for the info. I'll try disabling ACPI the next time I
encounter
one of these.
You need the information in the panic message and trace.
If you want to help get the problems with those machines tracked
down, you need to get that information, maybe take a photo and
type it in from there.
If the panic message itself has scrolled off show panic
should show it again.
The only way disabling ACPI is helpful, is if the machine saves the
dmesg buffer between boots, then you may be able to get the panic,
boot -c, disable acpi, and save the information.
ACPI should not be disabled on modern machines, they are not
meant to work that way.
Got a chance to try an ASUS system (k53e-xb1) and it did save the dmesg
over the reboot -- so here's the info. I don't have the AML since
there
was no obvious way to list it from ddb and I was in a bit of a hurry
and
didn't think to try e.g. acpidump after the reboot with acpi disabled.
If someone tells me the exact command to produce the needed AML info
I'll make sure to try it next time.
Dave
OpenBSD 4.9-current (GENERIC) #65: Fri Apr 29 16:17:01 MDT 2011
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz (GenuineIntel
686-class) 2.30 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36
,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-
CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,
AVX
real mem = 2996805632 (2857MB)
avail mem = 2937638912 (2801MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/03/10, SMBIOS rev. 2.6 @
0xeb9b0 (79 entries)
bios0: vendor American Megatrends Inc. version K53E.206 date
02/22/2011
bios0: ASUSTeK Computer Inc. K53E
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC DBGP ECDT SLIC HPET MCFG SSDT SSDT ASF!
acpi0: wakeup devices PEG0(S4) PEG1(S4) PEG2(S4) PEG3(S4) B0D4(S4)
P0P1(S4) HDEF(S4) GLAN(S4) EHC1(S3) USB1(S3) USB2(S3) USB3(S3)
USB4(S3) EHC2(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) RP02(S4)
WLAN(S3) RP03(S4) RP04(S4) XHCI(S3) RP05(S4) RP06(S4) GLAN(S4)
RP07(S4) RP08(S4) SLPB(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 99MHz
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiec0 at acpi0
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus -1 (PEG3)
acpiprt5 at acpi0: bus -1 (P0P1)
acpiprt6 at acpi0: bus 1 (RP01)
acpiprt7 at acpi0: bus 2 (RP02)
acpiprt8 at acpi0: bus -1 (RP03)
acpiprt9 at acpi0: bus -1 (RP04)
acpiprt10 at acpi0: bus -1 (RP05)
acpiprt11 at acpi0: bus 3 (RP06)
acpiprt12 at acpi0: bus -1 (RP07)
acpiprt13 at acpi0: bus -1 (RP08)
acpicpu0 at acpi0: C3, C1, PSS
acpitz0 at acpi0acpitz0: THRM: failed to read _CRT
: no critical temperature defined
acpiac0 at acpi0: AC unit in unknown state
acpibat0 at acpi0: BAT0 not present
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpivideo0 at acpi0: GFX0
acpivideo1 at acpi0: GFX0
acpivout0 at acpivideo1: LCDD
[\\_SB_.PCI0.SBRG.EC0_.PWAC] 0xd3bf5bc4 cnt:02 stk:00 buffer: 40 {33,
40, 4d, 5a, 67, 73, 80, 8d, a7, cd, ff, ff, ff, ff, ff, ff, 21, 2e,
3b, 48, 55, 61, 6e, 7b, 9a, c5, ff, ff, ff, ff, ff, ff, ff, ff, ff,
ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff,
ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff}
Index out of bounds 3818/64
61b1 Called: \\_SB_.PCI0.GFX0.LCDD._BCL
local0: 0xd3c0f3c4
Re: mount can't find fstab entry
On Tue, 24 May 2011 18:26:43 -0600, Theo de Raadt wrote: $ grep sd0k /etc/fstab /dev/sd0k /home/luca/ext2fs ext2fs rdonly,nodev,nosuid 0 0 ^^ There is no such keyword in a fstab file. Obvious PEBKAC here, blindly putting mount(1) options into fstab(5). The error message from mount is tricky though, getfsspec(3) which is used by mount just silently ignores the line. All entries in the file with a type field equivalent to FSTAB_XX are ignored. Lines which are formatted incorrectly are silently ignored. So formatted incorrectly includes invalid options. Could this be improved somehow by changing getfsspec() behaviour to report the issue to the caller? Or by expanding the manpage a bit? I guess making mount/fstab more consistent by using the same name for rdonly/ro is a compatibility can of worms. thanks Luca
Firewall PF with network alias
In the past, i configure a virtual machine with firewall PF in FreeBSD 8.1 with three network interface (in pf.conf) ext_if=ed0 # INTERNET dmz_if=ed1 # DMZ lan_if=ed2 # LAN Now i need configure this in real server but it only have two network interface. I beleive that the solution is network aliases but ext_if=ed0 # INTERNET dmz_if=ed0_alias0# DMZ lan_if=ed2 # LAN don't work. I need any solution for this problem. Thank advance. --- El lun, 23/5/11, Alexander Hall ha...@openbsd.org escribis: De: Alexander Hall ha...@openbsd.org Asunto: Re: Firewall PF con una interface de red con ALIAS Para: MArtin Grados Marquina themartin...@yahoo.es Fecha: lunes, 23 de mayo, 2011 00:23 1. English is used on misc@openbsd.org 2. Don't cross-post. On 05/22/11 02:58, MArtin Grados Marquina wrote: Buenas, Hace algun tiempo me virtulice un firewall PF en FreeBSD la cual tenia tres interfaces de red(mi archivo pf.conf) lop_if=lo0 ext_if=ed0 # INTERNET dmz_if=ed1 # DMZ lan_if=ed2 # LAN , ahora la quiero implementar en una maquina real pero esta solo tiene dos interfaces de red, la primera solucisn que se me ocurre es crear un alias a una interface pero ?como declaria esta en mi pf.conf?(no se puede hacer ext_if=ed0_alias0) ... me he bajado algunos libros y he googleado sin exito ... no creeria si alguien me dice que eso no se puede hacer ... debe haber una forma .. agradeceria mucho si alguien me da alguna pista. Gracias.
