Issue with adding default route

Hi All,

I am having some issues in adding default route.
The output of route command do not show any default route entry.
when i issue the command
route add default gw 192.168.1.1 dev ath0
i get an error
SIOCADDRT: No such process

Also when i say
route add default gw 192.168.1.1
then i get a default route entry but the device under IFace is vmnet1

I guess it happens because i use VMWare. My router is at 192.168.1.1 and i can ping this ip.

Is there any way i can make it associate with ath0 as that would help me route packets correctly.

Can anyone help me here as I searched a lot and tried many things but nothing seems to be working.

On Wed, 20 Aug 2008 03:16:02 GMT
Shadow Fax <Shadow_Fax@no-mx.forums.opensuse.org> wrote:

>
> Hi All,
>
> I am having some issues in adding default route.
> The output of route command do not show any default route entry.
> when i issue the command
> route add default gw 192.168.1.1 dev ath0
> i get an error
> SIOCADDRT: No such process
>
>
> Also when i say
> route add default gw 192.168.1.1
> then i get a default route entry but the device under IFace is vmnet1
>
> I guess it happens because i use VMWare. My router is at 192.168.1.1
> and i can ping this ip.
>
> Is there any way i can make it associate with ath0 as that would help
> me route packets correctly.
>
> Can anyone help me here as I searched a lot and tried many things but
> nothing seems to be working.
>
>

Is this from the host side or the client side of VMWare?

What is the name of your ethernet connection? eth0? ath0?

vmnet1 is usually the network connection for the VMWare client… don’t want
it going there.

Do you currently have a valid connection to your network? Is ath0
connected? Is eth0 connected?

if so, then:

route add default gw 192.168.1.1

should choose the proper device automatically.

Need some more information to help with this one.

Loni


L R Nix
lornix@lornix.com

This is just a guess based on what you said… but it looks like you are trying to access ath0 from within the virtual machine, you can’t do this. You can only access the virtual network cards created on the VM host.

Another important thing to note is that if you are using WEP or WPA, they’ll need to be configured and working on the VM host before your VM will be able to access the network.