Kevin, For starters, please do not use your mail software's "reply" function to generate new topics. It causes your posting to appear to be part of another thread. Changing the subject is not sufficient to break this association in good mailers that use the pertinent header fields to recognize and organize topic threads. On Wednesday 16 November 2005 13:29, kevin.kempter@dataintellect.com wrote:

Just a few more questions...

- Anyone know if Informix V10 runs on Suse 10 ?

I would gather from the fact there's a whole mailing list (http://lists.suse.com/archive/suse-informix/) devoted to Informix on SuSE that the answer is probably "yes." Check it out (the list archives) to see for sure. ... On the other hand, the list appears rather moribund. A quick glance at the Informix site showed that it's supported for SLES, which suggests it might work for SuSE Linux 10, but it's by no means certain unless someone produces a build specifically for this version of Linux. PostgreSQL 8.0 and MySQL 4.1 are included.

- How about sound. With Fedora pretty much the sound either a) worked out of the box or b) your chances of ever getting sound working were slim to none. I have an onboard Intel 82801DB/DBL/DBM AC'97 Audio Controller and It works using an out of the box configuration of alsa. How difficult of a time might I have getting sound to work?

I don't know for a fact, but I would be surprised if that gave you any trouble.

- Does the Vmware Workstation5 run under Suse V10 ?

Yes, though a small deviation from the normal installation procedure is required to make it work correctly. Here's the modified installation and setup procedure you need to make VMware 5.0 work on SuSE Linux 10.0: http://www.novell.com/coolsolutions/feature/15963.html.

- Do sound apps like real player, mplayer, etc run on Suse v10 and is it easy to get the mplayer codecs for windows media player files ?

They all work fine.

- Also does the boxed set come with mozilla / firefox plugins for java, flash and pdf ?

The commercial version includes Adobe Reader (for PDF viewing) as well as Sun's Java (including plug-ins). I'm pretty sure I did not have to do an independent installation of the Flash plug-in. Randall Schulz

Hi list, I just moved from Linspire to Suse 10 and like the transition very much. Everything works pretty well from the install but I cannot seem to get the WLAN to work. I can hit the Access point from any other machine and get to the Internet fine, but with Suse, I can hit the config screen on the Access Point and configure, etc. but still cannot get out to the Internet. The card is configured correctly using 64-bit WEP and it is recognized by the kwifimanager program with an excellent signal and a valid IP address assigned with DHCP from the AP. I must be overlooking something but am baffled at this point. Can someone shed some light on why I cannot get out to the internet? Many thanks in advance. JR

On Thu, 2005-11-17 at 07:26 +0100, Dominique Leuenberger wrote:

John Rittinghouse wrote:

...

Hi list,

I just moved from Linspire to Suse 10 and like the transition very much. Everything works pretty well from the install but I cannot seem to get the WLAN to work. I can hit the Access point from any other machine and get to the Internet fine, but with Suse, I can hit the config screen on the Access Point and configure, etc. but still cannot get out to the Internet. The card is configured correctly using 64-bit WEP and it is recognized by the kwifimanager program with an excellent signal and a valid IP address assigned with DHCP from the AP. I must be overlooking something but am baffled at this point. Can someone shed some light on why I cannot get out to the internet? Many thanks in advance.

Hi John,

Jave you checked if DNS name resolution works correct? Are there valid DNS servers in your /etc/resolv.conf? You receive them by DHCP? Try to connect to something like http://212.203.69.7 (so no dns is required)

I guess on such a failure as you say you can access the web interface of your AP (probably using it's IP) so it might be such a cause... in other cases I would try to check the routing table using 'route print'

This is not windows. Use route -n. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

Dominique, Ken, The /etc/resolv.conf table shows the correct dns servers that the ISP gave me. the AP uses a 10.2.2.1 address as the gateway to the ISP where the DNS servers reside. I tried the route -n command as suggested but bash says no such file or directory, which leads me to believe there is something not installed on my suse box that should be. Also, when I type in an address directly, (i.e., http://212.203.69.7) i get a connection refused error. Any suggestions on what to do from this point? JR On Thu, 17 Nov 2005 00:26:21 -0600, Dominique Leuenberger wrote:

John Rittinghouse wrote:

...

Hi list,

I just moved from Linspire to Suse 10 and like the transition very much. Everything works pretty well from the install but I cannot seem to get the WLAN to work. I can hit the Access point from any other machine and get to the Internet fine, but with Suse, I can hit the config screen on the Access Point and configure, etc. but still cannot get out to the Internet. The card is configured correctly using 64-bit WEP and it is recognized by the kwifimanager program with an excellent signal and a valid IP address assigned with DHCP from the AP. I must be overlooking something but am baffled at this point. Can someone shed some light on why I cannot get out to the internet? Many thanks in advance.

Hi John,

Jave you checked if DNS name resolution works correct? Are there valid DNS servers in your /etc/resolv.conf? You receive them by DHCP? Try to connect to something like http://212.203.69.7 (so no dns is required)

I guess on such a failure as you say you can access the web interface of your AP (probably using it's IP) so it might be such a cause... in other cases I would try to check the routing table using 'route print'

Greetings Dominique

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

On Thursday 17 November 2005 14:58, Dominique Leuenberger wrote:

you probably tried to execute 'route -n' as non-root user... as it's located under /sbin/ it's not in your path. try '/sbin/route -n' and it should be ok. If still not, the route binary is installed by the net-tools rpm... but I'm almost sure this one is installed /sbin/ip route list works too ;)

-- Damian Mihai Liviu Mobile: +40 741 226993; Fax: +1 347-632-4117 Phone : +1 360-526-6441; +1 347-632-4117; +44 0870-3403339 URL: http://liviudm.blogspot.com

further info - i logged in again as SU and the route -n provided a response. it gets me from local host address to 192.168.123.0 showing no gateway address. how to amend to go from 192.168.123.0 to 10.2.2.1? jr On Thu, 17 Nov 2005 06:49:18 -0600, John Rittinghouse wrote:

Dominique, Ken,

The /etc/resolv.conf table shows the correct dns servers that the ISP gave me. the AP uses a 10.2.2.1 address as the gateway to the ISP where the DNS servers reside. I tried the route -n command as suggested but bash says no such file or directory, which leads me to believe there is something not installed on my suse box that should be. Also, when I type in an address directly, (i.e., http://212.203.69.7) i get a connection refused error. Any suggestions on what to do from this point?

JR

On Thu, 17 Nov 2005 00:26:21 -0600, Dominique Leuenberger wrote:

...

John Rittinghouse wrote:

...

Hi list,

I just moved from Linspire to Suse 10 and like the transition very much. Everything works pretty well from the install but I cannot seem to get the WLAN to work. I can hit the Access point from any other machine and get to the Internet fine, but with Suse, I can hit the config screen on the Access Point and configure, etc. but still cannot get out to the Internet. The card is configured correctly using 64-bit WEP and it is recognized by the kwifimanager program with an excellent signal and a valid IP address assigned with DHCP from the AP. I must be overlooking something but am baffled at this point. Can someone shed some light on why I cannot get out to the internet? Many thanks in advance.

Hi John,

Jave you checked if DNS name resolution works correct? Are there valid DNS servers in your /etc/resolv.conf? You receive them by DHCP? Try to connect to something like http://212.203.69.7 (so no dns is required)

I guess on such a failure as you say you can access the web interface of your AP (probably using it's IP) so it might be such a cause... in other cases I would try to check the routing table using 'route print'

Greetings Dominique

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Ken, the wireless subnet of the AP is 192.168.123.xxx and it connects to the 10.x.x.x ISP controlled network. The DNS servers live on their side and are autodetected. the gateway from the AP to the Internet is a 10.2.2.1 address. I cannot change anything except my PC and the address for it is correctly allocated by DHCP from my AP as 192.168.123.107. I have two access points, one at home, one at work, both configured identically. When using a windows box (same box, dual partitions) everything works fine from either one. when i boot into suse, neither AP will allow me to see the Internet. I am new to Unix (not really, did a lot of Unix in 1986-1990, but not even the same anymore). I have used this YaST2 module to configure and actually got it working once, but when i rebooted, it was the same problem over again. I just do not know what to set or where to set it and really appreciate your taking the time to respond and help out. regards, jr

John Rittinghouse wrote:

Ken, Dominique, I got the problem solved - after reviewing the logs, i discovered that it was because DHCP had already allocated an IP address for the box from the eth0 (LAN) connection so it would not allocate another IP address to the same box for the same profile. The solution was to delete the wireless connection, set up a profile for the LAN, reboot, create a connection for the WLAN, set up a new profile for that, reboot, and switch profiles based on where i go. Now, the box has four profiles, one each for home/office LAN and home/office WLAN and they all work perfectly... Thanks very much for the guidance and suggestions...they were a big help.

jr

Hi John, glad we could help you. Cheers, Dominique