Klaas Punt wrote:
David,
Thank you for your reply.
I am answering from my mac.com account because it is not so easy to get the requested info to my kplists account.
Continued here under......
My wireless connecting definitely is not useful as nothing comes back (maybe it does not even go).
However I can see my Wireless net and interrogate it (??).
The firewall is off.
I am including the requested info. In ifconfig I noticed that the broadcast parameter is not set correctly (I think) so I changed it to 10.0.0.255 with ifconfig. I also deleted the double entry for 10.0.0.156 in hosts. All to no avail.
To transfer the myconfig etc files to the Mac. I just inserted the cable, the system told me it disconnected the wireless and connected the wire and then I could ftp the stuff to my other Mac and the internet connection is fully functional..
For starters, if you have wireless "except for ping" disable the firewall (as root, "rcSuSEfirewall2 stop" if that fixes it, then you have a firewall problem. If you have no wireless capability when connected by wireless, post the output from the command line (either x-term or konsole will do), as root, of:
# ifconfig
Klaas, For starters, there is NO wireless device even shown in your ifconfig output. eth0, eth1 are both _wired_ interfaces, lo is simply your local loopback address. If you run "iwconfig" you will see no wireless adapters available. You will need to create the wireless interface, generally this is done with wlanconfig. Example: wlanconfig ath0 create wlandev wifi0 wlanmode sta Check that it is created using "iwconfig" Now mind you, most of this should already be done for you when you installed the drivers you need for your wireless card. What kind is it? For example, if it is an Atheros based card, then you will need, aptly named, the madwifi driver. The suse madwifi driver is fine if you have an older atheros card, for newer cards you will need to use one of the drivers from the OSB (openSuSE Build Service). You will also need to have the kernel source installed so that the required kernel module can be built against the kernel source. If you are using atheros, stick with the ath_pci module, the ath_hal still isn't ready for prime time. When you install the correct driver package, with the kernel source already installed, then your wireless devices should be automagically created and you will see them with both ifconfig and iwconfig similar to: 13:41 alchemy~> sudo ifconfig ath0 Link encap:Ethernet HWaddr 00:1B:9E:7C:C6:DA inet addr:192.168.6.102 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::21b:9eff:fe7c:f6e7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:203778 errors:0 dropped:0 overruns:0 frame:0 TX packets:79709 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:126278022 (120.4 Mb) TX bytes:11030673 (10.5 Mb) eth0 Link encap:Ethernet HWaddr 00:1B:38:AF:36:B8 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:252 Base address:0x8000 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:348 errors:0 dropped:0 overruns:0 frame:0 TX packets:348 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:29092 (28.4 Kb) TX bytes:29092 (28.4 Kb) wifi0 Link encap:UNSPEC HWaddr 00-1B-9E-7C-C6-DA-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:509244 errors:0 dropped:0 overruns:0 frame:6251 TX packets:97023 errors:27 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:280 RX bytes:102333091 (97.5 Mb) TX bytes:14241924 (13.5 Mb) Interrupt:19 01:14 alchemy~> iwconfig lo no wireless extensions. eth0 no wireless extensions. wifi0 no wireless extensions. ath0 IEEE 802.11g ESSID:"skyline" Nickname:"" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:22:B2:A3:A1 Bit Rate:12 Mb/s Tx-Power:16 dBm Sensitivity=1/1 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality=33/70 Signal level=-63 dBm Noise level=-96 dBm Rx invalid nwid:5108 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 What card you have make a lot of difference in what drivers you must use. That is why we need to know what card you have. Post the output of lspci and let's figure out what card we are dealing with here. The rest of the stuff we will deal with after we get a working _wireless_ device recognized by your system. You will be looking for something like this in the lspci output: 17:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01) Good Luck and post the results back ;-) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org