Hi,

I have a IBM Thinkpad T23 with an internal WLAN card. The card works; I have
installed the wireless tools package, but something in the configuration is
not good: if I disable the eth0 card (by unplugging the ethernet cable),
and I execute /etc/rc.d/rc.inet1 restart, the wlan seems to be connected,
but:
1. the IP address is 192.168.1.2; I can ping the router 192.168.1.1, but
this is outside the DHCP pool (which starts from .33). and I cannot surf
the internet. but I can surf on the local router configuration web page.
2. I can connect through Samba to a Windows PC in the (W)LAN. and I can
transfer files.
Can anybody give me some hint on where to look to solve this issue?

Another issue is the DHCP client: if the ethernet cable is unplugged, the
system hangs for about 3 minutes at boot time.
Is there a way to avoid that?

Filippo wrote:

> Hi,
>
> I have a IBM Thinkpad T23 with an internal WLAN card. The card works; I
> have installed the wireless tools package, but something in the
> configuration is not good: if I disable the eth0 card (by unplugging the
> ethernet cable), and I execute /etc/rc.d/rc.inet1 restart, the wlan seems
> to be connected, but:
> 1. the IP address is 192.168.1.2; I can ping the router 192.168.1.1, but
> this is outside the DHCP pool (which starts from .33). and I cannot surf
> the internet. but I can surf on the local router configuration web page.
> 2. I can connect through Samba to a Windows PC in the (W)LAN. and I can
> transfer files.
> Can anybody give me some hint on where to look to solve this issue?
>
> Another issue is the DHCP client: if the ethernet cable is unplugged, the
> system hangs for about 3 minutes at boot time.
> Is there a way to avoid that?

About your DHCP client for the network card and the long timeout...
check /etc/rd.c/rc.inet1.conf. I would guess that your ethernet card is
eth0, so USE_DHCP[0]="" will do. I set mine to USE_DHCP[0]="no" to turn it
off. Otherwise it waited a minute.

I cannot tell you much about the wireless card. I have a Lenovo laptop (IBM
of sorts) that runs well. I start it with a routine in KDE, but I'm pretty
sure it can be started with iwconfig... Read the man page for iwconfig.

John.

--
jkherr at power - net dot net (wipe the spaces)

John K. Herreshoff wrote:

> About your DHCP client for the network card and the long timeout...
> check /etc/rd.c/rc.inet1.conf. I would guess that your ethernet card is
> eth0, so USE_DHCP[0]="" will do. I set mine to USE_DHCP[0]="no" to turn
> it
> off. Otherwise it waited a minute.

thanks, but that would not suit me: if I connect the ethernet, I want my pc
to get an address through DHCP, otherwise each time I have to configure my
pc...

> I cannot tell you much about the wireless card. I have a Lenovo laptop
> (IBM
> of sorts) that runs well. I start it with a routine in KDE, but I'm

which one?

Filippo wrote:

> John K. Herreshoff wrote:
>
>> About your DHCP client for the network card and the long timeout...
>> check /etc/rd.c/rc.inet1.conf. I would guess that your ethernet card is
>> eth0, so USE_DHCP[0]="" will do. I set mine to USE_DHCP[0]="no" to turn
>> it
>> off. Otherwise it waited a minute.
>
> thanks, but that would not suit me: if I connect the ethernet, I want my
> pc to get an address through DHCP, otherwise each time I have to configure
> my pc...
>
>> I cannot tell you much about the wireless card. I have a Lenovo laptop
>> (IBM
>> of sorts) that runs well. I start it with a routine in KDE, but I'm
>
> which one?

That's just for the lan card. Your wireless card should still get the IP
through the DHCP server that is broadcast from the wireless router that you
are using.

--
jkherr at power - net dot net (wipe the spaces)

Filippo wrote :

> 1. the IP address is 192.168.1.2; I can ping the router 192.168.1.1, but
> this is outside the DHCP pool (which starts from .33). and I cannot surf
> the internet. but I can surf on the local router configuration web page.

Sounds like a nameserver issue to me, to check it see if this address
gives you google:
<URL: http://64.233.183.147/>

If it is a nameserver issue and your router is the kind that works as an
DNS proxy then make sure that you have this line in /etc/resolv.conf:
nameserver 192.168.1.1

And if your router cat do this then put your ISP's nameservers here. A
bit of googling indicates that they might be:
194.158.230.53
194.158.230.54
--
Thomas O.

This area is designed to become quite warm during normal operation.

In article <ernelk$n9k$1@tdi.cu.mi.it>,
Filippo <someuser@somedomain.norg> wrote:
>1. the IP address is 192.168.1.2; I can ping the router 192.168.1.1, but
>this is outside the DHCP pool (which starts from .33). and I cannot surf
>the internet. but I can surf on the local router configuration web page.
>2. I can connect through Samba to a Windows PC in the (W)LAN. and I can
>transfer files.
>Can anybody give me some hint on where to look to solve this issue?

Sounds a bit like DHCP is running on the unplugged ethernet interface,
and isn't running on the wireless interface. How did you get
192.168.1.2, I wonder? Is that the IP address on the WLAN interface
or the LAN interface?

Does "route -n" list a gateway and show the right interface?

If not, you could try just running "dhcpcd wlan0" (or whatever IF your
wireless is) and see if that works.

You ought to be able to set all this up in /etc/rc.d/rc.inet1.conf.
(Personally I'm all over the place with the laptop; I don't bother with
the rc.inet1.conf and just run dhcpcd when I need it.)

-Beej

Beej Jorgensen wrote:

> Sounds a bit like DHCP is running on the unplugged ethernet interface,
> and isn't running on the wireless interface. How did you get
> 192.168.1.2, I wonder? Is that the IP address on the WLAN interface
> or the LAN interface?

I do not know. Today I switched the laptop on, and the problem was gone.
Boh...
Anyway thanks to everybody for the suggestions.