Hi; I would like to ask to the inverse especialists like Francois, Olivier to help me with this and also ask for patience. I really appreciate your help and time spent and for that thanks in advance.
I am still having problems with this NIC / MAC issue. I really dont know what is wrong within the configuration. I looked as Francois said : >> You should be able to see the MAC address in the VM properties in VMWare >> Workstation And in any window in VM properties in workstation we can see the MAC address that the virtual ethernet is using. Using workstation 7.1.3 nothing about it. There isnt anything regarding this, only about the network mode like NAT / bridge etc. But in the centos guest PF image I issued the ifconfig command and there I can see the MAC of the eth0 /eth1/eth2 so as the same to see the mac in centos host system. My question is what next? what I have to do? Lets put some fake MAC for an example: eth0 (VM) (00:1c:24:30:35:45) --> vmnet0 --> eth0 (host) (00:1B:24:98:02:29) eth1 (VM) (00:1c:24:30:35:30) --> vmnet1 --> eth0.2 (host) (doesnt appear an MAC in ifconfig should I put in ifcfg-eth0.2 an mac there if line HWADDR=????) eth2 (VM) (00:1c:24:30:35:1f ) --> vmnet2 --> eth0.3 (host)) (doesnt appear an MAC in ifconfig the same issue) I understand that in workstation network editor config window I should carelly match choosing dev/vmnet0 to bridge to the eth0 in the vmnet information tab so the same doing to the others interfaces. dev/vmnet1 to eth0.2 and dev/vmnet2 to eth0.3. If it is only this then I did it ok and there is this network problem where I cant ping vlans 2 and 3 only able to ping eth0 (VM). But If I am missing something in the middle like there is a MAC especific of this dev/vmnet0 for example? and I have to put it in somewhere I dont know how to see it. At this time I think you already know whats going on. Must be simple and I cant see it...I must be confusing something there. Again I appreciate your help. Jose. ----- Original Message ----- From: "Olivier Bilodeau" <[email protected]> To: <[email protected]> Sent: Thursday, January 20, 2011 12:25 PM Subject: Re: [Packetfence-users] Network problem Hi Adi, > 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… > For the record: this is not true. In our own lab where we have a lot of different switches and several PacketFence servers we don't even have ONE PacketFence server connected to a gigabit port. If you are doing traffic monitoring (snort) on a big uplink then you can reach the 100Mbps limit but, from what I understand of José's setup, it is not the case. Sorry but it's not going to be this easy ;) -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: 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 ------------------------------------------------------------------------------ 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
