pfSense Gold Subscription

Author Topic: 1 critical bug with 1.2.1-RC2 and one harmless problem  (Read 4791 times)

0 Members and 1 Guest are viewing this topic.

Offline hexa

  • Jr. Member
  • **
  • Posts: 73
  • Karma: +0/-0
    • View Profile
1 critical bug with 1.2.1-RC2 and one harmless problem
« on: November 27, 2008, 05:09:08 am »
Hi,

i just installed pfsense 1.2.1-RC2 and have found a critical bug. After successful setup (tied it a couple of times) i cannot access pfsense via LAN. It can only be accessed when i run tcpdump -i re0 -n on pfsense box (ifconfig re0 up didn't help), where re0 is local lan interface. As soon as i stop tcpdump pings won't return, neither will http admin interface respond. I'm sure i didn't configure anything wrong, iterface is UP and all IPs with netmask are correct. I have two identical machines and on both the same happened. Same machines version 1.2 final works n.p.
For you, i tracked the bug down to buggy driver for re (RealTek 8169SC/8110SC) network cards. I have 4 more labeled as em (Intel(R) PRO/1000) and if i move LAN over to let's say em0, no tcpdump -i em0 -n is required for me to be able to access pfsense.

XYZ:~ hexa$ ssh admin@10.20.20.4
The authenticity of host '10.20.20.4 (10.20.20.4)' can't be established.
DSA key fingerprint is 33:2b:8f:c0:be:65:8b:38:19:e7:e9:f7:85:52:26:6a.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.20.20.4' (DSA) to the list of known hosts.
Password:

*** Welcome to pfSense 1.2.1-RC2-pfSense on pfSense ***

  LAN*                     ->   em0   ->   10.20.20.4
  WAN                      ->   em1   ->   NONE(DHCP)

 pfSense console setup
***********************
 0)  Logout (SSH only)
 1)  Assign Interfaces
 2)  Set LAN IP address
 3)  Reset webConfigurator password
 4)  Reset to factory defaults
 5)  Reboot system
 6)  Halt system
 7)  Ping host
 8)  Shell
 9)  PFtop
10)  Filter Logs
11)  Restart webConfigurator
12)  pfSense PHP shell
13)  Upgrade from console
14)  Disable Secure Shell (sshd)

Enter an option: 8

