Nuno

Good call - I got my Client onto the switch and checked through the config.  
Sure enough one of the firewalls was plugged into a port that was mapped to a 
different VLAN.  Fixed that and it instantly sprang into life :-)

I am of course kicking myself:
a) Not checking the install thoroughly before I left the datacentre last week
b) Not doing the one obvious thing that would have told me about what was 
happening from remote over the weekend - I could have pinged the other 
firewall across that interface that was causing the problems (or not as it 
transpires) :-(

So - lessons learnt all round.

Now, as to the problem that other people are having with their Intel Pro/1000 
interfaces I am not sure.  Maybe it is the dual/quad nic cards that are iffy?  
My boxen are Portwell comms servers with 4 discrete Gigabit ports on the 
motherboard.

Now that the box is working as planned, it is time to throw the big switch and 
let the data through to really loadtest the system.

Regards

/Peter


On Monday 27 March 2006 18:10, Amorim, Nuno Alexandre (ext) wrote:
> The two switches are connected to each other by a trunk port with all the
> vlans, as a stp failover. The wan vlan was not passing in the trunk.
> Nothing much :)
>
> Making a tcpdump on the interfaces one can see if the advertisements are
> reaching the other node. It sends to a multicast address.
>
> -----Original Message-----
> From: Scott Ullrich [mailto:[EMAIL PROTECTED]
> Sent: segunda-feira, 27 de Março de 2006 16:07
> To: [email protected]
> Subject: Re: [pfSense Support] Carp is a bit confused...
>
> On 3/27/06, Amorim, Nuno Alexandre (ext) <[EMAIL PROTECTED]> 
wrote:
> > I have pfsense working on two SunFire v20z with two dual intel gigabit
> > NIC (copper).
> >
> > I had this similar problem also. First it was wrong netmasks. Then I had
> > some errors in the configuration of the switches (cisco). They were not
> > seeing the advertisements of each other.
>
> What changes did you need to make in the ciscos if you dont mind me asking?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to