HI. Jose..

 

Perhaps you NIC is not Gigabit Ethernet ? I don't know what is the correlation 
with Network Problem,but in my experience PF need gigabit Ethernet...

 

CMIIW :-) 

 

Regards,

Adi Ariyanto

 "Don't tell your GOD how big is your problem, but tell your problem how BIG is 
your GOD"

________________________________

From: José Carlos França Jr [mailto:[email protected]] 
Sent: Thursday, January 20, 2011 2:39 AM
To: [email protected]
Subject: Re: [Packetfence-users] Network problem

 

Francois,

 

I am using the version 1.9 of PF ZEN.

Let me see if I understand what you are saying.

 

>> Make sure the MAC addresses of the vmnet interfaces are the right ones in 
>> your VM networks config for eth0, eth1 and eth2.

You mean I need to put in the gui of vmware that:

dev/vmnet0 is bridged with eth0(host)

dev/vmnet1 is bridged with eth0.2(host)

dev/vmnet2 is bridged with eth0.3(host)

 

thats it?? how can I be sure that I am using the right ones MAC? Do I have to 
specify or copy any MAC to any interface?

 

>> Also, the host interfaces NEEDS to have an IP on the VLANs as well, so 
>> eth0.2 needs to have an IP in the registration VLAN, and eth0.3 needs to 
>> have an IP in the Isolation VLAN.  This is mandatory.

That I understand and already provided. Like eth0.2 = 192.168.2.2 and eth0.3 = 
192.168.3.2 so thats OK.

 

 

 

         

        ----- Original Message ----- 

        From: Francois Gaudreault <mailto:[email protected]>  

        To: [email protected] 

        Cc: José Carlos França Jr <mailto:[email protected]>  

        Sent: Wednesday, January 19, 2011 4:32 PM

        Subject: Re: [Packetfence-users] Network problem

         

        Jose,
        
        Are you using ZEN 1.9 or ZEN 2.0? Try using vmnet1 and vmnet2 instead 
of vmnet2 and vmnet3.
        
        So:
        eth0 (VM) --> vmnet0 --> eth0 (host)
        eth1 (VM) --> vmnet1 --> eth0.2 (host)
        eth2 (VM) --> vmnet2 --> eth0.3 (host)
        
        Make sure the MAC addresses of the vmnet interfaces are the right ones 
in your VM networks config for eth0, eth1 and eth2.  Also, the host interfaces 
NEEDS to have an IP on the VLANs as well, so eth0.2 needs to have an IP in the 
registration VLAN, and eth0.3 needs to have an IP in the Isolation VLAN.  This 
is mandatory.
        
        Again, if you are not able to ping your VM from your host on VLAN 2, 
the problem is in your VMWare.
        
        On 11-01-19 10:50 AM, José Carlos França Jr wrote: 

        HI Francois;

        I can ping from my host to the interface of the vlans 2 and 3 as well. 
But this is expected I think I am pinging myself with this. 

        So the problem must be on the bridge. I am attaching a snapshot of the 
vmware config so you can tell me if it is right.

        If the problem is on the bridge what can I do now?

         

        Thanks a lot for your help.

        Jose

                ----- Original Message ----- 

                From: José Carlos França Jr <mailto:[email protected]>  

                To: Francois Gaudreault <mailto:[email protected]>  

                Sent: Wednesday, January 19, 2011 12:37 PM

                Subject: Re: [Packetfence-users] Network problem

                 

                HI Francois;

                I can ping from my host to the interface of the vlans 2 and 3 
as well. But this is expected I think I am pinging myself with this. 

                So the problem must be on the bridge. I am attaching a snapshot 
of the vmware config so you can tell me if it is right.

                If the problem is on the bridge what can I do now?

                 

                Thanks a lot for your help.

                Jose

                 

                        ----- Original Message ----- 

                        From: Francois Gaudreault 
