Tuesday, October 17, 2006

Update: Wireless Connection

So it seems I may have been to hasty in blaming the schols network for my wireless network issues. I started using wireless at home to see if the problem would happen there -- and it did. There's nothing more annoying than watching a movie and all of a sudden having it stop playing. Not being able to slack off at school is one thing, but this is a whole other issue.

I grep'ed through my logs and found all sorts of this stuff:

Oct 15 00:00:37 wesley dhclient: DHCPREQUEST on eth1 to 192.168.0.1 port 67
Oct 15 00:00:38 wesley dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Oct 15 00:00:38 wesley dhclient: send_packet: Network is down
Oct 15 00:00:49 wesley dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Oct 15 00:00:49 wesley dhclient: send_packet: Network is down
Oct 15 00:00:52 wesley dhclient: DHCPREQUEST on eth1 to 192.168.0.1 port 67
Oct 15 00:01:01 wesley dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Oct 15 00:01:01 wesley dhclient: send_packet: Network is down
Oct 15 00:01:04 wesley dhclient: DHCPREQUEST on eth1 to 192.168.0.1 port 67
Oct 15 00:01:19 wesley dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Oct 15 00:01:19 wesley dhclient: send_packet: Network is down
Oct 15 00:01:22 wesley dhclient: DHCPREQUEST on eth1 to 192.168.0.1 port 67
Oct 15 00:01:30 wesley dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
Oct 15 00:01:30 wesley dhclient: send_packet: Network is down
Oct 15 00:01:30 wesley dhclient: DHCPREQUEST on eth1 to 192.168.0.1 port 67


The times on that correspond *exactly* to when I was booted offline. 'dhclient' is the default dhcp client in Ubuntu Dapper. However I prefer 'pump', it's something I always install after a re-format. It seems that my manually usage of pump doesn't work so well with Ubuntu's automagic dhcp stuff'n'crap. I guess the two daemons fight for who will hold control over the lease -- I'm not sure. In any case, after doing an apt-get remove dhcp3-client the problem was solved! No more wireless issues, yey!

Now...if I could only get something to automatically login to bluesocket for me I would be even happier

No comments: