internet connection - lan/wlan

I'm new to Linux so please bear with me. I've installed Linux 10 on my
compaq v2555 laptop. Everything went smoothly. I would like to access the
internet wireless through a Dlink DWL-650 wireless PCMCIA card. Suse
detected the card and installed the appropriate package for it.

My problem is that for some reason, I'm unable to connect wireless when I
boot up the computer. However, if I connect through the wired connection
first and then disconnect that connection and connect the wireless card,
then I can connect wireless without any problems. I suspect it had
something to do with the DNS. Is there some configuration that I need to
set? The wireless card is set for automatic DHCP.
Thanks for the help.

infinitedarkness@gmail.com wrote:
> I'm new to Linux so please bear with me. I've installed Linux 10 on my
> compaq v2555 laptop. Everything went smoothly. I would like to access the
> internet wireless through a Dlink DWL-650 wireless PCMCIA card. Suse
> detected the card and installed the appropriate package for it.
>
> My problem is that for some reason, I'm unable to connect wireless when I
> boot up the computer. However, if I connect through the wired connection
> first and then disconnect that connection and connect the wireless card,
> then I can connect wireless without any problems. I suspect it had
> something to do with the DNS. Is there some configuration that I need to
> set? The wireless card is set for automatic DHCP.
> Thanks for the help.

SUSE and wireless is a common thread starter. you might want to first
try a comprehensive resource.

http://en.opensuse.org/SDB%3AWireles...ith_SuSE_Linux

things that i discovered. configuring wlan settings in yast, kinternet
and kwifimanager are not interchangable eventhough they seem like that
all do the same thing.

try yast first. if it gives probs, then try one of the others and stick
to the one that works better with your hardware setup.


--
Cheers,
dg

''~``
( o o )
+------------------.oooO--(_)--Oooo.------------------+
| UofT AGAINST-TCPA |
| www.utoronto.ca .oooO www.againsttcpa.com |
| velut arbor aevo ( ) Oooo. |
+---------------------\ (----( )--------------------+
\_) ) /
(_/

> I'm new to Linux so please bear with me. I've installed Linux 10 on my
> compaq v2555 laptop. Everything went smoothly. I would like to access the
> internet wireless through a Dlink DWL-650 wireless PCMCIA card. Suse
> detected the card and installed the appropriate package for it.
>
> My problem is that for some reason, I'm unable to connect wireless when I
> boot up the computer. However, if I connect through the wired connection
> first and then disconnect that connection and connect the wireless card,
> then I can connect wireless without any problems. I suspect it had
> something to do with the DNS. Is there some configuration that I need to
> set? The wireless card is set for automatic DHCP.
> Thanks for the help.

Try setting the card to "wireless" in Yast. Normally it will be dealt with
as aethernet device. It worked fine on my old Compaq M700. So give it a try.

I have two profiles on my laptop:

1) sets eth0 to dhcp and has the wireless card unconfigured

2) sets eth0 to a fixe IP and turns on the wireless configured with dhcp

This works great for going from work (1) to home (2) or internet cafe (2)


However, just noticed today that while in (1), ifconfig shows the dhcp
obtained address - and I can certainly see that on the network from
another machine - but the laptop also still shows up as the fixed IP
address from the other profile!

Now, I certainly remember the last time I fired the laptop up on the
work network, I was in the 'other' profile, so I did an scpm switch
command - but this persists thru a power cycle!

So, I can ssh to the laptop thru the dhcp aquired address OR the
supposedly non-existant fixed IP (it is unfortunate I guess that both
home and work use the 192.168.1 convention.

This make sense to anyone?

And I doubt it makes much difference, but this is an up-to-date 9.3
installation on an HP ze1230 Pavillion with a Linksys DWL-G650 pcmcia
wireless card.

I am stumped, to say the least....

TIA

Timothy J. Bogart adjusted his/her tinfoil beanie to post:

> I have two profiles on my laptop:


Bear with me here Timothy ( the caffeine is just kicking in )

>
> 1) sets eth0 to dhcp and has the wireless card unconfigured

>
> 2) sets eth0 to a fixe IP and turns on the wireless configured with
> dhcp

So both nics ( wired and wireless ) are activated at the same time, but
only the wireless is used, even when the wired is not plugged in?


>
> This works great for going from work (1) to home (2) or internet cafe
> (2)
>
>
> However, just noticed today that while in (1), ifconfig shows the dhcp
> obtained address - and I can certainly see that on the network from
> another machine - but the laptop also still shows up as the fixed IP
> address from the other profile!
>
> Now, I certainly remember the last time I fired the laptop up on the
> work network, I was in the 'other' profile, so I did an scpm switch
> command - but this persists thru a power cycle!
>
> So, I can ssh to the laptop thru the dhcp aquired address OR the
> supposedly non-existant fixed IP (it is unfortunate I guess that both
> home and work use the 192.168.1 convention.
>
> This make sense to anyone?

Yep you can have more than one IP on the same interface ( virtual IP`s )


can you post the results of ifconfig when in both (1) and (2) profiles
please?

( should not make much difference but just so we know what is there)


--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

baskitcaise wrote:
> Timothy J. Bogart adjusted his/her tinfoil beanie to post:
>
>> I have two profiles on my laptop:
>
>
> Bear with me here Timothy ( the caffeine is just kicking in )
>
>> 1) sets eth0 to dhcp and has the wireless card unconfigured
>
>> 2) sets eth0 to a fixe IP and turns on the wireless configured with
>> dhcp
>
> So both nics ( wired and wireless ) are activated at the same time, but
> only the wireless is used, even when the wired is not plugged in?

Wired is used in home network - no wireless signal there.

Wireless is use at an internet cafe where I don't plug in
>
>
>> This works great for going from work (1) to home (2) or internet cafe
>> (2)
>>
>>
>> However, just noticed today that while in (1), ifconfig shows the dhcp
>> obtained address - and I can certainly see that on the network from
>> another machine - but the laptop also still shows up as the fixed IP
>> address from the other profile!
>>
>> Now, I certainly remember the last time I fired the laptop up on the
>> work network, I was in the 'other' profile, so I did an scpm switch
>> command - but this persists thru a power cycle!
>>
>> So, I can ssh to the laptop thru the dhcp aquired address OR the
>> supposedly non-existant fixed IP (it is unfortunate I guess that both
>> home and work use the 192.168.1 convention.
>>
>> This make sense to anyone?
>
> Yep you can have more than one IP on the same interface ( virtual IP`s )

Well, yes, but I guess it is the magic of a virtual IP showing up when I
didn't even ask that floored me. Been awhile since I looked, but I
recall you had to sort of ask for something like that. 8-)
>
>
> can you post the results of ifconfig when in both (1) and (2) profiles
> please?
>
> ( should not make much difference but just so we know what is there)
>
>
eth0 Link encap:Ethernet HWaddr 00:C0:9F:0B:68:1F
inet addr:192.168.1.222 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2c0:9fff:fe0b:681f/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5098 errors:0 dropped:0 overruns:0 frame:0
TX packets:6159 errors:3 dropped:0 overruns:3 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1172996 (1.1 Mb) TX bytes:5714418 (5.4 Mb)
Interrupt:11 Base address:0xe800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5838 errors:0 dropped:0 overruns:0 frame:0
TX packets:5838 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6200534 (5.9 Mb) TX bytes:6200534 (5.9 Mb)

I don't have a wireless source handy, but in the other mode it would be
the fixed address of 192.168.1.6 and an ath0 with an address on it were
I in the pressence of the magic EM from a router.

Now, as I recall, if I set up a virtual IP, it should show up as an
eth0:1 ... but I have only seen that on an IPCOP setup, and never did
one under SuSE ... but I would sure expect it to be the same????

Cheers.

Timothy J. Bogart adjusted his/her tinfoil beanie to post:

> baskitcaise wrote:
>> Timothy J. Bogart adjusted his/her tinfoil beanie to post:
>>
>>> I have two profiles on my laptop:
>>
>>
>> Bear with me here Timothy ( the caffeine is just kicking in )
>>
>>> 1) sets eth0 to dhcp and has the wireless card unconfigured
>>
>>> 2) sets eth0 to a fixe IP and turns on the wireless configured with
>>> dhcp

Just a thought Timothy,

Can you not make 3 profiles, one for each occasion?

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

baskitcaise wrote:
> Timothy J. Bogart adjusted his/her tinfoil beanie to post:
>
>> baskitcaise wrote:
>>> Timothy J. Bogart adjusted his/her tinfoil beanie to post:
>>>
>>>> I have two profiles on my laptop:
>>>
>>> Bear with me here Timothy ( the caffeine is just kicking in )
>>>
>>>> 1) sets eth0 to dhcp and has the wireless card unconfigured
>>>> 2) sets eth0 to a fixe IP and turns on the wireless configured with
>>>> dhcp
>
> Just a thought Timothy,
>
> Can you not make 3 profiles, one for each occasion?
>

Well, sure.

I could make 4, with one that does nothing different ... 8-)

Seriously, as an old UNIX guy, doing 2 rather than 3 when it works just
seems right. Besides, whether there are 2 or 3, one of them is going to
leave behind the greyed out static IP.

Or to put another way - there seems to be something wrong with the
profile switching if any profile that has a static IP leaves that static
IP 'lurking' as a virtual IP.

I am just a little confused where to start looking as I am not able to
even see the IP from the OS - only from the outside.

Does that make ANY sense?

Cheers.

Timothy J. Bogart wrote:
> baskitcaise wrote:
>> Timothy J. Bogart adjusted his/her tinfoil beanie to post:
>>
>>> baskitcaise wrote:
>>>> Timothy J. Bogart adjusted his/her tinfoil beanie to post:
>>>>
> IP 'lurking' as a virtual IP.
>
> I am just a little confused where to start looking as I am not able to
> even see the IP from the OS - only from the outside.
>
> Does that make ANY sense?
>
> Cheers.
try
ip addr
instead of
ifconfig to find the alias interfaces

also netstat -anp will show you addresses (and ports) that are being
listened on

Timothy J. Bogart adjusted his/her tinfoil beanie to post:


> Well, sure.
>
> I could make 4, with one that does nothing different ... 8-)
>
> Seriously, as an old UNIX guy, doing 2 rather than 3 when it works
> just
> seems right. Besides, whether there are 2 or 3, one of them is going
> to leave behind the greyed out static IP.
>
> Or to put another way - there seems to be something wrong with the
> profile switching if any profile that has a static IP leaves that
> static IP 'lurking' as a virtual IP.
>
> I am just a little confused where to start looking as I am not able to
> even see the IP from the OS - only from the outside.
>
> Does that make ANY sense?
>
> Cheers.

It does make perfect sense Timothy,

I did not realise that it is only visible from "outside" now forgive me
if this is totally wrong but could this not be down to the routers
internal table remembering the card by MAC when you swap or even the
machine requesting the same IP?

I know this sounds stupid and I am pushed for time but there does seem
something screwy there, that is why I suggest creating completely
separate profiles to narrow down the possibilities.

In the order of 1 each for static and wireless so that there should be
no possibility of a cross over effect.

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp