HI Kerry; Thanks a lot for your help. I will check your idea.
Once more, thanks. Jose. ----- Original Message ----- From: "Melcher, Kerry" <[email protected]> To: <[email protected]> Sent: Monday, January 24, 2011 2:55 PM Subject: Re: [Packetfence-users] Network problem Hi Jose, I think you maybe having the same trouble that I had when trying to run a desktop PC NIC on a trunk interface. The network switch trunk terminates at the PC physical NIC so the PC physical NIC driver has to know how to do trunking and VLAN packet tagging. Check to see if the physical NIC you are using has a driver that will do VLANs. The PC that I was using didn't. This is what I had to do: 1. I changed the hardware I was testing with to one of my spare servers that had a physical NIC and NIC driver that understood VLANs. 2. In the Vmware network config I assigned each VM NIC to a separate VLAN on the physical NIC. 3. In PF I configured each PF interface to a single VM NIC instead of doing sub interfaces. Thank You, Kerry Melcher -----Original Message----- From: José Carlos França Jr [mailto:[email protected]] Sent: Saturday, January 22, 2011 2:21 PM To: [email protected] Subject: Re: [Packetfence-users] Network problem HI Francois; everybody; After a lot of testing I concluded that my problem is only at the bridge of vmware. I`m sure. Its not bridging even althought I configured and matched up all interfaces carefully. I can ping from 192.168.67.2 to 192.168.67.10 all OK. NOT Pinging from 192.168.2.2 to 192.168.2.10 with the same kind of configuration of the above. Checked up config eth files everything its ok but cant ping. Why the above can ping and this not? The same for 192.168.3.2 to 192.168.3.10 cant ping. Now I`m filling with my hands tied. Any ideas? Thanks for any suggestion Jose. ----- Original Message ----- From: "Francois Gaudreault" <[email protected]> To: <[email protected]> Cc: "José Carlos França Jr" <[email protected]> Sent: Friday, January 21, 2011 12:33 PM Subject: Re: [Packetfence-users] Network problem > Hi Jose, > > Maybe you should try to remove or disable the bridging, and rebuild it > again. I see this issue in VMWare Fusion sometimes. Also, can you see > the mac addresses of each VM interface on the switch port using "sh mac > address-table"? Are they in the proper VLAN? > > Also, do you have iptables running on your host? Disable any kind of > firewall on your host (and on the VM), that could prevent the setup > working. > > On 11-01-20 11:12 AM, José Carlos França Jr wrote: >> 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 ;) > > > -- > 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) > ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
