- Joined
- Mar 31, 2007
- Messages
- 1,895 (0.30/day)
- Location
- ontario canada
System Name | home brew |
---|---|
Processor | Intel Corei7 3770K OC @ 4.5Ghz |
Motherboard | ASUS P8Z77-V |
Cooling | Corsair H100 |
Memory | 16GB DDR3 1600 GSKILL |
Video Card(s) | Powercolor Radeon 7970, MSI Radeon 7970 |
Storage | Mushkin Chronos Deluxe 240gb. 2 TB Hdd. |
Display(s) | 3x24inch Dell Ultra IPS |
Case | CM storm trooper |
Power Supply | Antec Quattro OC ed. 1200w |
Software | Windows 7 Business x64 |
Benchmark Scores | vantage: P43089 |
I have a SuSE host built on an IBM chassis. It has a bond interface for failover. It has an IP address of 10.10.138.196. SM 255.255.255.128. DG 10.10.138.129. I can ping this machine no problem. On this I have a virtual machine of SuSE. It has the same mask and gateway with an IP of 10.10.138.197. It can ping the host (196) and the host can ping it. However, it cannot ping the default gateway .129. It recieves an unreachable message from it's own virtual interface. I have setup bridged networking from the start with no luck.
I tried changing the DG on the guest to .196. I setup default routes, and specific routes to 10.10.138.129 on both the guest and the host with no luck. I have spoken to some collegues and they're not sure either. I need this available so it can be used for a variety of apps.
I posted on Vmware forums, no useful assistance yet. THought I'd try my favourite boards.
I tried changing the DG on the guest to .196. I setup default routes, and specific routes to 10.10.138.129 on both the guest and the host with no luck. I have spoken to some collegues and they're not sure either. I need this available so it can be used for a variety of apps.
I posted on Vmware forums, no useful assistance yet. THought I'd try my favourite boards.