Re: dhcp server returns core dump when i define network with mask 8
On 23/07/2013 09:03, jb wrote:
s m sam.gh1986 at gmail.com writes:
...
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
The 'range' denotes IP addresses that can be allocated to clients.
The IP 192.255.255.255 is a reserved broadcast address for the network.
jb
It's definitely bad idea to try to use it, but it doesn't explain the
core dump.
Also, using DHCP to dish out addresses that don't belong to you AND
aren't on a private network (as defined by IANA) will probably lead to
trouble. Valid private address ranges are:
10.0.0.0 - 10.255.255.255 (private class A)
172.16.0.0 - 172.31.255.255 (private class B x 16)
192.168.0.0 - 192.168.255.255 (private class C x 256)
Which block you use is really a matter of taste - classes haven't been
used in routing for quite a while so you can consider them all as
straight blocks but I (for one) still treat them as classed just to help
me visualise what's what. For example, I'll use one class C per site to
prevent conflicts over VPN.
192.0.0.0/24 addresses are allocated to real hosts on the wider
internet, although IIRC some of the lower ones are reserved for use in
documentation (like example.com) - is that where the idea came from?!? :-)
Regards, Frank.
___
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: dhcp server returns core dump when i define network with mask 8
thanks Frank,
192 is just a sample. if i want to define 125.0.0.0 netmask 255.0.0.0, dhcp
server core dump either. you're right, it is better to use just some
limited addresses to avoid possible troubles. but i want to run my dhcp
server for all possible networks.
now my question is: if i define a network with mask 8, the rang should be
like: 126.0.0.0 126.254.255.255?
and thank you jb but if i define my network like below, server runs
correctly:
log-facility local7;
subnet 192.168.0.0 netmask 255.255.0.0 {
range 192.168.0.1 192.168.255.255;
}
i think 192.168.255.55 is reserved for broadcast too. is it not true? if
yes, why dhcp server works correctly?
please help me to clear my mind.
regards,
SAM
On Tue, Jul 23, 2013 at 12:56 PM, Frank Leonhardt fra...@fjl.co.uk wrote:
On 23/07/2013 09:03, jb wrote:
s m sam.gh1986 at gmail.com writes:
...
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
The 'range' denotes IP addresses that can be allocated to clients.
The IP 192.255.255.255 is a reserved broadcast address for the network.
jb
It's definitely bad idea to try to use it, but it doesn't explain the
core dump.
Also, using DHCP to dish out addresses that don't belong to you AND aren't
on a private network (as defined by IANA) will probably lead to trouble.
Valid private address ranges are:
10.0.0.0 - 10.255.255.255 (private class A)
172.16.0.0 - 172.31.255.255 (private class B x 16)
192.168.0.0 - 192.168.255.255 (private class C x 256)
Which block you use is really a matter of taste - classes haven't been
used in routing for quite a while so you can consider them all as straight
blocks but I (for one) still treat them as classed just to help me
visualise what's what. For example, I'll use one class C per site to
prevent conflicts over VPN.
192.0.0.0/24 addresses are allocated to real hosts on the wider internet,
although IIRC some of the lower ones are reserved for use in documentation
(like example.com) - is that where the idea came from?!? :-)
Regards, Frank.
__**_
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-**
unsubscr...@freebsd.org 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: dhcp server returns core dump when i define network with mask 8
Quoting Frank Leonhardt fra...@fjl.co.uk: There are two common ways of defining a subnet mask - one is a dotted quad (e.g. 255.255.255.0) and the other is with a slash and the number of low-order bits - e.g. 192.168.1.0/8. Eight bits here means you get 2^8 addresses (i.e. 256). Don't use the first and last address in the range - the first is complicated (the network address) and the last is for broadcast packets. This doesn't always hold true but you're unlikely to come across exceptions. This is the wrong way round. the number after the slash indicates the number of bits in the network address - the high-order bits. So, when you say you want to define a network with mask 8 I don't really know what you mean from your example. Do you mean a /8? 192.168.1.0/8 = range 192.168.1.1192.168.1.254 with a subnet mask of 255.255.255.0 (0xFF00) Nope. 192.168.1.0/24 = 192.168.1.1-255 mask 255.255.255.0. 192.168.1.0/8 doesn't start where you think it does (and is arguably the wrong way to specify that network) because all but the first 8 bits are masked out - it's 192.0.0.0 - 192.255.255.255. ___ 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: dhcp server returns core dump when i define network with mask 8
s m sam.gh1986 at gmail.com writes:
and thank you jb but if i define my network like below, server runs
correctly:
log-facility local7;
subnet 192.168.0.0 netmask 255.255.0.0 {
range 192.168.0.1 192.168.255.255;
}
i think 192.168.255.55 is reserved for broadcast too. is it not true? if
yes, why dhcp server works correctly?
please help me to clear my mind.
regards,
SAM
Regarding subnets:
192.168.0.0 netmask 255.255.0.0
is equivalent to
192.168.0.0/16
which splits it into a network id 192.168. and host id .0.0
Another example:
192.168.0.0 netmask 255.0.0.0
is equivalent to
192.168.0.0/8
which splits it into a network id 192. and host id 168.0.0
Regarding broadcast address:
yes, for subnet 192.168.0.0/16 the broadcast ip is 192.168.255.255 .
What are the implications of including broadcast ip in range option ?
Firstly, it depends on how the authors of software, that is DHCP server,
interpreted the dhcpd.conf option data. They could have rejected that
option up front, or accept it (implying you are the boos !).
After all, dhcpd.conf(5) only says:
The range statement
range [ dynamic-bootp ] low-address [ high-address];
For any subnet on which addresses will be assigned dynamically, there
must be at least one range statement. The range statement gives
the lowest and highest IP addresses in a range. All IP addresses in
the range should be in the subnet in which the range statement is declared.
Well, looks good to me so far !
Next, dhcpd.conf(5) describes how DHCP server deals with:
DYNAMIC ADDRESS ALLOCATION
...
IP ADDRESS CONFLICT PREVENTION
...
You can analyse it and see if any trouble lurks there ...
Secondly, let's assume there was no problem and that ip was dispensed to a host.
But, in a different place of IP specs there is a RFC??? which says that
the 192.168.255.255 as a generically valid ip address will assume some
additional meaning, that is it will be treated as a broadcast address
(it will represent all hosts on a subnet).
Wow ! That should give you a pause ...
It is said that the broadcast address is used by an application to send
the same message to all other hosts in the network simultaneously.
Who is using it ?
Well, our client host is using it (let's assume it was assigned that ip
above ...).
What happens when the host sends a packet out with a source ip address of
a broadcast ip address ? One can imagine that the destination host will
respond and send back a packet to a destination ip address which is our
sender's broadcast ip address ... You mean to every host on that network ?
Something fishy is on the way ...
But while doing it, it will utilize some protocols, like ARP, RIP, etc.
In addition, it is said that broadcast messages are typically produced by
network protocols such as the Address Resolution Protocol (ARP) and
the Routing Information Protocol (RIP).
They will utilize that ip broadcast address regardless of the fact that it
has been presumably assigned to the client host too.
Wow, what a soup ...
Enjoy it while it lasts :-)
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: dhcp server returns core dump when i define network with mask 8
On 23/07/2013 13:35, j.mcke...@ru.ac.za wrote: Quoting Frank Leonhardt fra...@fjl.co.uk: There are two common ways of defining a subnet mask - one is a dotted quad (e.g. 255.255.255.0) and the other is with a slash and the number of low-order bits - e.g. 192.168.1.0/8. Eight bits here means you get 2^8 addresses (i.e. 256). Don't use the first and last address in the range - the first is complicated (the network address) and the last is for broadcast packets. This doesn't always hold true but you're unlikely to come across exceptions. This is the wrong way round. the number after the slash indicates the number of bits in the network address - the high-order bits. So, when you say you want to define a network with mask 8 I don't really know what you mean from your example. Do you mean a /8? 192.168.1.0/8 = range 192.168.1.1192.168.1.254 with a subnet mask of 255.255.255.0 (0xFF00) Nope. 192.168.1.0/24 = 192.168.1.1-255 mask 255.255.255.0. 192.168.1.0/8 doesn't start where you think it does (and is arguably the wrong way to specify that network) because all but the first 8 bits are masked out - it's 192.0.0.0 - 192.255.255.255. Quite correct - for some reason I got that bit backwards when I'm using it every day the right way around. It's ludicrously hot and humid in London at the moment, lack of sleep caused thereby c... ___ 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: dhcp server returns core dump when i define network with mask 8
s m sam.gh1986 at gmail.com writes:
...
subnet 192.0.0.0 netmask 255.0.0.0 {
range 192.0.0.1 192.255.255.255;
The 'range' denotes IP addresses that can be allocated to clients.
The IP 192.255.255.255 is a reserved broadcast address for the network.
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: DHCP Question
On Jun 14, 2011, at 11:19 AM, jh...@socket.net wrote: I am working with a vendor and they are wanting me to send them ip addresses via option 74 in DHCP (irc-server). After I defined this in my dhcpd.conf file, the option is still not being sent. However, I am not receiving a request for this option. I'm not sure why someone would care about setting an IRC server via DHCPd, but I won't second-guess the requirement. I have done a bunch of Googling this morning/afternoon, and have not been able to find a way to send the option whether it is requested or not. You want: option dhcp-parameter-request-list uint16; This option, when sent by the client, specifies which options the client wishes the server to return.Normally, in the ISC DHCP client, this is done using the request statement. If this option is not specified by the client, the DHCP server will normally return every option that is valid in scope and that fits into the reply. When this option is specified on the server, the server returns the specified options.This can be used to force a client to take options that it hasn't requested, and it can also be used to tailor the response of the DHCP server for clients that may need a more lim- ited set of options than those the server would normally return. Regards, -- -Chuck ___ 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: Re: DHCP Question
From : Chuck Swiger cswi...@mac.com To : jh...@socket.net Subject : Re: DHCP Question Date : Tue, 14 Jun 2011 11:28:00 -0700 You want: option dhcp-parameter-request-list uint16; This option, when sent by the client, specifies which options the client wishes the server to return.Normally, in the ISC DHCP client, this is done using the request statement. If this option is not specified by the client, the DHCP server will normally return every option that is valid in scope and that fits into the reply. When this option is specified on the server, the server returns the specified options.This can be used to force a client to take options that it hasn't requested, and it can also be used to tailor the response of the DHCP server for clients that may need a more lim- ited set of options than those the server would normally return. Regards, -- -Chuck They are not using the option for the IRC Server, but to point to the nodes where the Virutal Desktops are. Thank you for all your help. That did the trick! Jay Thank you! That did the trick. ___ 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: DHCP problem after upgrade [solved]
At 2010-09-23T11:17:48+05:30, N. Raghavendra wrote: I upgraded my system from 7.2-STABLE to 8.1-STABLE, and have done `mergemaster'. Earlier the system used to get its IP address by DHCP at boot time without any problem. After the upgrade, it is not doing so. I have ifconfig_em0=DHCP in /etc/rc.conf. After searching the Web and rc.conf(5), I came across the SYNCDHCP value for the ifconfig_interface variable. So, either setting ifconfig_em0=SYNCDHCP, or leaving ifconfig_em0=DHCP as it is and setting synchronous_dhclient=YES in rc.conf works, and the system gets an IP address from the DHCP server at boot time. Regards, Raghavendra. -- N. Raghavendra ra...@mri.ernet.in | http://www.retrotexts.net/ Harish-Chandra Research Institute | http://www.mri.ernet.in/ See message headers for contact and OpenPGP information. ___ 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: DHCP client questions
On Sun, Sep 20, 2009 at 3:19 PM, stan st...@panix.com wrote: We have been bought out, and the new powers that be, are changing things. They have decreed that there shall be no static entries in their DNS servers. They are using $MS DHCP/DNS servers. I have a corporate supported Win XP laptop, which I can plug in at various places in the network. It gets different IP addresses, based upon where it physically is, but always comes up with the same name. The question is whether by the same name you are referring to a dns lookup, a wins lookup, or a nbns broadcast query, or all of the above ;) I have several machines (such as a mailserver) which _MUST_ have fixed names. I have played around with /etc/dhcllient.conf, but not managed to get this working. I can get IP addresses, and various things such as default routers, and DNS servers, but I have not managed to get the suggested name put in their DNS. try running: tcpdump -r filename.pcap -vvv port bootpc in order to get a nice decode of your dhcp session. This will contain by the client discover/request/ack, and the server offer packets. I have captured packet traces with wireshark from the laptop, and from the FreebSD client, and I am putting these up at http://beachcave.net/pdumps. I would really appreciate it if someone more familiar with DHCP that I could take a look at theses. Your windows capture clearly shows a dhcp option 12 with the short name, and dhcp option 81 with FQDN Hostname Option 12, length 10: CHSLSBROWN FQDN Option 81, length 31: CHSLSBROWN.kapstonepaper.com Vendor-Class Option 60, length 8: MSFT 5.0 Parameter-Request Option 55, length 11: Subnet-Mask, Domain-Name, Default-Gateway, Domain-Name-Server Netbios-Name-Server, Netbios-Node, Netbios-Scope, Router-Discovery Static-Route, Classless-Static-Route-Microsoft, Vendor-Option END Option 255, length 0 Your freebsd captures show dhcp option 12 with the FQDN. You need to try using option 12 and option 81 just like in windows land. You may even need to put in the Vendor-Class and/or others to duplicate the windows request, but try one item at a time. Try adding these to your dhclient.conf as needed. Take the time to look at the man page for dhclient.conf, and dhcp-options, and also take a look at the full defined option numbers here: http://www.iana.org/assignments/bootp-dhcp-parameters/ Good Luck. --Dave H ___ 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: DHCP client questions
On Sunday 20 September 2009 21:19:28 stan wrote: I have several machines (such as a mailserver) which _MUST_ have fixed names. I have played around with /etc/dhcllient.conf, but not managed to get this working. I can get IP addresses, and various things such as default routers, and DNS servers, but I have not managed to get the suggested name put in their DNS. Ok, I know you're trying to make clear what your problem is, but it's still not. So, let's try step by step,, using a FreeBSD mailserver as the example: 1) Does the mailserver have a fixed HOSTNAME or can the HOSTNAME change if the DHCP server wants it to? 2) When you say but I have not managed to get the suggested name put in their DNS, does this mean you expect the FreeBSD mailserver to enter itself into the Microsoft DNS? Or can you not get the FreeBSD mailserver to name itself according to what the DHCP server tells them to? -- Mel ___ 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: DHCP client questions
Mel Flynn wrote: On Sunday 20 September 2009 21:19:28 stan wrote: I have several machines (such as a mailserver) which _MUST_ have fixed names. I have played around with /etc/dhcllient.conf, but not managed to get this working. I can get IP addresses, and various things such as default routers, and DNS servers, but I have not managed to get the suggested name put in their DNS. Ok, I know you're trying to make clear what your problem is, but it's still not. So, let's try step by step,, using a FreeBSD mailserver as the example: 1) Does the mailserver have a fixed HOSTNAME or can the HOSTNAME change if the DHCP server wants it to? 2) When you say but I have not managed to get the suggested name put in their DNS, does this mean you expect the FreeBSD mailserver to enter itself into the Microsoft DNS? Or can you not get the FreeBSD mailserver to name itself according to what the DHCP server tells them to? Don't seem to have all the details either, but from what little I can piece together is his company being bought by another necessitates the melding of his old systems with the new companies' Windows based environment. This could very well be an incorrect assumption on my part. In a Windows environment when DHCP is used, as it hands out IP addresses it then updates the IP/hostname pair in the DNS server database. This is configured to operate by the admins. Usually there are at least two DHCP scopes minimum for the dynamically assigned IPs, but there can also be configured a scope for static IPs for things such as mail servers. So it is still possible for a mail server to initialize networking via DHCP and be assigned the same statically assigned IP every time. It is the responsibility of the Windows DHCP servers to sync with the DNS server database. If you are not going to have static services such as a mail server initialize via DHCP then a system admin will have to manually enter this information into the DNS server database. Without possessing the administrative authority to do this things will get very frustrating. Bottom line is, if what I think is going on is correct, he can fight this battle in myriad different directions but inevitably all will lead back to the system admins of the purchasing company must get involved in order to properly meld the 2 networks together. All 10,000 different paths which can be pursued will ultimately lead back to this, so they ought to just bite the bullet and get it over with. (If one wants to run his own Unix based DNS servers so as to have this under his/her control set up for file based zone transfer from the Windows DNS servers. The key to making this work is to manually config the zone transfers on the Windows DNS machines to ascii instead of UTF8 or else the Unix box DNS zone files will be endlessly polluted with garbage characters. Of course this all is moot if you are not allowed to be delegated or be authoritative for your little piece of the DNS tree. Here again, this is still going to have to be handled by the purchasing companies' admins as they are the ones in the drivers seat. This type of melding of heterogeneous systems absolutely requires both sides to work together.) -Mike ___ 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: DHCP using ral
Robert Hall wrote: ifconfig ral0 inet 192.168.1.104 netmask 255.255.255.0 assigns the specified values. Ping no longer tells me that there's no route to the host, but I'm getting about 95% packet loss. netstat -r now shows that link1 (ral0) is the gateway to 192.168.1.0. I still don't have a usable connection. Not especially helpful but I thought I'd throw this out there, Linksys routers by default define their DHCP range as 192.168.1.100 - 192.168.1.149, so pick an address outside that space if you're trying to assign statically. You can often get away with setting the IP of the router (default of 192.168.1.1 for Linksys) as your DNS, as many Linksys routers have a built in DNS proxy. Are you sure you're getting a strong enough signal from the AP? Have you had success with this WiFi card accessing other APs? Do you have access to a different WiFi card you could try? ___ 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: DHCP using ral
On Mon, Jun 29, 2009 at 1:35 PM, Brent Bloxambre...@beanfield.com wrote: Robert Hall wrote: ifconfig ral0 inet 192.168.1.104 netmask 255.255.255.0 assigns the specified values. Ping no longer tells me that there's no route to the host, but I'm getting about 95% packet loss. netstat -r now shows that link1 (ral0) is the gateway to 192.168.1.0. I still don't have a usable connection. Not especially helpful but I thought I'd throw this out there, Linksys routers by default define their DHCP range as 192.168.1.100 - 192.168.1.149, so pick an address outside that space if you're trying to assign statically. Good point. I tried that, but 192.168.1.104 and 192.168.1.150 work the same. No difference that I can tell You can often get away with setting the IP of the router (default of 192.168.1.1 for Linksys) as your DNS, as many Linksys routers have a built in DNS proxy. Ah. That doesn't solve the problem, but it works and it's useful. Are you sure you're getting a strong enough signal from the AP? I think I am. The XP box is reporting a strong signal, and it's on the self below the FBSD box. Of course, the XP box is also reporting no Internet connection, and I'm using it to reply to you, so who knows. The XP box with a Belkin NIC works pretty well. The boxes are very close, so I'm guessing that signal strength is not an issue. Have you had success with this WiFi card accessing other APs? I have no other APs I can try it with. The only other AP within range is none of my business. Do you have access to a different WiFi card you could try? No. This Linksys card was the only PCI card at the local MicroCenter that was supported by FBSD 7.2. :) Thanks for your interest in my problem. :) ___ 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: DHCP using ral
Robert Hall wrote: I'm trying to set up a connection between an FBSD box and a wireless access point. The background is that there's no security on this network; as the person who set it up says, You just start your computer and it works! I have an XP box with a wireless NIC working, but I don't want to use the XP box as the gateway for my personal lan to an insecure network. On the XP box, if I point a browser to 192.168.1.1, I'm told that the router is WRT54GX2, which I take to be a popular Linksys router. I don't have physical access to the router and I don't have the password for the router. I've got a wireless Linksys NIC that uses the ral driver facing the wireless router. The NIC facing my lan uses the em driver and is working fine. uname -a says FreeBSD 7.2-RELEASE #0. In rc.conf I have ifconfig_ral0=DHCP After booting, if I ping 192.168.1.1, I get no route to host and I have no lease file in /var/db. ifconfig ral0 tells me that I have no inet address associated with ral0, status is no carrier, and the ssid is an empty string. dhclient ral0 sends a series of DHCPDISCOVER messages, but I get no DHCPOFFER messages, and I get an empty lease file. If I run ifconfig ral0 again, inet is 0.0.0.0, status is associated, and ssid is the proper ssid for the wireless router. ifconfig ral0 list scan gives the proper information for the router. At some point I did get a proper lease. I don't know when or how. I've never had a usable connection to the router from the FBSD box, and I've never had access to the nameservers listed in the lease. If I rename the old lease file to dhcp.leases.ral0, and then run dhclient ral0, I send 3 DHCPREQUEST messages, 2 DHCPDISCOVER messages, 2 DHCPREQUEST messages, and 6 DHCPDISCOVER messages. dhclient tells me that no DHCPOFFERs were received, and it binds to the address in lease file, 192.168.1.104. However, ifconfig ral0 shows no inet address. I still can't ping the router. ifconfig ral0 inet 192.168.1.104 netmask 255.255.255.0 assigns the specified values. Ping no longer tells me that there's no route to the host, but I'm getting about 95% packet loss. netstat -r now shows that link1 (ral0) is the gateway to 192.168.1.0. I still don't have a usable connection. resolv.conf says nameserver 192.168.0.1, which is the nameserver for my personal lan. I can't nslookup URLs outside of my lan. If I manually add the nameservers in the dhcp lease, I can nslookup www.google.com. But ping has 100% packet loss. /etc/hosts associates 127.0.0.1 with localhost.krig.net, and 192.168.0.6 with stamfordbru.krig.net, which is correct for my lan. I'm stumped. :) I don't know if this is related; the XP box is telling me that the router has no connection to the internet, but it obviously does have a connection because the XP box can load web pages and I can use my gmail account. Thanks for any help. I happen to have a Linksys router (not the same model though) and a Linksys pci card that uses the ral driver. Never had any problems, though I am not using DHCP. Here are a few manual steps to try: First off, try setting the ssid on the command line: ifconfig ral ssid Myssid Execute ifconfig by itself, and see if you get an associated message. (you may have to wait a minute before you do) If you don't, chances are the following will do nothing dhclient ral0 if this does not succeed, set an IP address manually: ifconfig ral0 inet 192.168.1.50 netmask 255.255.255.0 Before attempting to test the internet connection, add the router as nameserver in /etc/resolv.conf and don't forget to add the router's address as the default gateway: route add default 192.168.1.X From my experience, the important part is to get the associated message after the initial ifconfig. Not much hope otherwise. As an afterthought, is the XP machine on while you are trying to connect? If they are too close they maybe interfering. ___ 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: DHCP using ral
Manolis Kiagias napsal(a): Robert Hall wrote: I'm trying to set up a connection between an FBSD box and a wireless access point. The background is that there's no security on this network; as the person who set it up says, You just start your computer and it works! I have an XP box with a wireless NIC working, but I don't want to use the XP box as the gateway for my personal lan to an insecure network. On the XP box, if I point a browser to 192.168.1.1, I'm told that the router is WRT54GX2, which I take to be a popular Linksys router. I don't have physical access to the router and I don't have the password for the router. I've got a wireless Linksys NIC that uses the ral driver facing the wireless router. The NIC facing my lan uses the em driver and is working fine. uname -a says FreeBSD 7.2-RELEASE #0. In rc.conf I have ifconfig_ral0=DHCP After booting, if I ping 192.168.1.1, I get no route to host and I have no lease file in /var/db. ifconfig ral0 tells me that I have no inet address associated with ral0, status is no carrier, and the ssid is an empty string. dhclient ral0 sends a series of DHCPDISCOVER messages, but I get no DHCPOFFER messages, and I get an empty lease file. If I run ifconfig ral0 again, inet is 0.0.0.0, status is associated, and ssid is the proper ssid for the wireless router. ifconfig ral0 list scan gives the proper information for the router. At some point I did get a proper lease. I don't know when or how. I've never had a usable connection to the router from the FBSD box, and I've never had access to the nameservers listed in the lease. If I rename the old lease file to dhcp.leases.ral0, and then run dhclient ral0, I send 3 DHCPREQUEST messages, 2 DHCPDISCOVER messages, 2 DHCPREQUEST messages, and 6 DHCPDISCOVER messages. dhclient tells me that no DHCPOFFERs were received, and it binds to the address in lease file, 192.168.1.104. However, ifconfig ral0 shows no inet address. I still can't ping the router. ifconfig ral0 inet 192.168.1.104 netmask 255.255.255.0 assigns the specified values. Ping no longer tells me that there's no route to the host, but I'm getting about 95% packet loss. netstat -r now shows that link1 (ral0) is the gateway to 192.168.1.0. I still don't have a usable connection. resolv.conf says nameserver 192.168.0.1, which is the nameserver for my personal lan. I can't nslookup URLs outside of my lan. If I manually add the nameservers in the dhcp lease, I can nslookup www.google.com. But ping has 100% packet loss. /etc/hosts associates 127.0.0.1 with localhost.krig.net, and 192.168.0.6 with stamfordbru.krig.net, which is correct for my lan. I'm stumped. :) I don't know if this is related; the XP box is telling me that the router has no connection to the internet, but it obviously does have a connection because the XP box can load web pages and I can use my gmail account. Thanks for any help. I happen to have a Linksys router (not the same model though) and a Linksys pci card that uses the ral driver. Never had any problems, though I am not using DHCP. Here are a few manual steps to try: First off, try setting the ssid on the command line: ifconfig ral ssid Myssid Some wireless interfaces need to be gone UP by hand so set ssid by previous command and then execute ifconfig ral0 up william Execute ifconfig by itself, and see if you get an associated message. (you may have to wait a minute before you do) If you don't, chances are the following will do nothing dhclient ral0 if this does not succeed, set an IP address manually: ifconfig ral0 inet 192.168.1.50 netmask 255.255.255.0 Before attempting to test the internet connection, add the router as nameserver in /etc/resolv.conf and don't forget to add the router's address as the default gateway: route add default 192.168.1.X From my experience, the important part is to get the associated message after the initial ifconfig. Not much hope otherwise. As an afterthought, is the XP machine on while you are trying to connect? If they are too close they maybe interfering. ___ 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: DHCP and Bridge mode
Hi, I am trying to get two machines on the LAN share the same IP address assigned by DHCP server by using the bridge interface in rc.conf. But I have encountered two problems here. I am not sure I understand what you are trying to do, but in general: you cannot have two machine us ethe same IP address, it just does not work; whether you use bridge or not. The A machine, however, seems to have DNS problems as it cannot resolve any addresses. Try to work out your problems using IP address first and something simple like ping. Use tcpdump, you will most certainly see all packets going to machine B instead of machine A. Olivier ___ 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: DHCP and Bridge mode
What you are doing wont work as every machine has to have an individual ip address unless your talking multicast If you are trying to provide some fault tolerance eg two routers you should look at using carp. This will aloow you to have a floating ip between two or more machines. Only one machine has it at any one time though. rg wrote: Hello, I am trying to get two machines on the LAN share the same IP address assigned by DHCP server by using the bridge interface in rc.conf. But I have encountered two problems here. First, the B machine (the one that gets the same IP address as the main A machine) has no problem accessing the Internet. The A machine, however, seems to have DNS problems as it cannot resolve any addresses. And the second problem I've faced is that I cannot figure out how to use SSH to connect to the A machine from the B machine if they both share the same IP address. Or is there a better way to have that kind of remote access? Warm thank you for all the hints. ___ 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: DHCP Request in the background
On Wed, 7 Jan 2009 13:43:24 +0100, Fernando Apesteguía fernando.apesteg...@gmail.com wrote: I would like to know if there is a way (something in rc.conf?) to tell dhcp to run in the background, so while the crappy router is answering my request, hal, dbus and the whole thing can be loaded whitout delay. According to /etc/defaults/rc.conf, there is the following setting: background_dhclient=NO# Start dhcp client in the background. So if you put background_dhclient=YES into your /etc/rc.conf, it should work as expected. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: DHCP Request in the background
On Wed, Jan 7, 2009 at 2:11 PM, Polytropon free...@edvax.de wrote: On Wed, 7 Jan 2009 13:43:24 +0100, Fernando Apesteguía fernando.apesteg...@gmail.com wrote: I would like to know if there is a way (something in rc.conf?) to tell dhcp to run in the background, so while the crappy router is answering my request, hal, dbus and the whole thing can be loaded whitout delay. According to /etc/defaults/rc.conf, there is the following setting: background_dhclient=NO# Start dhcp client in the background. So if you put background_dhclient=YES into your /etc/rc.conf, it should work as expected. My bad, I should have looked at that file. It works fine, Thanks! -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: DHCP server
bofh42 wrote: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' eth0: checking 10.0.0.176 is available on attached networks Are you sure you are using the correct command to start the DHCP client? I'm not familiar with Archlinux, but on Debian linux the command you need is dhclient. On the other hand, dhcpd starts the dhcp *server* Yes, I'm sure. Notice the extra c in there. I'm using the DHCP client deamon. That is, a client that runs in the background keeping my DCHP lease up to speed. The -n option will cause it to signal a renewal. Also, I get similar results if I use the dhclient utility instead of dhcpcd. But thanks for your suggestion! sv. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server
On Sat, 25 Oct 2008 11:38:22 -0400, bofh42 [EMAIL PROTECTED] wrote: Are you sure you are using the correct command to start the DHCP client? I'm not familiar with Archlinux, but on Debian linux the command you need is dhclient. That's correcto about FreeBSD where dhclient or the respective RC script in /etc/rc.d/dhclient is responsible for initiating a DHCP request (by the client). A long time ago, I had played around with TomsRTBT (a Linux that fits on a disk - not a disc); there dhcpcd seemed to be the correct DHCP client site program. On the other hand, dhcpd starts the dhcp *server* Correct. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and MAC addresses
On Mon, Oct 27, 2008 at 3:53 PM, Deian Popov [EMAIL PROTECTED] wrote: Hello, try deny unknown-clients; and may be boot-unknown-clients false; in dhcpd.conf Hi Deian, You guys are great! Thank you very much. One response I got off list was that I could use deny unknown-clients; if I use isc-dhcpd-server, which got me thinking ... is there another dhcp server for FreeBSD in the ports tree, or outside it? BTW, why did you delete the b from your name?:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Life must be understood backwards; but... it must be lived forward. - Soren Kierkegaard Oh My God! They killed init! You Bastards! --from a /. post ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and MAC addresses
On Mon, Oct 27, 2008 at 2:12 PM, Odhiambo Washington [EMAIL PROTECTED]wrote: On Mon, Oct 27, 2008 at 3:53 PM, Deian Popov [EMAIL PROTECTED] wrote: Hello, try deny unknown-clients; and may be boot-unknown-clients false; in dhcpd.conf Hi Deian, You guys are great! Thank you very much. One response I got off list was that I could use deny Sorry for the off list response. It's my mistake of pressing Reply instead of Reply All, like i did now. all the best, v unknown-clients; if I use isc-dhcpd-server, which got me thinking ... is there another dhcp server for FreeBSD in the ports tree, or outside it? BTW, why did you delete the b from your name?:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Life must be understood backwards; but... it must be lived forward. - Soren Kierkegaard Oh My God! They killed init! You Bastards! --from a /. post ___ 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: DHCP and MAC addresses
Hello, try deny unknown-clients; and may be boot-unknown-clients false; in dhcpd.conf Deian On Mon, Oct 27, 2008 at 2:04 PM, Odhiambo Washington [EMAIL PROTECTED]wrote: Hello List, Suppose I have 100 Desktops, and I want my DHCP server to _only_ assign IP addresses to these hosts, using MAC addresses, is there a way to tell the DHCP server to NOT assign any IP address to a machine whose MAC address it doesn't know? I don't want any computer being plugged onto my LAN and getting/using resources without my knowledge. Just some level of paranoia:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Life must be understood backwards; but... it must be lived forward. - Soren Kierkegaard Oh My God! They killed init! You Bastards! --from a /. post ___ 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: DHCP and MAC addresses
On Mon, Oct 27, 2008 at 4:16 PM, Valentin Bud [EMAIL PROTECTED] wrote: On Mon, Oct 27, 2008 at 2:12 PM, Odhiambo Washington [EMAIL PROTECTED] wrote: On Mon, Oct 27, 2008 at 3:53 PM, Deian Popov [EMAIL PROTECTED] wrote: Hello, try deny unknown-clients; and may be boot-unknown-clients false; in dhcpd.conf Hi Deian, You guys are great! Thank you very much. One response I got off list was that I could use deny Sorry for the off list response. It's my mistake of pressing Reply instead of Reply All, like i did now. It wasn't a mistake. As a matter of fact, you can decide to reply to the poster or to the list. I appreciate your response anyway. What I was asking, out of curiosity, is whether there is an alternative to isc-dhcpd-server on FreeBSD. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Life must be understood backwards; but... it must be lived forward. - Soren Kierkegaard Oh My God! They killed init! You Bastards! --from a /. post ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: DHCP and MAC addresses
On Behalf Of Odhiambo Washington One response I got off list was that I could use deny unknown-clients; if I use isc-dhcpd-server, which got me thinking ... is there another dhcp server for FreeBSD in the ports tree, or outside it? I have used dnsmasq on Slackware Linux. It is a combined DNS/DHCP server that works well on small private networks. I don't know if it runs on BSD. Bob McConnell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and MAC addresses
On Mon, Oct 27, 2008 at 09:58:36AM -0400, Bob McConnell wrote: On Behalf Of Odhiambo Washington One response I got off list was that I could use deny unknown-clients; if I use isc-dhcpd-server, which got me thinking ... is there another dhcp server for FreeBSD in the ports tree, or outside it? I have used dnsmasq on Slackware Linux. It is a combined DNS/DHCP server that works well on small private networks. I don't know if it runs on BSD. It is available in the ports tree as ports/dns/dnsmasq -- Insert your favourite quote here. 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: DHCP and MAC addresses
Bob McConnell wrote: On Behalf Of Odhiambo Washington One response I got off list was that I could use deny unknown-clients; if I use isc-dhcpd-server, which got me thinking ... is there another dhcp server for FreeBSD in the ports tree, or outside it? I have used dnsmasq on Slackware Linux. It is a combined DNS/DHCP server that works well on small private networks. I don't know if it runs on BSD. Same here. I've used it on DebianUbuntu without any problem on home network and as Bob mentioned it talks both DNS and DHCP. -- en0f ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and MAC addresses
On Tue, 28 Oct 2008, en0f wrote: Bob McConnell wrote: On Behalf Of Odhiambo Washington One response I got off list was that I could use deny unknown-clients; if I use isc-dhcpd-server, which got me thinking ... is there another dhcp server for FreeBSD in the ports tree, or outside it? I have used dnsmasq on Slackware Linux. It is a combined DNS/DHCP server that works well on small private networks. I don't know if it runs on BSD. Same here. I've used it on DebianUbuntu without any problem on home network and as Bob mentioned it talks both DNS and DHCP. Just took a quick look: %locate dnsmasq /usr/ports/dns/dnsmasq ... Seems to be in the ports tree. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and MAC addresses
On Mon, Oct 27, 2008 at 5:07 PM, en0f [EMAIL PROTECTED] wrote: Bob McConnell wrote: On Behalf Of Odhiambo Washington One response I got off list was that I could use deny unknown-clients; if I use isc-dhcpd-server, which got me thinking ... is there another dhcp server for FreeBSD in the ports tree, or outside it? I have used dnsmasq on Slackware Linux. It is a combined DNS/DHCP server that works well on small private networks. I don't know if it runs on BSD. Same here. I've used it on DebianUbuntu without any problem on home network and as Bob mentioned it talks both DNS and DHCP. Interesting how many people dual-live on this list:-) I have been so allergic to Linux all these years until Ubuntu. I am from Africa and I did not settle on Ubuntu just for the name but because one client insisted he wanted a Unix server and it had to be Linux. I wonder what makes people live in both worlds - *BSD Linux - is it for similar reasons? As regards DNS and DHCP servers, I'd never thought beyond BIND djbdns and isc-dhcpd respectively all these years (yes, my own Unix epoch is 1997). -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Life must be understood backwards; but... it must be lived forward. - Soren Kierkegaard Oh My God! They killed init! You Bastards! --from a /. post ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and MAC addresses
On Mon, Oct 27, 2008 at 06:54:30PM +0300, Odhiambo Washington wrote: I wonder what makes people live in both worlds - *BSD Linux - is it for similar reasons? Living in both worlds is a good thing: keeping an open mind about operating systems and software is one of the best choices one can make. BSD falls short in some areas where Linux excels, and Linux falls short in some areas where BSD excels. It's about using whatever tool works to get things done. If that's BSD, great. If that's Linux, great. If that's Windows, great. But the worst thing one can do is remain close-minded about operating systems; one-sided advocacy (pro-BSD or pro-Linux) does nothing but hurt the open-source concept. (I'll remind folks that ZFS came from Solaris) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and MAC addresses
Hello List,
Suppose I have 100 Desktops, and I want my DHCP server to _only_
assign IP addresses to these hosts, using MAC addresses, is there a
way to tell the DHCP server to NOT assign any IP address to a machine
whose MAC address it doesn't know?
of course.
and you can assign IP to each MAC
first
deny unknown-clients;
(dont specify range at all)
then
host something {
hardware ethernet 00:11:22:33:44:55;
fixed-address 1.2.3.4;
option host-name something.somewhere;
option routers router_IP;
}
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and MAC addresses
On Mon, Oct 27, 2008 at 5:34 PM, Wojciech Puchar
[EMAIL PROTECTED] wrote:
Hello List,
Suppose I have 100 Desktops, and I want my DHCP server to _only_
assign IP addresses to these hosts, using MAC addresses, is there a
way to tell the DHCP server to NOT assign any IP address to a machine
whose MAC address it doesn't know?
of course.
and you can assign IP to each MAC
first
deny unknown-clients;
(dont specify range at all)
But do define the subnet:
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.1;
option domain-name-servers 1.2.3.4;
}
If you have 100 MAC address by this technique you avoid writing
options routers 1.2.3.4; in each host declaration.
No matter how many subnets you have, just define them and write the
router and DNS server(s) there and in the host declaration just the IP and
(optional)
a host-name.
all the best,
v
then
host something {
hardware ethernet 00:11:22:33:44:55;
fixed-address 1.2.3.4;
option host-name something.somewhere;
option routers router_IP;
}
___
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: DHCP server
On Friday 24 October 2008, Svein Halvor Halvorsen wrote: Hi, I'm not sure if this is an issue with my dhcp server or the client, but since I seem to get troubles with two different clients, I'm thinking it might be the server: I've got a FreeBSD 7.0-p4 machine running isc-dhcp3-server-3.0.5_2 serving my home network. When my Linux (Archlinux) client request a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' eth0: checking 10.0.0.176 is available on attached networks Are you sure you are using the correct command to start the DHCP client? I'm not familiar with Archlinux, but on Debian linux the command you need is dhclient. On the other hand, dhcpd starts the dhcp *server* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server
On Fri, Oct 24, 2008 at 11:43:32AM +0200, Svein Halvor Halvorsen wrote: Hi, I'm not sure if this is an issue with my dhcp server or the client, but since I seem to get troubles with two different clients, I'm thinking it might be the server: I've got a FreeBSD 7.0-p4 machine running isc-dhcp3-server-3.0.5_2 serving my home network. When my Linux (Archlinux) client request a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' eth0: checking 10.0.0.176 is available on attached networks ... and then it times out, and does not configure the network. This makes me think that there may be a client issue, since the DCHP server does indeed offer an address. But I also have troubles with a Mac OS X client (although it's a little more vague about the errors). If the server is handing out /24 network prefixes, then once your clients bind the offered address in 10.0.0/24, they can no longer communicate with the server in 10.0.1/24. You can a) give the DHCP server an alias IP address in 10.0.0/24 on the appropriate interface b) change the network prefix to 16 bits, so that 10.0.0 and 10.0.1 (and ALL other addresses with the prefix 10.0) are in the same logical network space c) renumber your DHCP pool Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpj91QEftOyE.pgp Description: PGP signature
Re: DHCP server
a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' what's your netmask? if /24 your dhcp server is misconfigured ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server
Wojciech Puchar wrote: a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' what's your netmask? if /24 your dhcp server is misconfigured No, it's /23, and the dhcp server has address 10.0.1.1, and it's handing out addresses in the the 10.0.0.2-10.0.0.200 range. 10.0.0.1 is a router with static address. It also uses /23. sv. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server
Daniel Bye wrote: On Fri, Oct 24, 2008 at 11:43:32AM +0200, Svein Halvor Halvorsen wrote: Hi, I'm not sure if this is an issue with my dhcp server or the client, but since I seem to get troubles with two different clients, I'm thinking it might be the server: I've got a FreeBSD 7.0-p4 machine running isc-dhcp3-server-3.0.5_2 serving my home network. When my Linux (Archlinux) client request a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' eth0: checking 10.0.0.176 is available on attached networks ... and then it times out, and does not configure the network. This makes me think that there may be a client issue, since the DCHP server does indeed offer an address. But I also have troubles with a Mac OS X client (although it's a little more vague about the errors). If the server is handing out /24 network prefixes, then once your clients bind the offered address in 10.0.0/24, they can no longer communicate with the server in 10.0.1/24. You can a) give the DHCP server an alias IP address in 10.0.0/24 on the appropriate interface b) change the network prefix to 16 bits, so that 10.0.0 and 10.0.1 (and ALL other addresses with the prefix 10.0) are in the same logical network space c) renumber your DHCP pool The dhcp server has netmask /23, and are also handing out this netmask to clients. I have lots of clients running FreeBSD, Windows and OS X not complaining. I do however, have one OS X client that's been constantly complaining, and recently also an Archlinux machine. It used to work on the Linux client up until recently. It might be the client, in which case I should probably ask some Lunux-folks, but since one of the apples also have a problem, I thought I might be the server. Can I diagnose this any further? sv. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: DHCP server
On Behalf Of Svein Halvor Halvorsen Daniel Bye wrote: On Fri, Oct 24, 2008 at 11:43:32AM +0200, Svein Halvor Halvorsen wrote: I'm not sure if this is an issue with my dhcp server or the client, but since I seem to get troubles with two different clients, I'm thinking it might be the server: The dhcp server has netmask /23, and are also handing out this netmask to clients. I have lots of clients running FreeBSD, Windows and OS X not complaining. I do however, have one OS X client that's been constantly complaining, and recently also an Archlinux machine. It used to work on the Linux client up until recently. It might be the client, in which case I should probably ask some Lunux-folks, but since one of the apples also have a problem, I thought I might be the server. Can I diagnose this any further? Set up Wireshark to capture the UDP packets. Compare a successful assignment with the unsuccessful variations. See which side stops responding in each conversation and troubleshoot that end. There may be some clues in the event log on MS-Windows or the syslog files on OS-X. Bob McConnell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP release/renew lease - elegant solution?
On Friday 17 October 2008 23:24:00 Nerius Landys wrote: I have an always-on FreeBSD box which is connected to the internet. My ISP is some cable company and the IP address is determined via DHCP; I used to always get the same IP address but recently the address seems to be changing very frequently whenever I reboot the machine. My problem is that recently, after being on for a day or so, the internet connection to the FreeBSD box breaks down, it stops working or becomes very intermittent/flaky. I then reboot the machine, and thereafter it usually uses a new IP address and the internet connection returns fo running fine. There is no need to reboot the cable modem. If this is an always on machine, it makes no sense, unless the ISP is doing agressive accounting on there IP's: - give out a lease for x hours - but invalidate it anyway after x hours. Doing a periodic dhclient -r would probably fix your problem, though the correct solution would be to complain with your ISP and switch to the competition if they don't get their stuff together. -- 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]
Re: DHCP release/renew lease - elegant solution?
On Mon, Oct 20, 2008 at 03:26:39PM +0200, Mel wrote: On Friday 17 October 2008 23:24:00 Nerius Landys wrote: I have an always-on FreeBSD box which is connected to the internet. My ISP is some cable company and the IP address is determined via DHCP; I used to always get the same IP address but recently the address seems to be changing very frequently whenever I reboot the machine. If this is an always on machine, it makes no sense, unless the ISP is doing agressive accounting on there IP's: - give out a lease for x hours - but invalidate it anyway after x hours. Doing a periodic dhclient -r would probably fix your problem, though the correct solution would be to complain with your ISP and switch to the competition if they don't get their stuff together. It would help if Nerius would spend some time in the system logs and dhclient man page to determine the state when his machine goes deaf. I suspect firewall rules using static host IP address. Believe I have also see this happen with natd, Once Upon A Time natd needed to be restarted when the external IP address changed. Is possible for dhclient to do this automatically. As for a static IP address, many ISPs charge extra for this feature. One ISP I deal with rotates our IP address every 18 to 48 hours and isn't courteous enough to do it on a regular schedule or wait until off hours. Means we have a couple of minutes of down time most every day when the router recovers. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP release/renew lease - elegant solution?
On Fri, 17 Oct 2008 14:24:00 -0700 Nerius Landys [EMAIL PROTECTED] wrote: The -r flag explicitly releases the current lease, and once the lease has been released, the client exits. I could put this into a crontab and run it every 12 hours. However, this does not seem like a very elegant solution to my problem. I am wondering whether there is a more elegant solution. Before you look for a more elegant solution I suggest you try the inelegant solution and see if it actually works. At the moment all you really know is that rebooting fixes the problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and Encapsulating Vendor Options
I have a need to encapsulate option 125 for my phone system on my isc-dhcp server. See http://www.mavetju.org/weblog/html/cat_DHCP.html#00161 and http://www.mavetju.org/weblog/html/cat_DHCP.html#00092 for examples how I did it with APC Power Racks and Cisco phones. I'm not sure what it expects with hexdata, you should give net/dhcpdump a try to figure out what goes over the wire! Edwin -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://www.mavetju.org/weblog/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server with no persistent storage
Quoting Luke Dean [EMAIL PROTECTED]: Will the DHCP server be this trouble-free if I switch my whole network to dynamic IPs? When the DHCP server goes offline, then comes back online, what happens? M0n0wall does it (http://m0n0.ch). I run M0n0 on my 4801 (I'm not using any DHCP on it however), but it seems to work. Maybe you'll find your answers at their site? Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP problem.Help please
On Mon, 2008-04-14 at 14:43 +0800, Ruel Luchavez wrote:
Hello,
I hope some one will me on my problem.
My friends has and existing DHCP server and squid proxy server running both
in freebsd.We purchased a new desktop PC, we gave it a permanent IP using
the DHCP server and we edit the config file in /usr/local/etc/dhcp.conf we
add this at the bottom
host test {
hardware ethernet 00:1d:27:64:e1:af; [this is the physical address of new
PC]
fixed address 192.168.1.16;
}
But as we ipconfig the new PC the IP is still the same?
Is there something i forgot to configure?
PLEASE HELP here...thanks in adnvanced
So you used dhcp to obtain an ip prior to setting up a fixed address on
the dhcp server? If so you may have to clear your dhclient.leases file-
rename to .old (correct me if theres a better way to do this anyone).
When testing, use dhcpd -d - this will run the dhcp server in the
foreground so you can see any messages realtime which you can then post
here if need be. Also, send the entries in your log files.
Good luck.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP problem.Help please
How to reload the dhcpd? what would be the command fo it?
Best regards..
On Mon, Apr 14, 2008 at 3:12 PM, Wojciech Puchar
[EMAIL PROTECTED] wrote:
add this at the bottom
host test {
hardware ethernet 00:1d:27:64:e1:af; [this is the physical address of
new
PC]
fixed address 192.168.1.16;
}
But as we ipconfig the new PC the IP is still the same?
Is there something i forgot to configure?
PLEASE HELP here...thanks in adnvanced
no idea. try turning off then on network interface in windoze.
did you reloaded dhcpd?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP problem.Help please
How to reload the dhcpd? what would be the command fo it?
/usr/local/etc/rc.d/isc-dhcpd restart
Best regards..
On Mon, Apr 14, 2008 at 3:12 PM, Wojciech Puchar
[EMAIL PROTECTED] wrote:
add this at the bottom
host test {
hardware ethernet 00:1d:27:64:e1:af; [this is the physical address of
new
PC]
fixed address 192.168.1.16;
}
But as we ipconfig the new PC the IP is still the same?
Is there something i forgot to configure?
PLEASE HELP here...thanks in adnvanced
no idea. try turning off then on network interface in windoze.
did you reloaded dhcpd?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: DHCP problem.Help please
How to reload the dhcpd? what would be the command fo it? Best regards.. On the freebsd server use: /usr/local/etc/rc.d/isc-dhcpd restart On a windows box do : Start -- run Type cmd klik ok Then you'll get a dos box ipconfig /release This releases the ip adres ipconfig /renew try to get a new adres. Regards, Johan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP problem.Help please
Thanks Johan Puchar, your advise is very effective. again thank you.. On Mon, Apr 14, 2008 at 3:36 PM, Johan Hendriks [EMAIL PROTECTED] wrote: How to reload the dhcpd? what would be the command fo it? Best regards.. On the freebsd server use: /usr/local/etc/rc.d/isc-dhcpd restart On a windows box do : Start -- run Type cmd klik ok Then you'll get a dos box ipconfig /release This releases the ip adres ipconfig /renew try to get a new adres. Regards, Johan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Question
On Wed, Mar 19, 2008 at 9:36 PM, [EMAIL PROTECTED] wrote:
I am in the process of moving my phone system DHCP from my Mitel 3300 to a
FreeBSD so I can parse the DHCP file. In order to make Mitel's option 125
work correctly, I have to specify some vendor specific options. I believe
this is option 124 if I understand the Mitel documentation correctly.
We have a Mitel 3300 and use OpenBSD servers with the ISC DHCP server.
We have 5212 and 5224 IP phones and 5550 IP consoles. The consoles
are the trickiest of all to get working with DHCP. Below are the
sections from our DHCP config that relate to the Mitel. A few things
to note about it. 10.1.254.254 is our name server and dhcp server.
10.1.5.1 is the IP of our Mitel 3300 controller/server. the
/sysro/e2t8260 is the path of our e2t. The two most key components to
get it to work are the option-128 and option-129. You need to set
these as the hex representation of the IP address of your Mitel
controller, so in our case, 10.1.5.1 became 0A:01:05:01. It won't
work otherwise. 10.1.254.255 is our VPN gateway to our other office.
The vendor-class-identifier for mitel phones is always null (at least
for the 5212, 5224, and 5550 consoles). We use this to separate the
Mitel phones into a separate class so they are in their own IP block.
We originally just used the vendor-class-identifier thing, but then
started to find NICs that had vendor-class-identifier = null, so I
noticed that all of our Mitel device MAC addresses start with
1:08:00:0f., so we use that to separate them as well. It is a bad
hack, but it works for us. Anyway, with this config, we have 5212,
5224, and 5550 consoles getting their addresses with DHCP. Feel free
to contact me if you have any questions.
# MITEL E2T TFTP boot
host mitele2t {
hardware ethernet 08:00:0f:1d:7e:e7;
fixed-address 10.1.5.2;
next-server 10.1.5.1;
filename /sysro/E2T8260;
}
#
#
#
# THESE DEFINITIONS MUST BE PRESERVED AS IS. The 5550 Mitel
# consoles will not work unless these options are EXACTLY
# as below.
#
#
#
option option-128 code 128 = string;
option option-129 code 129 = string;
option option-130 code 130 = text;
option option-66 code 66 = string;
option option-67 code 67 = string;
subnet 10.1.0.0 netmask 255.255.0.0 {
class mitel-phone {
match if option vendor-class-identifier = null
and substring(pick-first-value(option
dhcp-client-identifier,hardware), 0, 4) = 1:08:00:0f;
}
pool {
allow members of mitel-phone;
range 10.1.6.1 10.1.7.254;
option routers 10.1.254.254;
option option-66 10.1.5.1;
option option-67 /sysro/e2t8260;
option option-128 0A:01:05:01;
option option-129 0A:01:05:01;
#option tftp-server-name 10.1.1.1;
option option-130 MITEL IP PHONE;
}
pool {
deny members of mitel-phone;
range 10.1.3.100 10.1.4.255;
option routers 10.1.254.254;
}
option broadcast-address 10.1.255.255;
option subnet-mask 255.255.0.0;
option netbios-name-servers 10.1.254.254;
option netbios-dd-server 10.1.254.254;
option netbios-node-type 8;
option netbios-scope ;
}
Hope this helps.
Preston
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Question
Hi, Jay--
On Mar 19, 2008, at 7:36 PM, [EMAIL PROTECTED] wrote:
I am in the process of moving my phone system DHCP from my Mitel
3300 to a
FreeBSD so I can parse the DHCP file. In order to make Mitel's
option 125
work correctly, I have to specify some vendor specific options. I
believe
this is option 124 if I understand the Mitel documentation correctly.
[ ... ]
Can someone point me in the right direction?
For the ISC DHCP server, here's an example for setting option 252 for
auto-proxy config:
option wpad-url code 252 = text;
subnet _yournetwork_ netmask _yournetmask_ {
option wpad-url http://proxy/proxy.pac;;
...
}
You'd need to choose your own option name for option code 124, and a
type (probably string), and then set whatever config you need in that
option statement...
--
-Chuck
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Server
BSD box, the other client is connected via a bridge on the first client. I
have a section in my /usr/local/etc/dhcpd.conf to assign a specific IP to
client #1:
host myhost {
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed address 192.168.1.16;
}
The problem is, both client #1 and #2 get assigned the same IP address which
results in a conflict (I'm guessing because they appear to be behind the
it means that the first client's bridge is not a bridge.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: DHCP Server
-Original Message-
From: Wojciech Puchar [mailto:[EMAIL PROTECTED]
Sent: 24 February 2008 08:56 PM
To: Jaco le Roux
Cc: freebsd-questions@freebsd.org
Subject: Re: DHCP Server
BSD box, the other client is connected via a bridge on the first client.
I
have a section in my /usr/local/etc/dhcpd.conf to assign a specific IP
to
client #1:
host myhost {
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed address 192.168.1.16;
}
The problem is, both client #1 and #2 get assigned the same IP address
which
results in a conflict (I'm guessing because they appear to be behind the
it means that the first client's bridge is not a bridge.
Hm. Well it's a bridge made by windows xp from one interface to another.
You're telling me that it won't work like that?
If I use 'arp ip-address' on the two clients, it resolves to the same MAC
address :/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and DNS
-- Original message --
From: Thomas D. Dean [EMAIL PROTECTED]
I had a wired network with a FreeBSD gateway/firewall. The gateway
died and I converted to a mixed network with a Belkin N1 wireless
router.
I have 2 windows machines and 3 FreeBSD 6.2-stable machines.
fix etc/rc.conf and reboot.
dhclient is running. I have leases and can access the web.
All machines can ping the outside world by name and any other machine
by IP.
The windows machines can ping any other maching by name.
The FreeBSD machines can not ping any local machine by name.
What accesses the router to get DHCP info?
# cat /etc/hosts | sed '/^#/d'
::1 localhost localhost.my.domain
127.0.0.1 localhost localhost.my.domain
# hostname
dv6000
# ping dv6000
ping: cannot resolve dv6000: Unknown host
I am missing something. What?
tomdean
# cat /var/db/dhclient*
lease {
interface fxp0;
fixed-address 192.168.2.5;
option subnet-mask 255.255.255.0;
option routers 192.168.2.1;
option domain-name-servers 192.168.2.1,66.93.87.2,216.231.41.2;
option domain-name tddhome;
option dhcp-lease-time 283824000;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.2.1;
renew 3 2012/3/28 05:36:11;
rebind 3 2015/8/12 02:36:11;
expire 0 2016/9/25 17:36:11;
}
I cannot get DNS for machines inside the router
# dig dv6000
; DiG 9.3.4-P1 dv6000
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 42504
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;dv6000.IN A
;; Query time: 0 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Fri Sep 28 11:37:49 2007
;; MSG SIZE rcvd: 24
But, I can see machines outside the router
# dig mail.speakeasy.org
; DiG 9.3.4-P1 mail.speakeasy.org
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 27174
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;mail.speakeasy.org.IN A
;; ANSWER SECTION:
mail.speakeasy.org. 60 IN A 69.17.117.59
;; Query time: 1 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Fri Sep 28 11:46:20 2007
;; MSG SIZE rcvd: 52
Do you have an internal DNS server? Is it possible the windows boxes are using
NetBIOS for name resolution, and hence can ping each other by name? Absent and
internal DNS server, the FreeBSD machines would be stumped...for internal name
resolution.
Bob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and DNS
How can I get FreeBSD to query the router for IP information for other machines? tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and DNS
The router provides DHCP services. The windows boxes can ping the FreeBDS boxes by name. tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and DNS
On Sep 28, 2007, at 12:27 PM, Thomas D. Dean wrote: How can I get FreeBSD to query the router for IP information for other machines? Your question isn't very clear, but if you want to configure FreeBSD to use a nameserver on your router (or elsewhere), set up /etc/ resolv.conf. Otherwise, FreeBSD will issue ARP queries to locate other machines on the local subnet. Normally, the machine itself will reply, but it's certainly possible for other devices to publish that info (via proxy-arping; see man arp). -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and DNS
I have a Belkin N1 wireless router with a mix of wireless and wired machines. 2 wired FreeBSD machines, 1 wired Windows machine, 1 wireless FreeBSD machine, -current wpi driver in the works, and a wireless windows machine. The wired FreeBSD machines get leases with dhclient. Looking at the router with seamonkey, I can see the leases for all the machines. Do I have to manually create/maintain /etc/hosts on each FreeBSD machine to use names to access the other machines on the local network? Is there a tool to extract lease information from the router? tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and DNS
On Sep 28, 2007, at 1:19 PM, Thomas D. Dean wrote: I have a Belkin N1 wireless router with a mix of wireless and wired machines. 2 wired FreeBSD machines, 1 wired Windows machine, 1 wireless FreeBSD machine, -current wpi driver in the works, and a wireless windows machine. The wired FreeBSD machines get leases with dhclient. Looking at the router with seamonkey, I can see the leases for all the machines. Do I have to manually create/maintain /etc/hosts on each FreeBSD machine to use names to access the other machines on the local network? Is there a tool to extract lease information from the router? You could write something with curl or wget easily enough, but for that kind of situation, you're better off setting up a dhcpd on one of the machines and allocating fixed IPs to the MAC addresses of the boxes you care about. From there, you can either set up a static hosts file which matches the DHCP assignments, or set up local DNS. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and DNS
At 01:48 PM 9/28/2007, Thomas D. Dean wrote:
I had a wired network with a FreeBSD gateway/firewall. The gateway
died and I converted to a mixed network with a Belkin N1 wireless
router.
I have 2 windows machines and 3 FreeBSD 6.2-stable machines.
fix etc/rc.conf and reboot.
dhclient is running. I have leases and can access the web.
All machines can ping the outside world by name and any other machine
by IP.
The windows machines can ping any other maching by name.
The FreeBSD machines can not ping any local machine by name.
What accesses the router to get DHCP info?
# cat /etc/hosts | sed '/^#/d'
::1 localhost localhost.my.domain
127.0.0.1 localhost localhost.my.domain
You need to add the hostname dv6000 entry to hosts, or create your own zone
files and run bind. As these are private IP's you need either to update
hosts or run DNS. You may find it easier to give servers static private
IP's that way you are assured your hosts entries or DNS entries are correct.
# hostname
dv6000
# ping dv6000
ping: cannot resolve dv6000: Unknown host
I am missing something. What?
tomdean
# cat /var/db/dhclient*
lease {
interface fxp0;
fixed-address 192.168.2.5;
option subnet-mask 255.255.255.0;
option routers 192.168.2.1;
option domain-name-servers 192.168.2.1,66.93.87.2,216.231.41.2;
option domain-name tddhome;
option dhcp-lease-time 283824000;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.2.1;
renew 3 2012/3/28 05:36:11;
rebind 3 2015/8/12 02:36:11;
expire 0 2016/9/25 17:36:11;
}
I cannot get DNS for machines inside the router
# dig dv6000
; DiG 9.3.4-P1 dv6000
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 42504
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;dv6000.IN A
;; Query time: 0 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Fri Sep 28 11:37:49 2007
;; MSG SIZE rcvd: 24
But, I can see machines outside the router
# dig mail.speakeasy.org
; DiG 9.3.4-P1 mail.speakeasy.org
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 27174
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;mail.speakeasy.org.IN A
;; ANSWER SECTION:
mail.speakeasy.org. 60 IN A 69.17.117.59
;; Query time: 1 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Fri Sep 28 11:46:20 2007
;; MSG SIZE rcvd: 52
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP and DNS
You need to add the hostname dv6000 entry to hosts, or create your own zone files and run bind. As these are private IP's you need either to update hosts or run DNS. You may find it easier to give servers static private IP's that way you are assured your hosts entries or DNS entries are correct. AHA! where is my head? All the FreeBSD machines run samba. # nmblookup asus fueno dv6000 hp_pavillion nat-valid-name \ | sed -e '/^query/d' -e '/name.*failed/d' -e 's/00//' 192.168.2.6 asus 192.168.2.3 fueno 192.168.2.5 dv6000 192.168.2.4 hp_pavillion and, put this in /etc/hosts, periodically. Then, all I need to know is the names of the machines, which I can put on one machine and copy it to others. Any other ideas? tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP client configuration on FreeBSD
--- Beech Rintoul [EMAIL PROTECTED] wrote: On Saturday 28 April 2007, L Goodwin said: --- Beech Rintoul [EMAIL PROTECTED] wrote: On Friday 27 April 2007, L Goodwin said: When I ran the DHCP client configuration tool on FreeBSD 6.2, it added a new hostname variable to /etc/rc.conf below existing the hostname var (it did not remove or comment-out the old hostname variable). The NEW hostname includes the ISP's domain name: hostname=dhcppc0.ISP domain name here This hostname differs from the hostname listed in the router's DHCP table dhcpp0 (no domain name). It also shows unique IP addresses and MAC addresses for all hosts on the LAN. I can ping the IP address assigned to the FreeBSD system, but ping and net lookup fail when its hostname is specified (both with and without the domain name). Questions: 1) Why did the hostname get changed (does not occur for Windows clients)? 2) Why does the hostname in /etc/rc.conf contain the DNS domain name? FreeBSD uses the FQDN (fully qualified domain name) as the hostname. Example: hostname= yourmachine.yourdomain.com 3) How do I resolve this problem? Unless you provide your own DNS that resolves your internal network and supersede dhclient with your domain name, DHCP will use the domain and DNS from your provider. Your windows boxes point to your isp's nameservers which have no records of your server or it's address. Therefore it can't resolve your machine's hostname. If you do provide your own internal name service you will also need to edit /etc/dhclient.config (see man dhclient.conf), and point your windows boxes to your DNS instead of your isp's. You can use a fictitious domain name internally, just make sure that the domain doesn't actually exist on the net. You can also use the FreeBSD IP address as a domain name on your windows boxes to connect. Is there a way to a) make dhclient use hostname without a domain name appended, or b) make dhclient instruct the DHCP server to append the domain name to the hostname? You're confusing windows networking with real networking. If all you're trying to do is share files with the windows boxes, just put the machine name as hostname and don't worry what gets appended to it. Samba will handle the windows part of it (machine name and workgroup). Windows uses a different system to identify machines on it's network. Don't confuse a windows domain with a real domain they are different things. On a windows network you use samba to make the windows boxes think that the FreeBSD box is one of theirs and share files and printers. You can find detailed how-to's on samba's site. There is no need to ping by hostname unless you're running a server on the FreeBSD box in which case you need to setup real DNS or just use the FreeBSD IP as the hostname from windows. Running bind requires a fairly steep learning curve, but there are simple nameservers in the ports tree that would probably better suit your needs. Are you referring to the built-in command in bsh that lists/alters key bindings for the line editor? I don't understand what bind has to do with any of this. I'm not talking about binding keys, what I was talking about is bind. That's a dns server already in the base system. If you want to freely resolve your machines by hostname and domain you probably need to set up a caching nameserver to resolve your internal network. And point all your machines at it. I was wrestling with a few different issues. It finally came down to these few things: I needed to verify that the server was accessible from both Windows clients (XP Pro and Vista Home), and it was necessary to enable each Windows client to resolve the server hostname to its IP address. I did this by adding an entry to the hosts and lmhosts (for good measure) files on both clients. This was easy under XP Pro. It was a little more complicated under Vista -- I got to learn about the User Access Control, which was preventing me from saving changes to the hosts and lmhosts.sam files. After this I was able to view/read files on the share, but not write to it. I had to change directory permissions on the samba share (chmod o+w) to enable users to connect as guests with no authentication. I had assumed that since this is not mentioned anywhere that it was handled by Samba. I was finally able to create/copy files and folders to the share. Woo-hoo! The next step is to implement a form of security that will work for both Windows XP Pro and Windows Vista Home Premium. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list
Re: DHCP client configuration on FreeBSD
--- Beech Rintoul [EMAIL PROTECTED] wrote: On Friday 27 April 2007, L Goodwin said: When I ran the DHCP client configuration tool on FreeBSD 6.2, it added a new hostname variable to /etc/rc.conf below existing the hostname var (it did not remove or comment-out the old hostname variable). The NEW hostname includes the ISP's domain name: hostname=dhcppc0.ISP domain name here This hostname differs from the hostname listed in the router's DHCP table dhcpp0 (no domain name). It also shows unique IP addresses and MAC addresses for all hosts on the LAN. I can ping the IP address assigned to the FreeBSD system, but ping and net lookup fail when its hostname is specified (both with and without the domain name). Questions: 1) Why did the hostname get changed (does not occur for Windows clients)? 2) Why does the hostname in /etc/rc.conf contain the DNS domain name? FreeBSD uses the FQDN (fully qualified domain name) as the hostname. Example: hostname= yourmachine.yourdomain.com 3) How do I resolve this problem? Unless you provide your own DNS that resolves your internal network and supersede dhclient with your domain name, DHCP will use the domain and DNS from your provider. Your windows boxes point to your isp's nameservers which have no records of your server or it's address. Therefore it can't resolve your machine's hostname. If you do provide your own internal name service you will also need to edit /etc/dhclient.config (see man dhclient.conf), and point your windows boxes to your DNS instead of your isp's. You can use a fictitious domain name internally, just make sure that the domain doesn't actually exist on the net. You can also use the FreeBSD IP address as a domain name on your windows boxes to connect. Is there a way to a) make dhclient use hostname without a domain name appended, or b) make dhclient instruct the DHCP server to append the domain name to the hostname? Running bind requires a fairly steep learning curve, but there are simple nameservers in the ports tree that would probably better suit your needs. Are you referring to the built-in command in bsh that lists/alters key bindings for the line editor? I don't understand what bind has to do with any of this. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP client configuration on FreeBSD
On Saturday 28 April 2007, L Goodwin said: --- Beech Rintoul [EMAIL PROTECTED] wrote: On Friday 27 April 2007, L Goodwin said: When I ran the DHCP client configuration tool on FreeBSD 6.2, it added a new hostname variable to /etc/rc.conf below existing the hostname var (it did not remove or comment-out the old hostname variable). The NEW hostname includes the ISP's domain name: hostname=dhcppc0.ISP domain name here This hostname differs from the hostname listed in the router's DHCP table dhcpp0 (no domain name). It also shows unique IP addresses and MAC addresses for all hosts on the LAN. I can ping the IP address assigned to the FreeBSD system, but ping and net lookup fail when its hostname is specified (both with and without the domain name). Questions: 1) Why did the hostname get changed (does not occur for Windows clients)? 2) Why does the hostname in /etc/rc.conf contain the DNS domain name? FreeBSD uses the FQDN (fully qualified domain name) as the hostname. Example: hostname= yourmachine.yourdomain.com 3) How do I resolve this problem? Unless you provide your own DNS that resolves your internal network and supersede dhclient with your domain name, DHCP will use the domain and DNS from your provider. Your windows boxes point to your isp's nameservers which have no records of your server or it's address. Therefore it can't resolve your machine's hostname. If you do provide your own internal name service you will also need to edit /etc/dhclient.config (see man dhclient.conf), and point your windows boxes to your DNS instead of your isp's. You can use a fictitious domain name internally, just make sure that the domain doesn't actually exist on the net. You can also use the FreeBSD IP address as a domain name on your windows boxes to connect. Is there a way to a) make dhclient use hostname without a domain name appended, or b) make dhclient instruct the DHCP server to append the domain name to the hostname? You're confusing windows networking with real networking. If all you're trying to do is share files with the windows boxes, just put the machine name as hostname and don't worry what gets appended to it. Samba will handle the windows part of it (machine name and workgroup). Windows uses a different system to identify machines on it's network. Don't confuse a windows domain with a real domain they are different things. On a windows network you use samba to make the windows boxes think that the FreeBSD box is one of theirs and share files and printers. You can find detailed how-to's on samba's site. There is no need to ping by hostname unless you're running a server on the FreeBSD box in which case you need to setup real DNS or just use the FreeBSD IP as the hostname from windows. Running bind requires a fairly steep learning curve, but there are simple nameservers in the ports tree that would probably better suit your needs. Are you referring to the built-in command in bsh that lists/alters key bindings for the line editor? I don't understand what bind has to do with any of this. I'm not talking about binding keys, what I was talking about is bind. That's a dns server already in the base system. If you want to freely resolve your machines by hostname and domain you probably need to set up a caching nameserver to resolve your internal network. And point all your machines at it. Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP client configuration on FreeBSD
On Friday 27 April 2007, L Goodwin said: When I ran the DHCP client configuration tool on FreeBSD 6.2, it added a new hostname variable to /etc/rc.conf below existing the hostname var (it did not remove or comment-out the old hostname variable). The NEW hostname includes the ISP's domain name: hostname=dhcppc0.ISP domain name here This hostname differs from the hostname listed in the router's DHCP table dhcpp0 (no domain name). It also shows unique IP addresses and MAC addresses for all hosts on the LAN. I can ping the IP address assigned to the FreeBSD system, but ping and net lookup fail when its hostname is specified (both with and without the domain name). Questions: 1) Why did the hostname get changed (does not occur for Windows clients)? 2) Why does the hostname in /etc/rc.conf contain the DNS domain name? FreeBSD uses the FQDN (fully qualified domain name) as the hostname. Example: hostname= yourmachine.yourdomain.com 3) How do I resolve this problem? Unless you provide your own DNS that resolves your internal network and supersede dhclient with your domain name, DHCP will use the domain and DNS from your provider. Your windows boxes point to your isp's nameservers which have no records of your server or it's address. Therefore it can't resolve your machine's hostname. If you do provide your own internal name service you will also need to edit /etc/dhclient.config (see man dhclient.conf), and point your windows boxes to your DNS instead of your isp's. You can use a fictitious domain name internally, just make sure that the domain doesn't actually exist on the net. You can also use the FreeBSD IP address as a domain name on your windows boxes to connect. Running bind requires a fairly steep learning curve, but there are simple nameservers in the ports tree that would probably better suit your needs. Beech Thanks! __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP/NIC IP address contention issues
I'm pretty sure the XP box is configured correctly for DHCP (no static IP), but will check it again. By check the lease information in the DSL modem, do you mean to see if the CM IP Address Expires date is earlier than current date? I unplugged both the modem and the router today before connecting the new FreeBSD box, so I assume that they are both current. I'll investigate/try all of the things you listed and see if anything turns up. I'll also check to see if /etc/rc.conf contains the following entry: ifconfig_fxp0=DHCP Is there any way that the NIC on FreeBSD box could get configured multiple times (e.g., multiple entries in config files), and if so, could this cause this? If the FreeBSD system were configured as a DHCP server (in addition to the router, which definitely is), what would you expect to happen? It shouldn't be, but what if it were? Thank you! Daniel Marsh [EMAIL PROTECTED] wrote: On 4/26/07, L Goodwin [EMAIL PROTECTED] wrote: Will someone please lead me in the right direction towards resolving the following network issue? snip 1) Apr 25 13:33:19 SERVER kernel: arp 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! 2) dhcppc0# Apr 25 14:07:05 dhcpp0 kernel: arp: 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! I ran ipconfig /all on both Windows boxes and found that the FreeBSD box is assigned the same IP address as the Windows XP box (which had that IP address FIRST). Why is the FreeBSD box being assigned a non-unique IP address? Have you checked the network properties (tcp-ip settings) for the XP machine to make sure it's being assigned a dynamic IP address? Have you tried running ipconfig /renew on the XP machine? Have you checked the lease information in the DSL modem? A DHCP server will not hand out the same IP address twice. The only time I've seen something like this happen is when the DHCP lease times out for an IP and windows doesn't renew the lease on the IP, the IP is put into the free-ip's pool and handed out when the DHCP feels up to it... So if the XP machine is setup for DHCP, it got the IP via dhcp, it probably didn't renew the lease on the IP. - Ahhh...imagining that irresistible new car smell? Check outnew cars at Yahoo! Autos. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP/NIC IP address contention issues
I'll double-check the things you listed. If you can tell me what additional info I need to supply and where to get it, I'll be happy to oblige. Thanks... Beech Rintoul [EMAIL PROTECTED] wrote: On Wednesday 25 April 2007, L Goodwin said: Will someone please lead me in the right direction towards resolving the following network issue? I just added a FreeBSD server to a LAN that consists of a router and 2 pc's, one of which is running Windows XP Pro and the other Windows Vista. The lan is connected to the Internet via a cable modem that goes through the router. The router is set up to be the DHCP server. Now it is being assigned a non-unique IP address. Before adding the FreeBSD box to the mix, everybody was getting along fine (unique IP addresses were dynamically assigned to the pc's). I connected the FreeBSD box to the router, selected Configure additional network interfaces from the sysinstall menu, selected fxp0 Intel EtherExpress Pro/100B PCI Fast Ethernet card from the top of the list and clicked OK to prompts to try to configure IPv6 and DCHP. When done, the Network Configuration dialog contained the following values (which I did not alter): Host: dhcppc0 Domain: (the cable provider's domain name) IPv4 Gateway: 192.168.1.1 Name server: (IP address of ISP's name server) Configuration for Interface fxp0: IPv4 Address: 192.168.1.33 Netmask: 255.255.255.0 Extra options: (blank) Note that the Host field does not match the hostname of the FreeBSD box, which is named SERVER (real creative, huh?). I guess I should have changed the Host field to SERVER, eh? Then I got the following console messages on the FreeBSD server: 1) Apr 25 13:33:19 SERVER kernel: arp 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! 2) dhcppc0# Apr 25 14:07:05 dhcpp0 kernel: arp: 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! I ran ipconfig /all on both Windows boxes and found that the FreeBSD box is assigned the same IP address as the Windows XP box (which had that IP address FIRST). Why is the FreeBSD box being assigned a non-unique IP address? 1. Check that your router's dhcp server is set up properly. 2. Check that the windows box is not set up with a static ip. The box could be hard coded to an ip address and your dhcp server thinks the lease is free. Other than that you need to supply more info. Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- - Ahhh...imagining that irresistible new car smell? Check outnew cars at Yahoo! Autos. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP/NIC IP address contention issues
Beech Rintoul [EMAIL PROTECTED] wrote: On Wednesday 25 April 2007, L Goodwin said: Will someone please lead me in the right direction towards resolving the following network issue? I just added a FreeBSD server to a LAN that consists of a router and 2 pc's, one of which is running Windows XP Pro and the other Windows Vista. The lan is connected to the Internet via a cable modem that goes through the router. The router is set up to be the DHCP server. Now it is being assigned a non-unique IP address. Before adding the FreeBSD box to the mix, everybody was getting along fine (unique IP addresses were dynamically assigned to the pc's). I connected the FreeBSD box to the router, selected Configure additional network interfaces from the sysinstall menu, selected fxp0 Intel EtherExpress Pro/100B PCI Fast Ethernet card from the top of the list and clicked OK to prompts to try to configure IPv6 and DCHP. When done, the Network Configuration dialog contained the following values (which I did not alter): Host: dhcppc0 Domain: (the cable provider's domain name) IPv4 Gateway: 192.168.1.1 Name server: (IP address of ISP's name server) Configuration for Interface fxp0: IPv4 Address: 192.168.1.33 Netmask: 255.255.255.0 Extra options: (blank) Note that the Host field does not match the hostname of the FreeBSD box, which is named SERVER (real creative, huh?). I guess I should have changed the Host field to SERVER, eh? Then I got the following console messages on the FreeBSD server: 1) Apr 25 13:33:19 SERVER kernel: arp 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! 2) dhcppc0# Apr 25 14:07:05 dhcpp0 kernel: arp: 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! I ran ipconfig /all on both Windows boxes and found that the FreeBSD box is assigned the same IP address as the Windows XP box (which had that IP address FIRST). Why is the FreeBSD box being assigned a non-unique IP address? 1. Check that your router's dhcp server is set up properly. 2. Check that the windows box is not set up with a static ip. The box could be hard coded to an ip address and your dhcp server thinks the lease is free. Other than that you need to supply more info. Beech On Wednesday 25 April 2007, L Goodwin said: I'll double-check the things you listed. If you can tell me what additional info I need to supply and where to get it, I'll be happy to oblige. Thanks... First off, please don't top post. It makes the conversation hard to follow. On the XP box what does the output of 'ipconfig /all' tell you about the DHCP lease? On the FreeBSD box what is in /etc/rc.conf? On your router what is the DHCP range set to? and how long do the leases last before they expire? And from the other post it's not possible to accidentally make the FreeBSD box a DHCP server. You would have to install the isc-dhcpd port, then configure and start it. If all of the above looks ok, go to /var/db and delete anything that says dhclient.leases then restart your machine and see if you get a new IP. Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP/NIC IP address contention issues
--- Beech Rintoul [EMAIL PROTECTED] wrote:
Beech Rintoul [EMAIL PROTECTED] wrote: On
Wednesday 25
April 2007, L Goodwin said:
Will someone please lead me in the right
direction towards
resolving the following network issue?
I just added a FreeBSD server to a LAN that
consists of a router
and 2 pc's, one of which is running Windows XP
Pro and the other
Windows Vista. The lan is connected to the
Internet via a cable
modem that goes through the router. The router
is set up to be
the DHCP server. Now it is being assigned a
non-unique IP
address.
Before adding the FreeBSD box to the mix,
everybody was getting
along fine (unique IP addresses were dynamically
assigned to the
pc's).
I connected the FreeBSD box to the router,
selected Configure
additional network interfaces from the
sysinstall menu, selected
fxp0 Intel EtherExpress Pro/100B PCI Fast
Ethernet card from
the top of the list and clicked OK to prompts
to try to
configure IPv6 and DCHP. When done, the Network
Configuration
dialog contained the following values (which I
did not alter):
Host: dhcppc0
Domain: (the cable provider's domain name)
IPv4 Gateway: 192.168.1.1
Name server: (IP address of ISP's name server)
Configuration for Interface fxp0:
IPv4 Address: 192.168.1.33
Netmask: 255.255.255.0
Extra options: (blank)
Note that the Host field does not match the
hostname of the
FreeBSD box, which is named SERVER (real
creative, huh?). I
guess I should have changed the Host field to
SERVER, eh?
Then I got the following console messages on the
FreeBSD server:
1) Apr 25 13:33:19 SERVER kernel: arp
00:40:f4:47:fb:8e is using
my IP address xxx.xxx.x.xx! 2) dhcppc0# Apr 25
14:07:05 dhcpp0
kernel: arp: 00:40:f4:47:fb:8e is using my IP
address
xxx.xxx.x.xx!
I ran ipconfig /all on both Windows boxes and
found that the
FreeBSD box is assigned the same IP address as
the Windows XP box
(which had that IP address FIRST). Why is the
FreeBSD box being
assigned a non-unique IP address?
1. Check that your router's dhcp server is set up
properly.
2. Check that the windows box is not set up with a
static ip. The
box could be hard coded to an ip address and your
dhcp server
thinks the lease is free.
Other than that you need to supply more info.
Beech
On Wednesday 25 April 2007, L Goodwin said:
I'll double-check the things you listed. If you
can tell me what
additional info I need to supply and where to get
it, I'll be happy
to oblige. Thanks...
On the XP box what does the output of 'ipconfig
/all' tell you about the DHCP lease?
Lease Obtained: Thursday, April 26, 2007 7:36:42 AM
Lease Expires: Sunday, April 29, 2007 7:36:42 AM
(also says Dhcp Enabled: Yes and Autoconfiguration
enabled: Yes)
Given these settings, I don't think I need to run
ipconfig /renew on this system...
Note: I wasn't able to get on the Vista box to get
current ipconfig /all output. An older printout shows
DHCP Enabled: No, but it was enabled last time I
checked. I'll check again.
On the FreeBSD box what is in /etc/rc.conf?
I had a feeling I'd find something like this, but did
not know where to look):
--
hostname=SERVER (this is the hostname I want to use)
ipv6_enable=YES
sshd_enable=YES
usbd_enable=YES
samba_enable=YES
# -- sysinstall generated deltas --
# Wed Apr 25 13:38:08 2007
ifconfig_fxp0=DHCP
ipv6_enable=YES
hostname=dhcppc0.ISP's domain name here
--
Note that there are two each of the ipv6_enable and
hostname entries.
I assume I should remove one of each. I want to use
hostname SERVER. If I delete this one, will it
work?:
hostname=dhcppc0.ISP's domain name here
Please advise as to what to change.
On your router what is the DHCP range set to? and
how long do the leases last before they expire?
And from the other post it's not possible to
accidentally make the FreeBSD box a DHCP server.
You would have to install the isc-dhcpd
port, then configure and start it.
In any case, I verified that it's not installed.
If all of the above looks ok, go to /var/db and
delete anything that says dhclient.leases then
restart your machine and see if you get a new IP.
Found dbclient.leases.fxp0 containing 2 lease {...}
entries and moved it to $HOME (will delete once it's
all working).
I was surprised to find that the entries were for the
Vista system (not the XP box). I'll verify that DHCP
is enabled on the Vista box.
One more question: When using DHCP, do I need to do
anything to enable all hosts on the LAN to know each
other by hostname (i.e., do I need to add entries to
/etc/hosts file?)? Once I reboot the FreeBSD box and
ensure that DHCP is enabled on all hosts, should I be
able to ping the Windoze systems by hostname (does not
currently work)?
Thanks to Beech and
Re: DHCP/NIC IP address contention issues
On Thursday 26 April 2007, L Goodwin said:
--- Beech Rintoul [EMAIL PROTECTED] wrote:
Beech Rintoul [EMAIL PROTECTED] wrote: On
Wednesday 25
April 2007, L Goodwin said:
Will someone please lead me in the right
direction towards
resolving the following network issue?
I just added a FreeBSD server to a LAN that
consists of a router
and 2 pc's, one of which is running Windows XP
Pro and the other
Windows Vista. The lan is connected to the
Internet via a cable
modem that goes through the router. The router
is set up to be
the DHCP server. Now it is being assigned a
non-unique IP
address.
Before adding the FreeBSD box to the mix,
everybody was getting
along fine (unique IP addresses were dynamically
assigned to the
pc's).
I connected the FreeBSD box to the router,
selected Configure
additional network interfaces from the
sysinstall menu, selected
fxp0 Intel EtherExpress Pro/100B PCI Fast
Ethernet card from
the top of the list and clicked OK to prompts
to try to
configure IPv6 and DCHP. When done, the Network
Configuration
dialog contained the following values (which I
did not alter):
Host: dhcppc0
Domain: (the cable provider's domain name)
IPv4 Gateway: 192.168.1.1
Name server: (IP address of ISP's name server)
Configuration for Interface fxp0:
IPv4 Address: 192.168.1.33
Netmask: 255.255.255.0
Extra options: (blank)
Note that the Host field does not match the
hostname of the
FreeBSD box, which is named SERVER (real
creative, huh?). I
guess I should have changed the Host field to
SERVER, eh?
Then I got the following console messages on the
FreeBSD server:
1) Apr 25 13:33:19 SERVER kernel: arp
00:40:f4:47:fb:8e is using
my IP address xxx.xxx.x.xx! 2) dhcppc0# Apr 25
14:07:05 dhcpp0
kernel: arp: 00:40:f4:47:fb:8e is using my IP
address
xxx.xxx.x.xx!
I ran ipconfig /all on both Windows boxes and
found that the
FreeBSD box is assigned the same IP address as
the Windows XP box
(which had that IP address FIRST). Why is the
FreeBSD box being
assigned a non-unique IP address?
1. Check that your router's dhcp server is set up
properly.
2. Check that the windows box is not set up with a
static ip. The
box could be hard coded to an ip address and your
dhcp server
thinks the lease is free.
Other than that you need to supply more info.
Beech
On Wednesday 25 April 2007, L Goodwin said:
I'll double-check the things you listed. If you
can tell me what
additional info I need to supply and where to get
it, I'll be happy
to oblige. Thanks...
On the XP box what does the output of 'ipconfig
/all' tell you about the DHCP lease?
Lease Obtained: Thursday, April 26, 2007 7:36:42 AM
Lease Expires: Sunday, April 29, 2007 7:36:42 AM
(also says Dhcp Enabled: Yes and Autoconfiguration
enabled: Yes)
Given these settings, I don't think I need to run
ipconfig /renew on this system...
Note: I wasn't able to get on the Vista box to get
current ipconfig /all output. An older printout shows
DHCP Enabled: No, but it was enabled last time I
checked. I'll check again.
On the FreeBSD box what is in /etc/rc.conf?
I had a feeling I'd find something like this, but did
not know where to look):
--
hostname=SERVER (this is the hostname I want to use)
ipv6_enable=YES
sshd_enable=YES
usbd_enable=YES
samba_enable=YES
# -- sysinstall generated deltas --
# Wed Apr 25 13:38:08 2007
ifconfig_fxp0=DHCP
ipv6_enable=YES
hostname=dhcppc0.ISP's domain name here
--
Note that there are two each of the ipv6_enable and
hostname entries.
I assume I should remove one of each. I want to use
hostname SERVER. If I delete this one, will it
work?:
hostname=dhcppc0.ISP's domain name here
Please advise as to what to change.
Delete any duplicates that you don't want. You should only have one
entry for hostname=, same for ifconfig_fxp0=.
On your router what is the DHCP range set to? and
how long do the leases last before they expire?
And from the other post it's not possible to
accidentally make the FreeBSD box a DHCP server.
You would have to install the isc-dhcpd
port, then configure and start it.
In any case, I verified that it's not installed.
If all of the above looks ok, go to /var/db and
delete anything that says dhclient.leases then
restart your machine and see if you get a new IP.
Found dbclient.leases.fxp0 containing 2 lease {...}
entries and moved it to $HOME (will delete once it's
all working).
You don't need to save that. A new one has already been generated.
Backing up is always a good idea.
Re: DHCP/NIC IP address contention issues
On 4/26/07, L Goodwin [EMAIL PROTECTED] wrote: Will someone please lead me in the right direction towards resolving the following network issue? snip 1) Apr 25 13:33:19 SERVER kernel: arp 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! 2) dhcppc0# Apr 25 14:07:05 dhcpp0 kernel: arp: 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! I ran ipconfig /all on both Windows boxes and found that the FreeBSD box is assigned the same IP address as the Windows XP box (which had that IP address FIRST). Why is the FreeBSD box being assigned a non-unique IP address? Have you checked the network properties (tcp-ip settings) for the XP machine to make sure it's being assigned a dynamic IP address? Have you tried running ipconfig /renew on the XP machine? Have you checked the lease information in the DSL modem? A DHCP server will not hand out the same IP address twice. The only time I've seen something like this happen is when the DHCP lease times out for an IP and windows doesn't renew the lease on the IP, the IP is put into the free-ip's pool and handed out when the DHCP feels up to it... So if the XP machine is setup for DHCP, it got the IP via dhcp, it probably didn't renew the lease on the IP. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP/NIC IP address contention issues
On Wednesday 25 April 2007, L Goodwin said: Will someone please lead me in the right direction towards resolving the following network issue? I just added a FreeBSD server to a LAN that consists of a router and 2 pc's, one of which is running Windows XP Pro and the other Windows Vista. The lan is connected to the Internet via a cable modem that goes through the router. The router is set up to be the DHCP server. Now it is being assigned a non-unique IP address. Before adding the FreeBSD box to the mix, everybody was getting along fine (unique IP addresses were dynamically assigned to the pc's). I connected the FreeBSD box to the router, selected Configure additional network interfaces from the sysinstall menu, selected fxp0 Intel EtherExpress Pro/100B PCI Fast Ethernet card from the top of the list and clicked OK to prompts to try to configure IPv6 and DCHP. When done, the Network Configuration dialog contained the following values (which I did not alter): Host: dhcppc0 Domain: (the cable provider's domain name) IPv4 Gateway: 192.168.1.1 Name server: (IP address of ISP's name server) Configuration for Interface fxp0: IPv4 Address: 192.168.1.33 Netmask: 255.255.255.0 Extra options: (blank) Note that the Host field does not match the hostname of the FreeBSD box, which is named SERVER (real creative, huh?). I guess I should have changed the Host field to SERVER, eh? Then I got the following console messages on the FreeBSD server: 1) Apr 25 13:33:19 SERVER kernel: arp 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! 2) dhcppc0# Apr 25 14:07:05 dhcpp0 kernel: arp: 00:40:f4:47:fb:8e is using my IP address xxx.xxx.x.xx! I ran ipconfig /all on both Windows boxes and found that the FreeBSD box is assigned the same IP address as the Windows XP box (which had that IP address FIRST). Why is the FreeBSD box being assigned a non-unique IP address? 1. Check that your router's dhcp server is set up properly. 2. Check that the windows box is not set up with a static ip. The box could be hard coded to an ip address and your dhcp server thinks the lease is free. Other than that you need to supply more info. Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Server V3.0.5 No BPF under chroot. Works normally otherwise.
On Tue, Mar 06, 2007 at 07:03:35PM -0600, Martin McCormick wrote: I found some cook-book instructions for running dhcpd in a chroot environment. The article is 4 years old and appears to be set up for FreeBSD5x, but it isn't far off for FreeBSD6.2 which is what I need dhcpd to run on. I run isc-dhcp3-server-3.0.5 from ports, started from /etc/rc.conf with the following options: dhcpd_enable=YES # dhcpd enabled? dhcpd_flags=-q# command option(s) dhcpd_conf=/usr/local/etc/dhcpd.conf # configuration file dhcpd_ifaces= # ethernet interface(s) dhcpd_withumask=022 # file creation mask dhcpd_chuser_enable=YES # runs w/o privileges? dhcpd_withuser=dhcpd # user name to run as dhcpd_withgroup=dhcpd # group name to run as dhcpd_chroot_enable=YES # runs chrooted? dhcpd_devfs_enable=YES# use devfs if available? dhcpd_rootdir=/var/db/dhcpd # directory to run in dhcpd_includedir= # directory with config- Here's the full pkg-message: [EMAIL PROTECTED]/usr/ports/net/isc-dhcp3-server $ make display-message To setup dhcpd, you may have to copy /usr/local/etc/dhcpd.conf.sample to /usr/local/etc/dhcpd.conf for editing. This port installs dhcp daemon, but don't invokes dhcpd by default. If you want to invoke dhcpd at startup, put these lines into /etc/rc.conf. dhcpd_enable=YES # dhcpd enabled? dhcpd_flags=-q# command option(s) dhcpd_conf=/usr/local/etc/dhcpd.conf # configuration file dhcpd_ifaces= # ethernet interface(s) dhcpd_withumask=022 # file creation mask If compiled with paranoia support (the default), the following lines are also supported: dhcpd_chuser_enable=YES # runs w/o privileges? dhcpd_withuser=dhcpd # user name to run as dhcpd_withgroup=dhcpd # group name to run as dhcpd_chroot_enable=YES # runs chrooted? dhcpd_devfs_enable=YES # use devfs if available? dhcpd_makedev_enable=YES# use MAKEDEV instead? dhcpd_rootdir=/var/db/dhcpd # directory to run in dhcpd_includedir=some_dir # directory with config- files to include dhcpd_flags=-early_chroot # needs full root WARNING: -early_chroot requires a jail(8) like environment to work. WARNING: dhcpd_devfs_enable and dhcpd_makedev_enable are mutually exclusive dhcpd_makedev_enable make NO sense on FreeBSD 5.x and up! If compiled with jail support (the default), the following lines are also supported (-early_chroot and dhcpd_chroot_enable=YES are implied): dhcpd_jail_enable=YES # runs imprisoned? dhcpd_hostname=hostname # jail hostname dhcpd_ipaddress=ip address # jail ip address WARNING: dhcpd_rootdir needs to point to a full jail(8) environment. WARNING: never edit the chrooted or jailed dhcpd.conf file but /usr/local/etc/dhcpd.conf instead which is always copied where needed upon startup. WARNING: /usr/local/etc/rc.isc-dhcpd.conf is obsolete. rc.conf like variables are still read there but should be moved /etc/rc.conf or /etc/rc.conf.d/dhcpd instead. Also, the dhcpd_options variable must be renamed dhcpd_flags if any. -- Kelly D. Grills [EMAIL PROTECTED] pgpuJ4kh8oKPm.pgp Description: PGP signature
Re: DHCP server questions
On Jan 18, 2007, at 11:59 AM, Darryl Hoar wrote: I am considering modifying my web/email server by adding DHCP server duties to it. Any problems with this idea ? I can reboot the server if I need to without screwing up the clients that already have IP assigned, can't I ? No, the DHCP server is a rather lightweight daemon and will not add much load to your current system. And yes, one could reboot the machine acting as your DHCP server without screwing up the clients which have already gotten a IP/lease. Note that rebooting a Unix system is normally not needed for anything short of installing a new kernel... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: DHCP server questions
-Original Message- From: Chuck Swiger [mailto:[EMAIL PROTECTED] Sent: Thursday, January 18, 2007 2:28 PM To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: DHCP server questions On Jan 18, 2007, at 11:59 AM, Darryl Hoar wrote: I am considering modifying my web/email server by adding DHCP server duties to it. Any problems with this idea ? I can reboot the server if I need to without screwing up the clients that already have IP assigned, can't I ? No, the DHCP server is a rather lightweight daemon and will not add much load to your current system. And yes, one could reboot the machine acting as your DHCP server without screwing up the clients which have already gotten a IP/lease. Note that rebooting a Unix system is normally not needed for anything short of installing a new kernel... -- -Chuck Thanks Chuck. I do grok that rebooting is only really needed for new kernel installs. Just making network design decisions and want to avoid those Oh, crap moments. -Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server questions
Darryl Hoar wrote: Thanks Chuck. I do grok that rebooting is only really needed for new kernel installs. Just making network design decisions and want to avoid those Oh, crap moments. -Darryl I haven't found too many mutually exclusive services on Unix. In theory, if we did away with redundancy, and got a honkin' HUGE server to handle the load, we could run our entire University on one FreeBSD box (didn't they used to call that a Mainframe?). -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / [EMAIL PROTECTED] Today's Excuse: PEBKAC (Problem Exists Between Keyboard And Chair) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP IP range + auto hostname
Nagy László wrote:
Hello,
I have a DHCP server with this config file:
option domain-name cassiopeia.ronet;
option domain-name-servers 192.168.0.1;
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
ddns-update-style none;
subnet 192.168.0.0 netmask 255.255.0.0 {
range 192.168.0.101 192.168.0.139;
option routers 192.168.0.1;
use-host-decl-names on;
option broadcast-address 192.168.0.255;
filename pxeboot;
option root-path 192.168.0.1:/mnt/d1/rootfs;
}
I would like the diskless machines to set their hostname automatically.
I have a working named for this. For example:
cassiopeia# host diskless131.ronet
diskless131.ronet has address 192.168.0.131
cassiopeia# host 192.168.0.131
131.0.168.192.in-addr.arpa domain name pointer diskless131.ronet.
cassiopeia#
Of course I can create individual hosts in the dhcp config file and set
their hostnames. But I do not want to create 40 host declarations and
look for the hardware addresses by hand... The clients should be able
to determine their hostnames using a reverse dns lookup, and the set
their hostnames automatically. In the above example: after the machine
got its IP address (192.168.0.131) from the DHCP server, it should set
its hostname to 'diskless131.ronet'.
Sounds easy, but I do not know how to do that. Is it a standard
procedure, or do I need to write a custom script? (Where should I place
it?)
IIRC you need to build the kernel for the diskless clients with the
BOOTP options (I don't remember which of them right now), this should
allow the kernel to rerequest parameters later in the boot stage.
Cheers, Erik
--
Ph: +34.666334818 web: http://www.locolomo.org
X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt
Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP question
Walt Pawley writes:
I need to monitor and record that IP address and initiate a
series of processes if/when the IP address changes.
You could schedule a script that uses 'curl' or 'fetch' to
acquire the status page from the router and parse the upstream
IP address from it and compare it with a saved address.
How about:
netstat -rn -f inet | grep default | awk '{print $2}'
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: DHCP question
At 4:20 AM -0700 8/23/06, Vizion wrote: My home network is connected by my Linksys Broadband Router model RT31P2 to an upstream Cable company supplied Motorola SB5100 cable modem. A single IP address is allocated via DHCP to the Linksys to which my private network is attached. The IP address is rarely changed. I need to monitor and record that IP address and initiate a series of processes if/when the IP address changes. Suggestions please... and thanks in advance for any replies David, You could schedule a script that uses 'curl' or 'fetch' to acquire the status page from the router and parse the upstream IP address from it and compare it with a saved address. -- Walter M. Pawley [EMAIL PROTECTED] Wump Research Company 676 River Bend Road, Roseburg, OR 97470 541-672-8975 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP question
At 5:03 PM -0400 8/24/06, Robert Huff wrote:
I need to monitor and record that IP address and initiate a
series of processes if/when the IP address changes.
You could schedule a script that uses 'curl' or 'fetch' to
acquire the status page from the router and parse the upstream
IP address from it and compare it with a saved address.
How about:
netstat -rn -f inet | grep default | awk '{print $2}'
Wouldn't that just get his router's internal NAT address?
--
Walter M. Pawley [EMAIL PROTECTED]
Wump Research Company
676 River Bend Road, Roseburg, OR 97470
541-672-8975
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP question
Vizion írta: My home network is connected by my Linksys Broadband Router model RT31P2 to an upstream Cable company supplied Motorola SB5100 cable modem. A single IP address is allocated via DHCP to the Linksys to which my private network is attached. The IP address is rarely changed. I need to monitor and record that IP address and initiate a series of processes if/when the IP address changes. Suggestions please... and thanks in advance for any replies I do not have a ready-to-use solution, but you might try to download this site with lynx: www.whatismyip.com and extract your 'public' IP address from that page. Best, Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP question
Vizion wrote: My home network is connected by my Linksys Broadband Router model RT31P2 to an upstream Cable company supplied Motorola SB5100 cable modem. A single IP address is allocated via DHCP to the Linksys to which my private network is attached. The IP address is rarely changed. I need to monitor and record that IP address and initiate a series of processes if/when the IP address changes. Suggestions please... and thanks in advance for any replies Might 'ddclient' be what you are referring to? Its in the ports. -- Gerard Seibert [EMAIL PROTECTED] Consider everything in the nature of a hanging fixture a weakness, and naked radiators an abomination Frank Lloyd Wright ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhcp resolv.conf and loading priority of network cards
dick hoogendijk wrote: I have tow nics: a re0 (cabled) and an ath0 (wifi) card. I want the latter to use dhcp like this: defaultrouter=192.168.11.1 hostname=arwen.nagual.st ifconfig_re0=192.168.11.29 netmask 255.255.255.0 ifconfig_ath0=dhcp ssid air01 nwkey 0xc1e1639b753021ab6d64be2575 hidessid authmode shared What happens is that the ath0 card gets loaded first (not wanted!) plus the dhcp setting changes my resolv.conf (not wanted either). How do I get this changed? re0 first, than my ath0 and NO changes to resolv.conf? System: freebsd-6.1R Not sure about initialising interfaces in specific order but if you don't want to accept changes from a DHCP then: man dhclient.conf (look at supersede) Cheers, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: http://www.webanoide.org PGP Key ID: 0x4E148A3B PGP Key Fingerprint: D96B 7C14 79A5 8824 B99D 9562 F50E 2F5D 4E14 8A3B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhcp resolv.conf and loading priority of network cards
On Thu, 22 Jun 2006 21:51:15 +1000 Mikhail Goriachev [EMAIL PROTECTED] wrote: dick hoogendijk wrote: I have tow nics: a re0 (cabled) and an ath0 (wifi) card. I want the latter to use dhcp like this: defaultrouter=192.168.11.1 hostname=arwen.nagual.st ifconfig_re0=192.168.11.29 netmask 255.255.255.0 ifconfig_ath0=dhcp ssid air01 nwkey 0xc1e1639b753021ab6d64be2575 hidessid authmode shared What happens is that the ath0 card gets loaded first (not wanted!) plus the dhcp setting changes my resolv.conf (not wanted either). How do I get this changed? re0 first, than my ath0 and NO changes to resolv.conf? System: freebsd-6.1R Not sure about initialising interfaces in specific order but if you don't want to accept changes from a DHCP then: man dhclient.conf (look at supersede) Yes, I know. I foudn something like that on google. Also a file named dhclient-enter-hooks seems to do the trick, but I miss the option to just say don't use my existing resolv.conf badly. On linux it's easier as I remember (but that's years ago, so things might have changed there too. The initialising in a specific order is more important to me at the moment. Anybody? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 ++ The Power to Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP not working
Pietro Cerutti wrote: Hi List, I can't get a DHCP lease from my cable modem, here are the details: - The PC is a P4 500 MHz running 6.0-RELEASE just installed, GENERIC. - I tried with three different NICs, without result: - a 3Com 3C509 (driver vx), - a RealTek (can't remember the model, is about one year old) (obviously driver rl), - and a D-Link DFE-528TX (driver rl). - The first two NICs are OK with static IP assignement, worked for more than 1.5 years on 5.2.1-RELEASE and 5.4-RELEASE, I didn't tested the last one since I just bought it today... - The modem is OK, no problems with: - a laptop (i386 6-STABLE), - another laptop (Ubuntu), - a desktop PC (Win XP). - My laptop has an integrated RealTek 8139C+ (driver re), and the dhclient configuration is the same as the PC where the problem is (default config), therefor the problem shouldn't be in the configuration. - I don't know if it's important, but the DHCP client never worked, neither during sysinstall - I tried disabling PnP OS in the BIOS, as I read in some forums, but nothing Any ideas? If more detailed infos are needed, please ask! Thank you in advance! -- Pietro Cerutti [EMAIL PROTECTED] Non lasciar calpestare i TUOI diritti! Don't let 'em take YOUR rights! NO al Trusted Computing! Say NO to Trusted Computing! www.no1984.org www.againsttcpa.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Call your cable/internet provider. Some cable modems/providers limit the number of DHCP/mac addresses allowed per connection, here in our area the limit is 3, after than you have to pay for more. Have run into issues before, just call company and explain that MAC xx:xx:xx... is your new NIC and you can't get a dhcp lease with it, then ask if there is something they have blocking it? That would be my first thing to try, second would be to utilize a different network (cheap $20 dsl/cable router oughta work - try it isolated and see if it gets a dhcp lease) - that way you rule out the issue being the network vs the machine vs the software. -- Nathan Vidican [EMAIL PROTECTED] Windsor Match Plate Tool Ltd. http://www.wmptl.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP not working
On 3/1/06, Nathan Vidican [EMAIL PROTECTED] wrote: Pietro Cerutti wrote: Hi List, I can't get a DHCP lease from my cable modem, here are the details: - The PC is a P4 500 MHz running 6.0-RELEASE just installed, GENERIC. - I tried with three different NICs, without result: - a 3Com 3C509 (driver vx), - a RealTek (can't remember the model, is about one year old) (obviously driver rl), - and a D-Link DFE-528TX (driver rl). - The first two NICs are OK with static IP assignement, worked for more than 1.5 years on 5.2.1-RELEASE and 5.4-RELEASE, I didn't tested the last one since I just bought it today... - The modem is OK, no problems with: - a laptop (i386 6-STABLE), - another laptop (Ubuntu), - a desktop PC (Win XP). - My laptop has an integrated RealTek 8139C+ (driver re), and the dhclient configuration is the same as the PC where the problem is (default config), therefor the problem shouldn't be in the configuration. - I don't know if it's important, but the DHCP client never worked, neither during sysinstall - I tried disabling PnP OS in the BIOS, as I read in some forums, but nothing Any ideas? If more detailed infos are needed, please ask! Thank you in advance! -- Pietro Cerutti [EMAIL PROTECTED] Non lasciar calpestare i TUOI diritti! Don't let 'em take YOUR rights! NO al Trusted Computing! Say NO to Trusted Computing! www.no1984.org www.againsttcpa.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Call your cable/internet provider. Some cable modems/providers limit the number of DHCP/mac addresses allowed per connection, here in our area the limit is 3, after than you have to pay for more. Have run into issues before, just call company and explain that MAC xx:xx:xx... is your new NIC and you can't get a dhcp lease with it, then ask if there is something they have blocking it? With my ISP that number is two, but I tried with one and two different machines connected to the modem, no way... Neither it is the case that the modem remembers the first two MAC which get a lease and discard all different Ethernet addresses cause, as I said, the modem works well with three other machines (two laptops and a desktop, clearly not all three togheter). That would be my first thing to try, second would be to utilize a different network (cheap $20 dsl/cable router oughta work - try it isolated and see if it gets a dhcp lease) - that way you rule out the issue being the network vs the machine vs the software. I've got a switch, to which I could connect my laptop acting as the DHCP server, and the PC acting as the client, and see if it works, but I'm pretty shure that the network is not the problem. I'm sure there's something basilar I'm missing, but can't notice what Thank you Nathan, other advices are welcome! -- Nathan Vidican [EMAIL PROTECTED] Windsor Match Plate Tool Ltd. http://www.wmptl.com/ -- Pietro Cerutti [EMAIL PROTECTED] Non lasciar calpestare i TUOI diritti! Don't let 'em take YOUR rights! NO al Trusted Computing! Say NO to Trusted Computing! www.no1984.org www.againsttcpa.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP leases
On Friday 24 February 2006 12:43, Jose Borquez wrote: I know you can view the current DHCP leases in the dhcpd.leases file, but is there a command that can be used to dynamically view the DHCP leases as they are handed out? tail -f /var/db/dhcpd.leases Beech -- --- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Alaska Paradise Travel \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --- pgpxLnTGamTfW.pgp Description: PGP signature
Re: DHCP leases
On Fri, Feb 24, 2006 at 01:43:40PM -0800, Jose Borquez wrote: I know you can view the current DHCP leases in the dhcpd.leases file, but is there a command that can be used to dynamically view the DHCP leases as they are handed out? man dhcpd.conf man syslog.conf dhcpd writes status updates to syslogd. You can configure syslogd to redirect them to where ever you wish, including piped into another program for additional processing. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP failing with WiFi after 6.0 upgrade
Jesse Sheidlower wrote: I recently took my IBM ThinkPad X23, which had been running 4.11, and did a fresh install (backup files, wipe disk, install from scratch) to 6.0. Most things have gone smoothly, though there are still a few things to iron out. My biggest problem is that I can't seem to get DHCP to work with my wireless card. I have an Orinoco Gold 802.11b card that's always worked fine; I'm about to replace it with something else for 802.11g with a new WAP. There seem to be minor differences in how the card goes in; under 4.11 I would get various beeps when I plugged it in and after it associated, but now it's silent. And I had to remember to load WEP in my kernel. But I can seem to get things started by issuing the command ifconfig wi0 ssid jesterWAP wepmode on wepkey 0x[DELETED] which does seem to successfully reach my WAP: # ifconfig wi0 wi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::202:[DELETED] prefixlen 64 scopeid 0x3 ether 00:02:[DELETED] media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps) status: associated ssid jesterWAP channel 6 bssid 00:[DELETED] stationname FreeBSD WaveLAN/IEEE node authmode OPEN privacy MIXED deftxkey UNDEF wepkey 1:104-bit txpowmax 100 bintval 100 I can't seem to get a DHCP lease, however: # dhclient wi0 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 15 No DHCPOFFERS received. No working leases in persistent database - sleeping. (Under 4.11, I didn't get any verbose output from dhcpclient.) I can get a DHCP lease with fxp0, my Ethernet card; also, some Macs in the house have no problem getting leases through the WAP. (The DHCP server is in a separate router, not in the WAP.) Is there something that's changed under 6.0, or is there just something I'm forgetting to do? I do plan to get a new card, but I want to get this working too. Just about everything about dhclient has changed. The dhclient from ISC has been replaced by a complete new development from the OpenBSD team. Options that previously worked are nolonger recognized. Among these options are the options to configure what wireless network to associate with. Also, added is wpa_supplicant which is used to choose the WLAN to connect to. If there are other WLAN's in your neighbourhood and you have not configured wpa_supplicant, it is likely that you associate with the wrong network and that network doesn't offer a lease. One thing to do, mostly for testing: Reset completely your card so it does not appear to be associated with any network. When you run dhclient and it fails, you should at least be able to see what network it is associated with if any. So, read up on the man-pages, and start over. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhcp server on multiple interfaces.
I hope this helps, assuming you have
/usr/share/doc/dhcp-3.0pl1/dhcpd.conf.sample
Follow the steps
#cp /usr/share/doc/dhcp-3.0pl1/dhcpd.conf.sample
/etc/dhcpd.conf
#ee /etc/dhcpd.conf
your dhcpd.conf
###BEGIN DHCPD.CONF
authoritative
ddns-update-style interim
ignore client-updates
#INTERFACE fxp0 10.0.1.0/24
#It should not be written as 10.0.1.1/24
#The address of this interface (fxp0) is 10.0.1.1
subnet 10.0.1.0 netmask 255.255.255.0 {
range 10.0.1.1 10.0.1.254; #Your clients will get
10.0.1.2 through to 10.0.1.254
default-lease-time 86400;
max-lease-time 86400;
option routers 10.0.1.1; #Change this to the
internal IP address of the gateway
option ip-forwarding off;
option broadcast-address 10.0.1.255;
option subnet-mask 255.255.255.0;
option domain-name-servers 10.0.1.1; #Assuming that
the DHCPD box is also your nameserver
}
#INTERFACE xl0 10.0.0.0/24
#It should not be written as 10.0.0.1/24
#The address of this interface (xl0) is 10.0.0.1
subnet 10.0.0.0 netmask 255.255.255.0 {
range 10.0.0.1 10.0.0.200; #Your clients will get
10.0.0.2 through to 10.0.0.200
default-lease-time 86400;
max-lease-time 86400;
option routers 10.0.0.1; #Change this to the
internal IP address of the gateway
option ip-forwarding off;
option broadcast-address 10.0.0.255;
option subnet-mask 255.255.255.0;
option domain-name-servers 10.0.0.1; #Assuming that
the DHCPD box is also your nameserver
}
###END DHCPD.CONF
--- BSD Mail [EMAIL PROTECTED] wrote:
Hello everyone,
I'm configuring a gateway machine with 3 network
interfaces
int_ext (rl0) will obtained a real static IP from a
public dhcp server.
int_dmz (fxp0) 10.0.1.1/24 http://10.0.1.1/24
both internal networks will need a dhcp server to
assign them the right
subnet
int_lan (xl0) 10.0.0.1/24 http://10.0.0.1/24
I already figured out how to specify multiple
subnets and grouping, static
address etc... in the dhcp config file.
what I want to make sure of is the /etc/rc.conf
would this entry be valid and assign the right IP
from the range of subnet :
dhcpd_ifaces=fxp0 xl0
will that cause the dhcp server to assign
10.0.1.x/24 addresses to the
machines on the switch connected to fxp0 ?
and 10.0.0.x/24 to the machines on the switch
connected to xl0 ?
If not what's the maximum number of interfaces I can
specify in the option
dhcpd_ifaces= assuming I have all the
subnets and related information configured correctly
in the dhcpd.conf ?
--
thanks,
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
__
Yahoo! FareChase: Search multiple travel sites in one
click.
http://farechase.yahoo.com
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhcp client in freebsd 6 beta
The Script needs the Interface as second argument, e.g. /etc/rc.d/dhclient stop fxp0 Greetz, Ice Osmany Guirola Cruz schrieb: Hi people i upgrade my system from 5.4 to 6 Beta 4 and i am using dhclient for my network card i boot without problems get my IP, etc etc but if i do /etc/rc.d/dhclient stop , or start nothing happens . in 5.4 this works perfectly i Know that freebsd changes the dhclient but now how can i use the rc.d script Thanks Osmany ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Frank Mueller eMail: [EMAIL PROTECTED] Mobil: +49.177.6858655 Fax: +49.951.3039342 emendis GmbH Hofmannstr. 89, 91052 Erlangen, Germany Fon: +49.9131.817361 Fax: +49.9131.817386 Geschaeftsfuehrer: Gunter Kroeber, Volker Wiesinger Sitz Erlangen, Amtsgericht Fuerth HRB 10116 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Issue - could not get ip.
Hello. I have a problem with DHCP, i've tried to solve googling, reading post on forums. I have a DHCP cable modem connection. in rc.conf i have ifconfig_vr0=DHCP when i launch dhclient -d vr0 i get: I've tried differend things, like setting the nic for 10 mbps, half-dupplex, reseting the cable modem. (I've talk also with isp, they said does not support FreeBSD or linux) I've tried almost any parameter in dhclient.conf. If i boot on windoze (same box, same nic) DHCP works. I've taken ip and gateway from windoze put with ifconfig in freebsd and internet works. Have you any ideea what should I do? - Maybe tcpdump (propably use ethereal on Windows) the working winxp DHCP connection, then tcpdump the not working FreeBSD connection. Compare them both and try to find the difference. Hexren ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Issue - could not get ip.
Ovidiu Ene wrote:
Hello.
I have a problem with DHCP, i've tried to solve googling, reading post
on forums.
I have a DHCP cable modem connection.
in rc.conf i have ifconfig_vr0=DHCP
when i launch dhclient -d vr0 i get:
I've tried differend things, like setting the nic for 10 mbps,
half-dupplex, reseting the cable modem.
Starting to sound familiar...
(I've talk also with isp, they said does not support FreeBSD or linux)
I got that lame excuse too. My response was that I was really not
asking them to support my BSD box, but merely to tell me what their
DHCP server required. That is, I really needed them to provide
support information for *their* network components, not mine. Taking
this attitude got me escalated to a supervisor who was surprising
helpful and knew what the basic problem was (see below).
I've tried almost any parameter in dhclient.conf.
If i boot on windoze (same box, same nic) DHCP works. I've taken ip and
gateway from windoze put with ifconfig in freebsd and internet works.
Have you any ideea what should I do?
My cable ISP used to require that the client submit a host name with
its request, which if I recall correctly (this was a long time ago),
Windows does and FreeBSD doesn't do by default. I fixed it by adding
an option to dhclient.conf. Like:
interface fxp0 {
send host-name NOWINDRZ;
prepend domain-name-servers 127.0.0.1;
[other standard request stuff here];
}
Hope that helps. You might have tried sending a name before, but if
I recall, sending a FQDN did not work while sending a simple host
name did (using the same name my Windows box had previously
successfully used to get an address, BTW. Not sure that was needed
but it worked).
Also, after your Windows installation successfully got an IP, did
you release it before shutting down and trying FreeBSD? If I recall,
that was also required in my situation.
--
Greg Barniskis, Computer Systems Integrator
South Central Library System (SCLS)
Library Interchange Network (LINK)
gregb at scls.lib.wi.us, (608) 266-6348
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: DHCP Server Offline.
The du command is your friend. Have a look at 'man du' Maybe something like: du -d2 /var Cheers, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephan Weaver Sent: Friday, 15 July 2005 10:25 PM To: [EMAIL PROTECTED]; freebsd-questions@freebsd.org Subject: Re: DHCP Server Offline. I Found out the Problem, The /var partation is full. How do i find out where is taking up all the space? Thanks From: Ean Kingston [EMAIL PROTECTED] To: freebsd-questions@freebsd.org CC: [EMAIL PROTECTED] Subject: Re: DHCP Server Offline. Date: Fri, 15 Jul 2005 10:18:09 -0400 On July 15, 2005 10:11 am, Stephan Weaver wrote: Hello folks, I have a Stand Alone FreeBSD Firewall / Nat / Dhcp Server. Everything seems to work fine, up until this morning. Users seem to complain they could not get on the network anymore. Further investigation revealed the dhcp server could not be contacted. Further more, only some of the users were online. I am guessing that these clients who were online had an ip address from the dhcp server at a previous time and the lease didnt expire as yet. And users who were not online, the lease expired and attempted to contact the dhcp server and failed. I Would appreciate any help or suggestions. Set the lease expire time to at least 5 days (7 to 10 is better) and the renewal time to between 4 and 12 hours. Then setup a dhcp monitoring process that will alert you if it fails to get an address or renewal. Make sure you have more addresses available than you ever expect to give out. I go with 50% more. I've known some admins that want at least double. Like what to do in the future incase this happens again. Setup 2 dhcp servers on the network. If one fails, the other will hopefully continue to serve addresses. Monitor this one as well. I Would like to find out what had happened. Start reading logs. The last thing that i had done to the server was setup, configure and install 'ntop'; dont know if this would cause a problem. Thank you in advance. Stephan Weaver P.S. Please reply to my Directly at @ [EMAIL PROTECTED] -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ I am currently looking for work. If you need competent system/network administration please feel free to contact me directly. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ 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: DHCP assigned unregistered IP address
Bob Hall wrote: 1) It is a Motorola cable modem. (SB5100) The modem web page contained this: The SURFboard cable modem can be used as a gateway to the Internet by a maximum of 32 users on a Local Area Network (LAN). When the Cable Modem is disconnected from the Internet, users on the LAN can be dynamically assigned IP Addresses by the Cable On the SB4100, the Enable DHCP checkbox is right above this blurb. However, note the When the Cable Modem is disconnected from the Internet... so the only reason it should be handing you the local IP is if it cannot talk back to the DHCP server it gets your real IP from. If it happens again, you might want to talk to your provider to find out *why*. Does this thing have any flashing lights on the front? --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Server Offline.
On July 15, 2005 10:11 am, Stephan Weaver wrote: Hello folks, I have a Stand Alone FreeBSD Firewall / Nat / Dhcp Server. Everything seems to work fine, up until this morning. Users seem to complain they could not get on the network anymore. Further investigation revealed the dhcp server could not be contacted. Further more, only some of the users were online. I am guessing that these clients who were online had an ip address from the dhcp server at a previous time and the lease didnt expire as yet. And users who were not online, the lease expired and attempted to contact the dhcp server and failed. I Would appreciate any help or suggestions. Set the lease expire time to at least 5 days (7 to 10 is better) and the renewal time to between 4 and 12 hours. Then setup a dhcp monitoring process that will alert you if it fails to get an address or renewal. Make sure you have more addresses available than you ever expect to give out. I go with 50% more. I've known some admins that want at least double. Like what to do in the future incase this happens again. Setup 2 dhcp servers on the network. If one fails, the other will hopefully continue to serve addresses. Monitor this one as well. I Would like to find out what had happened. Start reading logs. The last thing that i had done to the server was setup, configure and install 'ntop'; dont know if this would cause a problem. Thank you in advance. Stephan Weaver P.S. Please reply to my Directly at @ [EMAIL PROTECTED] -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ I am currently looking for work. If you need competent system/network administration please feel free to contact me directly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Server Offline.
I Found out the Problem, The /var partation is full. How do i find out where is taking up all the space? Thanks From: Ean Kingston [EMAIL PROTECTED] To: freebsd-questions@freebsd.org CC: [EMAIL PROTECTED] Subject: Re: DHCP Server Offline. Date: Fri, 15 Jul 2005 10:18:09 -0400 On July 15, 2005 10:11 am, Stephan Weaver wrote: Hello folks, I have a Stand Alone FreeBSD Firewall / Nat / Dhcp Server. Everything seems to work fine, up until this morning. Users seem to complain they could not get on the network anymore. Further investigation revealed the dhcp server could not be contacted. Further more, only some of the users were online. I am guessing that these clients who were online had an ip address from the dhcp server at a previous time and the lease didnt expire as yet. And users who were not online, the lease expired and attempted to contact the dhcp server and failed. I Would appreciate any help or suggestions. Set the lease expire time to at least 5 days (7 to 10 is better) and the renewal time to between 4 and 12 hours. Then setup a dhcp monitoring process that will alert you if it fails to get an address or renewal. Make sure you have more addresses available than you ever expect to give out. I go with 50% more. I've known some admins that want at least double. Like what to do in the future incase this happens again. Setup 2 dhcp servers on the network. If one fails, the other will hopefully continue to serve addresses. Monitor this one as well. I Would like to find out what had happened. Start reading logs. The last thing that i had done to the server was setup, configure and install 'ntop'; dont know if this would cause a problem. Thank you in advance. Stephan Weaver P.S. Please reply to my Directly at @ [EMAIL PROTECTED] -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ I am currently looking for work. If you need competent system/network administration please feel free to contact me directly. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Server Offline.
du /var | sort -rn | more This will sort the output with the largest directories at the top. Then you can examine what is in the directories that is taking up the space. David http://freebsd.vangeyn.net/ I Found out the Problem, The /var partation is full. How do i find out where is taking up all the space? Thanks From: Ean Kingston [EMAIL PROTECTED] To: freebsd-questions@freebsd.org CC: [EMAIL PROTECTED] Subject: Re: DHCP Server Offline. Date: Fri, 15 Jul 2005 10:18:09 -0400 On July 15, 2005 10:11 am, Stephan Weaver wrote: Hello folks, I have a Stand Alone FreeBSD Firewall / Nat / Dhcp Server. Everything seems to work fine, up until this morning. Users seem to complain they could not get on the network anymore. Further investigation revealed the dhcp server could not be contacted. Further more, only some of the users were online. I am guessing that these clients who were online had an ip address from the dhcp server at a previous time and the lease didnt expire as yet. And users who were not online, the lease expired and attempted to contact the dhcp server and failed. I Would appreciate any help or suggestions. Set the lease expire time to at least 5 days (7 to 10 is better) and the renewal time to between 4 and 12 hours. Then setup a dhcp monitoring process that will alert you if it fails to get an address or renewal. Make sure you have more addresses available than you ever expect to give out. I go with 50% more. I've known some admins that want at least double. Like what to do in the future incase this happens again. Setup 2 dhcp servers on the network. If one fails, the other will hopefully continue to serve addresses. Monitor this one as well. I Would like to find out what had happened. Start reading logs. The last thing that i had done to the server was setup, configure and install 'ntop'; dont know if this would cause a problem. Thank you in advance. Stephan Weaver P.S. Please reply to my Directly at @ [EMAIL PROTECTED] -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ I am currently looking for work. If you need competent system/network administration please feel free to contact me directly. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ 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: DHCP assigned unregistered IP address
On Fri, Jul 15, 2005 at 11:38:07AM +0100, Alex Zbyslaw wrote: Bob Hall wrote: The modem web page contained this: The SURFboard cable modem can be used as a gateway to the Internet by a maximum of 32 users on a Local Area Network (LAN). When the Cable Modem is disconnected from the Internet, users on the LAN can be dynamically assigned IP Addresses by the Cable On the SB4100, the Enable DHCP checkbox is right above this blurb. Yes, I've seen screen shots with it. The SB5100 has no checkbox. However, note the When the Cable Modem is disconnected from the Internet... so the only reason it should be handing you the local IP is if it cannot talk back to the DHCP server it gets your real IP from. If Yea, that's pretty obvious. It's also pretty undesirable. Apparently, Motorola decided the checkbox was confusing and removed it, replacing it with this automatic behavior. Blea. it happens again, you might want to talk to your provider to find out *why*. Does this thing have any flashing lights on the front? There are LEDs, but they didn't indicate anything was wrong. There have been many reboots over the time I've been with this ISP, and this is the only time this happened. I'm not going to demand an explanation for a fluke. A better question is why the tech I talked to told me that the unregistered IP address wasn't a problem. But she did tell me that she was new, and generally the techs can distinguish between their cloacal anatomy and a geophysical excavation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
