Re: dhclient and the LiveCD
On Jul 30, 2013, at 8:56 PM, Sam Fourman Jr. wrote: > hello list, > > when using the bootonly.iso from the ftp servers... > > if you drop to a shell, use dhclient to obtain an ipaddress.. well you get > one.. but you have no DNS, because I think dhclient can't write to > /etc/resolv.conf > > what is the correct way to fix this? Well, if its anything like the LiveCD option from there regular full iso, then you can do 2 things; issue; mkdir /tmp/etc mount_unionfs /tmp/etc /etc * this makes all things done on the fs temporary or issue; mount -rw / * renders anything you write permanent I do either of these during LiveCD sessions depending on my goals. Unsure if this pertains to bootonly.iso but perhaps it helps? I'm also very new to the FreeBSD scene so any one feel free to correct. - aurf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
dhclient and the LiveCD
hello list, when using the bootonly.iso from the ftp servers... if you drop to a shell, use dhclient to obtain an ipaddress.. well you get one.. but you have no DNS, because I think dhclient can't write to /etc/resolv.conf what is the correct way to fix this? -- Sam Fourman Jr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: find netmask for offered lease in dhclient code
thank you so much. it is a hint for me to search more in code. i hope to find something. On Mon, Jul 15, 2013 at 2:04 PM, Olivier Nicole wrote: > > thanks Olivier, but may i ask you to explain it more? i have seen that > > there is a struct option_data in offered_lease in code but when these > > options set, how can i see the netmask value? where is it kept? > > Well, I am afraid I have no more explanation, I just did a dhcp renew > while running wireshark and check the contents of the dialog. I could > see that in the DHCP offer, there is an option field with holds the > netmask. I did not dig any further. > > Olivier > > > > > > > On Mon, Jul 15, 2013 at 1:43 PM, Olivier Nicole < > olivier.nic...@cs.ait.ac.th > >> wrote: > > > >> Hi, > >> > >> > i want to change dhclient code and customize it. in order to do that, > i > >> > need to know the netmask for offered ip. i see code and found that > struct > >> > client_lease *offered_leases, keeps information about offered lease > such > >> > as ip address but this structure hasn't any field about netmask. i > don't > >> > know how i can find the netmak for this offered ip address. > >> > >> According to wireshark, it's in option t=1, l=4 > >> > >> Olivier > >> > >> > any one has traced dhclient code before? how can i see the netmask for > >> > offered ip? > >> > > >> > thanks in advance, > >> > SAM > >> > ___ > >> > freebsd-questions@freebsd.org mailing list > >> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> > To unsubscribe, send any mail to " > >> freebsd-questions-unsubscr...@freebsd.org" > >> ___ > >> freebsd-questions@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to " > >> freebsd-questions-unsubscr...@freebsd.org" > >> > > > > > > > > -- > > *Sa.M* > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: find netmask for offered lease in dhclient code
> thanks Olivier, but may i ask you to explain it more? i have seen that > there is a struct option_data in offered_lease in code but when these > options set, how can i see the netmask value? where is it kept? Well, I am afraid I have no more explanation, I just did a dhcp renew while running wireshark and check the contents of the dialog. I could see that in the DHCP offer, there is an option field with holds the netmask. I did not dig any further. Olivier > > > On Mon, Jul 15, 2013 at 1:43 PM, Olivier Nicole > wrote: > >> Hi, >> >> > i want to change dhclient code and customize it. in order to do that, i >> > need to know the netmask for offered ip. i see code and found that struct >> > client_lease *offered_leases, keeps information about offered lease such >> > as ip address but this structure hasn't any field about netmask. i don't >> > know how i can find the netmak for this offered ip address. >> >> According to wireshark, it's in option t=1, l=4 >> >> Olivier >> >> > any one has traced dhclient code before? how can i see the netmask for >> > offered ip? >> > >> > thanks in advance, >> > SAM >> > ___ >> > freebsd-questions@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> > To unsubscribe, send any mail to " >> freebsd-questions-unsubscr...@freebsd.org" >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> freebsd-questions-unsubscr...@freebsd.org" >> > > > > -- > *Sa.M* > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: find netmask for offered lease in dhclient code
thanks Olivier, but may i ask you to explain it more? i have seen that there is a struct option_data in offered_lease in code but when these options set, how can i see the netmask value? where is it kept? On Mon, Jul 15, 2013 at 1:43 PM, Olivier Nicole wrote: > Hi, > > > i want to change dhclient code and customize it. in order to do that, i > > need to know the netmask for offered ip. i see code and found that struct > > client_lease *offered_leases, keeps information about offered lease such > > as ip address but this structure hasn't any field about netmask. i don't > > know how i can find the netmak for this offered ip address. > > According to wireshark, it's in option t=1, l=4 > > Olivier > > > any one has traced dhclient code before? how can i see the netmask for > > offered ip? > > > > thanks in advance, > > SAM > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > -- *Sa.M* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: find netmask for offered lease in dhclient code
Hi, > i want to change dhclient code and customize it. in order to do that, i > need to know the netmask for offered ip. i see code and found that struct > client_lease *offered_leases, keeps information about offered lease such > as ip address but this structure hasn't any field about netmask. i don't > know how i can find the netmak for this offered ip address. According to wireshark, it's in option t=1, l=4 Olivier > any one has traced dhclient code before? how can i see the netmask for > offered ip? > > thanks in advance, > SAM > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
find netmask for offered lease in dhclient code
hello all, i want to change dhclient code and customize it. in order to do that, i need to know the netmask for offered ip. i see code and found that struct client_lease *offered_leases, keeps information about offered lease such as ip address but this structure hasn't any field about netmask. i don't know how i can find the netmak for this offered ip address. any one has traced dhclient code before? how can i see the netmask for offered ip? thanks in advance, SAM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient and random disconnects
A follow-up: > third, > I would test with IPv6 disabled (entirely for the system), regardless of > connectivity type; > that also means to explicitly disable that failover setup line in your config > ipv6_activate_all_interfaces="**YES" > jb W/r to IPv6 (disable, enable, etc): read man pages for rc.conf(5) and search for ipv6; then set up whatever neccessary in /etc/rc.conf after considering what is in some preset variables in /etc/defaults/rc.conf. Btw, where did you get that "**YES" from in your config line for failover ? ipv6_activate_all_interfaces="**YES" The flag is "YES" or "NO". Also, are you running any firewall on your machine ? jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient and random disconnects
There are few things you should do. First, w/r to you complaint about first-kill-then restart, this will do it for you /etc/rc.d/dhclient lagg0 restart second, I remember you wrote that you have a trouble with disconnects even in wireless-only setup (no failover setup). If so, you should run and debug wireless only for the time being. Note: remember what wpa_supplicant does: It handles passing the login and encryption credentials to the authentication server. It also handles roaming from one wireless access point to another, in order to maintain connectivity. Here are some hints on setup: http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf and http://www.freebsd.org/cgi/man.cgi?query=wpa_supplicant&sektion=8 and debugging: http://www.examplenow.com/wpa_supplicant/ third, I would test with IPv6 disabled (entirely for the system), regardless of connectivity type; that also means to explicitly disable that failover setup line in your config ipv6_activate_all_interfaces="**YES" jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient and random disconnects
The thing very annoying, is that when my wireless disconnects, I must wait until wpa_supplicant re-associate to the AP. Then I have no working connection until I redo dhclient lagg0. And running dhclient lagg0 will say dhclient already running.. So I always need to kill it before. That issue does not let me work efficiently as I need to connect me again and again.. 2012/12/14 David Demelier > On 13/12/2012 23:39, jb wrote: > >> David Demelier gmail.com> writes: >> >> ... >>> I have setup lagg0 for a failover with ethernet, (note the problem >>> appears if I use wlan0 only too) >>> >>> # Fail over between wired/wireless. >>> cloned_interfaces="lagg0" >>> ifconfig_msk0="up" >>> ifconfig_ath0="ether 18:a9:05:87:38:0a" >>> ifconfig_wlan0="WPA" >>> ifconfig_lagg0="laggproto failover laggport msk0 laggport wlan0 DHCP" >>> ipv6_activate_all_interfaces="**YES" >>> >> According to the example in: >> http://www.freebsd.org/doc/en_**US.ISO8859-1/books/handbook/** >> network-aggregation.html<http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html> >> >> this line is missing in your setup: >> wlans_ath0="wlan0" >> >> which is also mentioned in: >> /etc/defaults/rc.conf >> ... >> #wlans_ath0="wlan0" # wlan(4) interfaces for ath0 device >> ... >> >> I can not test it as I do not have access to a FB machine right now. >> jb >> >> >> >> >> __**_ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions<http://lists.freebsd.org/mailman/listinfo/freebsd-questions> >> To unsubscribe, send any mail to "freebsd-questions-** >> unsubscr...@freebsd.org " >> > > Yes it is, but was earlier in the rc.conf, I forgot to paste it sorry, > > David > -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient and random disconnects
On 13/12/2012 23:39, jb wrote: David Demelier gmail.com> writes: ... I have setup lagg0 for a failover with ethernet, (note the problem appears if I use wlan0 only too) # Fail over between wired/wireless. cloned_interfaces="lagg0" ifconfig_msk0="up" ifconfig_ath0="ether 18:a9:05:87:38:0a" ifconfig_wlan0="WPA" ifconfig_lagg0="laggproto failover laggport msk0 laggport wlan0 DHCP" ipv6_activate_all_interfaces="YES" According to the example in: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html this line is missing in your setup: wlans_ath0="wlan0" which is also mentioned in: /etc/defaults/rc.conf ... #wlans_ath0="wlan0" # wlan(4) interfaces for ath0 device ... I can not test it as I do not have access to a FB machine right now. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Yes it is, but was earlier in the rc.conf, I forgot to paste it sorry, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient and random disconnects
David Demelier gmail.com> writes: > ... > I have setup lagg0 for a failover with ethernet, (note the problem > appears if I use wlan0 only too) > > # Fail over between wired/wireless. > cloned_interfaces="lagg0" > ifconfig_msk0="up" > ifconfig_ath0="ether 18:a9:05:87:38:0a" > ifconfig_wlan0="WPA" > ifconfig_lagg0="laggproto failover laggport msk0 laggport wlan0 DHCP" > ipv6_activate_all_interfaces="YES" According to the example in: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html this line is missing in your setup: wlans_ath0="wlan0" which is also mentioned in: /etc/defaults/rc.conf ... #wlans_ath0="wlan0" # wlan(4) interfaces for ath0 device ... I can not test it as I do not have access to a FB machine right now. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient and random disconnects
David Demelier gmail.com> writes: > ... Logs are your friends. If the lease actually expires and you have to get a new IP (a new lease), then you could have a temporary disconnect. But if dhcp server(s) are working correctly the lease should be renewed or rebound without problems. Search for "dhc" and check how much time (see time stamps) it takes to renew, or rebind your IP address, or if it has any trouble with both of them and it is forced to obtain a new lease: $ less -i /var/log/messages Look for any other errors in there too - e.g. WPA2 encryption protocol related, like failing of security key exchange. If you find any, post a sufficient copy to the list here. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient and random disconnects
On 30/11/2012 21:15, jb wrote:
David Demelier gmail.com> writes:
Hi,
In my university, I have a WPA-EAP wifi access point, it requires
authentification to access, with dhclient, I'm disconnected randomly and
I must run wpa_cli reconfigure / dhclient again to get it working.
This is really too general - it could be a problem with AP or your box.
When you say randomly, do you mean like every hour or so, or every 10 min or
so ? What is the pattern ?
Does it happen that your box is left alone for extended period of time, that
is without user and active application activity, while being connected ? If
so, do you find your box disconnected after such time (what is the time
interval) ?
Do the disconnects happen at IP lease renewal times (see output below) ?
What could the problem be with dhclient? I don't know very well what
these processes are doing. Does the process check for lease by a
specific interval?
Yes, it does IP lease renewal.
Post to the list the following outputs while using dhclient:
Your wireless configuration (relevant data only):
$ cat /etc/rc.conf
Review /etc/defaults/rc.conf w/r to dhclient and wpa_supplicant.
Do you have anything related to your wireless card driver in loader(8)
tunables or sysctl(8) variables ?
Your wpa_supplicant_conf_file, presumably:
$ cat /etc/wpa_supplicant.conf
$ ps auxwww | grep -i dhclient
Config file:
$ cat /etc/dhclient.conf
Your lease renewal log file:
# cat /var/db/dhclient.leases.
$ ifconfig -a
$ netstat -s
Any wireless card driver related messages (substitute wpi for yours):
$ grep -i wpi /var/log/messages
After that spend some time with:
$ apropos dhclient
dhclient(8) - Dynamic Host Configuration Protocol (DHCP) client
dhclient-script(8) - DHCP client network configuration script
dhclient.conf(5) - DHCP client configuration file
dhclient.leases(5) - DHCP client lease database
You should not hesitate to contact, if possible, your Uni sys admin and ask
about it.
By now you should be an expert - after all you use FreeBSD for a reason :-)
jb
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Hello thanks for your answer,
I have setup lagg0 for a failover with ethernet, (note the problem
appears if I use wlan0 only too)
# Fail over between wired/wireless.
cloned_interfaces="lagg0"
ifconfig_msk0="up"
ifconfig_ath0="ether 18:a9:05:87:38:0a"
ifconfig_wlan0="WPA"
ifconfig_lagg0="laggproto failover laggport msk0 laggport wlan0 DHCP"
ipv6_activate_all_interfaces="YES"
my wpa_supplicant.conf is like this :
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="osiris-sec"
proto=WPA2 WPA
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TTLS
ca_cert="/etc/iut-cert.pem"
anonymous_identity="anonym...@u-strasbg.fr"
phase2="auth=PAP"
identity="demelier"
password="***"
}
The dhclient.leases.lagg0 is populated with a very long list of :
lease {
interface "lagg0";
fixed-address 172.29.23.190;
option subnet-mask 255.255.0.0;
option routers 172.29.255.254;
option domain-name-servers 130.79.200.200;
option domain-name "u-strasbg.fr";
option dhcp-lease-time 300;
option dhcp-message-type 5;
option dhcp-server-identifier 172.29.255.253;
option dhcp-renewal-time 150;
option dhcp-rebinding-time 262;
renew 4 2012/12/13 13:16:16;
rebind 4 2012/12/13 13:18:08;
expire 4 2012/12/13 13:18:46;
}
I dont have any driver settings in sysctl.
And the ifconfig :
markand@Melon ~ $ ifconfig
ath0: flags=8843 metric 0 mtu 2290
ether 18:a9:05:87:38:0a
nd6 options=21
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
status: associated
msk0: flags=8843 metric 0 mtu 1500
options=c019b
ether 18:a9:05:87:38:0a
inet6 fe80::1aa9:5ff:fe87:380a%msk0 prefixlen 64 scopeid 0x2
nd6 options=21
media: Ethernet autoselect (none)
status: no carrier
lo0: flags=8049 metric 0 mtu 16384
options=63
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff00
nd6 options=21
lagg0: flags=8843 metric 0 mtu 1500
ether 18:a9:05:87:38:0a
inet6 fe80::1aa9:5ff:fe87:380a%lagg0 prefixlen 64 scopeid 0x4
inet 172.29.23.190 netmask 0x broadcast 172.29.255.255
nd6 options=21
media: Ethernet autoselect
status: active
laggproto failover lagghash l2,l3,l4
laggport: wlan0 flags=4
laggport: msk0 flags=1
wlan0: flags=8843 metric 0 mtu 1500
ether 18:a9:05:87:38:0a
inet6 fe80::1aa9:5ff:fe87:380a%wlan0 prefixlen 64 scopeid 0
Re: dhclient and random disconnects
David Demelier gmail.com> writes: > > Hi, > > In my university, I have a WPA-EAP wifi access point, it requires > authentification to access, with dhclient, I'm disconnected randomly and > I must run wpa_cli reconfigure / dhclient again to get it working. This is really too general - it could be a problem with AP or your box. When you say randomly, do you mean like every hour or so, or every 10 min or so ? What is the pattern ? Does it happen that your box is left alone for extended period of time, that is without user and active application activity, while being connected ? If so, do you find your box disconnected after such time (what is the time interval) ? Do the disconnects happen at IP lease renewal times (see output below) ? > What could the problem be with dhclient? I don't know very well what > these processes are doing. Does the process check for lease by a > specific interval? Yes, it does IP lease renewal. Post to the list the following outputs while using dhclient: Your wireless configuration (relevant data only): $ cat /etc/rc.conf Review /etc/defaults/rc.conf w/r to dhclient and wpa_supplicant. Do you have anything related to your wireless card driver in loader(8) tunables or sysctl(8) variables ? Your wpa_supplicant_conf_file, presumably: $ cat /etc/wpa_supplicant.conf $ ps auxwww | grep -i dhclient Config file: $ cat /etc/dhclient.conf Your lease renewal log file: # cat /var/db/dhclient.leases. $ ifconfig -a $ netstat -s Any wireless card driver related messages (substitute wpi for yours): $ grep -i wpi /var/log/messages After that spend some time with: $ apropos dhclient dhclient(8) - Dynamic Host Configuration Protocol (DHCP) client dhclient-script(8) - DHCP client network configuration script dhclient.conf(5) - DHCP client configuration file dhclient.leases(5) - DHCP client lease database You should not hesitate to contact, if possible, your Uni sys admin and ask about it. By now you should be an expert - after all you use FreeBSD for a reason :-) jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
dhclient and random disconnects
Hi, In my university, I have a WPA-EAP wifi access point, it requires authentification to access, with dhclient, I'm disconnected randomly and I must run wpa_cli reconfigure / dhclient again to get it working. I have never found a solution for that, so I tried for testing, to use dhcpcd instead, and it seems to work, I don't have disconnects anymore. What could the problem be with dhclient? I don't know very well what these processes are doing. Does the process check for lease by a specific interval? I don't care about using dhcpcd instead of dhclient, but I would like to make it working instead of dhclient but dhclient_program="/usr/local/sbin/dhcpcd" in the rc.conf does not start dhcpcd at boot. Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: problem with dhclient after update to FreeBSD-8.3
On Sun, 06 May 2012 10:48:31 +0100 Matthew Seaman articulated: >On 05/05/2012 19:30, Carmel wrote: >> I just updated my system to "FreeBSD 8.3-STABLE #0" from version >> 8.2. I was getting warning messages regarding "webcamd" at boot-up; >> however, I got them fixed (I think) I loaded: cuse4bsd_load="YES" in >> the loader.conf file and placed: webcamd_enable="YES" in the rc.conf >> file. I had never used it before; however, I am assuming that the >> 8.3 version somehow requires it. > >What's happening is that 8.3 has introduced more comprehensive support >for a wider range of USB devices. It's just picking up on the presence >of a webcam now and suggesting software that could manage it. > >You don't need to enable the webcam at all: the kernel will recognise >it as a webcam from its built-in identifying codes, but unless you >enable some software to deal with it, it won't be able to do anything. While that may well be true, it does clutter up the boot-up process with a lot of sinister if only benign looking warning messages. There should be a way to silence them or at least make the warning message less sinister looking. Something like: "webcamd present but not enabled" like is done for other devices. >This usually shows up with USB ethernet devices suddenly appearing and >cluttering up ifconfig(8) output -- unlike webcams, ethernet interfaces >generally do have kernel level support automatically enabled. devd >will try and run dhclient on the interface to configure it, which I >guess is where your extra dhclent invocation is coming from. It is >possible to turn this behaviour off by adding something like: > > hint.usb.0.disabled=1 > >into /boot/loader.conf but this is using a sledgehammer to crack a nut, >as that turns off that usb bus entirely. (Warning: This may well have >deleterious effects on your ability to use a keyboard or mouse with the >system: use cautiously. Also, change that '0' to the appropriate bus >number if you need to) I think I will skip the sledgehammer technique for now. Thanks for the suggestion though. :) >> "dhclient" is listed as starting at the beginning of the log and >> again at the end. I never had this happen when using FreeBSD-8.2. I >> am still confused as to why "devd" wants to start "webcamd" > >devd only wants to start webcamd because you've installed the webcamd >software including /usr/local/etc/devd/webcamd.conf If you pkg_delete >the webcamd stuff and then restart devd, it won't try starting up >webcamd any more. I don't think removing it is really an option: pkg_info -R webcamd-3.5.0.2 Information for webcamd-3.5.0.2: Required by: gstreamer-plugins-all-1.3.0.10.1_12 gstreamer-plugins-v4l2-0.10.30,3 kde-4.7.4_1 kde-workspace-4.7.4_1 kdeartwork-4.7.4_1 kdenetwork-4.7.4_2 kdeplasma-addons-4.7.4_1 kdetoys-4.7.4_1 kdeutils-4.7.4_2 phonon-gstreamer-4.5.1 qt4-4.7.4 qt4-qtconfig-4.7.4 Interestingly enough, I never had "webcamd" initiated in the /etc/rc.conf file and never received a warning message about it having to be initialized until the update to FreeBSD-8.3. I am not sure if this should be considered a BUG or what. It doesn't appear that any of the software that requires it to be installed also require it to be running at boot-up. I don't even know who, if anyone, I should report this behavior to. >> All I guess I really have to get corrected is the "dhclient" thing, >> assuming it is a real problem and just not some useless noise. > >The 'dhclient already running' message is untidy, but harmless. It's >the rc system refusing to start a duplicate dhclient process on some >interface. As your network interface is via a PCI device, I can't see >why devd would think it should try and restart dhclient for it. There does appear to be a PR listed against this behavior as noted in Warren's post on this thread. <http://www.freebsd.org/cgi/query-pr.cgi?pr=165477> Thanks for your assistance Matthew. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: problem with dhclient after update to FreeBSD-8.3
On Sun, 6 May 2012 04:25:52 -0600 (MDT) Warren Block articulated: >On Sun, 6 May 2012, Matthew Seaman wrote: >> On 05/05/2012 19:30, Carmel wrote: > >>> All I guess I really have to get corrected is the "dhclient" thing, >>> assuming it is a real problem and just not some useless noise. >> >> The 'dhclient already running' message is untidy, but harmless. It's >> the rc system refusing to start a duplicate dhclient process on some >> interface. As your network interface is via a PCI device, I can't >> see why devd would think it should try and restart dhclient for it. > >http://www.freebsd.org/cgi/query-pr.cgi?pr=165477 may be relevant. >It's on 9-stable, I haven't compared with 8.3. Warren, I posted an addendum to that PR to indicate that the behavior is also occurring on "8.3" systems as well. Do you think it would be prudent to open a new PR with my info since it concerns FreeBSD-8.3 STABLE and not the "9.0" branch? I was also wondering if anyone other than myself is seeing this phenomenon on the "8.3" version. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: problem with dhclient after update to FreeBSD-8.3
On Sun, 6 May 2012, Matthew Seaman wrote: On 05/05/2012 19:30, Carmel wrote: All I guess I really have to get corrected is the "dhclient" thing, assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. http://www.freebsd.org/cgi/query-pr.cgi?pr=165477 may be relevant. It's on 9-stable, I haven't compared with 8.3. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: problem with dhclient after update to FreeBSD-8.3
On 05/05/2012 19:30, Carmel wrote: > I just updated my system to "FreeBSD 8.3-STABLE #0" from version 8.2. I > was getting warning messages regarding "webcamd" at boot-up; however, I > got them fixed (I think) I loaded: cuse4bsd_load="YES" in the > loader.conf file and placed: webcamd_enable="YES" in the rc.conf file. > I had never used it before; however, I am assuming that the 8.3 version > somehow requires it. What's happening is that 8.3 has introduced more comprehensive support for a wider range of USB devices. It's just picking up on the presence of a webcam now and suggesting software that could manage it. You don't need to enable the webcam at all: the kernel will recognise it as a webcam from its built-in identifying codes, but unless you enable some software to deal with it, it won't be able to do anything. This usually shows up with USB ethernet devices suddenly appearing and cluttering up ifconfig(8) output -- unlike webcams, ethernet interfaces generally do have kernel level support automatically enabled. devd will try and run dhclient on the interface to configure it, which I guess is where your extra dhclent invocation is coming from. It is possible to turn this behaviour off by adding something like: hint.usb.0.disabled=1 into /boot/loader.conf but this is using a sledgehammer to crack a nut, as that turns off that usb bus entirely. (Warning: This may well have deleterious effects on your ability to use a keyboard or mouse with the system: use cautiously. Also, change that '0' to the appropriate bus number if you need to) > "dhclient" is listed as starting at the beginning of the log and again > at the end. I never had this happen when using FreeBSD-8.2. I am still > confused as to why "devd" wants to start "webcamd" devd only wants to start webcamd because you've installed the webcamd software including /usr/local/etc/devd/webcamd.conf If you pkg_delete the webcamd stuff and then restart devd, it won't try starting up webcamd any more. > All I guess I really have to get corrected is the "dhclient" thing, > assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
problem with dhclient after update to FreeBSD-8.3
I just updated my system to "FreeBSD 8.3-STABLE #0" from version 8.2. I was getting warning messages regarding "webcamd" at boot-up; however, I got them fixed (I think) I loaded: cuse4bsd_load="YES" in the loader.conf file and placed: webcamd_enable="YES" in the rc.conf file. I had never used it before; however, I am assuming that the 8.3 version somehow requires it. I am still receiving an error message regarding "dhclient". This is an snippet of the screen logging at boot-up: nfe0: link state changed to DOWN Starting dhclient. nfe0: no link nfe0: link state changed to UP got link DHCPREQUEST on nfe0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.101 -- renewal in 43200 seconds. Starting Network: lo0 nfe0. lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 nd6 options=3 nfe0: flags=8843 metric 0 mtu 1500 options=82008 ether 00:19:21:5d:34:de inet 192.168.1.101 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active add net :::0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1nfe0: link state changed to DOWN Starting devd. Starting webcamd. Attached ugen1.3[0] to cuse unit -1 Starting webcamd. Attached ugen1.3[1] to cuse unit -1 Starting webcamd. Attached ugen1.3[2] to cuse unit -1 Starting ums0 moused. Starting webcamd. Attached ugen1.4[0] to cuse unit -1 Starting webcamd. Attached ugen1.4[1] to cuse unit -1 dhclient already running? (pid=435). "dhclient" is listed as starting at the beginning of the log and again at the end. I never had this happen when using FreeBSD-8.2. I am still confused as to why "devd" wants to start "webcamd" All I guess I really have to get corrected is the "dhclient" thing, assuming it is a real problem and just not some useless noise. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
dhclient not working with wpa
Hi. Problem is that my wireless card doesn't see any replies from DHCP server when I use wpa_cupplicant (it works fine without encryption), even tho it is associated with that access point. So it looks like the encryption bit is working but then dhclient fails. If I turn the encryption off then dhclient works. I've tried with isc dhclient both 31 and 41 versions. I've tried with manually setting IP/netmask and route. Nothing helps, my FreeBSD box just can't talk with the router over the wireless with encryption. I know that the router is OK because other clients can get IP address without any problems. I know that wireless card is OK because it works with that access point from other operating systems, it also works with other access points. I guess it may be related to PR number 145269. But it's marked as serious+open for a year now so maybe somebody got a working workaround? Any suggestions please? Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient doesn't work over wireless
> From owner-freebsd-questi...@freebsd.org Wed Dec 8 16:31:12 2010
> Date: Wed, 08 Dec 2010 23:01:30 +
> From: Michael
> To: freebsd-questions@freebsd.org
> Subject: dhclient doesn't work over wireless
>
> Hello,
>
> My FreeBSD laptop is unable to get IP address over DHCP but the same
> network works fine on Windows, Ubuntu and Android so I believe the
> problem lies in my FreeBSD configuration and not on the router/access
> point. Problem occurs only for wireless interface.
>
> FreeBSD 8.1 amd64 with Atheros interface. Wireless networking was
> working fine on that system (the same config files) until I had to
> replace my wireless router.
you replaced the "wireless router". Presumably this is also the wireless
'Access point', to which the laptop connects.
What are the chances that it doesn't support WPA, but *ONLY* supports WPA2?
May need to tweak the ifconfig params, and/or the supplicant 'key_mgmt' type.
>
> My rc.conf file:
>wlans_ath0="wlan0"
>ifconfig_wlan0="WPA SYNCDHCP"
>
> I'm using standard dhclient.conf file.
>
> My wpa_supplicant.conf file:
>network={
>ssid="wifi"
>scan_ssid=1
>bssid=XX:XX:XX:XX:XX:XX
>priority=9
>mode=0
>proto=RSN
>key_mgmt=WPA-PSK
>auth_alg=OPEN
>pairwise=CCMP
>group=CCMP
>psk="x"
> }
>
> Now after reboot I'm geting wlan0 connection (status associated):
> wlan0: flags=8843 metric 0 mtu 1500
>ether xx:xx:xx:xx:xx:xx
>inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255
>media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11g
>status: associated
>ssid wifi channel 9 (2452 MHz 11g) bssid d8:5d:4c:ea:cb:ee
>regdomain 103 indoor ecm authmode WPA2/802.11i privacy ON
>deftxkey UNDEF AES-CCM 2:128-bit txpower 20 bmiss 7 scanvalid 450
>bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5
>protmode CTS wme burst roaming MANUAL
>
> But for some reason it doesn't get the IP address!
> And whrn I manually try to: dhclient wlan0
>DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
>DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
>DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
>DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
>DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
>No DHCPOFFERS received.
>No working leases in persistent database - sleeping.
>
> Again, other systems doesn't seem to have any trouble with getting IP
> from this DHCP server and wired interface (em0) works fine too.
>
> Any ideas please?
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient doesn't work over wireless
On 09/12/2010 10:16, Paul B Mahol wrote:
On 12/9/10, Michael wrote:
Ok it looks like PR number 145269. Unfortunately there is no fix yet.
Thank you for your help, at least I know it's not just me.
That PR is invalid/useless. If you want feedback give more.
You have wpa_supplicant.conf?
Yes, this is my wpa_supplicant.conf file:
network={
ssid="wifi"
scan_ssid=1
bssid=XX:XX:XX:XX:XX:XX
priority=9
mode=0
proto=RSN
key_mgmt=WPA-PSK
auth_alg=OPEN
pairwise=CCMP
group=CCMP
psk="x"
}
Just to remind you - ifconfig says that wlan0 is associated with my
access point.
I'm happy to provide all details needed, just tell me what you need. I'm
running FreeBSD 8.1-RELEASE with all SA+errata patches. Standard
dhclient.conf file.
Michael
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient doesn't work over wireless
On 12/9/10, Michael wrote: > On 09/12/2010 02:51, Adam Vande More wrote: >> On Wed, Dec 8, 2010 at 5:01 PM, Michael wrote: >> >>> >>> Again, other systems doesn't seem to have any trouble with getting IP >>> from >>> this DHCP server and wired interface (em0) works fine too. >>> >>> Any ideas please? >>> >> >> Your answer lies within: >> >> http://www.freebsd.org/cgi/query-pr-summary.cgi > > Ok it looks like PR number 145269. Unfortunately there is no fix yet. > Thank you for your help, at least I know it's not just me. That PR is invalid/useless. If you want feedback give more. You have wpa_supplicant.conf? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient doesn't work over wireless
On 9 December 2010 09:11, Michael wrote: > On 09/12/2010 02:51, Adam Vande More wrote: > >> On Wed, Dec 8, 2010 at 5:01 PM, Michael wrote: >> >> >>> Again, other systems doesn't seem to have any trouble with getting IP >>> from >>> this DHCP server and wired interface (em0) works fine too. >>> >>> Any ideas please? >>> >>> >> Your answer lies within: >> >> http://www.freebsd.org/cgi/query-pr-summary.cgi >> > > Ok it looks like PR number 145269. Unfortunately there is no fix yet. > Thank you for your help, at least I know it's not just me. > > Michael > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > you could try isc-dhcp31-client or another client as a stop gap until the pr is resolved ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient doesn't work over wireless
On 09/12/2010 02:51, Adam Vande More wrote: On Wed, Dec 8, 2010 at 5:01 PM, Michael wrote: Again, other systems doesn't seem to have any trouble with getting IP from this DHCP server and wired interface (em0) works fine too. Any ideas please? Your answer lies within: http://www.freebsd.org/cgi/query-pr-summary.cgi Ok it looks like PR number 145269. Unfortunately there is no fix yet. Thank you for your help, at least I know it's not just me. Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient doesn't work over wireless
On Wed, Dec 8, 2010 at 5:01 PM, Michael wrote: > > Again, other systems doesn't seem to have any trouble with getting IP from > this DHCP server and wired interface (em0) works fine too. > > Any ideas please? > Your answer lies within: http://www.freebsd.org/cgi/query-pr-summary.cgi -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhclient doesn't work over wireless
On Wed, Dec 8, 2010 at 6:01 PM, Michael wrote: > > Again, other systems doesn't seem to have any trouble with getting IP from > this DHCP server and wired interface (em0) works fine too. > > Any ideas please? > A question first, is this a VirtualBox VM? If so, you'll need to either install the bridging adapter from vBox or use a NAT configuration, in which case you will get a 10.0.0.x IP address. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
dhclient doesn't work over wireless
Hello,
My FreeBSD laptop is unable to get IP address over DHCP but the same
network works fine on Windows, Ubuntu and Android so I believe the
problem lies in my FreeBSD configuration and not on the router/access
point. Problem occurs only for wireless interface.
FreeBSD 8.1 amd64 with Atheros interface. Wireless networking was
working fine on that system (the same config files) until I had to
replace my wireless router.
My rc.conf file:
wlans_ath0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"
I'm using standard dhclient.conf file.
My wpa_supplicant.conf file:
network={
ssid="wifi"
scan_ssid=1
bssid=XX:XX:XX:XX:XX:XX
priority=9
mode=0
proto=RSN
key_mgmt=WPA-PSK
auth_alg=OPEN
pairwise=CCMP
group=CCMP
psk="x"
}
Now after reboot I'm geting wlan0 connection (status associated):
wlan0: flags=8843 metric 0 mtu 1500
ether xx:xx:xx:xx:xx:xx
inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255
media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11g
status: associated
ssid wifi channel 9 (2452 MHz 11g) bssid d8:5d:4c:ea:cb:ee
regdomain 103 indoor ecm authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit txpower 20 bmiss 7 scanvalid 450
bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5
protmode CTS wme burst roaming MANUAL
But for some reason it doesn't get the IP address!
And whrn I manually try to: dhclient wlan0
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Again, other systems doesn't seem to have any trouble with getting IP
from this DHCP server and wired interface (em0) works fine too.
Any ideas please?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NANOBSD dhclient freeze
I did again the same build with include generic option and all binaries.
same results.
Did truss on the build host
Here is the result
truss /sbin/dhclient wlan-[K0
__sysctl(0xbfbfe5a4,0x2,0xbfbfe5ac,0xbfbfe5b0,0x0,0x0) = 0 (0x0)
mmap(0x0,328,PROT_READ|PROT_WRITE,MAP_ANON,-1,0x0) = 671764480 (0x280a5000)
munmap(0x280a5000,328) = 0 (0x0)
__sysctl(0xbfbfe608,0x2,0x2809be3c,0xbfbfe610,0x0,0x0) = 0 (0x0)
mmap(0x0,32768,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) =
671764480 (0x280a5000)
issetugid(0x28094867,0xbfbfeadc,0x104,0x0,0x0,0x0) = 0 (0x0)
open("/etc/libmap.conf",O_RDONLY,0666) ERR#2 'No such file or
directory'
open("/var/run/ld-elf.so.hints",O_RDONLY,00) = 2 (0x2)
read(2,"ehnt\^a\0\0\0...@\0\0\0\m^o\0\0"...,128) = 128 (0x80)
lseek(2,0x80,SEEK_SET) = 128 (0x80)
read(2,"/lib:/usr/lib:/usr/lib/compat:/u"...,143) = 143 (0x8f)
close(2) = 0 (0x0)
access("/lib/libc.so.7",0) = 0 (0x0)
open("/lib/libc.so.7",O_RDONLY,00) = 2 (0x2)
fstat(2,{ mode=-r--r--r-- ,inode=218,size=1369196,blksize=16384 }) = 0 (0x0)
pread(0x2,0x2809ad80,0x1000,0x0,0x0,0x0) = 4096 (0x1000)
mmap(0x0,1376256,PROT_NONE,MAP_PRIVATE|MAP_ANON|MAP_NOCORE,-1,0x0) =
671797248 (0x280ad000)
mmap(0x280ad000,1257472,PROT_READ|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_NOCORE,2,0x0)
= 671797248 (0x280ad000)
mmap(0x281e,24576,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_FIXED,2,0x133000)
= 673054720 (0x281e)
mprotect(0x281e6000,94208,PROT_READ|PROT_WRITE) = 0 (0x0)
close(2) = 0 (0x0)
sysarch(0xa,0xbfbfe670,0x2805d89b,0x2809a2f8,0x28072929,0x2809a2f8) = 0 (0x0)
mmap(0x0,736,PROT_READ|PROT_WRITE,MAP_ANON,-1,0x0) = 673173504 (0x281fd000)
munmap(0x281fd000,736) = 0 (0x0)
mmap(0x0,21896,PROT_READ|PROT_WRITE,MAP_ANON,-1,0x0) = 673173504 (0x281fd000)
munmap(0x281fd000,21896) = 0 (0x0)
sigprocmask(SIG_BLOCK,SIGHUP|SIGINT|SIGQUIT|SIGKILL|SIGPIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SIGPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2,0x0)
= 0 (0x0)
sigprocmask(SIG_SETMASK,0x0,0x0) = 0 (0x0)
__sysctl(0xbfbfe624,0x2,0x805c520,0xbfbfe62c,0x0,0x0) = 0 (0x0)
sigprocmask(SIG_BLOCK,SIGHUP|SIGINT|SIGQUIT|SIGKILL|SIGPIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SIGPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2,0x0)
= 0 (0x0)
sigprocmask(SIG_SETMASK,0x0,0x0) = 0 (0x0)
socket(PF_LOCAL,SOCK_DGRAM,0)= 2 (0x2)
fcntl(2,F_SETFD,FD_CLOEXEC) = 0 (0x0)
connect(2,{ AF_UNIX "/var/run/logpriv" },106)= 0 (0x0)
__sysctl(0xbfbfe754,0x2,0x281ec400,0xbfbfe75c,0x0,0x0) = 0 (0x0)
__sysctl(0xbfbfe644,0x2,0xbfbfe5dc,0xbfbfe64c,0x281d7c34,0xc) = 0 (0x0)
__sysctl(0xbfbfe5dc,0x2,0x281ec4f8,0xbfbfe6a8,0x0,0x0) = 0 (0x0)
readlink("/etc/malloc.conf",0xbfbfe763,1024) ERR#2 'No such file or
directory'
issetugid(0x281d6951,0xbfbfe763,0x400,0xbfbfe75c,0x0,0x0) = 0 (0x0)
break(0x810) = 0 (0x0)
__sysctl(0xbfbfe9e4,0x2,0xbfbfe9ec,0xbfbfe9f0,0x0,0x0) = 0 (0x0)
mmap(0x0,1048576,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) =
673173504 (0x281fd000)
mmap(0x282fd000,12288,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0)
= 674222080 (0x282fd000)
munmap(0x281fd000,12288) = 0 (0x0)
access("/etc/localtime",4) = 0 (0x0)
open("/etc/localtime",O_RDONLY,00) = 3 (0x3)
fstat(3,{ mode=-r--r--r-- ,inode=49456,size=751,blksize=16384 }) = 0 (0x0)
read(3,"TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,29000) = 751 (0x2ef)
close(3) = 0 (0x0)
clock_gettime(13,{1275078174.0 })= 0 (0x0)
open("/etc/dhclient.conf",O_RDONLY,0666) = 3 (0x3)
fstat(3,{ mode=-rw-r--r-- ,inode=49370,size=277,blksize=16384 }) = 0 (0x0)
read(3,"# $FreeBSD: src/etc/dhclient.con"...,16384) = 277 (0x115)
read(3,0x2820d000,16384) = 0 (0x0)
close(3) = 0 (0x0)
socket(PF_INET,SOCK_DGRAM,0) = 3 (0x3)
ioctl(3,SIOCGIFMEDIA,0xbfbfebb0) = 0 (0x0)
close(3) = 0 (0x0)
open("/dev/null",O_RDWR,00) = 3 (0x3)
stat("/etc/nsswitch.conf",{ mode=-rw-r--r--
,inode=49408,size=327,blksize=16384 }) = 0 (0x0)
open("/etc/nsswitch.conf",O_RDONLY,0666) = 4 (0x4)
ioctl(4,TIOCGETA,0xbfbfe920) ERR#25 'Inappropriate ioctl
for device'
fstat(4,{ mode=-rw-r--r-- ,inode=49408,size=327,blksize=16384 }) = 0 (0x0)
read(4,"#\n# nsswitc
NANOBSD dhclient freeze
Hello,
I'm having an issue with dhclient on nanobsd.
It requests a lease and never exits
truss /sbin/dhclient vr0
__sysctl(0xbfbfe684,0x2,0xbfbfe68c,0xbfbfe690,0x0,0x0) = 0 (0x0)
mmap(0x0,328,PROT_READ|PROT_WRITE,MAP_ANON,-1,0x0) = 671698944 (0x28095000)
munmap(0x28095000,328) = 0 (0x0)
__sysctl(0xbfbfe6e8,0x2,0x2808be3c,0xbfbfe6f0,0x0,0x0) = 0 (0x0)
mmap(0x0,32768,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) =
671698944 (0x28095000)
issetugid(0x280848a7,0xbfbfebac,0x104,0x0,0x0,0x0) = 0 (0x0)
open("/etc/libmap.conf",O_RDONLY,0666) ERR#2 'No such file
or directory'
open("/var/run/ld-elf.so.hints",O_RDONLY,00) = 2 (0x2)
read(2,"ehnt\^a\0\0\0...@\0\0\0\^]\0\0\0"...,128) = 128 (0x80)
lseek(2,0x80,SEEK_SET) = 128 (0x80)
read(2,"/lib:/usr/lib:/usr/local/lib\0",29) = 29 (0x1d)
close(2) = 0 (0x0)
access("/lib/libc.so.7",0) = 0 (0x0)
open("/lib/libc.so.7",O_RDONLY,00) = 2 (0x2)
fstat(2,{ mode=-r--r--r-- ,inode=173008,size=1148004,blksize=4096 }) = 0 (0x0)
pread(0x2,0x2808ad80,0x1000,0x0,0x0,0x0) = 4096 (0x1000)
mmap(0x0,1155072,PROT_NONE,MAP_PRIVATE|MAP_ANON|MAP_NOCORE,-1,0x0) =
671731712 (0x2809d000)
mmap(0x2809d000,1036288,PROT_READ|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_NOCORE,2,0x0)
= 671731712 (0x2809d000)
mmap(0x2819a000,24576,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_FIXED,2,0xfd000)
= 672768000 (0x2819a000)
mprotect(0x281a,94208,PROT_READ|PROT_WRITE) = 0 (0x0)
close(2) = 0 (0x0)
sysarch(0xa,0xbfbfe750,0x2805b37b,0x2808a2f8,0x2806ddd9,0x2808a2f8) = 0 (0x0)
mmap(0x0,736,PROT_READ|PROT_WRITE,MAP_ANON,-1,0x0) = 672886784 (0x281b7000)
munmap(0x281b7000,736) = 0 (0x0)
mmap(0x0,21896,PROT_READ|PROT_WRITE,MAP_ANON,-1,0x0) = 672886784 (0x281b7000)
munmap(0x281b7000,21896) = 0 (0x0)
sigprocmask(SIG_BLOCK,SIGHUP|SIGINT|SIGQUIT|SIGKILL|SIGPIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SIGPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2,0x0)
= 0 (0x0)
sigprocmask(SIG_SETMASK,0x0,0x0) = 0 (0x0)
__sysctl(0xbfbfe704,0x2,0x805a520,0xbfbfe70c,0x0,0x0) = 0 (0x0)
sigprocmask(SIG_BLOCK,SIGHUP|SIGINT|SIGQUIT|SIGKILL|SIGPIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SIGPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2,0x0)
= 0 (0x0)
sigprocmask(SIG_SETMASK,0x0,0x0) = 0 (0x0)
socket(PF_LOCAL,SOCK_DGRAM,0)= 2 (0x2)
fcntl(2,F_SETFD,FD_CLOEXEC) = 0 (0x0)
connect(2,{ AF_UNIX "/var/run/logpriv" },106)= 0 (0x0)
__sysctl(0xbfbfe824,0x2,0x281a6400,0xbfbfe82c,0x0,0x0) = 0 (0x0)
__sysctl(0xbfbfe744,0x2,0xbfbfe6dc,0xbfbfe74c,0x28192294,0xc) = 0 (0x0)
__sysctl(0xbfbfe6dc,0x2,0x281a64f8,0xbfbfe788,0x0,0x0) = 0 (0x0)
readlink("/etc/malloc.conf",0xbfbfe833,1024) ERR#2 'No such file
or directory'
issetugid(0x28190fb1,0xbfbfe833,0x400,0xbfbfe82c,0x0,0x0) = 0 (0x0)
break(0x810) = 0 (0x0)
__sysctl(0xbfbfeab4,0x2,0xbfbfeabc,0xbfbfeac0,0x0,0x0) = 0 (0x0)
mmap(0x0,1048576,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) =
672886784 (0x281b7000)
mmap(0x282b7000,299008,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0)
= 673935360 (0x282b7000)
munmap(0x281b7000,299008)= 0 (0x0)
access("/etc/localtime",4) = 0 (0x0)
open("/etc/localtime",O_RDONLY,00) = 3 (0x3)
fstat(3,{ mode=-r--r--r-- ,inode=133,size=751,blksize=16384 }) = 0 (0x0)
read(3,"TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,29000) = 751 (0x2ef)
close(3) = 0 (0x0)
clock_gettime(13,{1274949738.0 })= 0 (0x0)
open("/etc/dhclient.conf",O_RDONLY,0666) = 3 (0x3)
fstat(3,{ mode=-rw-r--r-- ,inode=142,size=162,blksize=16384 }) = 0 (0x0)
read(3,"initial-interval 1;\nsend host-n"...,16384) = 162 (0xa2)
read(3,0x2820d000,16384) = 0 (0x0)
close(3) = 0 (0x0)
socket(PF_INET,SOCK_DGRAM,0) = 3 (0x3)
ioctl(3,SIOCGIFMEDIA,0xbfbfec80) = 0 (0x0)
close(3) = 0 (0x0)
open("/dev/null",O_RDWR,00) = 3 (0x3)
stat("/etc/nsswitch.conf",{ mode=-rw-r--r--
,inode=76,size=323,blksize=16384 }) = 0 (0x0)
open("/etc/nsswitch.conf",O_RDONLY,0666) = 4 (0x4)
ioctl(4,TIOCGETA,0xbfbfea10) ERR#25 'Inappropriate
ioctl for device'
fstat(4,{ mode=-rw-r--r-- ,inode=76,size=323,blksize=16384 }) = 0 (0x0)
read(4,"#\n# nsswitch.conf(5) - name ser"...,16384) = 323 (0x143)
read(4,0x2823600
Re: diskless & dhclient
On 22/03/10 21:35, Mats Lindberg wrote: I've tried to get my freebsd diskless system to get hold of some of the dhcp-options. E.g. my dhcp-server will always be the nfs-server as well. So I was hoping to create the /etc/fstab with the the dhcpd's ip as the nfs server. Thus not needing to have the hard coded nfsroot:/conf/'ip-address'/etc. Instead i'm looking for having almost all necessary files in the nfsroot:/conf/base/etc directory. you only need /conf/'ip-address' if you need different configurations for different clients. The ip-address is that of the diskless client, not the server. I've tried to set ifconfig_ETHDEV="DHCP" in /etc/rc.conf and creating a bourne shell script /etc/dhclient_enter_hooks, but as far as I can detect the script is never run. I guess since the kernel already got the ip-address during pxeboot it does not care about renewing the ip-address, or?? No, when the client detects it is a diskless client, /etc/rc.initdiskless is executed. See documentation in that file. Anyway, iirc you can find the dhcp options with kenv(1). BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
diskless & dhclient
Hi all, I've tried to get my freebsd diskless system to get hold of some of the dhcp-options. E.g. my dhcp-server will always be the nfs-server as well. So I was hoping to create the /etc/fstab with the the dhcpd's ip as the nfs server. Thus not needing to have the hard coded nfsroot:/conf/'ip-address'/etc. Instead i'm looking for having almost all necessary files in the nfsroot:/conf/base/etc directory. I've tried to set ifconfig_ETHDEV="DHCP" in /etc/rc.conf and creating a bourne shell script /etc/dhclient_enter_hooks, but as far as I can detect the script is never run. I guess since the kernel already got the ip-address during pxeboot it does not care about renewing the ip-address, or?? I'm running a legacy FreeBSD 6.4. So - not really a specific question, more like a cry for guidance - anyone? /Mats ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
One MAC, two IP with DHCP (dhclient) how?
In an enviroment where the ethernet network interface is connected to a public ethernet network (internet). And a IPv4 address assignment scheme is static. One can simple add primary IP by: ifconfig inet 1.2.3.4 And an additional aliases with: ifconfig inet 1.2.3.5 alias This alias IP can then be used within a jail(8) enviroment. So far all is perfectly fine. But in an enviroment where the primary IP is retrieved or set with DHCP by using: dhclient How does one request an additional IP beside the primary one ..? Setting an alias directly with ifconfig won't work because the upstream network won't route it. Should one set an explicit xid or Client ID somehow? and how is that done in such case? (option dhcp-client-identifier data-string; in dhclient.conf) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ifconfig query/dhclient
On Mon, Aug 04, 2008 at 07:54:06PM +1000, Warren Liddell wrote: > Im trying to find out how i can change my net card on re0 to be a > 10BaseT full duplex instead of auto @ 100. > 'ifconfig re0 media 10baseT/UTP mediaopt full-duplex' should work. (See the re(4) and ifconfig(8) manpages.) Be aware that if you are forcing one end of the link to a specific mode (instead of letting it auto-negotiate speed and duplex) you will normally also have to force the other end of the link to the same settings. Most cheap (and some not-so-cheap) ethernet switches only support auto-negotiation. > Also trying to work out why when using dhclient fwe0 (presuming its > my wireless card) it never gets a link .. is there more to getting a > link with wireless? there is no encryption. fwe0 is not your wireless card. fwe(4) is for ethernet emulation over FireWire (aka ieee1394). (As clearly described in the fwe(4) manpage.) There are a large number of settings that can be used with wireless connections. See ifconfig(8) for the full list (look for references to 802.11). A couple of settings that you will probably need to set are the mode (11a, 11b or 11g) as well as the SSID. > > Any an all assistance is greatly appreciated. > -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ifconfig query/dhclient
On Mon, Aug 4, 2008 at 4:54 AM, Warren Liddell <[EMAIL PROTECTED]> wrote: > Im trying to find out how i can change my net card on re0 to be a 10BaseT > full duplex instead of auto @ 100. I don't know, but someone else can probably help. > Also trying to work out why when using dhclient fwe0 (presuming its my > wireless card) it never gets a link .. is there more to getting a link with > wireless? there is no encryption. Have you done 'ifconfig fwe0 up" first? -- Ned Ruggeri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ifconfig query/dhclient
Im trying to find out how i can change my net card on re0 to be a 10BaseT full duplex instead of auto @ 100. Also trying to work out why when using dhclient fwe0 (presuming its my wireless card) it never gets a link .. is there more to getting a link with wireless? there is no encryption. Any an all assistance is greatly appreciated. -- No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.5.12/1589 - Release Date: 3/08/2008 1:00 PM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
MPD5 + dhclient: Problem adding dns and search domain
Hi list, I finally managed to establish a PPTP VPN connection to my employer using mpd5. My problem now is that in order for the setup to work properly I need to supersede search domain and dns'es in "/etc/resolv.conf" either by hand or by editing "dhclient.conf". If I use "dhclient.conf" the VPN stuff is added way too soon, as I don't want to run mpd5 all the time, and consequently do it by hand. A couple of things slow down noticeably when being unable to reach the search domain. I can't imagine I'll have to edit "resolv.conf" by hand every time - also it's being overwritten once in a while anyway - probably by the dhcp daemon. What's a good man to do here?? thanks - Nikolaj Thygesen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: dhclient and dhcpd
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sam > Fourman Jr. > Sent: Tuesday, June 10, 2008 3:08 PM > To: [EMAIL PROTECTED] > Subject: dhclient and dhcpd > > quick question I can't seem to figure out > I have a FreeBSD 7 computer and I am having trouble with dhclient > > here is my setup > > Ethernet cable directly from fxp0 to a DSL Modem(that serves > 192.168.0.x via > DHCP) > A wireless card(ral0) in hostap mode it has a static ip of > 192.168.1.1. I > have dhcpd running and configured to listen on ral0 interface. it is > supposed to had out DHCP(192.168.1.x) to wifi clients. > > fxp0 needs to use dhclient to obtain a IP from the DSL modem > the problem is, if I run dhclient fxp0, I get a reply from > the ral0 dhcpd > server. > how do I tell fxp0 to forget about ral0 and listen for the > DSL modem's dhcp > server ? > > isn't there some quick dhclient.conf setting? man dhclient.conf suggests you should use: reject 192.168.1.1; Hope this helps Tobias ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhclient and dhcpd
quick question I can't seem to figure out I have a FreeBSD 7 computer and I am having trouble with dhclient here is my setup Ethernet cable directly from fxp0 to a DSL Modem(that serves 192.168.0.x via DHCP) A wireless card(ral0) in hostap mode it has a static ip of 192.168.1.1. I have dhcpd running and configured to listen on ral0 interface. it is supposed to had out DHCP(192.168.1.x) to wifi clients. fxp0 needs to use dhclient to obtain a IP from the DSL modem the problem is, if I run dhclient fxp0, I get a reply from the ral0 dhcpd server. how do I tell fxp0 to forget about ral0 and listen for the DSL modem's dhcp server ? isn't there some quick dhclient.conf setting? Sam Fourman Jr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dummy dhclient
I suspect that what you are looking for is something that is just looking for DHCP traffic, but doesn¹t actually grab a lease. I don¹t think that there is a current port for this but this program http://dhcp-agent.sourceforge.net/ but dhcp-agent alleges to have a sniffer option. http://dhcp-agent.sourceforge.net/man/dhcp-sniff.1.html I haven¹t used it but I recall stumbling upon this a while back when I was looking for the same. If you try it out, let me know if it works. -J On 5/12/08 9:34 AM, "Wojciech Puchar" <[EMAIL PROTECTED]> wrote: > is there an option in dhclient (or other program) to try getting IP > address but - don't set anything in system. > > i mean something to just check for dhcp servers. > > or maybe something that just detects what DHCP servers are available. > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Johan Dowdy - CISSP Senior Systems Administrator nCircle Network Security 415.318.2880 "Any sufficiently advanced technology is indistinguishable from magic." -- Arthur C. Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dummy dhclient
On Monday 12 May 2008 18:34:32 Wojciech Puchar wrote: > is there an option in dhclient (or other program) to try getting IP > address but - don't set anything in system. > > i mean something to just check for dhcp servers. > > or maybe something that just detects what DHCP servers are available. The largely undocumented dhclient_exit|enter_hooks are suitable for this. Look at the source of /sbin/dhclient-script. In short, if you set exit_status to non-zero in /etc/dhclient-enter-hooks, nothing will be set. Some environment variables will be available to you, among which should be the ip of the dhcp server that responded. If you simply dump the env to stdout, you will see things available. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dummy dhclient
is there an option in dhclient (or other program) to try getting IP address but - don't set anything in system. i mean something to just check for dhcp servers. or maybe something that just detects what DHCP servers are available. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Binding dhclient to a particular network interface
Chuck, Oddly enough, after the system has finished starting up, running "dhclient ed1" on the command line does work (though "sockstat -l4" still shows local address as "*:68"). I could I have sworn that when I tried doing this the first time I added the dhclient_flags line, it failed. One thing I noticed as the system was starting up (after adding the dhclient_flags entry into /etc/rc.conf), was that dhclient completed too quickly. Normally when dhclient runs, it usually takes several seconds to do its thing (i.e... a noticeable delay between the "Starting dhclient" message appearing and the message immediately after it), however there was no delay between the appearance of the two messages - dhclient fails instantly. I doubt its relevant, but keep in mind this is a very old machine - an Intel Pentium 120MHz, 48MB RAM equipped with two ISA network cards, running FreeBSD 5.5. I'm afraid I cant run the command you suggested on the DHCP server, as the DHCP server in this case is built into the cable modem (to which I do not have shell access, if it even provides such). As for sticking a switch in between and connecting an a third PC to monitor - i'd prefer to leave that as a last resort for the time being as finding and setting up the additional hardware will be a bit of a pain. If you (or indeed anyone else) has any other suggestions, please do share. Thanks, Jazz - Original Message - From: "Chuck Swiger" <[EMAIL PROTECTED]> To: "Jasvinder S. Bahra" <[EMAIL PROTECTED]> Cc: "FreeBSD-questions List" Sent: Monday, July 30, 2007 9:38 PM Subject: Re: Binding dhclient to a particular network interface > Jasvinder S. Bahra wrote: > > Chuck, > > > > I gave this a shot, but this stopped the interface being assigned an IP > > address at all (i.e... before the change, the interface had a valid IP > > address assigned by the DHCP server in my cable modem, but after making the > > change and restarting, the "ifconfig" command shows the interface having an > > IP address of 0.0.0.0). > > > > I do agree though - the man page explicitly says that this should work. > > Does running "dhclient ed1" from the command line work? > Is the DHCP server providing the right answer? > > Running "tcpdump -s 0 arp or port bootps" would give you insight into what the > network is seeing, at least. Doing this from your DHCP server or a laptop on > a hub with the interface in question would be useful vantages, or a "trunk" or > "span" port on a smart switch, depending on what you might have handy. > > -- > -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Binding dhclient to a particular network interface
Jasvinder S. Bahra wrote: Chuck, I gave this a shot, but this stopped the interface being assigned an IP address at all (i.e... before the change, the interface had a valid IP address assigned by the DHCP server in my cable modem, but after making the change and restarting, the "ifconfig" command shows the interface having an IP address of 0.0.0.0). I do agree though - the man page explicitly says that this should work. Does running "dhclient ed1" from the command line work? Is the DHCP server providing the right answer? Running "tcpdump -s 0 arp or port bootps" would give you insight into what the network is seeing, at least. Doing this from your DHCP server or a laptop on a hub with the interface in question would be useful vantages, or a "trunk" or "span" port on a smart switch, depending on what you might have handy. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Binding dhclient to a particular network interface
Chuck, I gave this a shot, but this stopped the interface being assigned an IP address at all (i.e... before the change, the interface had a valid IP address assigned by the DHCP server in my cable modem, but after making the change and restarting, the "ifconfig" command shows the interface having an IP address of 0.0.0.0). I do agree though - the man page explicitly says that this should work. Oh, and i'm absolutely sure that the interface is configured to use DHCP. i.e... -- /etc/rc.conf snippet --- network_interfaces="ed1 ed2 lo0" ifconfig_ed1="DHCP" ifconfig_ed2="inet 10.1.0.1 netmask 255.255.255.0" ifconfig_lo0="inet 127.0.0.1" -- I added the dhclient_flags line you suggested, after the ifconfig_lo0 line shown above, though as far as I know the order does not matter. Thanks for the suggestion though. Anyone have anymore ideas? Regards, Jazz - Original Message - From: "Chuck Swiger" <[EMAIL PROTECTED]> To: "Jasvinder S. Bahra" <[EMAIL PROTECTED]> Cc: Sent: Monday, July 30, 2007 8:25 PM Subject: Re: Binding dhclient to a particular network interface > Jasvinder S. Bahra wrote: > > Terry, > > > > I tried adding the interface line to the dhclient configuration file (and > > then rebooting), but it had no effect. Entering the "sockstat -l4" command > > showed that local address was still "*:68". > > "man dhclient" suggests that the interface needs to be specified on the > command line. Try adding: > >dhclient_flags="ed1" > > ...to /etc/rc.conf, and double-check that you already have that interface > configured to use DHCP while you're there. :-) > > Regards, > -- > -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Binding dhclient to a particular network interface
Jasvinder S. Bahra wrote: Terry, I tried adding the interface line to the dhclient configuration file (and then rebooting), but it had no effect. Entering the "sockstat -l4" command showed that local address was still "*:68". "man dhclient" suggests that the interface needs to be specified on the command line. Try adding: dhclient_flags="ed1" ...to /etc/rc.conf, and double-check that you already have that interface configured to use DHCP while you're there. :-) Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Binding dhclient to a particular network interface
Terry, I tried adding the interface line to the dhclient configuration file (and then rebooting), but it had no effect. Entering the "sockstat -l4" command showed that local address was still "*:68". I had a look at the man pages for the configuration file, but other than trying again with the word "interface" (as opposed to "Interface"), couldn't think of any other approach. Thanks for the suggestion though, and if you (or indeed, anyone else) has any other ideas, please do share. Regards, Jazz - Original Message - From: "Terry Sposato" <[EMAIL PROTECTED]> To: "'Jasvinder S. Bahra'" <[EMAIL PROTECTED]> Cc: Sent: Monday, July 30, 2007 1:16 AM Subject: RE: Binding dhclient to a particular network interface > Hi Jasvinder, > > I believe if you add the following to /etc/dhclient.conf your problem will > be resolved. > > Interface "ed1"; > > Then reboot or alternatively restart your network and you should finding it > only binding to that interface. > > Regards, > > Terry > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jasvinder S. Bahra > Sent: Monday, 30 July 2007 9:27 AM > To: freebsd-questions@freebsd.org > Subject: Re: Binding dhclient to a particular network interface > > Adam, > > Thanks for responding, but I think theres been a misunderstanding here. > > The network setup on my machine is working correctly. My switch-facing > network card has a fixed IP address, while the cable-modem facing network > card is assigned one by the DHCP server built into the cable modem. This is > achieved by the following settings in /etc/rc.conf ... > > network_interfaces="ed1 ed2 lo0" > ifconfig_ed1="DHCP" > ifconfig_ed2="inet 10.1.0.1 netmask 255.255.255.0" > ifconfig_lo0="inet 127.0.0.1" > > The DHCP reference for ed1 means dhclient is started (thereafter running > continuously as a daemon), which sets ed1's IP address to that assigned by > the cable modem. > > Note that dhclient generally runs as a daemon because it has to handle lease > renewals and/or expiration. I have no issues with it running as a daemon. > > However, it is listening on all interfaces (which I do have an issue with), > i.e. running the command "sockstat -l4" on my system returns... > > USER: root > COMMAND: dhclient > PID: 267 > FD: 4 > PROTO: udp4 > LOCAL ADDRESS: *:68 > FOREIGN ADDRESS: *:* > > As you can see, local address is listed as "*:68", which means its listening > on port 68 on all interfaces. I want to instruct dhclient to only listen on > my cable-modem facing network card. If this were the case, issuing the > "sockstat -l4" command would return as above, but with local address saying > "<>:68" (where > <> is, unsurprisingly, the IP address > assigned to the network card by the DHCP server in the cable modem). > > Thanks again, > > Jazz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Binding dhclient to a particular network interface
Adam, No problem *smiles*. I'm at the same limit myself after all, and I do appreciate you stepping forward with your suggestions. Thanks again, Jazz - Original Message - From: "Adam J Richardson" <[EMAIL PROTECTED]> To: "Jasvinder S. Bahra" <[EMAIL PROTECTED]> Cc: Sent: Monday, July 30, 2007 1:02 AM Subject: Re: Binding dhclient to a particular network interface > > The DHCP reference for ed1 means dhclient is started (thereafter running > > continuously as a daemon), which sets ed1's IP address to that assigned by > > the cable modem. > > > > Note that dhclient generally runs as a daemon because it has to handle lease > > renewals and/or expiration. I have no issues with it running as a daemon. > > Oh, interesting. I had assumed the interface called dhclient itself if > the lease expired, or something. > > > As you can see, local address is listed as "*:68", which means its listening > > on port 68 on all interfaces. I want to instruct dhclient to only listen on > > my cable-modem facing network card. If this were the case, issuing the > > "sockstat -l4" command would return as above, but with local address saying > > "<>:68" (where > > <> is, unsurprisingly, the IP address > > assigned to the network card by the DHCP server in the cable modem). > > Is there a dhclient.conf somewhere in your /etc? That would surely hold > the answer. Possibly editing /etc/rc.d/dhclient or /etc/netstart might > help? I'm at the edge of my FreeBSD knowledge and in danger of falling > off, so I'll stop with the suggestions now. :) > > Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Binding dhclient to a particular network interface
Hi Jasvinder, I believe if you add the following to /etc/dhclient.conf your problem will be resolved. Interface "ed1"; Then reboot or alternatively restart your network and you should finding it only binding to that interface. Regards, Terry -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jasvinder S. Bahra Sent: Monday, 30 July 2007 9:27 AM To: freebsd-questions@freebsd.org Subject: Re: Binding dhclient to a particular network interface Adam, Thanks for responding, but I think theres been a misunderstanding here. The network setup on my machine is working correctly. My switch-facing network card has a fixed IP address, while the cable-modem facing network card is assigned one by the DHCP server built into the cable modem. This is achieved by the following settings in /etc/rc.conf ... network_interfaces="ed1 ed2 lo0" ifconfig_ed1="DHCP" ifconfig_ed2="inet 10.1.0.1 netmask 255.255.255.0" ifconfig_lo0="inet 127.0.0.1" The DHCP reference for ed1 means dhclient is started (thereafter running continuously as a daemon), which sets ed1's IP address to that assigned by the cable modem. Note that dhclient generally runs as a daemon because it has to handle lease renewals and/or expiration. I have no issues with it running as a daemon. However, it is listening on all interfaces (which I do have an issue with), i.e. running the command "sockstat -l4" on my system returns... USER: root COMMAND: dhclient PID: 267 FD: 4 PROTO: udp4 LOCAL ADDRESS: *:68 FOREIGN ADDRESS: *:* As you can see, local address is listed as "*:68", which means its listening on port 68 on all interfaces. I want to instruct dhclient to only listen on my cable-modem facing network card. If this were the case, issuing the "sockstat -l4" command would return as above, but with local address saying "<>:68" (where <> is, unsurprisingly, the IP address assigned to the network card by the DHCP server in the cable modem). Thanks again, Jazz - Original Message - From: "Adam J Richardson" <[EMAIL PROTECTED]> To: "Jasvinder S. Bahra" <[EMAIL PROTECTED]> Cc: Sent: Sunday, July 29, 2007 9:27 PM Subject: Re: Binding dhclient to a particular network interface > Jasvinder S. Bahra wrote: > > > > Is there a way of instructing dhclient to listen only on the cable-modem > > facing network interface? > > Hi Jazz, > > I don't find it necessary to run dhclient as a daemon. My server has two > interfaces, one wired and one wifi. In my /etc/rc.conf: > > ifconfig_fxp0="DHCP" > ifconfig_ndis0="WPA DHCP" > > [You might recognise ndis as the Project Evil driver for using Windows > network drivers under BSD.] > > When the netstart script runs, those two lines have the effect of > starting wpa_supplicant on ndis0, and running dhclient on both interfaces. > > Supposing I temporarily assign a static IP to fxp0, I can revert to DHCP > by typing: > > $ sudo dhclient fxp0 > > which does some DHCP magic and gets a lease. > > If I take ndis0 down I find I have to run /etc/netstart again to get it > back up, but you didn't want to know that. > > HtH > Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Binding dhclient to a particular network interface
The DHCP reference for ed1 means dhclient is started (thereafter running continuously as a daemon), which sets ed1's IP address to that assigned by the cable modem. Note that dhclient generally runs as a daemon because it has to handle lease renewals and/or expiration. I have no issues with it running as a daemon. Oh, interesting. I had assumed the interface called dhclient itself if the lease expired, or something. As you can see, local address is listed as "*:68", which means its listening on port 68 on all interfaces. I want to instruct dhclient to only listen on my cable-modem facing network card. If this were the case, issuing the "sockstat -l4" command would return as above, but with local address saying "<>:68" (where <> is, unsurprisingly, the IP address assigned to the network card by the DHCP server in the cable modem). Is there a dhclient.conf somewhere in your /etc? That would surely hold the answer. Possibly editing /etc/rc.d/dhclient or /etc/netstart might help? I'm at the edge of my FreeBSD knowledge and in danger of falling off, so I'll stop with the suggestions now. :) Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Binding dhclient to a particular network interface
Adam, Thanks for responding, but I think theres been a misunderstanding here. The network setup on my machine is working correctly. My switch-facing network card has a fixed IP address, while the cable-modem facing network card is assigned one by the DHCP server built into the cable modem. This is achieved by the following settings in /etc/rc.conf ... network_interfaces="ed1 ed2 lo0" ifconfig_ed1="DHCP" ifconfig_ed2="inet 10.1.0.1 netmask 255.255.255.0" ifconfig_lo0="inet 127.0.0.1" The DHCP reference for ed1 means dhclient is started (thereafter running continuously as a daemon), which sets ed1's IP address to that assigned by the cable modem. Note that dhclient generally runs as a daemon because it has to handle lease renewals and/or expiration. I have no issues with it running as a daemon. However, it is listening on all interfaces (which I do have an issue with), i.e. running the command "sockstat -l4" on my system returns... USER: root COMMAND: dhclient PID: 267 FD: 4 PROTO: udp4 LOCAL ADDRESS: *:68 FOREIGN ADDRESS: *:* As you can see, local address is listed as "*:68", which means its listening on port 68 on all interfaces. I want to instruct dhclient to only listen on my cable-modem facing network card. If this were the case, issuing the "sockstat -l4" command would return as above, but with local address saying "<>:68" (where <> is, unsurprisingly, the IP address assigned to the network card by the DHCP server in the cable modem). Thanks again, Jazz - Original Message - From: "Adam J Richardson" <[EMAIL PROTECTED]> To: "Jasvinder S. Bahra" <[EMAIL PROTECTED]> Cc: Sent: Sunday, July 29, 2007 9:27 PM Subject: Re: Binding dhclient to a particular network interface > Jasvinder S. Bahra wrote: > > > > Is there a way of instructing dhclient to listen only on the cable-modem > > facing network interface? > > Hi Jazz, > > I don't find it necessary to run dhclient as a daemon. My server has two > interfaces, one wired and one wifi. In my /etc/rc.conf: > > ifconfig_fxp0="DHCP" > ifconfig_ndis0="WPA DHCP" > > [You might recognise ndis as the Project Evil driver for using Windows > network drivers under BSD.] > > When the netstart script runs, those two lines have the effect of > starting wpa_supplicant on ndis0, and running dhclient on both interfaces. > > Supposing I temporarily assign a static IP to fxp0, I can revert to DHCP > by typing: > > $ sudo dhclient fxp0 > > which does some DHCP magic and gets a lease. > > If I take ndis0 down I find I have to run /etc/netstart again to get it > back up, but you didn't want to know that. > > HtH > Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Binding dhclient to a particular network interface
Jasvinder S. Bahra wrote: Is there a way of instructing dhclient to listen only on the cable-modem facing network interface? Hi Jazz, I don't find it necessary to run dhclient as a daemon. My server has two interfaces, one wired and one wifi. In my /etc/rc.conf: ifconfig_fxp0="DHCP" ifconfig_ndis0="WPA DHCP" [You might recognise ndis as the Project Evil driver for using Windows network drivers under BSD.] When the netstart script runs, those two lines have the effect of starting wpa_supplicant on ndis0, and running dhclient on both interfaces. Supposing I temporarily assign a static IP to fxp0, I can revert to DHCP by typing: $ sudo dhclient fxp0 which does some DHCP magic and gets a lease. If I take ndis0 down I find I have to run /etc/netstart again to get it back up, but you didn't want to know that. HtH Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Binding dhclient to a particular network interface
One of my machines has two network cards in it - one of which connects to a switch, and the other to a cable modem. The IP address assigned to the switch facing network interface is fixed. However, the IP address assigned to the network interface connected to the cable modem, is dynamically assigned by the DHCP server built into the cable modem. If I run the following command at the command line... sockstat -l4 I am presented with a list of IPv4 listening services. Unsurprisingly, one of these services is "dhclient". However, unlike some of the other services listed, it seems to be listening on both network interfaces - local address is listed as "*.68". Is there a way of instructing dhclient to listen only on the cable-modem facing network interface? Note that I did check the man pages for dhclient and dhclient.conf, but I didn't see anything specific to my requirements. There was something mentioned about how to configure settings for a particular interface, but that is not exactly what I need. Thanks all, Jazz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Confused about dhclient .conf and -script..
B. Cook wrote:
After reading way more about isc-dhcpd than I wanted to, I found out
that I can customize /etc/dhclient.conf (great). I found a great
dhclient.conf but it seemed to do things that I could not get my FreeBSD
box(es) to do.
I'm not quite sure what problems you're experiencing, but here's the one I use
to configure a secondary interface to a cable tv isp:
interface "fxp0" {
supersede domain-name "mydomain.com";
supersede domain-name-servers 127.0.0.1;
prepend routers 208.34.1.33;
request subnet-mask, broadcast-address, routers;
}
And of course: fconfig_fxp0="DHCP" in rc.conf
I just want an address for it, I DON'T want their Hostname or DNS, so the
supersede lines prevent it from replacing those. You probably want to remove
those.
-RW
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient: Can't update forward map bogus ... timed out
On Jun 11, 2007, at 11:48 AM, Noah wrote: I recently added firewall filters to my home linux box, and now I am experiencing named errors. I am running DDNS that sends out updates for my dynamically assigned IP address for the router/linux box at the edge of my home network. It appears that those updates periodically time out. I can telnet from the linux box to port 53 of the DNS server just fine. While DNS traffic can use 53/tcp, most DNS queries are done over UDP and not TCP. Presumably you should adjust your firewall rules or improve the logging of your firewall rulesets so you can better understand where the issue is. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhclient: Can't update forward map bogus ... timed out
HI List Folk,
I recently added firewall filters to my home linux box, and now I am
experiencing named errors. I am running DDNS that sends out updates for
my dynamically assigned IP address for the router/linux box at the edge
of my home network. It appears that those updates periodically time
out. I can telnet from the linux box to port 53 of the DNS server just
fine.
It appears that the logging on the server side is not working as well.
syslog is certainly running on the machine. I have directory
permissions set correctly.
here is my configuration:
--- logging configuration ---
logging {
channel simple_log {
file "/var/log/named/bind.log" versions 3 size 5m;
severity warning;
print-time yes;
print-severity yes;
print-category yes;
};
category default{
simple_log;
};
category dnssec { security_log; };
category update { security_log; };
category security { security_log; };
channel security_log {
file "/var/log/named/dns-security.log" versions 5 size 20m;
print-time yes;
print-category yes;
print-severity yes;
severity info;
};
};
--- logging configuration ---
# ls -ld /var/log/named/
drwx-- 2 bind wheel 512 Jun 11 08:19 /var/log/named/
# ls -l /var/log/named/
total 0
ps -auxww | grep syslog
root 68320 0.0 0.0 1376 988 ?? Is8:26AM 0:00.01
/usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s
dns server side system info
# pkg_info | grep bind
bind9-9.3.4 Completely new version of the BIND DNS suite with
updated D
FreeBSD-6.2
--- snip ---
Jun 11 07:17:10 hostname dhclient: Can't update forward map
bogus.domain.com. to 10.0.0.1: timed out
--- sinp ---
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Confused about dhclient .conf and -script..
I am trying to make a FreeBSD machine that gets a dynamic ip from a pfsense box work the same way as a Windows machine does. After reading way more about isc-dhcpd than I wanted to, I found out that I can customize /etc/dhclient.conf (great). I found a great dhclient.conf but it seemed to do things that I could not get my FreeBSD box(es) to do. So I found out that this config file actually came from a linux box (some ubuntu version) and that it runs a dhclient-script which I then found out that FreeBSD also has.. So I'm closer but not there yet and can not seem to figure out what I am missing. This is my /etc/dhclient.conf : send host-name "$HOSTNAME"; request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, host-name, netbios-name-servers, netbios-scope; timeout 30; script "/sbin/dhclient-script"; the dhclient-script is the stock one (6.2-p5) the linux one had the host-name set to "" after looking at the dhclient-script it looks like I need to use $HOSTNAME. Except when I change the hostname of the box (via hostname -s blahblah.local.domain) and then run dig against the dns server, the name blahblah did not register. Jun 11 09:47:11 pfsense dhcpd: DHCPACK on 192.168.1.13 to 00:b0:d0:a1:8f:17 ($HOSTNAME) via dc0 Jun 11 09:47:13 pfsense dhcpd: DHCPREQUEST for 192.168.1.13 from 00:b0:d0:a1:8f:17 ($HOSTNAME) via dc0 So what am I doing wrong, can I get what I am looking for? doing this: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient overwrites reslov.conf
On 1/26/07, [LoN]Kamikaze <[EMAIL PROTECTED]> wrote: I'm in a LAN with a relatively short lease time. That wouldn't be a problem if I wouldn't run a vpnc connection through this LAN. The vpnc connection sets /etc/resolv.conf as required, but dhclient overwrites it every couple of minutes, causing DNS not to work any more. Is there a way to make dhclient set up resolv.conf only when the IP of the interface is changed? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to " [EMAIL PROTECTED]" take a look at the /etc/dhclient.conf man page. You can add a line to set dns servers. example: # $FreeBSD: src/etc/dhclient.conf,v 1.3 2001/10/27 03:14:37 rwatson Exp $ # # This file is required by the ISC DHCP client. # See ``man 5 dhclient.conf'' for details. # # In most cases an empty file is sufficient for most people as the # defaults are usually fine. # prepend domain-name-server 130.253.166.41; just change 130.253.166.41 with the correct value jeremy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhclient overwrites reslov.conf
I'm in a LAN with a relatively short lease time. That wouldn't be a problem if I wouldn't run a vpnc connection through this LAN. The vpnc connection sets /etc/resolv.conf as required, but dhclient overwrites it every couple of minutes, causing DNS not to work any more. Is there a way to make dhclient set up resolv.conf only when the IP of the interface is changed? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Problems running dhclient on 6.1
Thanks for the response. That has fixed the problem. -Original Message- From: Doug Hardie [mailto:[EMAIL PROTECTED] Sent: Monday, December 25, 2006 2:09 PM To: [EMAIL PROTECTED] Subject: Re: Problems running dhclient on 6.1 On Dec 25, 2006, at 13:06, Calvin Smith wrote: > I just built a new system as a firewall using FreeBSD 6.1-RELEASE- > p11, IP > Filter V4.1.8 and am getting "No DHCPOFFERS received". I am > connected to the > internet via Comcast broadband. My old system running FreeBSD 4.6- > RELEASE > and IP Filter V 3.4.29 works just fine. I plugged my external > network port > into the internal network to see if I could get an assigned ip > using my > internal dhcp server and this worked just fine. When I try to use the > external connection to Comcast via the cable modem I receive no > replys to my > dhcp requests. I have tried swapping out different net cards with > the same > problem. There is probably something simple I am missing, but I > can't see > it at this time. Any help would be appreciated. You may need to reset the Cable Modem. Power it off for 5 minutes to clear its memory of the original computer MAC address. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems running dhclient on 6.1
I just built a new system as a firewall using FreeBSD 6.1-RELEASE-p11, IP Filter V4.1.8 and am getting "No DHCPOFFERS received". I am connected to the internet via Comcast broadband. My old system running FreeBSD 4.6-RELEASE and IP Filter V 3.4.29 works just fine. I plugged my external network port into the internal network to see if I could get an assigned ip using my internal dhcp server and this worked just fine. When I try to use the external connection to Comcast via the cable modem I receive no replys to my dhcp requests. I have tried swapping out different net cards with the same problem. There is probably something simple I am missing, but I can't see it at this time. Any help would be appreciated. Calvin Smith ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhcpd with wi and base system dhclient stopped working
I have a FreeBSD 6.x machine with an ath interface that serves as a wireless access point, dhcp server, router and gateway for my network. I have a FreeBSD 6.x laptop with an older wi interface that until recently was working just fine, using the base system dhclient. However, the other day when I fired it up it couldn't get an IP address from the dhcp server. Watching the logs I could see the server sending DHCPOFFER's, but the laptop wasn't receiving them for some reason. The same laptop booted to Windows gets an IP address just fine. Back on the FreeBSD side, I installed the net/isc-dhcp3-client port and it also gets an address just fine. The only think I can think of that changed between the last time this worked and the other day is the version of the dhcpd port running on the router. I updated to the 3.0.5-RC2 version of the net/isc-dhcp3-server port from the 3.0.4 version. What I'm wondering is how I can tell if this is a bug in the new dhcpd, a bug in the base system dhclient (newly exposed by a change in the dhcp server), or something else entirely (wi driver quirk? phase of the moon?). Any ideas? If this is something unique to my setup then I can live with my solution, but if it's an actual bug then I'd like to report it in the hopes of saving someone else the same headache. Thanks, JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Dhclient crashes my laptop
If I run dhclient wi0 the lights on the card go out, dhclient reports failure, and usually locks and reboots the machine. I am not sure what information you need, but here is what I have and what I have learned so far. I will gladly collect and post any info that may help. PCMCIA NIC card is a 3com airconnect, came with the access point. Laptop is an IBM ThinkPad 380xd (machine was free, rescued from trash at work to be a FreeBSD project) It is always plugged in when in use because the battery has about 5-10 minutes of life. Installed FreeBSD 6.1. dmesg shows that the wireless card is found and looks like it configures ok. If I enter IP & gateway manually it works. Tried using the other card slot, same problem. Tried to start pccardd per the web site, command not found. I found a post that says to run OLDCARD on this machine, but that's not in 6.1 and the card is fine until dhclient tries to help. It's a project and has no significant documents (I think), so wiping it and going to a version with OLDCARD can be done if necessary. After I get this working I may tackle APM so the thing will shut off when I tell it to. Thanks, Matthew Stremcha Technical Applications Analyst Sisu Medical Solutions 218.529.7972 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhclient in giant lock after a few days
Hi all, My FreeBSD server at home is running natd and ipfw on 6.1-STABLE. So it's the router and firewall for me at home. However, after a few days the dhclient, used for obtaining an IP address from my ISP (and the FreeBSD box gets that external IP address) gets into the giant lock and won't come out unless I kill dhclient and restart it again. Note that the dhclient runs fine for a few days first. After it comes in the giant lock, the functionality doesn't break or anything, it's just unusual behavior. I've been running 6.0 on this box first, where this behavior did not appear. However, after upgrading to 6.1-PRERELEASE (this was not intended, but that's besides the point) I've been experiencing this. Since it was a version before the betas I figured this would be fixed with the release of 6.1. However, I still have the same issue after upgrading to 6.1-STABLE. This is a little snapshot from top. And yes, it is constantly the most highest process when no HTTP or SMTP traffic passes trough. last pid: 5339; load averages: 0.09, 0.06, 0.01up 9+15:47:15 12:04:13 105 processes: 1 running, 103 sleeping, 1 lock CPU states: % user, % nice, % system, % interrupt, % idle Mem: 177M Active, 164M Inact, 82M Wired, 26M Cache, 57M Buf, 17M Free Swap: 935M Total, 280K Used, 934M Free PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 193 _dhcp1 960 1460K 964K *Giant 172:09 5.57% dhclient Note that this box has 6 jails with Postfix, Apache, BIND, MySQL and stuff like that. Also I'm using the vr(4) drivers for my NICs. Yes, I know that they aren't all that great, but that's the only thing I can use, since my VIA box doesn't have space for an external NIC. So if anybody has any advices or ideas, I'd really appreciate it. Thank you in advance. Jorn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"dhclient: unknown dhcp option value 0x51"
After updating to FreeBSD 6.1, this error is logged in /var/log/messages every hour (every time dhclient runs, my ISP's DHCP lease time). After googling, it seems like the option 0x51 is Client FQDN, fully qualified domain name, but why is it an "unknown option value" to dhclient? How can I tell dhclient to ignore this value? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient-exit-hooks
On Thu, May 04, 2006 at 10:41:05AM -0400, fbsd wrote: > Today I installed the isc-dhcp-client package. 'K. Hope you have better luck. I have never used it, so don't know anything about it. > I think this is another indicator of a bug with the base dhclient > and > that this bug makes the pkg version unusable. Yep, it certainly seems that something funky is going on. > How do I turn on this xtrace you talk about to capture the rc.conf > boot process? > I can not find man xtrace. There is a ktrace. No, it's a shell feature. You enable it by editing your shebang, so it looks like this: #!/bin/sh -x Or for interactive use, you can run it like this: # sh -x /path/to/your/script Sorry dude, I am now completely out of ideas. I hope you get it sorted. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpuedjx4x2cq.pgp Description: PGP signature
Help with isc-dhcp dhclient from port collection
I installed the isc-dhcp-client port. I have this in my rc.conf dhcp_program="/usr/local/sbin/dhclient" dhcp_flags="-q" ifconfig_dc0="DHCP" I get these error messages over and over. Have to reboot in single user mode to edit rc.conf to fix. Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. I have no other dhcp server running and there's no entry for dhcp or bootp in /etc/inetd.conf. Is there something else that has to be configured to get this to work? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: dhclient-exit-hooks
Today I installed the isc-dhcp-client package. It installs a completlly different dhclient-script. One that looks like it matchhes what your begin/exit scripts are designed to work with. # base version /etc/dhclient-exit-hooks /etc/dhclient-exit-hooks.sav /etc/dhclient.conf /sbin/dhclient /sbin/dhclient-script # port version /etc/rc.d/dhclient /usr/local/etc/dhclient.conf /usr/local/etc/dhclient.conf.sample /usr/local/sbin/dhclient /usr/local/sbin/dhclient-script At the end of the pkg install it says this. To setup dhclient, you may need to edit /etc/rc.conf to replace the base system dhclient, such as : dhcp_program="/usr/local/sbin/dhclient" dhcp_flags="-q" When I boot with this in my rc.conf dhcp_program="/usr/local/sbin/dhclient" dhcp_flags="-q"# no banner background_dhclient="YES" # Start dhcp client in the background. ifconfig_dc0="DHCP" I get these error messages over and over. Have to reboot in single user mode to edit rc.conf to fix. Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. When I boot with the same rc.conf content execpt with #ifconfig_dc0="DHCP" commented out, I do not get ip address from dhcp server. Next run I edited the pkg version of /usr/local/etc/dhclient.conf and added 'interface dc0' to it and rebooted and got same results. I think this is another indicator of a bug with the base dhclient and that this bug makes the pkg version unusable. How do I turn on this xtrace you talk about to capture the rc.conf boot process? I can not find man xtrace. There is a ktrace. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient-exit-hooks
(Apologies for the rather fragmentary nature of this post - I've been
typing and reading the scripts and man pages, trying to get my head round
what's going on...)
On Wed, May 03, 2006 at 05:43:48PM -0400, fbsd wrote:
> I figured the "Shared object not found" error is another sign
> of what is wrong in general so I commented out the mail command
> to concentrate on just the logger problem.
Fair enough - we'll come back to this later!
> During testing the
> logger problem I determined the script "if" statement is not
> working.
It ought to - the test is structured correctly, so I can't see any
reason it would not behave in any way other than you would expect.
> Problem seems more like bug in how and or when during the boot
> process the script is getting executed.
Yeah, it's beginning to look like it, isn't it? Did you try running it
with xtrace turned on? Perhaps you could even try running rc under
xtrace? (I have done this in the past, it spews forth a great deal of
noise, but among the noise you may find what you are looking for.)
> This has nothing to do with my script code.
> This is how FreeBSD is handling the default dhclient-script that
> comes pre installed on the system.
>
> The recorder directives have made no difference.
Yep, that makes sense - now I understand where your code is being called
from.
> Please note I am not using the isc-dhcp port dhclient.
> I am running the dhclient that comes as part of the base
> install of FreeBSD.
Noted.
> I have ifconfig_dc0="DHCP" in rc.conf to launch
> /sbin/dhclient-script.
> dhclient-script calls dhclient-exit-hooks
> I don't think the recorder directives get into play because
> dhclient does not use the rc.d environment.
No, not the ones you added to the dhclient-exit-hooks, but dhclient is
started by this block of code in /etc/network.subr:
if dhcpif $1; then
if [ $_cfg -ne 0 ] ; then
ifconfig $1 up
fi
/etc/rc.d/dhclient start $1
_cfg=0
fi
(dhcpif() tests the value of $1, returning true if it is DHCP or dhcp or
any combination in mixed case)
/etc/network.subr gets called from /etc/rc.d/netif (among others, but it
is netif that is called earliest, I believe).
/etc/rc.d/dhclient does use rcorder, although you are right in that
/sbin/dhclient doesn't know anything about it.
As far as I can tell, the sequence of events is something like this:
rc builds a list of files to run, using rcorder(8)
These scripts run, occasionally calling in other helper scripts (such as
/etc/network.subr).
When netif is called, it calls network.subr, which calls
/etc/rc.d/dhclient as necessary.
/etc/rc.d/dhclient starts /sbin/dhclient, which in turn calls
/sbin/dhclient-script at various points in its execution.
/sbin/dhclient-script then calls the enter and exit hooks at the
appropriate times.
> I know the dhclient-exit-hooks script is executing because of the
> echo commands I put in it before and after the IF statement.
Yep, that's fair comment.
> I also know the dhclient variables are being loaded in the
> /etc/dhcpd.name-servers file because I empty it before rebooting
> system, and after words I edit it and it contains the correct
> values.
Which suggests that your code is indeed Doing the Right Thing.
> I am beginning to think that something changed between 4.x and 6.0
> in
> the way the dhclient-script get processed during boot.
> It's acting like it gets executed to early in the boot process.
> Do I have enough evidence on this to submit a bug report???
I reckon it's worth trying under xtrace to see if that provides any clue.
You could also try adding -s to the logger call, so it prints its
messages to STDERR as well as to the nominated log file.
Dan
--
Daniel Bye
PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc
PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A
_
ASCII ribbon campaign ( )
- against HTML, vCards and X
- proprietary attachments in e-mail / \
pgpcKvJGJmCSp.pgp
Description: PGP signature
RE: dhclient-exit-hooks
You missed this statement I posted > IF I execute the same logger statements from the command > line they work as expected. That only could happen if the log files were all ready in syslog.conf. Good try. You have good grasp of how logging works. -Original Message- From: Duane Whitty [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 03, 2006 6:50 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] ORG Subject: Re: dhclient-exit-hooks fbsd wrote: > When this script runs the logger statements do not create any > message in the targeted log files. > IF I execute the same logger statements from the command > line they work as expected. Hi, Forgive my ignorance if it turns out I'm totally off track here but do you need a line in /etc/syslog.conf such as: !name-of-your-script *.* /var/log/dhcpd.log ^^^ or whatever level of logging you want I couldn't get named to log so to /etc/syslog.conf I added !named *.*/var/log/named.log and manually created /var/log/named.log to have messages of all levels logged. Just a shot in the dark... Best Regards, Duane Whitty -- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient-exit-hooks
fbsd wrote: When this script runs the logger statements do not create any message in the targeted log files. IF I execute the same logger statements from the command line they work as expected. Hi, Forgive my ignorance if it turns out I'm totally off track here but do you need a line in /etc/syslog.conf such as: !name-of-your-script *.* /var/log/dhcpd.log ^^^ or whatever level of logging you want I couldn't get named to log so to /etc/syslog.conf I added !named *.*/var/log/named.log and manually created /var/log/named.log to have messages of all levels logged. Just a shot in the dark... Best Regards, Duane Whitty -- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: dhclient-exit-hooks
I figured the "Shared object not found" error is another sign of what is wrong in general so I commented out the mail command to concentrate on just the logger problem. During testing the logger problem I determined the script "if" statement is not working. Problem seems more like bug in how and or when during the boot process the script is getting executed. This has nothing to do with my script code. This is how FreeBSD is handling the default dhclient-script that comes pre installed on the system. The recorder directives have made no difference. Please note I am not using the isc-dhcp port dhclient. I am running the dhclient that comes as part of the base install of FreeBSD. I have ifconfig_dc0="DHCP" in rc.conf to launch /sbin/dhclient-script. dhclient-script calls dhclient-exit-hooks I don't think the recorder directives get into play because dhclient does not use the rc.d environment. I know the dhclient-exit-hooks script is executing because of the echo commands I put in it before and after the IF statement. I also know the dhclient variables are being loaded in the /etc/dhcpd.name-servers file because I empty it before rebooting system, and after words I edit it and it contains the correct values. I am beginning to think that something changed between 4.x and 6.0 in the way the dhclient-script get processed during boot. It's acting like it gets executed to early in the boot process. Do I have enough evidence on this to submit a bug report??? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Daniel Bye Sent: Wednesday, May 03, 2006 4:42 PM To: Daniel Bye; freebsd-questions@freebsd.org Subject: Re: dhclient-exit-hooks On Wed, May 03, 2006 at 03:35:13PM -0400, fbsd wrote: > I do not see why postfix would have any thing to do with logger not > working. ACK. I've been talking about the "Shared object not found" error, which is definitely, from the error message you posted, caused by postfix not being able to find pcre. Has that problem gone away with the addition of the rcorder directives? (I've made the assumption here that your script is being called by rc, from one of your rc.d directories - if this is NOT the case, then you can pretty well ignore all I've said, and I apologise for being off the mark...) > I added some ehco statments to test if the "if" statment is working. > In this pass /etc/dhcpd.name-servers.tmp = /etc/dhcpd.name-servers > so the second echo should not have been executed, but it was Have you run the script with xtrace turned on? That at least will show you which lines of the script are being run. It might help you narrow down on the part that goes wrong. I really can't see anything wrong with the logic or syntax of your script, so this part of it is somewhat baffling to me. > >From testing it looks like only the dhcpc variables plus mv, > and echo commands work in the script. > > from the boot log > dc0: link state changed to DOWN > dc0: no link dc0: link state changed to UP > got link > dc0: link state changed to DOWN > before if check > after if check > DHCPREQUEST on dc0 to 255.255.255.255 port 67 > dc0: link state changed to UP > DHCPACK from 10.0.10.2 > dc0: link state changed to DOWN > bound to 10.0.10.4 -- renewal in 43200 seconds. > > > and here is the dhclient-exit-hooks script > > #!/bin/sh > > # PROVIDE: dhclient-exit-hooks > # REQUIRE: SERVERS > > ### Start of refresh dhcpd dns ip > # This script will propagate to dhcpd the changed dns servers ip > address > # which dhcp-client puts in resolv.conf. > # > # In dhcpd.conf replace the "option domain-name-servers" line with > this > # > # include "/etc/dhcpd.name-servers"; > # > # Spript uses the dhcpc variables to build temp line in dhcpd > format. > # Then compare temp content to production content. > # If different replace production content with new content from > temp, > # and restart dhcp to reread dhcpd.conf containing new ISP dns ip > addresses. > # > # logging event and sending email to user root is optional. > # > # Note: All LAN machines using dhcpd will not get new ISP dns ip > addresses > # until they reboot or their lease comes up for renewal. > # > # Each of the following lines must be one long line. IE: no wrap > arounds > > > > # load my_domain_name_servers variable with ISP dns ip addresses > from dhcpc > my_domain_name_servers=`echo $new_domain_name_servers | sed -e 's/ > /, /g'` > > # Create single line in file to be included in dhcpd.conf > echo "option domain-name-servers $my_domain_name_servers ;" > > /etc/dh
Re: dhclient-exit-hooks
On Wed, May 03, 2006 at 03:35:13PM -0400, fbsd wrote: > I do not see why postfix would have any thing to do with logger not > working. ACK. I've been talking about the "Shared object not found" error, which is definitely, from the error message you posted, caused by postfix not being able to find pcre. Has that problem gone away with the addition of the rcorder directives? (I've made the assumption here that your script is being called by rc, from one of your rc.d directories - if this is NOT the case, then you can pretty well ignore all I've said, and I apologise for being off the mark...) > I added some ehco statments to test if the "if" statment is working. > In this pass /etc/dhcpd.name-servers.tmp = /etc/dhcpd.name-servers > so the second echo should not have been executed, but it was Have you run the script with xtrace turned on? That at least will show you which lines of the script are being run. It might help you narrow down on the part that goes wrong. I really can't see anything wrong with the logic or syntax of your script, so this part of it is somewhat baffling to me. > >From testing it looks like only the dhcpc variables plus mv, > and echo commands work in the script. > > from the boot log > dc0: link state changed to DOWN > dc0: no link dc0: link state changed to UP > got link > dc0: link state changed to DOWN > before if check > after if check > DHCPREQUEST on dc0 to 255.255.255.255 port 67 > dc0: link state changed to UP > DHCPACK from 10.0.10.2 > dc0: link state changed to DOWN > bound to 10.0.10.4 -- renewal in 43200 seconds. > > > and here is the dhclient-exit-hooks script > > #!/bin/sh > > # PROVIDE: dhclient-exit-hooks > # REQUIRE: SERVERS > > ### Start of refresh dhcpd dns ip > # This script will propagate to dhcpd the changed dns servers ip > address > # which dhcp-client puts in resolv.conf. > # > # In dhcpd.conf replace the "option domain-name-servers" line with > this > # > # include "/etc/dhcpd.name-servers"; > # > # Spript uses the dhcpc variables to build temp line in dhcpd > format. > # Then compare temp content to production content. > # If different replace production content with new content from > temp, > # and restart dhcp to reread dhcpd.conf containing new ISP dns ip > addresses. > # > # logging event and sending email to user root is optional. > # > # Note: All LAN machines using dhcpd will not get new ISP dns ip > addresses > # until they reboot or their lease comes up for renewal. > # > # Each of the following lines must be one long line. IE: no wrap > arounds > > > > # load my_domain_name_servers variable with ISP dns ip addresses > from dhcpc > my_domain_name_servers=`echo $new_domain_name_servers | sed -e 's/ > /, /g'` > > # Create single line in file to be included in dhcpd.conf > echo "option domain-name-servers $my_domain_name_servers ;" > > /etc/dhcpd.name-servers.tmp > > echo " before if check" > > # See if different from what production file contains > cmp -s /etc/dhcpd.name-servers.tmp /etc/dhcpd.name-servers > if [ $? -gt 0 ]; then > echo " after if check" > # move the new file into place > mv /etc/dhcpd.name-servers.tmp /etc/dhcpd.name-servers > # restart dhcp using whatever is appropriate for your platform > #service dhcpd restart > #/usr/local/etc/rc.d/isc-dhcpd.sh restart -q > # Write message to /var/log/dhcpc.log to document event. > /usr/bin/logger -p user.warning -t dhclient Your ISP DNS IP > addresses changed. > # Write message to /var/log/dhcpd.log to document event. > /usr/bin/logger -p local1.warning -t dhclient Your ISP DNS IP > addresses changed. > fi > #rm -f /etc/dhcpd.name-servers.tmp > ### End of refresh dhcpd dns ip script > ### [---snip---] > > > using sendmail to construct the email made no difference. > > > Still get this message > > > > > > /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, > > > required by "send-mail" Has this gone away? --^ Apologies for the crossed wires. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgp5P3b2BRhsM.pgp Description: PGP signature
RE: dhclient-exit-hooks
I do not see why postfix would have any thing to do with logger not working. I added some ehco statments to test if the "if" statment is working. In this pass /etc/dhcpd.name-servers.tmp = /etc/dhcpd.name-servers so the second echo should not have been executed, but it was >From testing it looks like only the dhcpc variables plus mv, and echo commands work in the script. from the boot log dc0: link state changed to DOWN dc0: no link dc0: link state changed to UP got link dc0: link state changed to DOWN before if check after if check DHCPREQUEST on dc0 to 255.255.255.255 port 67 dc0: link state changed to UP DHCPACK from 10.0.10.2 dc0: link state changed to DOWN bound to 10.0.10.4 -- renewal in 43200 seconds. and here is the dhclient-exit-hooks script #!/bin/sh # PROVIDE: dhclient-exit-hooks # REQUIRE: SERVERS ### Start of refresh dhcpd dns ip # This script will propagate to dhcpd the changed dns servers ip address # which dhcp-client puts in resolv.conf. # # In dhcpd.conf replace the "option domain-name-servers" line with this # # include "/etc/dhcpd.name-servers"; # # Spript uses the dhcpc variables to build temp line in dhcpd format. # Then compare temp content to production content. # If different replace production content with new content from temp, # and restart dhcp to reread dhcpd.conf containing new ISP dns ip addresses. # # logging event and sending email to user root is optional. # # Note: All LAN machines using dhcpd will not get new ISP dns ip addresses # until they reboot or their lease comes up for renewal. # # Each of the following lines must be one long line. IE: no wrap arounds # load my_domain_name_servers variable with ISP dns ip addresses from dhcpc my_domain_name_servers=`echo $new_domain_name_servers | sed -e 's/ /, /g'` # Create single line in file to be included in dhcpd.conf echo "option domain-name-servers $my_domain_name_servers ;" > /etc/dhcpd.name-servers.tmp echo " before if check" # See if different from what production file contains cmp -s /etc/dhcpd.name-servers.tmp /etc/dhcpd.name-servers if [ $? -gt 0 ]; then echo " after if check" # move the new file into place mv /etc/dhcpd.name-servers.tmp /etc/dhcpd.name-servers # restart dhcp using whatever is appropriate for your platform #service dhcpd restart #/usr/local/etc/rc.d/isc-dhcpd.sh restart -q # Write message to /var/log/dhcpc.log to document event. /usr/bin/logger -p user.warning -t dhclient Your ISP DNS IP addresses changed. # Write message to /var/log/dhcpd.log to document event. /usr/bin/logger -p local1.warning -t dhclient Your ISP DNS IP addresses changed. fi #rm -f /etc/dhcpd.name-servers.tmp ### End of refresh dhcpd dns ip script ### -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Daniel Bye Sent: Wednesday, May 03, 2006 2:35 PM To: freebsd-questions@freebsd.org Subject: Re: dhclient-exit-hooks On Wed, May 03, 2006 at 02:25:08PM -0400, fbsd wrote: > There is nothing to rebuild. > I am using the built in dhclient that comes with the system. But it's not dhclient that's emitting the error, is it? It's your MTA. (check in /etc/mail/mailer.conf, and you will see that send-mail is an alias for the binary of your MTA) Atom's suggestion is worth pursuing. Dan > > -Original Message- > From: Atom Powers [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 03, 2006 1:05 PM > To: [EMAIL PROTECTED] > Cc: Norbert Papke; freebsd-questions@freebsd.org > Subject: Re: dhclient-exit-hooks > > > On 5/3/06, fbsd <[EMAIL PROTECTED]> wrote: > > I changed #! /bin/sh to #!/bin/sh it had no effect. > > Logger command still not producing output. > > > > using sendmail to construct the email made no difference. > > Still get this message > > > > /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, > > required by "send-mail" > > > > Did you rebuild the package? > I have had a similar problem with, in my case, net-snmp. > Reinstalling > the port fixed it. > Something about statically linked libraries I think. > > > -- > -- > Perfection is just a word I use occasionally with mustard. > --Atom Powers-- > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( )
Re: dhclient-exit-hooks
On Wed, May 03, 2006 at 02:25:08PM -0400, fbsd wrote: > There is nothing to rebuild. > I am using the built in dhclient that comes with the system. But it's not dhclient that's emitting the error, is it? It's your MTA. (check in /etc/mail/mailer.conf, and you will see that send-mail is an alias for the binary of your MTA) Atom's suggestion is worth pursuing. Dan > > -Original Message- > From: Atom Powers [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 03, 2006 1:05 PM > To: [EMAIL PROTECTED] > Cc: Norbert Papke; freebsd-questions@freebsd.org > Subject: Re: dhclient-exit-hooks > > > On 5/3/06, fbsd <[EMAIL PROTECTED]> wrote: > > I changed #! /bin/sh to #!/bin/sh it had no effect. > > Logger command still not producing output. > > > > using sendmail to construct the email made no difference. > > Still get this message > > > > /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, > > required by "send-mail" > > > > Did you rebuild the package? > I have had a similar problem with, in my case, net-snmp. > Reinstalling > the port fixed it. > Something about statically linked libraries I think. > > > -- > -- > Perfection is just a word I use occasionally with mustard. > --Atom Powers-- > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpOzKIawEEOF.pgp Description: PGP signature
RE: dhclient-exit-hooks
There is nothing to rebuild. I am using the built in dhclient that comes with the system. -Original Message- From: Atom Powers [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 03, 2006 1:05 PM To: [EMAIL PROTECTED] Cc: Norbert Papke; freebsd-questions@freebsd.org Subject: Re: dhclient-exit-hooks On 5/3/06, fbsd <[EMAIL PROTECTED]> wrote: > I changed #! /bin/sh to #!/bin/sh it had no effect. > Logger command still not producing output. > > using sendmail to construct the email made no difference. > Still get this message > > /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, > required by "send-mail" > Did you rebuild the package? I have had a similar problem with, in my case, net-snmp. Reinstalling the port fixed it. Something about statically linked libraries I think. -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient-exit-hooks
On Wed, May 03, 2006 at 12:52:07PM -0400, fbsd wrote: > Added this and still no joy. > > # PROVIDE: 'dhclient-exit-hooks' > # REQUIRE: SERVERS I'm sure it won't fix the problem, but you shouldn't include the quotes around the term for # PROVIDE:. Also, I think the rcorder block needs a blank line before and after it to be parsed properly by rcorder at startup. > As a side bar. This problem started in 6.0 I think. > I only ran 5.4 for short time before going to 6.0 > But I do know I did not have this problem in 3.x and 4.x versions. If these suggestions don't help, I'm afraid I'm out of ideas, sorry. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgplzQ5ZtQpNf.pgp Description: PGP signature
Re: dhclient-exit-hooks
On 5/3/06, fbsd <[EMAIL PROTECTED]> wrote: I changed #! /bin/sh to #!/bin/sh it had no effect. Logger command still not producing output. using sendmail to construct the email made no difference. Still get this message /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, required by "send-mail" Did you rebuild the package? I have had a similar problem with, in my case, net-snmp. Reinstalling the port fixed it. Something about statically linked libraries I think. -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: dhclient-exit-hooks
Added this and still no joy. # PROVIDE: 'dhclient-exit-hooks' # REQUIRE: SERVERS As a side bar. This problem started in 6.0 I think. I only ran 5.4 for short time before going to 6.0 But I do know I did not have this problem in 3.x and 4.x versions. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Daniel Bye Sent: Wednesday, May 03, 2006 12:22 PM To: Daniel Bye; freebsd-questions@freebsd.org Subject: Re: dhclient-exit-hooks On Wed, May 03, 2006 at 12:17:00PM -0400, fbsd wrote: > What goes in "your_script_service"? > Is it suppose to be script name dhclient-exit-hooks? Yes. Sorry, hadn't been paying due attention, otherwise I would have put 'dhclient-exit-hooks' ;-) > Is the # comment char to be removed? No - leave them in. Take a look at some of the scripts in /etc/rc.d/ and /usr/local/etc/rc.d/ Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient-exit-hooks
On Wed, May 03, 2006 at 12:17:00PM -0400, fbsd wrote: > What goes in "your_script_service"? > Is it suppose to be script name dhclient-exit-hooks? Yes. Sorry, hadn't been paying due attention, otherwise I would have put 'dhclient-exit-hooks' ;-) > Is the # comment char to be removed? No - leave them in. Take a look at some of the scripts in /etc/rc.d/ and /usr/local/etc/rc.d/ Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpkgbwkztiiG.pgp Description: PGP signature
RE: dhclient-exit-hooks
What goes in "your_script_service"? Is it suppose to be script name dhclient-exit-hooks? Is the # comment char to be removed? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Daniel Bye Sent: Wednesday, May 03, 2006 11:42 AM To: freebsd-questions@freebsd.org Subject: Re: dhclient-exit-hooks On Wed, May 03, 2006 at 08:07:39AM -0400, fbsd wrote: > I changed #! /bin/sh to #!/bin/sh it had no effect. > Logger command still not producing output. > > using sendmail to construct the email made no difference. > Still get this message > > /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, > required by "send-mail" Try putting something like this in your script file: # PROVIDE: your_script_service # REQUIRE: SERVERS If my understanding is correct, this should ensure that your script will not be called until after the dummy dependency SERVERS is run, which requires that ldconfig has already run. Note: not tested, not even sure it'll work, but it can't hurt to try. In any event, rcorder(8) might help. Dan > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Norbert > Papke > Sent: Tuesday, May 02, 2006 9:47 PM > To: [EMAIL PROTECTED] > Cc: freebsd-questions@freebsd.org > Subject: Re: dhclient-exit-hooks > > > On Tuesday 02 May 2006 06:12, fbsd wrote: > > IF I execute the cat command to issue the notification email > > from the command line it works fine, but when used in the > > script I get these messages during boot process. > > I am running postfix launched by the sendmail wrappers > > on a FreeBSD 6.0 system. > > > > "~/.mailrc": No match. > > Use sendmail(8) rather than mail(1). mail(1) expects to be run from > a user > session and looks for the user's preferences stored in the user's > ,mailrc > file. No user is available during the boot process. > > In your script, > > > #! /bin/sh > > Also, try removing the space between "#!" and "/bin/sh". It may be > causing > some weirdness. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient-exit-hooks
On Wed, May 03, 2006 at 08:07:39AM -0400, fbsd wrote: > I changed #! /bin/sh to #!/bin/sh it had no effect. > Logger command still not producing output. > > using sendmail to construct the email made no difference. > Still get this message > > /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, > required by "send-mail" Try putting something like this in your script file: # PROVIDE: your_script_service # REQUIRE: SERVERS If my understanding is correct, this should ensure that your script will not be called until after the dummy dependency SERVERS is run, which requires that ldconfig has already run. Note: not tested, not even sure it'll work, but it can't hurt to try. In any event, rcorder(8) might help. Dan > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Norbert > Papke > Sent: Tuesday, May 02, 2006 9:47 PM > To: [EMAIL PROTECTED] > Cc: freebsd-questions@freebsd.org > Subject: Re: dhclient-exit-hooks > > > On Tuesday 02 May 2006 06:12, fbsd wrote: > > IF I execute the cat command to issue the notification email > > from the command line it works fine, but when used in the > > script I get these messages during boot process. > > I am running postfix launched by the sendmail wrappers > > on a FreeBSD 6.0 system. > > > > "~/.mailrc": No match. > > Use sendmail(8) rather than mail(1). mail(1) expects to be run from > a user > session and looks for the user's preferences stored in the user's > ,mailrc > file. No user is available during the boot process. > > In your script, > > > #! /bin/sh > > Also, try removing the space between "#!" and "/bin/sh". It may be > causing > some weirdness. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpg8lWu8kCaE.pgp Description: PGP signature
RE: dhclient-exit-hooks
I changed #! /bin/sh to #!/bin/sh it had no effect. Logger command still not producing output. using sendmail to construct the email made no difference. Still get this message /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, required by "send-mail" -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Norbert Papke Sent: Tuesday, May 02, 2006 9:47 PM To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: dhclient-exit-hooks On Tuesday 02 May 2006 06:12, fbsd wrote: > IF I execute the cat command to issue the notification email > from the command line it works fine, but when used in the > script I get these messages during boot process. > I am running postfix launched by the sendmail wrappers > on a FreeBSD 6.0 system. > > "~/.mailrc": No match. Use sendmail(8) rather than mail(1). mail(1) expects to be run from a user session and looks for the user's preferences stored in the user's ,mailrc file. No user is available during the boot process. In your script, > #! /bin/sh Also, try removing the space between "#!" and "/bin/sh". It may be causing some weirdness. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient-exit-hooks
On Tuesday 02 May 2006 06:12, fbsd wrote: > IF I execute the cat command to issue the notification email > from the command line it works fine, but when used in the > script I get these messages during boot process. > I am running postfix launched by the sendmail wrappers > on a FreeBSD 6.0 system. > > "~/.mailrc": No match. Use sendmail(8) rather than mail(1). mail(1) expects to be run from a user session and looks for the user's preferences stored in the user's ,mailrc file. No user is available during the boot process. In your script, > #! /bin/sh Also, try removing the space between "#!" and "/bin/sh". It may be causing some weirdness. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhclient-exit-hooks
When this script runs the logger statements do not create any message in the targeted log files. IF I execute the same logger statements from the command line they work as expected. This is the boot time messages. dc0: link state changed to DOWN dc0: no link dc0: link state changed to UP got link dc0: link state changed to DOWN DHCPREQUEST on dc0 to 255.255.255.255 port 67 dc0: link state changed to UP DHCPACK from 10.0.10.2 dc0: link state changed to DOWN bound to 10.0.10.4 -- renewal in 43200 seconds. IF I execute the cat command to issue the notification email from the command line it works fine, but when used in the script I get these messages during boot process. I am running postfix launched by the sendmail wrappers on a FreeBSD 6.0 system. "~/.mailrc": No match. DHCPREQUEST on dc0 to 255.255.255.255 port 67 /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, required by "send-mail" dc0: link state changed to UP DHCPREQUEST on dc0 to 255.255.255.255 port 67 DHCPACK from 10.0.10.2 dc0: link state changed to DOWN bound to 10.0.10.4 -- renewal in 43200 seconds. #! /bin/sh # Start of refresh dhcpd dns ip script # # This script will propagate to dhcpd the changed dns servers ip # addresswhich dhcp-client puts in resolv.conf. # # In dhcpd.conf replace the "option domain-name-servers" line with this # # include "/etc/dhcpd.name-servers"; # # Script uses the dhcpc variables to build temp line in dhcpd format. # Then compare temp content to production content. # If different replace production content with new content from temp and # restart dhcp to reread dhcpd.conf containing new ISP dns ip addresses. # # logging event and sending email to user root is optional. # # Note: All LAN machines using dhcpd will not get new ISP dns ip # addresses until they reboot or their lease comes up for renewal. # # Each of the following lines must be one long line. IE: no wrap around # load my_domain_name_servers variable with ISP dns ip addresses from dhcpc my_domain_name_servers=`echo $new_domain_name_servers | sed -e 's/ /, /g'` # Create single line in file to be included in dhcpd.conf echo "option domain-name-servers $my_domain_name_servers ;" > /etc/dhcpd.name-servers.tmp # See if different from what production file contains cmp -s /etc/dhcpd.name-servers.tmp /etc/dhcpd.name-servers if [ $? -gt 0 ]; then # move the new file into place mv /etc/dhcpd.name-servers.tmp /etc/dhcpd.name-servers # restart dhcp using whatever is appropriate for your platform #service dhcpd restart #/usr/local/etc/rc.d/isc-dhcpd.sh restart -q # Write message to /var/log/dhcpc.log to document event. logger -p user.warning -t dhclient Your ISP DNS IP addresses changed. # Write message to /var/log/dhcpd.log to document event. logger -p local1.warning -t dhclient Your ISP DNS IP addresses changed. # Send notification email to root user. This can wrap to next line. # cat << EOF | mail -s "dhcp client changed ISP DNS IP addresses" root #The dhclient-exit-hook script was invoked and has determined that your #ISP changed the IP address of their DNS servers. The new values have been #auto updated to dhcpd.conf and dhcp restarted so they are now in effect. # #Note: All LAN machines using dhcpd will not start using the new ISP dns #ip addresses until they reboot or their lease comes up for renewal. #EOF fi rm -f /etc/dhcpd.name-servers.tmp ### End of refresh dhcpd dns ip script ### ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
man dhclient [was Re: resolv.conf getting rewritten at system startup]
Erik Trulsson wrote: On Thu, Mar 16, 2006 at 05:29:45PM -0400, Duane Whitty wrote: Hi all, I am running FBSD 6.0-RELEASE I use DHCP to configure my network interface Thanks in advance, Duane P.S. Is there a man page for the dhcp client FBSD 6 is using (what is FBSD 6 using)? 'man dhclient' should work fine. FBSD 6 uses the OpenBSD dhclient (which I believe derive from an older version of the ISC one.) Hi, Yes, man dhclient in FBSD 6 does work fine. I misinterpreted how to apply its instructions. Duane -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
I had the same problem. Mine was with a wireless card, so my exact fix is probably not yours but this may point the way. I had to load a driver not autoloaded in 6.0 (wlan_wep.ko) and add an extra parm to the ifconfig: old: ifconfig wi0 wep wepkey new: ifconfig wi0 wep wepkey deftxkey 1 From reading of the ifconfig man page I thought that was the default. Many thanks to Robert Watson for the right answer. I did not have a dhclient.conf in 5.3 or 6.0. In general - it may not be dhclient, you may need an addition module or some additional setting on the ifconfig for your card. In my case I think I got an error about the missing module. I hope this helps. DougD On Thu, 2 Feb 2006, make stuff up wrote: hi all.. this is new - just installed 6 and here: # dhclient fxp0 DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 8 .. and a few other intervals... so if the fxp0 is up and the dhcp server is up then whats wrong with dhclient?... i'm actually writing from a machine on the same dhcp server... thanks... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient and bootpd on same system OK?
Rob <[EMAIL PROTECTED]> writes: > I have a home network with a router connected to the > external internet, and four PCs on the home network. > The router provides IPs with its DHCP server. > (The router is a small commercial box skrewed to > the wall). > > One of the PCs on the home network is a FreeBSD > (6-Stable). This FreeBSD PC runs dhclient to get its > IP configuration. So far so good. > > All other PCs on the network are Windows PCs, > but have a BIOS that allow Network boots. > Therefore I would like to set up the possibility to > boot these PCs as diskless boxes from the > FreeBSD PC, using the bootpd server. > > Hence, I'd like to make this FreeBSD PC a > bootpd server. But it is already running dhclient. > Would such a setup cause conflicts? It should be fine. Client and server use different UDP ports. But you'd have to try it to be sure. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhclient and bootpd on same system OK?
Hi, I have a home network with a router connected to the external internet, and four PCs on the home network. The router provides IPs with its DHCP server. (The router is a small commercial box skrewed to the wall). One of the PCs on the home network is a FreeBSD (6-Stable). This FreeBSD PC runs dhclient to get its IP configuration. So far so good. All other PCs on the network are Windows PCs, but have a BIOS that allow Network boots. Therefore I would like to set up the possibility to boot these PCs as diskless boxes from the FreeBSD PC, using the bootpd server. Hence, I'd like to make this FreeBSD PC a bootpd server. But it is already running dhclient. Would such a setup cause conflicts? Thanks, Rob. - Yahoo! Mail Use Photomail to share photos without annoying attachments. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
Robert Huff wrote: Erik Norgaard writes: - Do you use a dhclient.conf from your previous install? These are incompatible. The new dhclient is a port from OpenBSD who completely rewrote dhclient. The old is from ISC. I do not believe this to be correct - the part about incompatible config files, that is. I am using my (ISC) dhclient.conf unmodified under (OpenBSD) dhclient with (as far as I know) no adverse results. And I think I specificly remember the announcement of the change explicitly saying most config files would need no changes. Ok, let me be more precise, there are options in the old ISC files that are not supported in the new and the new also introduces new options. Of course, whenever possible it is advantageous to reuse keywords and meanings. I do not know if dhclient defaults to ignore the unknown or it chokes and dies. Anyway, the problem may be solved by toggling with the dhclient.conf and OP does not mention any such thing nor it old files have been left from a previous install. Sniffing on the interface (snort -vC -i fxp0) would give some good clues as to where the problem is, maybe no responses get back because the request is blocked? or no requests are sent at all? I don't know if OP have reverted to 5.4 yet. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
Erik Norgaard writes: > - Do you use a dhclient.conf from your previous install? These > are incompatible. The new dhclient is a port from OpenBSD who > completely rewrote dhclient. The old is from ISC. I do not believe this to be correct - the part about incompatible config files, that is. I am using my (ISC) dhclient.conf unmodified under (OpenBSD) dhclient with (as far as I know) no adverse results. And I think I specificly remember the announcement of the change explicitly saying most config files would need no changes. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
make stuff up wrote: hi all.. this is new - just installed 6 and here: # dhclient fxp0 DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 8 .. and a few other intervals... so if the fxp0 is up and the dhcp server is up then whats wrong with dhclient?... i'm actually writing from a machine on the same dhcp server... Hi there, I just read through this thread. I run dhclient on 6.0 with no problem at all. Normally, it will start sending a DHCPREQUEST then DHCPDISCOVER. Some questions: - Do you use a dhclient.conf from your previous install? These are incompatible. The new dhclient is a port from OpenBSD who completely rewrote dhclient. The old is from ISC. - Have you tried to toggle timeout/retry in dhclient.conf? - Can you sniff traffic on the NIC? - Do you have any firewalling set? or did you forget to disable ipfw? I think that ipfw defaults to block everything, I'm not sure if that is new in 6.0. Yes, I know the last two are somewhat basic stuff, but sometimes one just forget to check it. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
> kalin mintchev wrote: >>>>try install /usr/ports/net/isc-dhcp3-client >>>>and edit your rc.conf: >>>>dhclient_program="/usr/local/sbin/dhclient" >>>>dhclient_flags= see manual for isc-dhcp3-client >>> >>> ok.. this sounds reasonable... >>> but how do i tell the dhcp server what number am i assigning to fxp0? >>> now ifconfig shows exactly the same as on the other laptop except the >>> IP >>>of course. >>> >>> route get 192.168.1.1 shows also the same output except expire is a >>>negative number. how do i make the dhcp sever aware of the IP i assigned >>>to fxp0? >> >> >> anybody?! >> i lost too much time on this... i mean it's dhclient its not even >> trying to make RAID work... sorry to say i'm going back to 5.4... >> unless somebody has a quick workaround... >> >> thanks to the people that tried to help.. >> >> >>> thanks >>> >>> >>> >>> >>>>2006/2/3, Frank Altpeter <[EMAIL PROTECTED]>: >>>> >>>>>Hi there, >>>>> >>>>>kalin mintchev wrote on 2006-02-03 at 13:55:01 CET: >>>>> >>>>>>>2006/2/3, make stuff up <[EMAIL PROTECTED]>: >>>>>>> >>>>>>> >>>>>>>> thank you... does that mean back to 5.4 for now? >>>>>>> >>>>>>>Try install /usr/ports/net/isc-dhcp3-client/ >>>>>> >>>>>> without a connection? >>>>> >>>>>try to manually ifconfig your fxp0 - this should work. >>>>> >>>>> >>>>>Le deagh dhùraghd, >>>>> >>>>> Frank Altpeter >>>>> >>>>>-- >>>>>*** FA-RIPE *** http://blog.foxalpha.de/ *** SIG at 11 *** >>>>>| I'm always ravenous when I'm about to take a long journey. >>>>>| Rygel - DNA Mad Scientist >>>>>___ > > Hi, > > In 5.4 I had these a dhclient.conf that > had these options: > > option router-discovery 1 > option perform-mask-discovery 1 > > It was the only way my notebook would > get a dhcp address. It seems I don't > need these settings anylonger in 6.0 but > maybe making them explicit will help > your cause. thanks Duane... but there is something really screwed up with the dhclient out of the box. i just tried reinstalling just vary basic system and even at the configuration prompt to set up the fxp0 when i select dhcp nothing happens... so i'm going back to 5.4. if i have to spend 2 more days on something as basic as dhclient. i mean i have to eat too... thanks... > Hope this helps. > > --Duane Whitty > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
kalin mintchev wrote: try install /usr/ports/net/isc-dhcp3-client and edit your rc.conf: dhclient_program="/usr/local/sbin/dhclient" dhclient_flags= see manual for isc-dhcp3-client ok.. this sounds reasonable... but how do i tell the dhcp server what number am i assigning to fxp0? now ifconfig shows exactly the same as on the other laptop except the IP of course. route get 192.168.1.1 shows also the same output except expire is a negative number. how do i make the dhcp sever aware of the IP i assigned to fxp0? anybody?! i lost too much time on this... i mean it's dhclient its not even trying to make RAID work... sorry to say i'm going back to 5.4... unless somebody has a quick workaround... thanks to the people that tried to help.. thanks 2006/2/3, Frank Altpeter <[EMAIL PROTECTED]>: Hi there, kalin mintchev wrote on 2006-02-03 at 13:55:01 CET: 2006/2/3, make stuff up <[EMAIL PROTECTED]>: thank you... does that mean back to 5.4 for now? Try install /usr/ports/net/isc-dhcp3-client/ without a connection? try to manually ifconfig your fxp0 - this should work. Le deagh dhùraghd, Frank Altpeter -- *** FA-RIPE *** http://blog.foxalpha.de/ *** SIG at 11 *** | I'm always ravenous when I'm about to take a long journey. | Rygel - DNA Mad Scientist ___ Hi, In 5.4 I had these a dhclient.conf that had these options: option router-discovery 1 option perform-mask-discovery 1 It was the only way my notebook would get a dhcp address. It seems I don't need these settings anylonger in 6.0 but maybe making them explicit will help your cause. Hope this helps. --Duane Whitty ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
>> try install /usr/ports/net/isc-dhcp3-client >> and edit your rc.conf: >> dhclient_program="/usr/local/sbin/dhclient" >> dhclient_flags= see manual for isc-dhcp3-client > > ok.. this sounds reasonable... > but how do i tell the dhcp server what number am i assigning to fxp0? > now ifconfig shows exactly the same as on the other laptop except the IP > of course. > > route get 192.168.1.1 shows also the same output except expire is a > negative number. how do i make the dhcp sever aware of the IP i assigned > to fxp0? anybody?! i lost too much time on this... i mean it's dhclient its not even trying to make RAID work... sorry to say i'm going back to 5.4... unless somebody has a quick workaround... thanks to the people that tried to help.. > thanks > > > >> >> 2006/2/3, Frank Altpeter <[EMAIL PROTECTED]>: >>> >>> Hi there, >>> >>> kalin mintchev wrote on 2006-02-03 at 13:55:01 CET: >>> > > 2006/2/3, make stuff up <[EMAIL PROTECTED]>: >>> > > >>> > >> thank you... does that mean back to 5.4 for now? >>> > > >>> > > Try install /usr/ports/net/isc-dhcp3-client/ >>> > >>> > without a connection? >>> >>> try to manually ifconfig your fxp0 - this should work. >>> >>> >>> Le deagh dhùraghd, >>> >>>Frank Altpeter >>> >>> -- >>> *** FA-RIPE *** http://blog.foxalpha.de/ *** SIG at 11 *** >>> | I'm always ravenous when I'm about to take a long journey. >>> | Rygel - DNA Mad Scientist >>> ___ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to >>> "[EMAIL PROTECTED]" >>> >> > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
> try install /usr/ports/net/isc-dhcp3-client > and edit your rc.conf: > dhclient_program="/usr/local/sbin/dhclient" > dhclient_flags= see manual for isc-dhcp3-client ok.. this sounds reasonable... but how do i tell the dhcp server what number am i assigning to fxp0? now ifconfig shows exactly the same as on the other laptop except the IP of course. route get 192.168.1.1 shows also the same output except expire is a negative number. how do i make the dhcp sever aware of the IP i assigned to fxp0? thanks > > 2006/2/3, Frank Altpeter <[EMAIL PROTECTED]>: >> >> Hi there, >> >> kalin mintchev wrote on 2006-02-03 at 13:55:01 CET: >> > > 2006/2/3, make stuff up <[EMAIL PROTECTED]>: >> > > >> > >> thank you... does that mean back to 5.4 for now? >> > > >> > > Try install /usr/ports/net/isc-dhcp3-client/ >> > >> > without a connection? >> >> try to manually ifconfig your fxp0 - this should work. >> >> >> Le deagh dhùraghd, >> >>Frank Altpeter >> >> -- >> *** FA-RIPE *** http://blog.foxalpha.de/ *** SIG at 11 *** >> | I'm always ravenous when I'm about to take a long journey. >> | Rygel - DNA Mad Scientist >> ___ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "[EMAIL PROTECTED]" >> > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
On Fri, 3 Feb 2006 14:02:41 +0100 Frank Altpeter <[EMAIL PROTECTED]> wrote: > Hi there, > > kalin mintchev wrote on 2006-02-03 at 13:55:01 CET: > > > 2006/2/3, make stuff up <[EMAIL PROTECTED]>: > > > > > >> thank you... does that mean back to 5.4 for now? > > > > > > Try install /usr/ports/net/isc-dhcp3-client/ > > > > without a connection? > > try to manually ifconfig your fxp0 - this should work. Son't be silly. What if you dont know what IP you will get from the lease? That's what working implementation of DHCP is for... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient in 6.0
try install /usr/ports/net/isc-dhcp3-client and edit your rc.conf: dhclient_program="/usr/local/sbin/dhclient" dhclient_flags= see manual for isc-dhcp3-client 2006/2/3, Frank Altpeter <[EMAIL PROTECTED]>: > > Hi there, > > kalin mintchev wrote on 2006-02-03 at 13:55:01 CET: > > > 2006/2/3, make stuff up <[EMAIL PROTECTED]>: > > > > > >> thank you... does that mean back to 5.4 for now? > > > > > > Try install /usr/ports/net/isc-dhcp3-client/ > > > > without a connection? > > try to manually ifconfig your fxp0 - this should work. > > > Le deagh dhùraghd, > >Frank Altpeter > > -- > *** FA-RIPE *** http://blog.foxalpha.de/ *** SIG at 11 *** > | I'm always ravenous when I'm about to take a long journey. > | Rygel - DNA Mad Scientist > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