<mailto:[email protected]>  

                        To: [email protected] 

                        Cc: José Carlos França Jr <mailto:[email protected]> 
 

                        Sent: Wednesday, January 19, 2011 12:06 PM

                        Subject: Re: [Packetfence-users] Network problem

                         

                        Hi Jose,
                        
                        Can you ping something on VLAN2 and VLAN3 from your 
host (not your VM) ?  If the host cannot ping anything, the VM won't be able to 
as well.
                        
                        If the bridge between the VM and the Host is done 
properly, you should be able to ping the host from the VM, and the VM from the 
host.  You might try that as well.
                        
                        On 11-01-19 8:58 AM, José Carlos França Jr wrote: 

                        Hi everybody; 
                        I`m attaching every configuration file in this email. I 
dont know whats going on. 
                        Running HOST = CENTOS 5.5 final with workstation 7 with 
PF ZEN image on a notebook linked to uplink port 24 (trunk port) on a cisco 
2950. 
                        I ran the /usr/local/pf/test/connect_and_read.pl and 
all came ok no errors. 
                        
                        I`m having problem with my network. Everything seems 
properly configured. All NIC is mounted. I cant ping the vlan interfaces. 
                        
                        Created ifcfg-eth0.2 / ifcfg-eth0.3 correctly. 
                        VMware eth0/eth1/eth2 is linked to /dev/vmnet0, 
/dev/vmnet2 and /dev/vmnet3 all 3 put in bridged mode with host NICS. 
                        
                        My IPs: 
                        
                        eth0 (VLAN1) --> eth0 on your host 
                        192.168.67.10            192.168.67.2 
                        
                        I can ping from 192.168.67.2 to 192.168.67.10 ok 
                        
                        eth1 (VLAN2) --> eth0.2 on your host 
                        192.168.2.10                192.168.2.2 
                        
                        CANT PING - Destination host unreachable 
                        
                        eth2 (VLAN3) --> eth0.3 on your host 
                        192.168.3.10                192.168.3.2 
                        
                        CANT PING - Destination host unreachable 
                        
                        
                        I would apreciate any help. 
                        Jose. 

                         
                        
------------------------------------------------------------------------------
                        Protect Your Site and Customers from Malware Attacks
                        Learn about various malware tactics and how to avoid 
them. Understand 
                        malware threats, the impact they can have on your 
business, and how you 
                        can protect your company and customers by using code 
signing.
                        http://p.sf.net/sfu/oracle-sfdevnl
                         
                        _______________________________________________
                        Packetfence-users mailing list
                        [email protected]
                        
https://lists.sourceforge.net/lists/listinfo/packetfence-users

                        
                        
                        
                        

                        -- 
                        Francois Gaudreault, ing. jr
                        [email protected]  ::  +1.514.447.4918 (x130) ::  
www.inverse.ca
                        Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and 
PacketFence (www.packetfence.org) 

         
        
------------------------------------------------------------------------------
        Protect Your Site and Customers from Malware Attacks
        Learn about various malware tactics and how to avoid them. Understand 
        malware threats, the impact they can have on your business, and how you 
        can protect your company and customers by using code signing.
        http://p.sf.net/sfu/oracle-sfdevnl
         
        _______________________________________________
        Packetfence-users mailing list
        [email protected]
        https://lists.sourceforge.net/lists/listinfo/packetfence-users

        
        
        
        

        -- 
        Francois Gaudreault, ing. jr
        [email protected]  ::  +1.514.447.4918 (x130) ::  www.inverse.ca
        Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence 
(www.packetfence.org) 


The above message is for the intended recipient only and may contain 
confidential information and/or may be subject to legal privilege. If you are 
not the intended recipient, you are hereby notified that any dissemination, 
distribution, or copying of this message, or any attachment, is strictly 
prohibited. If it has reached you in error please inform us immediately by 
reply e-mail or telephone, reversing the charge if necessary. Please delete the 
message and the reply (if it contains the original message) thereafter. Thank 
you.
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to