Posted: Wed Oct 29, 2008 21:20 Post subject: VMware setup with dd-wrt x86
I am able to get the image to work and I do get the console and I can login but I can't get to the web gui. There is an error in the console saying "eth0: No such process"
In the console I gave eth0 an IP address and a drstaddr and still it doesn't work. I must be missing a step. Is there a sticky on the exact steps to get this to work? I have read some posts here with similar problems but nobody seemed to explain how they corrected it.
Thanks for your time.
Joined: 21 Jul 2006 Posts: 1898 Location: Fortaleza Ce Brazil
Posted: Thu Oct 30, 2008 20:43 Post subject:
U must link ethernet to another computer or a switch , after that do a repair in the conection ( windows ) .. after u get the ip giving by dhcp of x86 ;;; u can webgui it . ( 192.168.1.1 )
_________________ DDwrt ...it rocks ....
1 R7800 54420 AP Wireguard webserver JFFS SAMBA FTP usb HD Mesh
1 R7800 54420 Cli Mesh
1 WZR1750 54389 AP Webserver Samba Wireguard
1 TP link Archer C7v5 54420 Cli Mesh
1 DD x86_64 48296 Gateway Samba Ftp Webserver
Update:
I tried again and it now seems to be working. I tried everything before and no go but now it works. It's weird. I didn't change anything. Thanks for everyones help.
Ok here is an update:
I have the LAN side working but I can't seem to get the WAN side working. Do I just bind say vmnet0 to one physical adapter and vmnet1 to the other physical adapter? Or do I have to assign one as a NAT and the other as a host (or kept as a bridge)? Do I even use the Virtual Network Editor? I am slightly confused again.
I got the WAN and the LAN to work now. Apparently, just bridging the 2 adapters in workstation wasn't enough. By doing so, they are both in the same subnet. My WAN port kept getting an IP from the routers internal DHCP. Hosting and Nating in Vmware's setup didn't work either since the router should do that for you within the image.
The way I got it to work was that I had to force bridge by choosing "Custom virtual networks" and bridging eth1 to vmnet1 and eth0 to vmnet0 (or what ever labels you have for each virtual connections).
This round about way may not be the best way but it worked for me.
