they really should not be... (but in a sense they are) they are all connected to the same netgear switch with different vlan's (port based, not q)
1 Default 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 2 ISP1 01 03 05 3 ISP2 02 04 4 MONITOR 06 (had no vlan before at all on 6, but added one just to be sure) monitored ports are 03 04 05 -> 06 (monitor port) incoming ethernet isp1 is connected to 01 isp2 is connected to 02 physical firewalls FW1 is connected to 03 FW2 is connected to 04 pfsense hme3 is connected to 05 hme2 is connected to 06 hme0 is connected to 07 did a clean reinstall today (and it seems stable (crashed with small traffic load before)) (unlikely since it was a clean install before aswell) changes done... vlan for monitor port (think this did it?, not sure how netgear handles a non-vlan port in this config???) clocked cpu from 500 (66x7.5) to 1000 (133x7.5) (guess this could be it, but unlikely? will verify later) theese still pops up though (will turn off arp later on) Dec 20 09:37:43 last message repeated 177 times Dec 20 09:35:43 last message repeated 39 times Dec 20 09:35:12 kernel: arp: 83.176.208.1 is on hme3 but got reply from 00:50:0b:3e:e4:1a on hme2 // Johan ps. over a gig of data pushed through it... and it still works (crashed on mb's before...) "Fuchs, Martin" <[EMAIL PROTECTED]> 2006-12-20 10:01 Please respond to support@pfsense.com To <support@pfsense.com> cc Subject AW: [pfSense Support] NTOP coredumped!? sounds like all cards are running on the same psysical netword ? turn off arp-messages in advanced options... Martin Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 20. Dezember 2006 07:25 An: support@pfsense.com Betreff: [pfSense Support] NTOP coredumped!? trying out pfsense for real now at home and run into a small problem using Sun HME quad ethernet card Intel P3 500E / 512mb hme0 = LAN hme2 = MON (connected to monitor port in my switch) hme3 = WAN i guess it can be the hme drivers? had some problem in alpha / beta stadium with lost connection over time... but really like it :/ Dec 20 06:17:22 kernel: hme2: promiscuous mode disabled Dec 20 06:17:22 kernel: pid 788 (ntop), uid 0: exited on signal 11 (core dumped) Dec 20 06:17:22 last message repeated 113 times Dec 20 06:16:16 last message repeated 55 times Dec 20 06:15:45 kernel: arp: 83.176.208.1 is on hme3 but got reply from 00:50:0b:3e:e4:1a on hme2 Dec 20 06:15:43 kernel: arp: 83.176.209.70 is on hme3 but got reply from 00:90:7f:14:d6:9e on hme2 Dec 20 06:15:43 last message repeated 56 times Dec 20 06:15:23 last message repeated 73 times Dec 20 06:14:52 kernel: arp: 83.176.208.1 is on hme3 but got reply from 00:50:0b:3e:e4:1a on hme2 Best Regards // Johan