# dmesg
Copyright (c) 1992-2008 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 7.0-RELEASE-p5 #0: Wed Nov 19 22:15:37 EST 2008
    sullrich@freebsd7-releng_1_2.pfsense.org:/usr/obj.pfSense/usr/src/sys/pfSense_SMP.7
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz (1862.01-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6f6  Stepping = 6
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0xe3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
  AMD Features=0x20100000<NX,LM>
  AMD Features2=0x1<LAHF>
  Cores per package: 2
real memory  = 2146304000 (2046 MB)
avail memory = 2090610688 (1993 MB)
ACPI APIC Table: <AWARD  ASUSACPI>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Changing APIC ID to 4
ioapic0 <Version 0.3> irqs 0-23 on motherboard
ioapic1 <Version 0.3> irqs 24-47 on motherboard
wlan: mac acl policy registered
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
hptrr: HPT RocketRAID controller driver v1.1 (Nov 19 2008 22:15:18)
cryptosoft0: <software crypto> on motherboard
acpi0: <AWARD ASUSACPI> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 100000, 7fde0000 (3) failed
acpi0: reservation of 0, a0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 728072806000728
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
acpi_button0: <Power Button> on acpi0
acpi_button1: <Sleep Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 27 at device 2.0 on pci0
pci2: <ACPI PCI bus> on pcib2
vgapci0: <VGA-compatible display> port 0xac00-0xacff mem 0xc0000000-0xcfffffff,0xdfdf0000-0xdfdfffff irq 24 at device 0.0 on pci2
vgapci1: <VGA-compatible display> mem 0xdfde0000-0xdfdeffff at device 0.1 on pci2
pcib3: <ACPI PCI-PCI bridge> irq 31 at device 3.0 on pci0
pci3: <ACPI PCI bus> on pcib3
atapci0: <VIA 8237A SATA150 controller> port 0xfc00-0xfc07,0xf800-0xf803,0xf400-0xf407,0xf000-0xf003,0xec00-0xec0f,0xe800-0xe8ff irq 21 at device 15.0 on pci0
atapci0: [ITHREAD]
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
atapci1: <VIA 8237A UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe400-0xe40f at device 15.1 on pci0
ata0: <ATA channel 0> on atapci1
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci1
ata1: [ITHREAD]
uhci0: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 20 at device 16.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xdc00-0xdc1f irq 22 at device 16.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
uhci2: <VIA 83C572 USB controller> port 0xd800-0xd81f irq 21 at device 16.2 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb2: <VIA 83C572 USB controller> on uhci2
usb2: USB revision 1.0
uhub2: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
uhci3: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 23 at device 16.3 on pci0
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb3: <VIA 83C572 USB controller> on uhci3
usb3: USB revision 1.0
uhub3: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
ehci0: <VIA VT6202 USB 2.0 controller> mem 0xdffff000-0xdffff0ff irq 21 at device 16.4 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4: <VIA VT6202 USB 2.0 controller> on ehci0
usb4: USB revision 2.0
uhub4: <VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4
uhub4: 8 ports with 8 removable, self powered
isab0: <PCI-ISA bridge> at device 17.0 on pci0
isa0: <ISA bus> on isab0
pcib4: <ACPI PCI-PCI bridge> at device 19.1 on pci0
pci4: <ACPI PCI bus> on pcib4
em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 0x9c00-0x9c3f mem 0xdfbe0000-0xdfbfffff,0xdfcc0000-0xdfcdffff irq 17 at device 3.0 on pci4
em0: Ethernet address: 00:0e:0c:d0:db:7b
em0: [FILTER]
em1: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 0x9800-0x983f mem 0xdfca0000-0xdfcbffff,0xdfc80000-0xdfc9ffff irq 18 at device 4.0 on pci4
em1: Ethernet address: 00:0e:0c:d0:db:7c
em1: [FILTER]
em2: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 0x9400-0x943f mem 0xdfc60000-0xdfc7ffff,0xdfc40000-0xdfc5ffff irq 19 at device 5.0 on pci4
em2: Ethernet address: 00:0e:0c:d8:09:5d
em2: [FILTER]
em3: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 0x9000-0x903f mem 0xdfc20000-0xdfc3ffff,0xdfc00000-0xdfc1ffff irq 16 at device 6.0 on pci4
em3: Ethernet address: 00:0e:0c:d0:14:6f
em3: [FILTER]
re0: <RealTek 8169SC/8110SC Single-chip Gigabit Ethernet> port 0x8c00-0x8cff mem 0xdfcff000-0xdfcff0ff irq 20 at device 7.0 on pci4
re0: Chip rev. 0x18000000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
re0: Ethernet address: 00:17:31:5f:2f:b1
re0: [FILTER]
pcib5: <ACPI Host-PCI bridge> on acpi0
pci128: <ACPI PCI bus> on pcib5
acpi_tz0: <Thermal Zone> on acpi0
speaker0: <PC speaker> port 0x61 on acpi0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcefff,0xd5000-0xd5fff,0xd6000-0xd6fff,0xd7000-0xd7fff,0xd8000-0xd8fff pnpid ORM0000 on isa0
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
ppbus0: [ITHREAD]
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 1.000 msec
Fast IPsec: Initialized Security Association Processing.
hptrr: no controller detected.
acd0: CDROM <LTN526/YH0G> at ata0-slave PIO4
ad4: 305244MB <Seagate ST3320620AS 3.AAK> at ata2-master SATA150
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad4s1a
re0: link state changed to DOWN

If you need more info let me know.
Please also let me know if you're going to fix this, how fast, etc. Since it's probably a bug in freebsd 7 network driver i'm not sure if you can fix it. I'm hesitant to use the solution with one network card less, 'cause this would mean i would have to move pfsync over to another used interface and won't be alone as recommended by you. I wonder weather should I use old pfsense instead? Please advise me on it.

The second problem is that in the wizard where you set the WAN settings option Static is already selected in the drop down menu but you cannot enter the static IP in the box, cause it is gray. You have to select dhcp first then static back in order to be able to enter static IP manually in the box below. This is in Safari.
« Last Edit: November 27, 2008, 08:36:05 am by hexa »

Offline Gloom

  • Full Member
  • ***
  • Posts: 208
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #1 on: November 27, 2008, 07:42:29 am »
There was a patch for this driver on Current back in July but I've no idea if it made it into RELENG_7

This is the thread for it. If you read through it might help confirm or rule out if you are having the same issue.
https://kerneltrap.org/mailarchive/freebsd-current/2008/6/7/2056194
Never underestimate the power of human stupidity

Offline Perry

  • Hero Member
  • *****
  • Posts: 1152
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #2 on: November 27, 2008, 08:03:49 am »
It ain't listed as support in re(4) not even current
ifconfig re0 -tso is one thing you could try next would be to upgrade to pfsense 2.0 as it's based on 7.0 stable

The output of pciconf -lv is in most cases needed.

I think the right place for support would be the FreeBSD maling list.

Quote
The second problem is that in the wizard where you set the WAN settings option Static is already selected in the drop down menu but you cannot enter the static IP in the box, cause it is gray. You have to select dhcp first then static back in order to be able to enter static IP manually in the box below. This is in Safari.
Can confirm this, using firefox
/Perry
doc.pfsense.org

Offline hexa

  • Jr. Member
  • **
  • Posts: 73
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #3 on: November 27, 2008, 08:35:27 am »
Perry it worked O.K. in pfsense 1.2-FINAL with freebsd 6, so i suppose it should be supported in 7* as well. I doubt the support would be dropped. Or maybe i just understood you wrong. Well i'm still waiting for pfsense developers to recommend me what to do. Cause i'm short on time i just used LAN interface for (pf)sync for now.

I found another bug. When using the wizard to set WAN IP it doesn't set it. Gateway gets set but IP field on wan interface after the wizard finishes is empty! Also when using PING thru web interface you get no output if DNS servers aren't reachable and you use FQDN for ping, should say can't find host or somth.

Offline hexa

  • Jr. Member
  • **
  • Posts: 73
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #4 on: November 27, 2008, 08:36:54 am »
BTW isn't pfsense 1.2.1-RC2 based on freebsd 7 stable?

Offline Vancouver

  • Full Member
  • ***
  • Posts: 152
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #5 on: November 27, 2008, 08:51:34 am »
Sure. Also 1.2.1 is based entirely on FreeBSD 7-Stable

Offline hexa

  • Jr. Member
  • **
  • Posts: 73
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #6 on: November 27, 2008, 08:58:38 am »
So Perrys suggestion to upgrade to 2.0 version to use freebsd 7 stable is nonsense since i'm already with 1.2.1-RC2 on freebsd 7 stable.

Offline Perry

  • Hero Member
  • *****
  • Posts: 1152
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #7 on: November 27, 2008, 09:10:12 am »
AFAIK
1.2.1 based on 7.0 Release
2.0 7.0 stable becoming 7.1
Anyways you could look for yourself :) http://www.freebsd.org/releases/
I guess it it's poor luck that it work's in 1.2  
/Perry
doc.pfsense.org

Offline hexa

  • Jr. Member
  • **
  • Posts: 73
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #8 on: November 27, 2008, 09:30:24 am »
In case anyone needs this:

# pciconf -lv
hostb0@pci0:0:0:0:   class=0x060000 card=0x81ce1043 chip=0x03271106 rev=0x00 hdr=0x00
    class      = bridge
    subclass   = HOST-PCI
hostb1@pci0:0:0:1:   class=0x060000 card=0x00000000 chip=0x13271106 rev=0x00 hdr=0x00
    class      = bridge
    subclass   = HOST-PCI
hostb2@pci0:0:0:2:   class=0x060000 card=0x00000000 chip=0x23271106 rev=0x00 hdr=0x00
    class      = bridge
    subclass   = HOST-PCI
hostb3@pci0:0:0:3:   class=0x060000 card=0x00000000 chip=0x33271106 rev=0x00 hdr=0x00
    class      = bridge
    subclass   = HOST-PCI
hostb4@pci0:0:0:4:   class=0x060000 card=0x00000000 chip=0x43271106 rev=0x00 hdr=0x00
    class      = bridge
    subclass   = HOST-PCI
ioapic0@pci0:0:0:5:   class=0x080020 card=0x00000000 chip=0x53271106 rev=0x00 hdr=0x00
    class      = base peripheral
    subclass   = interrupt controller
hostb5@pci0:0:0:6:   class=0x060000 card=0x00000000 chip=0x63271106 rev=0x00 hdr=0x00
    class      = bridge
    subclass   = HOST-PCI
hostb6@pci0:0:0:7:   class=0x060000 card=0x00000000 chip=0x73271106 rev=0x00 hdr=0x00
    class      = bridge
    subclass   = HOST-PCI
pcib1@pci0:0:1:0:   class=0x060400 card=0x00000000 chip=0xb1981106 rev=0x00 hdr=0x01
    class      = bridge
    subclass   = PCI-PCI
pcib2@pci0:0:2:0:   class=0x060400 card=0xc3231106 chip=0xa3271106 rev=0x00 hdr=0x01
    class      = bridge
    subclass   = PCI-PCI
pcib3@pci0:0:3:0:   class=0x060400 card=0xc3231106 chip=0xc3271106 rev=0x00 hdr=0x01
    class      = bridge
    subclass   = PCI-PCI
atapci0@pci0:0:15:0:   class=0x010400 card=0x81cf1043 chip=0x05911106 rev=0x80 hdr=0x00
    class      = mass storage
    subclass   = RAID
atapci1@pci0:0:15:1:   class=0x01018a card=0x81cf1043 chip=0x05711106 rev=0x07 hdr=0x00
    class      = mass storage
    subclass   = ATA
uhci0@pci0:0:16:0:   class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0xa0 hdr=0x00
    class      = serial bus
    subclass   = USB
uhci1@pci0:0:16:1:   class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0xa0 hdr=0x00
    class      = serial bus
    subclass   = USB
uhci2@pci0:0:16:2:   class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0xa0 hdr=0x00
    class      = serial bus
    subclass   = USB
uhci3@pci0:0:16:3:   class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0xa0 hdr=0x00
    class      = serial bus
    subclass   = USB
ehci0@pci0:0:16:4:   class=0x0c0320 card=0x31041106 chip=0x31041106 rev=0x86 hdr=0x00
    class      = serial bus
    subclass   = USB
isab0@pci0:0:17:0:   class=0x060100 card=0x81cf1043 chip=0x33371106 rev=0x00 hdr=0x00
    class      = bridge
    subclass   = PCI-ISA
hostb7@pci0:0:17:7:   class=0x060000 card=0x337e1106 chip=0x287e1106 rev=0x00 hdr=0x00
    class      = bridge
    subclass   = HOST-PCI
pcib4@pci0:0:19:0:   class=0x060400 card=0xb57ffbf7 chip=0x337b1106 rev=0x00 hdr=0x01
    class      = bridge
    subclass   = PCI-PCI
pcib5@pci0:0:19:1:   class=0x060401 card=0xff7777bd chip=0x337a1106 rev=0x00 hdr=0x01
    class      = bridge
    subclass   = PCI-PCI
vgapci0@pci0:2:0:0:   class=0x030000 card=0x01741043 chip=0x71871002 rev=0x00 hdr=0x00
    class      = display
    subclass   = VGA
vgapci1@pci0:2:0:1:   class=0x038000 card=0x01751043 chip=0x71a71002 rev=0x00 hdr=0x00
    class      = display
em0@pci0:5:3:0:   class=0x020000 card=0x13768086 chip=0x107c8086 rev=0x05 hdr=0x00
    class      = network
    subclass   = ethernet
em1@pci0:5:4:0:   class=0x020000 card=0x13768086 chip=0x107c8086 rev=0x05 hdr=0x00
    class      = network
    subclass   = ethernet
em2@pci0:5:5:0:   class=0x020000 card=0x13768086 chip=0x107c8086 rev=0x05 hdr=0x00
    class      = network
    subclass   = ethernet
em3@pci0:5:6:0:   class=0x020000 card=0x13768086 chip=0x107c8086 rev=0x05 hdr=0x00
    class      = network
    subclass   = ethernet
re0@pci0:5:7:0:   class=0x020000 card=0x816710ec chip=0x816710ec rev=0x10 hdr=0x00
    class      = network
    subclass   = ethernet


Offline Tikimotel

  • Full Member
  • ***
  • Posts: 157
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #9 on: November 27, 2008, 11:56:27 am »
I have the same issue with realtek 8110SC chips. (integrated into mini-itx board, J7F4K1G2E (7W / Fanless) )
After reboots. (31-aug-2008 1.2.1RC1 release worked fine.)
Usually the DHCP client (internet/WAN) will get a ip and "works".
Then the LAN gets/sets it's IP to "192.168.0.1" (dhcpserver for LAN).
But I can not make contact with my pfSense box, not even a renew ip.
Choosing the " 2)  Set LAN IP address" option and setting it up again solves this connection problem.

Offline sullrich

  • Hero Member
  • *****
  • Posts: 5110
  • Karma: +3/-0
    • View Profile
    • pfSense
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #10 on: November 27, 2008, 01:09:20 pm »
Is there any reasons you cannot use Intel nics?  we do not recommend using realtek.

Offline hexa

  • Jr. Member
  • **
  • Posts: 73
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #11 on: November 28, 2008, 03:25:07 am »
O.K. then. :-) As you developers say. I'll have to sync the firewalls over the LAN interface now thou. If i remember correctly separate interface was recommended.
1. WAN (x/29, ab/24)
2. LAN
3. SERV (NATED a/25)
4. SERV2 (ROUTED b/25)

See here for more info.
http://forum.pfsense.org/index.php/topic,12794.0.html

Offline Gloom

  • Full Member
  • ***
  • Posts: 208
  • Karma: +0/-0
    • View Profile
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #12 on: November 28, 2008, 08:12:41 am »
It ain't listed as support in re(4) not even current
ifconfig re0 -tso is one thing you could try next would be to upgrade to pfsense 2.0 as it's based on 7.0 stable

Just to clarify my original post and slightly off topic, as it does not solve the problem but current is FreeBSD 8 (Has the patch) Release is 7.0 (No patch) The upcomming 7.1 release should have the patch, so I think the only hope you have is to wait for pfsense 2. 
Never underestimate the power of human stupidity

Offline cmb

  • Administrator
  • Hero Member
  • *****
  • Posts: 6333
  • Karma: +0/-0
    • LinkedIn
    • Twitter
    • View Profile
    • Chris Buechler
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #13 on: November 28, 2008, 01:45:43 pm »
That's a driver regression, sounds like it's been fixed in newer FreeBSD versions. Nothing we can do about it. You can force the interface to stay in promiscuous mode by using shellcmd with 'ifconfig re0 promisc'. I'm sure that's why tcpdump makes it work.


Offline sullrich

  • Hero Member
  • *****
  • Posts: 5110
  • Karma: +3/-0
    • View Profile
    • pfSense
Re: 1 critical bug with 1.2.1-RC2 and one harmless problem
« Reply #14 on: November 28, 2008, 04:17:03 pm »
Which patch are you talking about?  Please provide me a link to it.