summaryrefslogtreecommitdiffstats
path: root/release/sysinstall/tcpip.c
Commit message (Collapse)AuthorAgeFilesLines
* Sysinstall has been repocopied to src/usr.sbin/sysinstall and everythingjhb2001-01-171-660/+0
| | | | now uses the sources found there.
* Add better IP, netmask and gateway checks.eivind2000-12-141-14/+92
| | | | | | | | - IP addresses are verified as being correct dotted quad format. - Netmasks are verified as being in correct dotted quad or 0x* format, and being consecutive 1 bits followed by consecutive 0 bits. - The gateway is verified as being correct dotted quad format and being reachable through the configured IP address and netmask.
* Adapt sysinstall to use the new msgNoYes() function which assumesjkh2000-12-141-2/+2
| | | | | | no as a default. Sysinstall should be both less dangerous and less annoying as a result of this change, though that's just my opinion (since they're the defaults which annoy ME the least :).
* Wait DAD complete after ifconfig up.ume2000-12-041-1/+7
|
* Popup IPv6 dialog, again.ume2000-10-211-1/+1
|
* Correct variable check for VAR_TRY_DHCP.jkh2000-09-151-1/+1
|
* This allows you to script sysinstall to say "NO" to DHCP and IPv6.murray2000-08-281-2/+4
| | | | | | | | | Previously, you could only script these features if you said YES. Oops. Accidentally commited to releng_4 first. PR: 20334 Approved by: jkh
* Restore the screen after possibly spamming it.jkh2000-07-251-0/+3
| | | | Reported by: Brian J. McGovern <mcgovern@spoon.beta.com>
* IPv6 support.ume2000-07-141-20/+101
| | | | | | | | | | | IPv6 configuration is only done by rtsol. Does someone really need manual configuration? :-) You can specify IPv6 DNS server as well. We have only one server ftp7.jp.freebsd.org that speaks IPv6 in this time. ftp7.jp speaks IPv4 as well and also listed as Japan #7. Approved by: jkh
* Fixed minor annoyance with sysinstall being redundant / braindead inmurray2000-04-061-1/+3
| | | | | | the network -> interfaces menu. Approved by: jkh
* Now I remember why I didn't write out the gateway in the DHCP case;jkh2000-02-201-1/+1
| | | | it was a feature.
* OK, I admit defeat - allow the user to override hostname and gatewayjkh2000-01-281-2/+2
| | | | values set by dhcp.
* Set pccard_ifconfig in /etc/rc.conf automatically.hosokawa2000-01-141-0/+5
|
* In retrospect, msgNotify() should leave its contents on the screenjkh1999-12-171-1/+1
| | | | | longer to give the user something to look at while things are happening. Change it to do so and insert the appropriate screen saves elsewhere.
* Completely rip-out and redesign sysinstall's refresh model as welljkh1999-12-141-1/+1
| | | | | | | | | | | | as redoing all the menus to have proper, or at least non-hallucinogenic, keyboard accelerators. This requires my recent update to libdialog to work properly and will probably also exhibit some other "interesting" behavior while the last few missing screen clears are found (which is why I'm not going to MFC immediately). At least now, however, sysinstall does not gratuitously redraw random screens at the drop of a hat and drive serial console installers out of their minds.
* I shouldn't have incremented PART_OFF; it was wrong and broke labeljkh1999-12-121-2/+0
| | | | | display to boot. Also fix some various warning fluff while I'm in here cleaning up.
* Defensive coding to prevent a potential segfault.jkh1999-11-081-1/+1
| | | | | PR: 14706 Submitted by: ru
* Really fix the auto keyword botch correctly by just letting itjkh1999-10-051-2/+2
| | | | | | do its job and not override it when set. Submitted by: Ruslan Ermilov <ru@FreeBSD.org>
* Sigh, too many late nights!jkh1999-09-301-1/+1
|
* Oh bollocks, I really screwed up the "auto" check here. Timejkh1999-09-271-1/+1
| | | | | | to crack the K&R; I must have forgotten the C language. :) Embarrassingly noticed by: Howard Gutch <logix@foobar.franken.de>
* Deal with new "auto" setting for network_interfaces.jkh1999-09-191-1/+1
|
* Only do dhclient once; it has its own internal retry which is more thanjkh1999-09-061-8/+10
| | | | | long enough (and doing it multiple times results in a dialog which waits AGES to complete).
* Oh crud, did I ever screw the pooch! Rather than sync this with -stable,jkh1999-09-021-29/+109
| | | | | | | | | | I backed-out the changes in -current and didn't touch stable at all (I thought I had my patch order reversed, not what actually happened). AIEEE! I can't even blame the crack for this one since I broke my crack pipe a few weeks ago. I think sleep deprivation gets the blame for this one. Medal for noticing this one goes to: Jim Bloom <bloom@acm.org>
* MFC: Catch 3.2-stable sysinstall up to 4.0-current level functionality,jkh1999-09-011-109/+29
| | | | | | | bringing in DHCP support. The only thing I left out were Poul-Henning's newfs changes since I'm not sure if he's brought the rest of that support into -stable yet. If it turns out that this is the case, I'll MFC those changes too.
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Quiet some overly chatty debug output, do some minor cleanups tojkh1999-08-211-13/+12
| | | | the DHCP support code.
* Re-enable play-nice-with-DHCP option now that bpf is the defaultjkh1999-08-071-3/+1
| | | | | in GENERIC. Now a dhcp-configured system will both install and boot initially with proper interface configuration.
* Intentionally do the wrong thing in using the initial DHCP values forjkh1999-07-221-1/+3
| | | | | | | | | | | | | ifconfig, essentially stealing the lease until the user goes and changes it. The alternative, sadly, is total dysfunction since bpf isn't in GENERIC and network connectivity would otherwise fail completely on first bootup when DHCP configuration was attempted again. The ultimate answer here is to make either bpf a loadable kernel module (which security conscious admins will be able to simply remove from /modules) or come up with a lighter weight mechanism just for dhcp and other apps that need to see broadcast packets but not otherwise sniff the wire in full bpf glory.
* Wait for dhclient in a far saner fashion.jkh1999-07-191-4/+9
| | | | Submitted by: obrien
* cleanup pass over new stuff.jkh1999-07-191-14/+5
|
* Another batch of fixes for dhcp support in sysinstall, now draggingjkh1999-07-191-63/+79
| | | | | | | | in some code from C. Stone to parse the lease information. This is still a WIP and this commit is largely intended to allow others to sync up; the dhclient code still only works when doing dhcp configuration post-install and requires a bit more work on the boot floppy before it will truly work in the minimal bootstrapping role.
* Some additional optimizations for using DHCP.jkh1999-07-181-5/+9
|
* Miscellaneous fixes for dhcp client support.jkh1999-07-181-2/+3
|
* Re-enable DHCP client support again (but optional and turned off by defaultjkh1999-07-161-12/+59
| | | | | | for the time being) for debugging purposes. Fix bug in options selection.
* Erm, correct mighty braino in previous "don't annoy me" change.jkh1999-05-071-7/+10
|
* Commit a more general version of the last patch; don't do any back-fillingjkh1999-05-071-18/+21
| | | | of values more than once. User might want to override them.
* Argh, those last two commits snuck in with the other one by mistake.jkh1999-05-061-1/+3
| | | | Disable the non-working dhcp client code I just committed by mistake.
* Fix includes; I had a slightly different Makefile than everyone elsejkh1999-05-061-1/+16
| | | | | | which is why I didn't see this. :) Noted by: Maxim Sobolev <sobomax@altavista.net>
* Totally change the way variables are accounted for in sysinstall.jkh1999-02-051-9/+9
| | | | | | | | Now we know which variables are internal and which need to be backed to /etc/rc.conf.site. rc.conf is not touched now. Also kget kernel change information back properly and set up a loader.rc file to use it.
* o Break fixups into binary fixups and XFree86 based fixups.jkh1998-11-151-2/+2
| | | | | | | | o Move fixups into extraction routine so all consumers don't have to duplicate the right behavior. o Make some things more orthogonal (just for asthetics sake) o Add option to go back and do it again if XF86Setup fails (possibly with a different setup - this one has always annoyed me).
* Accept gateway value of NOjkh1998-08-311-2/+2
|
* Put all variables in VAR_ #define's to force a single location for allpst1997-09-171-2/+3
| | | | | of these magic knobs. This is purely cosmetic and a documentation issue so we don't have to glop through the source code looking for gems.
* Add a new netInteractive variable so that the interactiveness of the TCPjkh1997-09-171-3/+9
| | | | | | setup dialog from scripts is more controllable. No more biasing off of hostname (which is now non-optional in the non-netInteractive case). Requested by: pst
* Make upgrade potentially a little less interactive.jkh1997-09-081-7/+9
| | | | | Add and document new loadConfig function (sort of like a script #include). Make TCP/IP setup far less chatty when it doesn't need to be.
* 1. Add a noWarn flag so that scripts can turn warnings off.jkh1997-06-181-2/+2
| | | | 2. If hostname not set from script, bring up interactive dialog anyway.
* YAMF22jkh1997-06-121-2/+2
|
* YAMF22jkh1997-06-121-2/+2
|
* 1. Make it possible to set up all the TCP/IP values from a script.jkh1997-06-091-30/+41
| | | | 2. Update to XFree86 3.3
* Add a registration screen so we can finally start counting our little userjkh1997-03-091-1/+3
| | | | puppies.
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
OpenPOWER on IntegriCloud