LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 04-13-2005, 02:20 PM   #1
anon111
Member
 
Registered: Oct 2004
Posts: 38

Rep: Reputation: Disabled
Orinoco Wifi Card


Hey guys,

I have a proxim orinoco gold card and I want to use it on campus with my campus wide wifi network. I'm using Suse Linux 9.2 and it detected it and all. I setup encryption and set it to be dhcp etc.

The really weird thing is it pulls and IP address from the dhcp server but I cannot access any network/internet resources. I know the card/signal are fine because I am using it right now under windows.

I was wondering if anyone could give me any ideas on a fix or how to troubleshoot this. I'm realtively new to linux and troubleshooting tends to be a bit difficult.

The only other info I can say is that when I use YAST to configure the wifi card by clicking "change" is that I set the hostname to "tuxbox" and I leave the domain name blank since it changes between my home/school network. I aslo have the "change hostname via DHCP" unchecked. When I click ok it says that there was an error. Maybe this is my problem, but I am unsure.

Any guidance would be of great help....Thanks again, it is much appreciated.


//Mark
 
Old 04-13-2005, 02:28 PM   #2
snecklifter
Member
 
Registered: Mar 2004
Location: UK/West Yorkshire/Huddersfield
Distribution: Fedora 7
Posts: 982

Rep: Reputation: 30
Check with campus services dude. Most likely you will need to access using a proxy server - they will have the address and port (if necessary) as uni's dont generally tend to allow complete network access.
 
Old 04-13-2005, 02:30 PM   #3
anon111
Member
 
Registered: Oct 2004
Posts: 38

Original Poster
Rep: Reputation: Disabled
Thanks snecklifter but I didn't have to configure anything for windows and DHCP only the encryption key and the network ssid. Any other shots in the dark.
 
Old 04-13-2005, 02:52 PM   #4
snecklifter
Member
 
Registered: Mar 2004
Location: UK/West Yorkshire/Huddersfield
Distribution: Fedora 7
Posts: 982

Rep: Reputation: 30
Ah okay. Try some stuff in this order.
ping 127.0.0.1
ping localhost
If both of these are okay then run
route
or
ifconfig
and ping the ip address dhcp has assigned your computer.
If all of this works (okay I know its a b***-ache but it helps) then post back the iwconfig and ifconfig outputs as well as route output and I'll have another look.
Regards
Chris
 
Old 04-15-2005, 02:19 PM   #5
anon111
Member
 
Registered: Oct 2004
Posts: 38

Original Poster
Rep: Reputation: Disabled
Snecklifter here's my output...


divzr0@M-Alice:~> ping 127.0.0.1

PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.

M-Alice:~ # ping 127.0.0.1

PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.

64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.046 ms

64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.072 ms

64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.091 ms

64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.093 ms

64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.091 ms

64 bytes from 127.0.0.1: icmp_seq=6 ttl=64 time=0.093 ms


Pinging localhost

M-Alice:~ # ping localhost

PING localhost (127.0.0.1) 56(84) bytes of data.

64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.093 ms

64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.090 ms

64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.095 ms

64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.093 ms

64 bytes from localhost (127.0.0.1): icmp_seq=5 ttl=64 time=0.091 ms

64 bytes from localhost (127.0.0.1): icmp_seq=6 ttl=64 time=0.094 ms



--- localhost ping statistics ---

6 packets transmitted, 6 received, 0% packet loss, time 5000ms

rtt min/avg/max/mdev = 0.090/0.092/0.095/0.011 ms



M-Alice:~ # route

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

144.118.xx.x * 255.255.248.0 U 0 0 0 eth1

link-local * 255.255.0.0 U 0 0 0 eth1

loopback * 255.0.0.0 U 0 0 0 lo



M-Alice:~ # ifconfig

eth0 Link encap:Ethernet HWaddr 00:0BB:xx:xx:xx

inet6 addr: fe80::20b:dbff:fe17:5b0e/64 Scope:Link

UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:19 errors:0 dropped:0 overruns:0 carrier:19

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:8130 (7.9 Kb)

Interrupt:11 Base address:0xec80



eth1 Link encap:Ethernet HWaddr 00:02:2D:xx:xx:x

inet addr:144.118.xx.xx Bcast:144.118.23.255 Mask:255.255.248.0

inet6 addr: fe80::202:2dff:feab:4f7e/64 Scope:Link

UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1

RX packets:7513 errors:0 dropped:0 overruns:0 frame:0

TX packets:8 errors:1 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:800121 (781.3 Kb) TX bytes:1542 (1.5 Kb)

