| === dyfet` is now known as dyfet | ||
| === ogra_ is now known as ogra | ||
| === rgreening_ is now known as rgreening | ||
| stinsoni34 | hey | 15:54 |
|---|---|---|
| persia | Hi | 15:54 |
| Invisrc | hey | 16:08 |
| Invisrc | I'm having a wierd problem with my wireless, when i pull up iwconfig it seems to be showing that im connected(that is if im reading it correctly) but when i try to ping something it doesnt work | 16:09 |
| persia | Does the output of `ifconfig -a` and `netstat -rn` provide any insight? | 16:10 |
| Invisrc | i tried ifconfig -a but i really didnt see anything | 16:11 |
| Invisrc | im thinking it may have to do with my netgear router | 16:11 |
| Invisrc | because when i unplug it then plug it in, i always get connected | 16:11 |
| persia | That does sound like a router issue rather than a client issue. | 16:12 |
| Invisrc | i was wondering if maybe there was a line i could add to my interface settings to enable and auto retry till connect | 16:12 |
| Invisrc | because when i pull up iwconfig it is showing the name of the router and the ap | 16:14 |
| persia | Beyond my knowledge, sorry. | 16:15 |
| Invisrc | kkk | 16:15 |
| Invisrc | thanks though | 16:15 |
| Invisrc | anybone else lo | 16:15 |
| Invisrc | l | 16:15 |
| tfried2001 | what kind of message do you get when you ping? | 16:23 |
| tfried2001 | and what are you trying to ping? | 16:24 |
| Invisrc | i try to ping google.com | 16:25 |
| Invisrc | and my router 192.168.1.1 | 16:25 |
| Invisrc | i know that when i am actually connected those pings work | 16:26 |
| tfried2001 | what kind of messages are you getting? | 16:26 |
| tfried2001 | "destination unreachable (ip address)" or "no reply" or what? | 16:27 |
| Invisrc | i think it says unreachable but not a 100% sure, ill have to go down stairs if its necessary | 16:27 |
| Invisrc | oo and it it reporting the link quality as well | 16:27 |
| tfried2001 | have you tried a traceroute to the destination to see where it stops? | 16:28 |
| Invisrc | but when i do go to my router setting page to seee the devices that are connected the box is not lister | 16:28 |
| tfried2001 | can you ping your default gateway? | 16:29 |
| tfried2001 | if you're on a 192.168.1.? network it's probably 192.168.1.1 | 16:29 |
| Invisrc | nope doesnt work | 16:29 |
| tfried2001 | :( | 16:29 |
| Invisrc | i dont think its actually connected | 16:29 |
| tfried2001 | do you have a link quality when you do an iwconfig? | 16:30 |
| Invisrc | that why i was hoping to find maybe some line that i could add to ect/network/interfaces that would do an auto reconnect till a ping is sucesful | 16:30 |
| Invisrc | ya link quality is like 55/70 | 16:30 |
| tfried2001 | well...if you're using ubuntu, you can right click the network icon in the upper right corner and edit your network connections there... | 16:30 |
| tfried2001 | that's probably the most user friendly way of doing things... | 16:31 |
| Invisrc | im running the no gui version lol | 16:32 |
| tfried2001 | lol, well played | 16:32 |
| Invisrc | lol that why i was hopign for the sript lol | 16:34 |
| tfried2001 | it's been awhile since I've had to manually program an access point, I'm not sure what the procedures are these days | 16:35 |
| tfried2001 | I'm used to utilities like ettercap anymore lol | 16:35 |
| tfried2001 | do you happen to have WEP or WPA turned on? | 16:36 |
| Invisrc | ya | 16:38 |
| Invisrc | i know that all works because im able to get it to connect just not always | 16:38 |
| tfried2001 | so intermittent connection | 16:38 |
| tfried2001 | does 'iwevent' show you any sort of connect/disconnect event? | 16:40 |
| Invisrc | ill have to get back to u on that | 16:43 |
| Invisrc | wont be able to check for liek 20 mins | 16:43 |
| tfried2001 | cool | 16:43 |
| tfried2001 | we could also double check that your wireless controller driver is recognized and operating.... "lspci | grep Network" and look for your wireless card | 16:44 |
| tfried2001 | I would imagine that if you're able to 'iwconfig' and get valid information in return, your driver would be fine though | 16:45 |
| Invisrc | it def is | 16:46 |
| Invisrc | since ive used and connected to the internet plenty of times | 16:46 |
| Invisrc | its just a pain to have to keep restarting till it does | 16:46 |
| tfried2001 | well that's something else entirely | 16:48 |
| tfried2001 | that could be an overheating/missbehaving wireless access point (quite common among all wireless access points) | 16:49 |
| tfried2001 | usually a resetting of the access point will fix that | 16:49 |
| Invisrc | its brand new | 16:51 |
| tfried2001 | after resetting the access point just do a "sudo networking --full-restart" | 16:51 |
| tfried2001 | as long as your /etc/network/interfaces file is setup to auto-connect to your access point, you'll be straight | 16:53 |
| tfried2001 | do you need that set up? | 16:53 |
| Invisrc | tfried2001 what line should be to auto-connect | 16:54 |
| tfried2001 | ah, so I was missing the story entirely, I apologize! | 16:56 |
| tfried2001 | so, to do your wpa, you have wpasupplicant installed? | 16:57 |
| tfried2001 | if so, your config for your interface file should be something like the following: | 16:57 |
| tfried2001 | auto wlan0 | 16:57 |
| tfried2001 | iface wlan0 inet dhcp | 16:57 |
| tfried2001 | wpa-driver "your wireless card's driver" | 16:58 |
| tfried2001 | wpa-conf /etc/wpa_supplicant.conf | 16:58 |
| tfried2001 | I believe that wpa is installed by default anymore... | 16:59 |
| tfried2001 | but the wpa_supplicant.conf is no longer under /etc | 17:00 |
| tfried2001 | 1 sec | 17:00 |
| tfried2001 | ok, it is if you have wpa_supplicant set up | 17:01 |
| tfried2001 | I don't so my machine doesn't | 17:01 |
| Invisrc | lol | 17:03 |
| Invisrc | u would think something like this would be easy | 17:03 |
| tfried2001 | lol, command line never is, that's why us geeks love it ;) | 17:03 |
| Invisrc | let me run down and se the iwevent hing | 17:04 |
| tfried2001 | ok, and to see what driver you are using do a "sudo lshw -C network" and look for your network device. Under that you will see a 'driver=???', that's the driver you are using and can put in your interfaces config | 17:06 |
| Invisrcm | hey | 17:08 |
| Invisrcm | im on another pc just ran wievent | 17:08 |
| Invisrcm | it stopped at waiting for wireless events from interfaces | 17:08 |
| Invisrcm | and i just rand a program to see if the box finally connected and it did | 17:09 |
| Invisrcm | the problem is that its not doing it once it turns on, its now been on for about 2 hours so at one point in that time it decided to connect | 17:10 |
| Invisrcm12 | sorry about that got disconnected this other pc wireless is on the fritz | 17:11 |
| Invisrc | <tfried2001> any ides | 17:14 |
| Invisrc | heres what my config file looks like http://pastebin.com/aBtQWTTt | 17:18 |
| === dmart is now known as Guest73678 | ||
| === Guest73678 is now known as dmart_ | ||
| === dmart_ is now known as dmart | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!