[nmglug] Re: nmglug Digest, Vol 31, Issue 16
chochoms at earthlink.net
chochoms at earthlink.net
Fri Apr 28 14:44:34 PDT 2006
The DNS nameserver addresses should be able to be entered in any GUI.
At least you can in Red Hat, Mandriva, and Suse. I never touched the
resolve file and it worked fine once the correct IP addresses were
entered using the GUI.
Another mistake I made was trying to setup my network settings for
DSL. You don't do that. The DSL is handled transparently by the
router and you just set it up as any other Lan instead.
Also I should mention that I use a Qwest actiontec and that I turned
DHCP off. It works extremely well without it. It did not work with
DHCP on (probably because I have no clue how to configure DHCP). For
a newbie like me, DHCP just adds another layer of complexity I don't
need. Fortunately, the criminals running Qwest do not assign dynamic
IP addresses, so turning off DHCP in the router and in LINUX makes
for a simpler setup and provides greater control. Also I like know
exactly what all my IP addresses are all the time.
At 11:00 AM 4/28/2006, you wrote:
>Send nmglug mailing list submissions to
> nmglug at nmglug.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://www.nmglug.org/mailman/listinfo/nmglug
>or, via email, send a message with subject or body 'help' to
> nmglug-request at nmglug.org
>
>You can reach the person managing the list at
> nmglug-owner at nmglug.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of nmglug digest..."
>
>
>Today's Topics:
>
> 1. Re: Re:lost xserver upon upgrade is OK now, no network tho!
> (Brian O'Keefe)
> 2. Re: Re:lost xserver upon upgrade is OK now, no network tho!
> (Sam Noble)
> 3. Re: Re:lost xserver upon upgrade is OK now, no network tho!
> (Brian O'Keefe)
> 4. test message (a_kaluta)
> 5. Re: Re:lost xserver upon upgrade is OK now, no network tho!
> (Brian O'Keefe)
> 6. Re: Re:lost xserver upon upgrade is OK now, no network tho!
> (Brian O'Keefe)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Thu, 27 Apr 2006 11:37:59 -0600
>From: "Brian O'Keefe" <okeefe at cybermesa.com>
>Subject: Re: [nmglug] Re:lost xserver upon upgrade is OK now, no
> network tho!
>To: "NMGLUG.org mailing list" <nmglug at nmglug.org>
>Message-ID: <200604271138.00195.okeefe at cybermesa.com>
>Content-Type: text/plain; charset="iso-8859-6"
>
>On Thursday 27 April 2006 1:01 am, Sam Noble wrote:
>Thanks everyone. This is a bit for me to handle as I am not that profficient
>in this sort of thing, always relying on GUI's mostly but I'm willing!
>I checked via my router ( D-Link) and found WAN info:
>DNS -198.59.109.7
> 206.165.6.11
>Not to sound stupid but my /etc/resolc.conf file does not have the
>"nameserver" now, just the address 192.168.0.1. I just want to be sure that
>when I edit the file I would add exactly this:
>
>nameserver 198.59.109.7
>nameserver 206.165.6.11
>
>or do I need the brackets too?
>
>Also Jason, I cannot access any ip in Linux right now. I'm writing this from
>my OS X partition so I need to reboot into Linux to try these suggestions but
>would like the clarification I requested above first to save headaches.
>PS-I'm not with Qwest but rather Cybermesa
>Again-a multitude of thanks!!
>
>Brian
>
> > On Wed, 2006-04-26 at 17:52 -0600, Brian O'Keefe wrote:
> > > brianokeefe at ubuntu:~$ pico /etc/resolv.conf
> > >
> > > file has: 192.168.01
> >
> > Brian it looks like Jason and chochoms have diagnosed this for you.
> > If you want to make sure that the problem is DNS you could try putting a
> > few known good IP's in a web browser and seeing if that works.
> > http://65.19.10.22/
> > http://64.233.167.104/
> > http://216.93.164.69/
> > http://64.58.141.4/
> >
> > Assuming that works the problem, my favorite solution is adding a
> > prepend line to the dhclient config, so that everytime you pull a new
> > dhcp lease, the top nameserver is the one you set and the ones sent via
> > dhcp are added as secondary and tertiary. (Been trying to use tertiary
> > in conversation for a year now, finally!)
> >
> > Pick your favorite DNS server, and then edit the file dhcpd.conf:
> >
> > $ sudo vi /etc/dhcp3/dhclient
> >
> > and add/edit the line:
> > #prepend domain-name-servers 127.0.0.1;
> >
> > replacing 127.0.0.1 with your favorite DNS server and removing the
> > leading hash.
> >
> > So if you want to use the qwest nameservers:
> >
> > prepend domain-name-servers 205.171.3.65;
> > request subnet-mask, broadcast-address, time-offset, routers,
> > domain-name, domain-name-servers, host-name,
> > netbios-name-servers, netbios-scope;
> >
> > Good luck.
> > sam
> >
> >
> > _______________________________________________
> > nmglug mailing list
> > nmglug at nmglug.org
> > http://www.nmglug.org/mailman/listinfo/nmglug
>
>
>
>------------------------------
>
>Message: 2
>Date: Thu, 27 Apr 2006 13:04:06 -0600
>From: Sam Noble <sam at laclinux.com>
>Subject: Re: [nmglug] Re:lost xserver upon upgrade is OK now, no
> network tho!
>To: "NMGLUG.org mailing list" <nmglug at nmglug.org>
>Message-ID: <1146164647.12298.18.camel at localhost.localdomain>
>Content-Type: text/plain
>
>On Thu, 2006-04-27 at 11:37 -0600, Brian O'Keefe wrote:
> > Thanks everyone. This is a bit for me to handle as I am not that
> > profficient
> > in this sort of thing, always relying on GUI's mostly but I'm willing!
> > I checked via my router ( D-Link) and found WAN info:
> > DNS -198.59.109.7
> > 206.165.6.11
> > Not to sound stupid but my /etc/resolc.conf file does not have the
> > "nameserver" now, just the address 192.168.0.1. I just want to be sure
> > that
> > when I edit the file I would add exactly this:
> >
> > nameserver 198.59.109.7
> > nameserver 206.165.6.11
>
>Yes exactly like that.
>
> > or do I need the brackets too?
>
>No.
>
> > Also Jason, I cannot access any ip in Linux right now. I'm writing
> > this from
> > my OS X partition so I need to reboot into Linux to try these
> > suggestions but
> > would like the clarification I requested above first to save
> > headaches.
> > PS-I'm not with Qwest but rather Cybermesa
> > Again-a multitude of thanks!!
>
>Yeah those are cybermesa's DNS servers.
>
>We've all seen this problem lots with Qwest and actiontec
>modem/bridge/routers.
>I don't think I've seen this with cybermesa customers. It's not
>impossible that this could be fixed with the right setting in the
>D-link. Though go ahead for now and implement one of these three
>solutions and you should be able to get online from your dapper install
>and decide if you want to dig any deeper.
>
>Of course this will only solve it if we're all correct in thinking your
>problem is the DNS server that your router sends via dhcp.
>
>As I said last night the way to check is to visit some sites directly by
>IP.
>http://65.19.10.22/
>http://64.233.167.104/
>http://216.93.164.69/
>http://64.58.141.4/
>
>
>
>
>
>------------------------------
>
>Message: 3
>Date: Thu, 27 Apr 2006 15:47:36 -0600
>From: "Brian O'Keefe" <okeefe at cybermesa.com>
>Subject: Re: [nmglug] Re:lost xserver upon upgrade is OK now, no
> network tho!
>To: "NMGLUG.org mailing list" <nmglug at nmglug.org>
>Message-ID: <200604271547.36880.okeefe at cybermesa.com>
>Content-Type: text/plain; charset="iso-8859-6"
>
>On Thursday 27 April 2006 1:04 pm, Sam Noble wrote:
>I tried and tried!!
>This seems to be one of those really frustrating issues and I had
>trouble with
>the last version of Ubuntu but finally got it working when I installed
>WiFiRadar and used it. Clicked on the found network and was off and running.
>Until then I always had to try as many combinatiuons of GUI settings for
>network as I could and then got online not really knowing why or how.
>Anyway, here is a log that I made of my attempts and any help is greatly
>appreciated. If any fellow user would be at all interested in coming to my
>home to help, I would reward them with a free lunch, at least!
>As a side note, I was always able to connect at SFBaking Co. but I haven't
>tried with Dapper yet so perhaps I'll give it a shot this PM.
>Here's my log and thanks again-you're all great!
>The latest in the saga-
>I cannot open any of the addresses in Linux so I assume it is a DNS issue
>-I used WiFiRadar and set home to manual configurtion with the settings:
> IP 65.19.28.231
> Netmask 255.255.255.0
> Gateway 65.19.28.1
> Domain cybermesa.com
> DNS 198.59.109.7
> DNS 206.165.6.11
>-These are the settings both from logging into my D-Link router
>@ 192.168.0.1 as well as those written on the box the modem came in.
>-I cannot log into the 192... address from Linux however, just from
>OS X (KDE
>by Fink)
>-I checked both the Gnome-Network settings as well as from the command
> line and the settings are correct.
>-I pinged the 65.19.28.231 address successfully from both the
> command line as well as with Gnome-network tools but could not ping the
>192...address
>-I can ping both addresses in OS X
>This in Linux after correcting settings
>-When I tried my home page in Firefox no connection
>-When I tried connecting from command line WiFiRadar reconnected
> to 192.168.0.1 and /etc.resolv.conf was reset to same.
>-I reset the correct addresses, etc. and again was able to ping and portscan
> in network tools showed:
>
>port 22 open SSH
>port 53 open Domain
>port 80 open WWW
>port 5222 open xmpp client
>port 5269 open xmpp-server
>-/etc/resolv.conf settings correct still
>-Lookup information in network tools shows no info.
>-Results of command line efforts:
>
>$ ifconfig
>eth1 Link encap:Ethernet HWaddr 00:30:65:25:8D:87
> inet addr:65.19.28.231 Bcast:65.19.28.255 Mask:255.255.255.0
> inet6 addr: fe80::230:65ff:fe25:8d87/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1977 errors:0 dropped:0 overruns:0 frame:0
> TX packets:108 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:643336 (628.2 KiB) TX bytes:20892 (20.4 KiB)
> Interrupt:57
>
>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:14062 errors:0 dropped:0 overruns:0 frame:0
> TX packets:14062 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:721730 (704.8 KiB) TX bytes:721730 (704.8 KiB)
>
>brianokeefe at ubuntu:~$ iwconfig
>lo no wireless extensions.
>
>eth0 no wireless extensions.
>
>eth1 IEEE 802.11b ESSID:"home" Nickname:"home"
> Mode:Managed Frequency:2.437 GHz Access Point: 00:13:46:BF:5C:BE
> Bit Rate:11 Mb/s Sensitivity:1/3
> Retry limit:4 RTS thr:off Fragment thr:off
> Power Management:off
> Link Quality=43/92 Signal level=-56 dBm Noise level=-99 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:1
> Tx excessive retries:2 Invalid misc:0 Missed beacon:0
>
>sit0 no wireless extensions.
>
>brianokeefe at ubuntu:~$ iwlist scan
>lo Interface doesn't support scanning.
>
>eth0 Interface doesn't support scanning.
>
>eth1 Scan completed :
> Cell 01 - Address: 00:13:46:BF:5C:BE
> ESSID:"home"
> Mode:Master
> Frequency=2.437 GHz (Channel 6)
> Signal level:-61 dBm Noise level:-100 dBm
> Encryption key:off
>
>sit0 Interface doesn't support scanning.
>
>brianokeefe at ubuntu:~$ ping 65.19.28.231
>PING 65.19.28.231 (65.19.28.231) 56(84) bytes of data.
>64 bytes from 65.19.28.231: icmp_seq=1 ttl=64 time=0.132 ms
>64 bytes from 65.19.28.231: icmp_seq=2 ttl=64 time=0.112 ms
>64 bytes from 65.19.28.231: icmp_seq=3 ttl=64 time=0.111 ms
>64 bytes from 65.19.28.231: icmp_seq=4 ttl=64 time=0.110 ms
>64 bytes from 65.19.28.231: icmp_seq=5 ttl=64 time=0.115 ms
>64 bytes from 65.19.28.231: icmp_seq=6 ttl=64 time=0.114 ms
>64 bytes from 65.19.28.231: icmp_seq=7 ttl=64 time=0.418 ms
>64 bytes from 65.19.28.231: icmp_seq=8 ttl=64 time=0.121 ms
>64 bytes from 65.19.28.231: icmp_seq=9 ttl=64 time=0.115 ms
>64 bytes from 65.19.28.231: icmp_seq=10 ttl=64 time=0.118 ms
>64 bytes from 65.19.28.231: icmp_seq=11 ttl=64 time=0.113 ms
>64 bytes from 65.19.28.231: icmp_seq=12 ttl=64 time=0.111 ms
>64 bytes from 65.19.28.231: icmp_seq=13 ttl=64 time=0.116 ms
>64 bytes from 65.19.28.231: icmp_seq=14 ttl=64 time=0.112 ms
>64 bytes from 65.19.28.231: icmp_seq=15 ttl=64 time=0.113 ms
>64 bytes from 65.19.28.231: icmp_seq=16 ttl=64 time=0.111 ms
>
>--- 65.19.28.231 ping statistics ---
>16 packets transmitted, 16 received, 0% packet loss, time 14996ms
>rtt min/avg/max/mdev = 0.110/0.133/0.418/0.075 ms
> > On Thu, 2006-04-27 at 11:37 -0600, Brian O'Keefe wrote:
> > > Thanks everyone. This is a bit for me to handle as I am not that
> > > profficient
> > > in this sort of thing, always relying on GUI's mostly but I'm willing!
> > > I checked via my router ( D-Link) and found WAN info:
> > > DNS -198.59.109.7
> > > 206.165.6.11
> > > Not to sound stupid but my /etc/resolc.conf file does not have the
> > > "nameserver" now, just the address 192.168.0.1. I just want to be sure
> > > that
> > > when I edit the file I would add exactly this:
> > >
> > > nameserver 198.59.109.7
> > > nameserver 206.165.6.11
> >
> > Yes exactly like that.
> >
> > > or do I need the brackets too?
> >
> > No.
> >
> > > Also Jason, I cannot access any ip in Linux right now. I'm writing
> > > this from
> > > my OS X partition so I need to reboot into Linux to try these
> > > suggestions but
> > > would like the clarification I requested above first to save
> > > headaches.
> > > PS-I'm not with Qwest but rather Cybermesa
> > > Again-a multitude of thanks!!
> >
> > Yeah those are cybermesa's DNS servers.
> >
> > We've all seen this problem lots with Qwest and actiontec
> > modem/bridge/routers.
> > I don't think I've seen this with cybermesa customers. It's not
> > impossible that this could be fixed with the right setting in the
> > D-link. Though go ahead for now and implement one of these three
> > solutions and you should be able to get online from your dapper install
> > and decide if you want to dig any deeper.
> >
> > Of course this will only solve it if we're all correct in thinking your
> > problem is the DNS server that your router sends via dhcp.
> >
> > As I said last night the way to check is to visit some sites directly by
> > IP.
> > http://65.19.10.22/
> > http://64.233.167.104/
> > http://216.93.164.69/
> > http://64.58.141.4/
> >
> >
> >
> > _______________________________________________
> > nmglug mailing list
> > nmglug at nmglug.org
> > http://www.nmglug.org/mailman/listinfo/nmglug
>
>
>
>------------------------------
>
>Message: 4
>Date: Thu, 27 Apr 2006 17:03:57 -0600
>From: "a_kaluta" <akaluta at zianet.com>
>Subject: [nmglug] test message
>To: "NMGLUG.org mailing list" <nmglug at nmglug.org>
>Message-ID: <000301c66a4e$ddfebb50$1f251fd8 at bigboy>
>Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
>Dear Glug;
>Test message A.Kaluta NY5F
>
>
>
>------------------------------
>
>Message: 5
>Date: Thu, 27 Apr 2006 22:29:49 -0600
>From: "Brian O'Keefe" <okeefe at cybermesa.com>
>Subject: Re: [nmglug] Re:lost xserver upon upgrade is OK now, no
> network tho!
>To: "NMGLUG.org mailing list" <nmglug at nmglug.org>
>Message-ID: <1146198589.4994.14.camel at localhost.localdomain>
>Content-Type: text/plain
>
>On Thu, 2006-04-27 at 15:47 -0600, Brian O'Keefe wrote:
> > On Thursday 27 April 2006 1:04 pm, Sam Noble wrote:
> > I tried and tried!!
>
>Well, serendipity has shined on me 2 nights in a row!! Last night my
>wife and I went to see if we could get tickets at the Lensic for Howard
>Zinn. It was sold out but as we walked up to the door, there was a guy
>holding 2 tickets. I asked him if he was selling them and he said "no,
>I'm giving them away"! We took him up on his offer.
>Today I took my limping powerbook to SFBC to see if I could log on there
>but no luck. I thought, "I wonder if any NMGLUG members will be hanging
>around", but I didn't spot any overt activity and I had no idea of who
>looked like who. I overheard a couple guys talking Ubuntu and when they
>were done I asked if they were members of the list. They said yes and I
>introduced myself and they were Jason and Sam! Jason had to go but Sam
>said he'd stay and fix me up. Well, almost 3 hours later, after
>searching and hacking and not a small amount of frustration, it turned
>out that:
>My distro was all screwed up from my bad attempts at upgrading
>I had ipmasq installed and it was blocking my connection from any router
>
>Sam turned off the ipmasq package and did some clean up and here I am,
>at home, on Dapper, sending this message! Little did I know that Sam was
>leaving the state tomorrow morning!
>Anyway, the good thing is that I'm all fixed up, I could not have ever
>figured this out and I cannot imagine if we could have pulled it off
>using the list but that's all done with.
>The only question is how ipmasq got installed in the first place.
>Thanks again everyone and good fortune Sam-I owe you big time!!
>
>
>
>
>------------------------------
>
>Message: 6
>Date: Fri, 28 Apr 2006 10:52:46 -0600
>From: "Brian O'Keefe" <okeefe at cybermesa.com>
>Subject: Re: [nmglug] Re:lost xserver upon upgrade is OK now, no
> network tho!
>To: "NMGLUG.org mailing list" <nmglug at nmglug.org>
>Message-ID: <1146243166.10007.18.camel at localhost.localdomain>
>Content-Type: text/plain
>
>A note: I met Josh not Jonas (Povilas Skadis) last night. Jonas was at a
>table nearby selling his Powerbook and gave me his card.
>I thought that I should add an update for general information in case it
>adds to the knowledge base.
>Last night I was connected to the cybermesa DNS addresses according to
>my /etc/resov.conf file. I did an upgrade of packages last night when
>the update daemon showed up in the menu bar. Many packages installed
>that were updates Sam did only hours before, Evolution, etc. So I did
>the upgades. I got a restart notification so I did and guess what? No
>internet upon rebooting. I futzed around with all of the command line
>stuff and all the settings were correct. I tried network tools and could
>ping cybermesa but not my router. I thought back to the D-Link manual
>where it said "be sure your computer is set to the D-Link address
>192.168.0.1". I used the gnome-network-manager and chose my home account
>and then noticed that WiFiradar should no connection to home. I chose
>connect for home in WiFiradar and it connected to 192.168.0.1. I am on
>line.
>My understanding of what makes sense here is zero. I seem to be in the
>"click on a bunch of stuff and hope for the best" mode.
>BTW, /etc/resolv.conf now has (set by wifiradar):
>domain cybermesa.com
>nameserver 192.168.0.1
>
>Anyway, thanks again and I hope to see everyone at the next NMGLUG
>meeting. Good luck Sam!
>
>On Thu, 2006-04-27 at 22:29 -0600, Brian O'Keefe wrote:
> > On Thu, 2006-04-27 at 15:47 -0600, Brian O'Keefe wrote:
> > > On Thursday 27 April 2006 1:04 pm, Sam Noble wrote:
> > > I tried and tried!!
> >
> > Well, serendipity has shined on me 2 nights in a row!! Last night my
> > wife and I went to see if we could get tickets at the Lensic for Howard
> > Zinn. It was sold out but as we walked up to the door, there was a guy
> > holding 2 tickets. I asked him if he was selling them and he said "no,
> > I'm giving them away"! We took him up on his offer.
> > Today I took my limping powerbook to SFBC to see if I could log on there
> > but no luck. I thought, "I wonder if any NMGLUG members will be hanging
> > around", but I didn't spot any overt activity and I had no idea of who
> > looked like who. I overheard a couple guys talking Ubuntu and when they
> > were done I asked if they were members of the list. They said yes and I
> > introduced myself and they were Jason and Sam! Jason had to go but Sam
> > said he'd stay and fix me up. Well, almost 3 hours later, after
> > searching and hacking and not a small amount of frustration, it turned
> > out that:
> > My distro was all screwed up from my bad attempts at upgrading
> > I had ipmasq installed and it was blocking my connection from any router
> >
> > Sam turned off the ipmasq package and did some clean up and here I am,
> > at home, on Dapper, sending this message! Little did I know that Sam was
> > leaving the state tomorrow morning!
> > Anyway, the good thing is that I'm all fixed up, I could not have ever
> > figured this out and I cannot imagine if we could have pulled it off
> > using the list but that's all done with.
> > The only question is how ipmasq got installed in the first place.
> > Thanks again everyone and good fortune Sam-I owe you big time!!
> >
> >
> > _______________________________________________
> > nmglug mailing list
> > nmglug at nmglug.org
> > http://www.nmglug.org/mailman/listinfo/nmglug
>
>
>
>
>------------------------------
>
>_______________________________________________
>nmglug mailing list
>nmglug at nmglug.org
>http://www.nmglug.org/mailman/listinfo/nmglug
>
>
>End of nmglug Digest, Vol 31, Issue 16
>**************************************
More information about the nmglug
mailing list