• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

arp tables and network interfaces

darrenster

Weaksauce
Joined
Nov 28, 2009
Messages
99
strange vm issue:

I'm trying to configure Vyatta in Vmware 6.5 with 5 Ethernet interfaces.

Within Vyatta the interfaces are configured as followed:
eth0 192.168.10.2/24 00:0c:29:59:7b:1d
eth1 192.168.10.3/24 00:0c:29:59:7b:27
eth2 192.168.10.4/24 00:0c:29:59:7b:31
eth3 192.168.10.5/24 00:0c:29:59:7b:3b
eth4 192.168.10.6/24 00:0c:29:59:7b:45

in Vmware, i have the 5 Ethernet interfaces assigned as followed:
network interface 1 -> VMnet1
network interface 2 -> VMnet2
network interface 3 -> VMnet3
network interface 4 -> VMnet4
network interface 5 -> VMnet5

in the VMware network editor, i have VMnet1 bridged to an Ethernet jack on my desktop in which i have my laptop connected to. In the network editor, i have turned off NAT and the DHCP functions.
the laptop ip address is 192.168.10.20

im trying to figure out which network interface in vmware corresponds to which eth interface within vyatta

i have my laptop pinging each of the 5 ip address as listed above thinking the one who responds will be the eth assigned to the vm network interface

however, they all responds to network interface 1. on the laptop when i type "arp -a" the arp table states that each ip address links to 00:0c:29:59:7b:1d

there seems to be some sort of linking issue here and i can not figure it out... does anyone have any ideas of what is going on here????

Thanks!
 
vmware, meaning vmware workstation, or...?

VMware is a company, not a product ;)
 
vmware workstation, of course not the company....

Anyways, I think i have figured it out. I dont know how or why it worked this way, but i guess it had something to do with the fact that each interface was on the same subnet. after changing the ip address to separate subnet, it worked as it supposed to.
 
strange vm issue:

I'm trying to configure Vyatta in Vmware 6.5 with 5 Ethernet interfaces.

Within Vyatta the interfaces are configured as followed:
eth0 192.168.10.2/24 00:0c:29:59:7b:1d
eth1 192.168.10.3/24 00:0c:29:59:7b:27
eth2 192.168.10.4/24 00:0c:29:59:7b:31
eth3 192.168.10.5/24 00:0c:29:59:7b:3b
eth4 192.168.10.6/24 00:0c:29:59:7b:45

in Vmware, i have the 5 Ethernet interfaces assigned as followed:
network interface 1 -> VMnet1
network interface 2 -> VMnet2
network interface 3 -> VMnet3
network interface 4 -> VMnet4
network interface 5 -> VMnet5

in the VMware network editor, i have VMnet1 bridged to an Ethernet jack on my desktop in which i have my laptop connected to. In the network editor, i have turned off NAT and the DHCP functions.
the laptop ip address is 192.168.10.20

im trying to figure out which network interface in vmware corresponds to which eth interface within vyatta

i have my laptop pinging each of the 5 ip address as listed above thinking the one who responds will be the eth assigned to the vm network interface

however, they all responds to network interface 1. on the laptop when i type "arp -a" the arp table states that each ip address links to 00:0c:29:59:7b:1d

there seems to be some sort of linking issue here and i can not figure it out... does anyone have any ideas of what is going on here????

Thanks!

Well since you have all the IP's in the same subnet, there is only 1 routing table. So if you do a 'route print', it will show you the default interface.
 
Back
Top