Routing Table and Multiple Interfaces

Typical ME laptop.
Has an Ethernet interface.
I've added a PC Card Wireless interface.

If the ethernet interface isn't disabled, then the wireless card doesn't
work right because the routing table is wrong. Specifically the routing
table has:

255.255.255.255 255.255.255.255 192.168.1.9 192.168.1.9

where 192.168.1.9 is for the wired interface.

Accordingly the wireless interface can't ping out but can be pinged.

If the wired interface is disabled or taken out of the hardware profile,
then this line changes to have the IP address of the wireless interface and
it works.

It weems that hardware profiles is NOT the way to go.... Any other
suggestions?

Thanks,

Fred

In message , Fred Marshall
wrote:

Typical ME laptop.
Has an Ethernet interface.
I've added a PC Card Wireless interface.

If the ethernet interface isn't disabled, then the wireless card doesn't
work right because the routing table is wrong. Specifically the routing
table has:

255.255.255.255 255.255.255.255 192.168.1.9 192.168.1.9

where 192.168.1.9 is for the wired interface.

Accordingly the wireless interface can't ping out but can be pinged.

If the wired interface is disabled or taken out of the hardware profile,
then this line changes to have the IP address of the wireless interface
and it works.

It weems that hardware profiles is NOT the way to go.... Any other
suggestions?

What do you want it to do?

If you want it to use the wired interface whenever it is plugged in, and
wireless interface it isn't, then I suggest you try ensuring that the
option "Detect connection to network media" is set in the propieties of the
wired ethernet card.

If you have some subnets connected to the wired interface, and some
connected to the wireless interface, then adjust the routing table, using
the route command. (Or some 3rd party tool)

Timothy,

Thanks for the reply.

I want to be able to use either the wired or the wireless interface without
a lot of fuss. That means that I should be able to plug in the wireless
interface (only) and have it work.

I originally wanted to assign static IP addresses to the interfaces. This
appears to not be possible.

I want to understand this pretty well as we have a service business that
does this sort of thing.....

OK - so sensing the wired link will update the routing table in ME without
rebooting it seems.... I also have now read that D-Link suggests it *not*
be selected for wireless interfaces - which is what you implied I guess.

All this seems to work.... thanks!

Fred

"Timothy Baldwin" wrote in message
...
In message , Fred Marshall
wrote:

Typical ME laptop.
Has an Ethernet interface.
I've added a PC Card Wireless interface.

If the ethernet interface isn't disabled, then the wireless card doesn't
work right because the routing table is wrong. Specifically the routing
table has:

255.255.255.255 255.255.255.255 192.168.1.9 192.168.1.9

where 192.168.1.9 is for the wired interface.

Accordingly the wireless interface can't ping out but can be pinged.

If the wired interface is disabled or taken out of the hardware profile,
then this line changes to have the IP address of the wireless interface
and it works.

It weems that hardware profiles is NOT the way to go.... Any other
suggestions?

What do you want it to do?

If you want it to use the wired interface whenever it is plugged in, and
wireless interface it isn't, then I suggest you try ensuring that the
option "Detect connection to network media" is set in the propieties of
the
wired ethernet card.

If you have some subnets connected to the wired interface, and some
connected to the wireless interface, then adjust the routing table, using
the route command. (Or some 3rd party tool)