[nmglug] Re:lost xserver upon upgrade is OK now, no network tho!

Brian O'Keefe okeefe at cybermesa.com
Thu Apr 27 14:47:36 PDT 2006 

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

More information about the nmglug mailing list