summaryrefslogtreecommitdiffstats
path: root/usr.sbin/sysinstall/tcpip.c
Commit message (Collapse)AuthorAgeFilesLines
* Explicitly release a existing lease before we start dhclient (again).mbr2003-02-091-0/+1
| | | | | | | | | If we already have a lease and restart sysinstall (or something with the net configuration goes wrong), we would have to reboot just because there is a dhclient hanging around. Reviewed by: murray (re) MFC after: 5 days
* debugMsg() should end with "\n".kuriyama2002-11-011-1/+1
|
* If 'netInteractive' is set to true in an installation script, thenjhb2002-05-311-0/+18
| | | | | | temporarily turn off the nonInteractive variable around the DHCP and IPv6 Yes/No questions in a network device setup so that those questions are asked.
* Only build and link the pccard module on architectures that support it (andmurray2002-03-291-0/+2
| | | | that have room for pccardd on mfsroot.flp).
* Provide a more specific help line for PLIP installs, reminding themurray2001-12-101-0/+5
| | | | | | | user that they must provide the peer's IP address in the 'extra options to ifconfig' box. PR: misc/21273
* Silence warnings.murray2001-09-221-1/+1
|
* Rework the RTSOL logic from previous patch (it was wrong)jkh2001-09-151-4/+15
| | | | | PR: 26187 && 24136 Submitted by: Glenn Trewitt <trewitt@trewitt.org>
* Allow network device name to be given on the command line in themurray2001-09-051-1/+1
| | | | | | | | | | | | | interactive case. This already works for non-interactive installs, but at least one user thinks it would be useful and it certainly seems more correct to allow it here as well. So, this will now work : # sysinstall netDev=fxp0 tcpMenuSelect PR: bin/30229 Submitted by: Mikhail Teterin <mi@aldan.algebra.com>
* Whoops, forgot a hunk on the previous patch. Fix RTSOL variable handlingjkh2001-08-311-1/+1
| | | | AND DHCP handling.
* PR: 26187jkh2001-08-311-1/+1
| | | | Submitted by: Glenn Trewitt <glenn@trewitt.org>
* Fix IP address checking, now we allow addresses like 172.17.0.0/23 asjesper2001-07-121-12/+18
| | | | | | | | | a host address PR: misc/27799 Reviewed by: jkh Approved by: jkh MFC after: 1 month
* Mark relevant functions __printflike()/__printf0like() and silence some ofkris2001-07-051-1/+1
| | | | | | the non-constant format string warnings. MFC after: 1 week
* Introduce DEVICE_INIT, DEVICE_GET, and DEVICE_SHUTDOWN macros. As thedd2001-07-021-1/+1
| | | | | | | | | names suggest, they perform methods on Device's. In addition, they check that the pointer passed to them is valid; if it isn't, they pretend that the action failed. This fixes some crashes due to NULL dereferences (e.g., PR 26509). Approved by: jkh (some time ago)
* Ack! I finally got annoyed enough to actually kill this. There is nopeter2001-03-021-9/+0
| | | | | | need to manually force the network_interfaces variable in /etc/rc.conf, and it only ever gets in the way. rc.network and rc.network6 DTRT with the default of 'auto'. This should have died over a year ago.
* 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.
OpenPOWER on IntegriCloud