From: Don Gould <don@bowenvale.co.nz>
To: lartc@vger.kernel.org
Subject: [LARTC] How to become your IP range...
Date: Sat, 05 Aug 2006 09:57:27 +0000 [thread overview]
Message-ID: <44D46B87.4010003@bowenvale.co.nz> (raw)
I have laptops visiting my network.
If they're configured for DHCP then I have no problem.
However if they're got static IPs set then I want my server to set it
self up automatically to provide internet access.
Eg.
Laptop Ip: 192.168.6.234 - just because the owners admin decided to.
Laptop default GW: 192.168.6.37 - also very random, but allowable...
My servers lan side is eth1, on detecting a packets running around with
the ip range above, it will then assign a new ip range to it self so
that the laptop will function.
Has anyone heard of an OSS system that will do this?
Cheers Don
--
Don Gould
www.thinkdesignprint.co.nz - www.tcn.bowenvale.co.nz -
www.bowenvale.co.nz - www.hearingbooks.co.nz - SkypeMe: ThinkDesignPrint
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-08-05 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 9:57 Don Gould [this message]
2006-08-05 15:05 ` [LARTC] How to become your IP range Roy-Magne Mo
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=44D46B87.4010003@bowenvale.co.nz \
--to=don@bowenvale.co.nz \
--cc=lartc@vger.kernel.org \
/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