Interrupt:3 Base address:0x100



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:144 errors:0 dropped:0 overruns:0 frame:0

TX packets:144 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:10652 (10.4 Kb) TX bytes:10652 (10.4 Kb)

M-Alice:~ # ping 144.118.xx.xx

PING 144.118.xx.xx (144.118.xx.xx) 56(84) bytes of data.

64 bytes from 144.118.xx.xx: icmp_seq=1 ttl=64 time=0.055 ms

64 bytes from 144.118.xx.xx: icmp_seq=2 ttl=64 time=0.043 ms

64 bytes from 144.118.xx.xx: icmp_seq=3 ttl=64 time=0.046 ms

64 bytes from 144.118.xx.xx: icmp_seq=4 ttl=64 time=0.094 ms

64 bytes from 144.118.xx.xx: icmp_seq=5 ttl=64 time=0.094 ms

64 bytes from 144.118.xx.xx: icmp_seq=6 ttl=64 time=0.093 ms



--- 144.118.xx.xx ping statistics ---

6 packets transmitted, 6 received, 0% packet loss, time 4998ms

rtt min/avg/max/mdev = 0.043/0.070/0.094/0.025 ms



M-Alice:~ # iwconfig

lo no wireless extensions.



eth0 no wireless extensions.



eth1 IEEE 802.11-DS ESSID:"xxxxxx" Nickname:"M-Alice"

Mode:Managed Frequency:2.417 GHz Access Point: 00:0F:8F:4F9:70

Bit Rate:11 Mb/s Tx-Power=15 dBm Sensitivity:1/3

Retry limit:4 RTS thrff Fragment thrff

Encryption key:xxxx-xxxx-xx

Power Managementff

Link Quality=33/92 Signal level=-52 dBm Noise level=-85 dBm

Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:58

Tx excessive retries:0 Invalid misc:0 Missed beacon:0


Anything that has a "x" has been blocked out for privacy reasons....

Any ideas?
 
Old 04-15-2005, 05:18 PM   #6
snecklifter
Member
 
Registered: Mar 2004
Location: UK/West Yorkshire/Huddersfield
Distribution: Fedora 7
Posts: 982

Rep: Reputation: 30
Well, it means that your TCP/IP stack is functioning fine and you've got an IP address no probs using DHCP. The problem I think you have is that you do not have a gateway IP in your routing table. This is basically the IP address of the AP that assigned your IP address and will handle DNS and other such. For example, my routing table:
Code:
[chris@snecklifter ~]$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.0     *               255.255.255.0   U     0      0        0 eth1
169.254.0.0     *               255.255.0.0     U     0      0        0 eth1
default         192.168.2.1     0.0.0.0         UG    0      0        0 eth1
whereas yours is
Code:
144.118.xx.x * 255.255.248.0 U 0 0 0 eth1

link-local * 255.255.0.0 U 0 0 0 eth1

loopback * 255.0.0.0 U 0 0 0 lo
Your computer doesn't know where to go next basically. You'll notice there is no "UG" route. I'm not sure why as this process is usually all automated - you dont really need to know all this. I'm not experienced enough to tell you how to fix this im afraid. I suggest you check the man pages
Code:
man route
and see if they help at all or contact campus network services.
Good luck.
Chris
 
Old 04-15-2005, 05:20 PM   #7
snecklifter
Member
 
Registered: Mar 2004
Location: UK/West Yorkshire/Huddersfield
Distribution: Fedora 7
Posts: 982

Rep: Reputation: 30
As a footnote, I would however try disabling eth0 with
Code:
ifconfig eth0 down
and then renew your ip
Code:
dhclient eth1
and see if your wired interface isnt causing grief.
 
Old 04-17-2005, 12:27 AM   #8
WMD
Member
 
Registered: Jul 2004
Location: Florida
Distribution: Slackware, Debian
Posts: 484

Rep: Reputation: 30
route add default gw 192.168.0.1

Just change the IP to your known gateway, and run it. (You must be root)
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't get wifi working, Orinoco on IBM T22 laptop sharp11 Linux - Wireless Networking 7 10-31-2005 05:13 PM
wifi kernel orinoco questions mpelts Linux - Wireless Networking 1 10-15-2004 04:14 PM
Red Hat 8.0+Orinoco Gold WiFi KePSuX Linux - Wireless Networking 3 08-02-2004 01:32 PM
orinoco wifi in mandrake 10 litehedded Linux - Newbie 3 07-25-2004 07:51 AM
Proxim Orinoco 11 b/g WiFi card celticselph Linux - Laptop and Netbook 45 07-20-2004 10:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 07:20 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration