Linux Netfilter discussions
 help / color / mirror / Atom feed
From: jim@netgate.com (Jim Thompson)
To: doug@aircomwireless.net, hostap@shmoo.com, ,
	netfilter@lists.netfilter.org, nocat@lists.nocat.net, ,
	nocatnet@lists.nocat.net,
Subject: Re: [NoCat] spoofing client IP configuration
Date: Thu, 13 Mar 2003 16:52:30 -0800 (PST)	[thread overview]
Message-ID: <20030314005230.85F27F4006@netgate.com> (raw)
In-Reply-To: <5.2.0.9.0.20030313064430.0323ecb0@yeagerautomation.com>

Its been discussed on the list before.  Its basically spoofed ARP responses and NAT.

Check the archives...

Jim

	From nocat-admin@lists.nocat.net  Thu Mar 13 04:14:29 2003
	X-Original-To: jim@netgate.com
	X-Sender: doug@ycomsystems.com@yeagerautomation.com
	X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
	To: nocat@lists.nocat.net;, nocatnet@lists.nocat.net;,
		hostap@shmoo.com;, netfilter@lists.netfilter.org
	From: Doug Yeager <doug@aircomwireless.net>
	Mime-Version: 1.0
	Content-Type: text/plain; charset="us-ascii"; format=flowed
	Subject: [NoCat] spoofing client IP configuration
	Sender: nocat-admin@lists.nocat.net
	Errors-To: nocat-admin@lists.nocat.net
	X-BeenThere: nocat@lists.nocat.net
	X-Mailman-Version: 2.0.12
	Precedence: bulk
	List-Help: <mailto:nocat-request@lists.nocat.net?subject=help>
	List-Post: <mailto:nocat@lists.nocat.net>
	List-Subscribe: <http://lists.nocat.net/mailman/listinfo/nocat>,
		<mailto:nocat-request@lists.nocat.net?subject=subscribe>
	List-Id: Development list for the NoCatAuth project <nocat.lists.nocat.net>
	List-Unsubscribe: <http://lists.nocat.net/mailman/listinfo/nocat>,
		<mailto:nocat-request@lists.nocat.net?subject=unsubscribe>
	List-Archive: <http://lists.nocat.net/pipermail/nocat/>
	Date: Thu, 13 Mar 2003 06:58:24 -0500

	o.k.,
	managing a public WLAN, people have all sorts of IP configurations preset 
	on their clients (not all are dhcp clients enabled).
	i am currently running a DHCP server and it works *MOST* of the time.  the 
	ultimate solution would be to somehow ignore the client ip configuration 
	and map to the clients on the server side based on their mac address, or 
	something like that.  i know this is possible because there are hotels that 
	do this kind of thing.....some terms like "nomadic server" have popped up.

	i want the server to route based on local addresses, so this service 
	hopefully would run at the mac level.
	the public wlan currently runs:
	nocat gateway
	HostAP
	Iptables firewall
	DHCPD  (server in question by this email)

	any alternatives to DHCP that do this would be great....i just want people 
	configured to their work ip configs to be able to get on.  would moving to 
	802.11 auth help?  i don't think so because after authentication you still 
	need an IP to do anything...unless i'm thinking about this wrong.

	thx,
	doug


	_______________________________________________
	NoCat mailing list
	NoCat@lists.nocat.net
	http://lists.nocat.net/mailman/listinfo/nocat

      reply	other threads:[~2003-03-14  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 11:58 spoofing client IP configuration Doug Yeager
2003-03-14  0:52 ` Jim Thompson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030314005230.85F27F4006@netgate.com \
    --to=jim@netgate.com \
    --cc=doug@aircomwireless.net \
    --cc=hostap@shmoo.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=nocat@lists.nocat.net \
    --cc=nocatnet@lists.nocat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox