1 critical bug with 1.2.1-RC2 and one harmless problem
-
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.
-
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 -
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 -
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. -
Is there any reasons you cannot use Intel nics? we do not recommend using realtek.
-
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 -
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 stableJust 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.
-
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.
-
Which patch are you talking about? Please provide me a link to it.
-
http://people.freebsd.org/~yongari/re/re.HEAD.20080607
But like I said this is a FreeBSD 8 patch AFAIK it should work on RELENG_7 but I know no one who has applied it and I don't have any Realtek cards to test it on.
Pyun YongHyeon Did commit some further changes to this driver, again to 8, in September but I really can't remember what they were for.