<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: wireless issues in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/wireless-issues/m-p/3690752#M20965</link>
    <description>check the network configuration file.&lt;BR /&gt;If there's a line PEERDNS=no. If so change it to PEERDNS=yes.&lt;BR /&gt;First statement prevents from DHCP to update the /etc/resolv.conf file</description>
    <pubDate>Wed, 14 Dec 2005 01:40:44 GMT</pubDate>
    <dc:creator>Alexander Chuzhoy</dc:creator>
    <dc:date>2005-12-14T01:40:44Z</dc:date>
    <item>
      <title>wireless issues</title>
      <link>https://community.hpe.com/t5/operating-system-linux/wireless-issues/m-p/3690750#M20963</link>
      <description>My HP nc6220 with SuSE 10.0 seems to have wireless problems:&lt;BR /&gt;&lt;BR /&gt;the wireless card (an IntelPro 2915abg) seems&lt;BR /&gt;to be configured properly when looking at the /etc/sysconfig/network file.&lt;BR /&gt;SuSE come's with the proper firmware and driver, the card does get an IP/MAC address with dhcpcd -d,  Kinternet shows good signal strength,  but I'm not getting a DNS entry in the the resolv conf. &lt;BR /&gt;Shutting down the firewall doesn't make any difference either.&lt;BR /&gt;&lt;BR /&gt;Anyone with suggestions?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Gert&lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Tue, 13 Dec 2005 19:09:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/wireless-issues/m-p/3690750#M20963</guid>
      <dc:creator>gert ormel</dc:creator>
      <dc:date>2005-12-13T19:09:00Z</dc:date>
    </item>
    <item>
      <title>Re: wireless issues</title>
      <link>https://community.hpe.com/t5/operating-system-linux/wireless-issues/m-p/3690751#M20964</link>
      <description>Shalom Gert,&lt;BR /&gt;&lt;BR /&gt;While connected, see if you can ping the addresses in /etc/resolv.conf&lt;BR /&gt;&lt;BR /&gt;In a dhcp situation, Linux likes to update the /etc/resolv.conf file and in a wireless environment where there are many access points sometimes gets it wrong.&lt;BR /&gt;&lt;BR /&gt;Check the time and date stamp on /etc/resolv.conf and also see if the settings in /etc/nsswitch.conf are consistent.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 14 Dec 2005 01:18:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/wireless-issues/m-p/3690751#M20964</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-12-14T01:18:08Z</dc:date>
    </item>
    <item>
      <title>Re: wireless issues</title>
      <link>https://community.hpe.com/t5/operating-system-linux/wireless-issues/m-p/3690752#M20965</link>
      <description>check the network configuration file.&lt;BR /&gt;If there's a line PEERDNS=no. If so change it to PEERDNS=yes.&lt;BR /&gt;First statement prevents from DHCP to update the /etc/resolv.conf file</description>
      <pubDate>Wed, 14 Dec 2005 01:40:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/wireless-issues/m-p/3690752#M20965</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2005-12-14T01:40:44Z</dc:date>
    </item>
  </channel>
</rss>

