[SATLUG] Firewall and Wireless Laptop Problem

[Ed Coates]

Othniel,

That's not a problem here.  I have the wireless NIC hardcoded for 
192.168.1.6.  The scenario you described just doesn't fit all that well 
since it's only one machine on the network that it can't reach at these 
times.  It can ping the .1, .5, and .9 addresses, just not the 
firewall/gateway at .2.

Ed

On Wed, 28 Apr 2004, Graichen, Othniel M Mr AMEDDCS wrote:

> Ed:
> 
> One word for ya:  APIPA
> 
> If your wireless is unable to communicate with the DHCP server for
> any reason, it will APIPA.  I suspect this is what is happening to
> you.  The next time it happens, check if your IP address on the
> XP box is not within 169.254.x.x  If so, you are an APIPA victim.
> 
> When you restart Windows, you get out of APIPA mode.  The system 
> negotiates DHCP again and gets a proper lease.  Plus you've already
> checked that the AP is functioning and moves your notebook closer
> to the AP.  If that's not it -- it sure fits the description you gave.
> 
> Or you could just release/renew your XP box instead of rebooting /
> wearing out your pcmcia connector.
> 
> Give it a shot
> 
> OTHNIEL Graichen
> 
> Auth knee ell  
> (Campaigning for SATLUG President early this year)
> 
> -----Original Message-----
> From: satlug-bounces at satlug.org [mailto:satlug-bounces at satlug.org]On
> Behalf Of Ed Coates
> Sent: Friday, April 23, 2004 3:56 PM
> To: satlug at satlug.org
> Subject: [SATLUG] Firewall and Wireless Laptop Problem
> 
> 
> Hi All,
> 
> Here's one that has me scratching my head.  First a little bit about my 
> setup.  I have a Packard Bell P120 with 128MB of RAM acting as my 
> firewall (192.168.1.2) running SuSE 9.0.  One NIC goes to the DSL modem, 
> and the other into a D-Link 650+ Wireless Switch (192.168.1.1).  I also 
> have an AMD 900MHz machine with 512MB of RAM that acts as my 
> web/mail/mysql etc, you get the point server (192.168.1.9) running SuSE 
> 9.0.  Another machine is a P4 2.0 GHz with 512 MB of RAM (192.168.1.5) 
> running Windows XP Pro.  And lastly, the problem child, is a Dell 
> Lattitude D600 with built in wireless capabilities (192.168.1.6) running 
> Windows XP Pro.
> 
> Here's the problem.  Every once in a while, the laptop won't be able to 
> surf the web.  If I open a command prompt, I can ping .5, .1, and .9, but 
> when I try and ping .2 the request times out.  This will happen until I 
> disable the wireless NIC and restart it.  Then, when I connect to the 
> wireless network again, everything is back to normal.
> 
> It donned on me the other day to take a look at the firewall log and see 
> if there was anything going wrong there to cause it.  Here are a couple of 
> entries that show the ping packets being dropped.  Also here are the 
> output lines for iptables.  What I don't understand, is why it happens 
> some of the time, and not all of the time.
> 
> Any ideas out there?
> 
> Ed
> 
> iptables -A OUTPUT -p udp --dport 137:139 -j DROP
> iptables -A OUTPUT -p tcp -d 63.211.210.20 -j DROP
> iptables -A OUTPUT -p udp -d 63.211.210.20 -j DROP
> iptables -A OUTPUT -m state -p icmp --state INVALID -j OLOG_DROPB
> 
> Apr 22 20:24:32 nighthawk kernel: OUTPUT_DROPIN= OUT=lo SRC=192.168.1.2 
> DST=192.168.1.2 LEN=88 TOS=0x00 PREC=0xC0 TTL=64 ID=35954 PROTO=ICMP 
> TYPE=3 CODE=1 [SRC=192.168.1.2 DST=192.168.1.6 LEN=60 TOS=0x00 PREC=0x00 
> TTL=64 ID=35952 PROTO=ICMP TYPE=0 CODE=0 ID=1024 SEQ=11520 ] 
> 
> Apr 22 20:25:55 nighthawk kernel: OUTPUT_DROPIN= OUT=lo SRC=192.168.1.2 
> DST=192.168.1.2 LEN=88 TOS=0x00 PREC=0xC0 TTL=64 ID=35972 PROTO=ICMP 
> TYPE=3 CODE=1 [SRC=192.168.1.2 DST=192.168.1.6 LEN=60 TOS=0x00 PREC=0x00 
> TTL=64 ID=35970 PROTO=ICMP TYPE=0 CODE=0 ID=1024 SEQ=11776 ] 
> _______________________________________________
> Satlug mailing list
> Satlug at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug
> _______________________________________________
> Satlug mailing list
> Satlug at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug
>