Re: [gentoo-user] Trouble Getting Wireless Networking Configured -- SOLVED

2007-07-03 Thread Drew Tomlinson

On 6/27/2007 7:45 AM Drew Tomlinson said the following:


On 6/27/2007 1:12 AM Alan McKinnon said the following:


On Wednesday 27 June 2007, Randy Barlow wrote:
 


Drew Tomlinson wrote:
  


I ran tcpdump on eth1 and no packets are leaving the interface.
Thus I assume that's why I'm not getting an address.



I don't know how to solve your problem, but I don't think DHCP is at
the TCP layer of your network, and so you shouldn't see packets for
DHCP there.  DHCP is a special protocol if I recall...
  



That's correct, dhcp is an ethernet protocol, and tcp/ip are one 
layer above it.


Drew should be able to see the packets with the 'proto ether' 
expression.

man tcpdump for more info

alan
 



Thank you both for your ideas.  I've tested and it seems that I should 
be able to see the packets without any special expressions.  I've run 
tcpdump on my DHCP server and can see packets from other nodes on my 
network:


 Client IP: bigdaddy
 Client Ethernet Address: 00:50:8d:d7:8d:89 (oui Unknown) 
[|bootp]
15:39:48.229850 IP (tos 0x0, ttl 128, id 25950, offset 0, flags 
[none], proto: UDP (17), length: 328) bigdaddy.bootpc  
255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:8d:d7:8d:89 
(oui Unknown), length: 300, xid:0x7707a3b2, secs:768, flags: [none]


When I run 'tcpdump -i eth1' on the laptop, I see no traffic 
whatsoever.  I read the man page for tcpdump regarding the 'proto 
ether' expression Alan mentions.  While it is true that this 
expression will limit the traffic captured, not specifying any 
expression will show all traffic.  Plus DHCP works by sending UDP 
packets and thus 'proto ether' does not seem to be appropriate.


Thanks,

Drew



For the archives...  Ditching wpa_supplicant in favor of iwconfig 
(wireless tools port) solved my problems.  Only downside is that I am 
unable to use WPA-PSK authentication.  Maybe a future version of 
wpa_supplicant will work?


Drew

--
Be a Great Magician!
Visit The Alchemist's Warehouse

http://www.alchemistswarehouse.com


--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Trouble Getting Wireless Networking Configured -- SOLVED

2007-07-03 Thread Thomas Tuttle
On Tue, 03 Jul 2007 06:08:17 -0700, Drew Tomlinson
[EMAIL PROTECTED] said:
 For the archives...  Ditching wpa_supplicant in favor of iwconfig 
 (wireless tools port) solved my problems.  Only downside is that I am 
 unable to use WPA-PSK authentication.  Maybe a future version of 
 wpa_supplicant will work?

Unlikely.  ;-)

I've used it a couple times and it always strikes me as much less stable
than wireless-tools, even when authenticating to non-WEP networks.  It
would routinely fail to associate, even when wireless-tools worked
effortlessly.  I'd love to run WPA, just because it's better, but I'm
unwilling to put up with wpa_supplicant.

My two cents,

Thomas Tuttle
-- 
Thomas Tuttle - [EMAIL PROTECTED] - http://www.ttuttle.net/

-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Trouble Getting Wireless Networking Configured

2007-06-27 Thread Alan McKinnon
On Wednesday 27 June 2007, Randy Barlow wrote:
 Drew Tomlinson wrote:
  I ran tcpdump on eth1 and no packets are leaving the interface.
  Thus I assume that's why I'm not getting an address.

 I don't know how to solve your problem, but I don't think DHCP is at
 the TCP layer of your network, and so you shouldn't see packets for
 DHCP there.  DHCP is a special protocol if I recall...

That's correct, dhcp is an ethernet protocol, and tcp/ip are one layer 
above it.

Drew should be able to see the packets with the 'proto ether' 
expression.
man tcpdump for more info

alan

-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Trouble Getting Wireless Networking Configured

2007-06-27 Thread Drew Tomlinson

On 6/27/2007 1:12 AM Alan McKinnon said the following:


On Wednesday 27 June 2007, Randy Barlow wrote:
 


Drew Tomlinson wrote:
   


I ran tcpdump on eth1 and no packets are leaving the interface.
Thus I assume that's why I'm not getting an address.
 


I don't know how to solve your problem, but I don't think DHCP is at
the TCP layer of your network, and so you shouldn't see packets for
DHCP there.  DHCP is a special protocol if I recall...
   



That's correct, dhcp is an ethernet protocol, and tcp/ip are one layer 
above it.


Drew should be able to see the packets with the 'proto ether' 
expression.

man tcpdump for more info

alan
 



Thank you both for your ideas.  I've tested and it seems that I should 
be able to see the packets without any special expressions.  I've run 
tcpdump on my DHCP server and can see packets from other nodes on my 
network:


 Client IP: bigdaddy
 Client Ethernet Address: 00:50:8d:d7:8d:89 (oui Unknown) [|bootp]
15:39:48.229850 IP (tos 0x0, ttl 128, id 25950, offset 0, flags [none], 
proto: UDP (17), length: 328) bigdaddy.bootpc  255.255.255.255.bootps: 
BOOTP/DHCP, Request from 00:50:8d:d7:8d:89 (oui Unknown), length: 300, 
xid:0x7707a3b2, secs:768, flags: [none]


When I run 'tcpdump -i eth1' on the laptop, I see no traffic 
whatsoever.  I read the man page for tcpdump regarding the 'proto ether' 
expression Alan mentions.  While it is true that this expression will 
limit the traffic captured, not specifying any expression will show all 
traffic.  Plus DHCP works by sending UDP packets and thus 'proto ether' 
does not seem to be appropriate.


Thanks,

Drew

--
Be a Great Magician!
Visit The Alchemist's Warehouse

http://www.alchemistswarehouse.com


--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Trouble Getting Wireless Networking Configured

2007-06-26 Thread Randy Barlow

Drew Tomlinson wrote:
I ran tcpdump on eth1 and no packets are leaving the interface. Thus I 
assume that's why I'm not getting an address.


I don't know how to solve your problem, but I don't think DHCP is at the 
TCP layer of your network, and so you shouldn't see packets for DHCP 
there.  DHCP is a special protocol if I recall...


--
Randy Barlow
http://electronsweatshop.com

But you are a chosen race, a royal priesthood, a holy nation, a people 
for his own possession, that you may proclaim the excellencies of him 
who called you out of darkness into his marvelous light. Once you were 
not a people, but now you are God's people; once you had not received 
mercy, but now you have received mercy. ~1 Peter 2:9-10


--
[EMAIL PROTECTED] mailing list