|
||||||||
New information: I've got pfSense running at my cablemodem for two days now. No problems with that. Here's the log: pfSense: Feb 11 00:19:59 dhclient[2102]: bound to 88.134.155.13 -- renewal in 2700 seconds. Feb 11 00:19:59 dhclient[2102]: DHCPACK from 83.169.185.50 Feb 11 00:19:59 dhclient[2102]: DHCPREQUEST on fxp0 to 83.169.185.50 port 67 Feb 10 23:34:59 dhclient[2102]: bound to 88.134.155.13 -- renewal in 2700 seconds. Feb 10 23:34:59 dhclient[2102]: DHCPACK from 83.169.185.50 Feb 10 23:34:58 dhclient[2102]: DHCPREQUEST on fxp0 to 83.169.185.50 port 67 Feb 10 22:49:58 dhclient[2102]: bound to 88.134.155.13 -- renewal in 2700 seconds. Feb 10 22:49:58 dhclient[2102]: DHCPACK from 83.169.185.50 Feb 10 22:49:58 dhclient[2102]: DHCPREQUEST on fxp0 to 83.169.185.50 port 67 Feb 10 22:04:59 dhclient[2102]: bound to 88.134.155.13 -- renewal in 2700 seconds. Feb 10 22:04:58 dhclient[2102]: DHCPACK from 83.169.185.50 Feb 10 22:04:58 dhclient[2102]: DHCPREQUEST on fxp0 to 83.169.185.50 port 67 Feb 10 21:19:58 dhclient[2102]: bound to 88.134.155.13 -- renewal in 2700 seconds. Feb 10 21:19:58 dhclient[2102]: DHCPACK from 83.169.185.50 Feb 10 21:19:58 dhclient[2102]: DHCPREQUEST on fxp0 to 83.169.185.50 port 67 Compare: m0n0wall: Jan 14 23:05:33 dhclient: bound to 88.134.151.111 -- renewal in 2329 seconds. Jan 14 23:05:32 dhclient: DHCPACK from 83.169.185.50 Jan 14 23:05:32 dhclient: DHCPREQUEST on xl0 to 83.169.185.50 port 67 Jan 14 22:21:16 dhclient: bound to 88.134.151.111 -- renewal in 2656 seconds. Jan 14 22:21:15 dhclient: DHCPACK from 83.169.185.50 Jan 14 22:21:15 dhclient: DHCPREQUEST on xl0 to 83.169.185.50 port 67 Jan 14 22:00:50 dhclient: bound to 88.134.151.111 -- renewal in 1225 seconds. Jan 14 22:00:49 dhclient: DHCPACK from 83.169.185.50 Jan 14 22:00:49 dhclient: DHCPREQUEST on xl0 to 83.169.185.50 port 67 Jan 14 21:23:38 dhclient: bound to 88.134.151.111 -- renewal in 2231 seconds. Jan 14 21:23:36 dhclient: DHCPACK from 83.169.185.50 Jan 14 21:23:35 dhclient: DHCPREQUEST on xl0 to 83.169.185.50 port 67 Jan 14 21:04:41 dhclient: bound to 88.134.151.111 -- renewal in 1134 seconds. Jan 14 21:04:40 dhclient: DHCPACK from 83.169.185.50 Jan 14 21:04:40 dhclient: DHCPREQUEST on xl0 to 83.169.185.50 port 67 As you can see it refreshes its IP over midnight without problems. Something I mentioned is that pfSense refreshes the lease every 2700 seconds (=45 minutes), where m0n0wall does that after amounts of time that might be chosen randomly (see below). The standard says that the DHCP-client should renew its lease after 50% of the lease time. Ideas? Carsten Holbach schrieb: > Ooops, forgot the logfile snapshot: > > Jan 14 23:45:39 dhclient: New Routers (xl0): 88.134.151.254 > Jan 14 23:45:39 dhclient: No working leases in persistent database > - sleeping. > Jan 14 23:45:38 dhclient: New Routers (xl0): 88.134.151.254 > Jan 14 23:45:38 dhclient: New Broadcast Address (xl0): > 255.255.255.255 > Jan 14 23:45:38 dhclient: New Subnet Mask (xl0): 255.255.254.0 > Jan 14 23:45:38 dhclient: New IP Address (xl0): 88.134.151.111 > Jan 14 23:45:38 dhclient: Trying recorded lease 88.134.151.111 > Jan 14 23:45:38 dhclient: No DHCPOFFERS received. > Jan 14 23:45:33 dhclient: DHCPDISCOVER on xl0 to 255.255.255.255 > port 67 interval 5 > Jan 14 23:45:17 dhclient: DHCPDISCOVER on xl0 to 255.255.255.255 > port 67 interval 16 > Jan 14 23:44:58 dhclient: DHCPDISCOVER on xl0 to 255.255.255.255 > port 67 interval 19 > Jan 14 23:44:47 dhclient: DHCPDISCOVER on xl0 to 255.255.255.255 > port 67 interval 11 > Jan 14 23:44:41 dhclient: DHCPDISCOVER on xl0 to 255.255.255.255 > port 67 interval 6 > Jan 14 23:44:37 dhclient: DHCPDISCOVER on xl0 to 255.255.255.255 > port 67 interval 4 > Jan 14 23:44:29 dhclient: DHCPREQUEST on xl0 to 83.169.185.50 port 67 > Jan 14 23:44:22 dhclient: DHCPREQUEST on xl0 to 83.169.185.50 port 67 > Jan 14 23:05:33 dhclient: bound to 88.134.151.111 -- renewal in > 2329 seconds. > Jan 14 23:05:32 dhclient: DHCPACK from 83.169.185.50 > Jan 14 23:05:32 dhclient: DHCPREQUEST on xl0 to 83.169.185.50 port 67 > > > Additional information: > Somebody at a messageboard mentioned to me that he had a similar > problem. When he changed to pfSense it went away. > Yet somebody else mentioned that he had a similar problem because the > NIC on his mainboard had a MAC adress which was used widely on the > Internet. When he changed that MAC, the problem went away. Now I tried > the "MAC spoofing" feature of m0n0wall, my problem persists. > > Greetings > Carsten Holbach > > > Carsten Holbach schrieb: >> Hello >> >> My internet connection runs over Kabel Deutschland, which is a cable >> provider here in Germany (guess the name :-)) >> >> Since some week I have a problem: >> Every night between 11:50pm and 0:10am the m0n0wall will lose it's >> WAN IP adress. It tries to renew it via DHCP, but it won't receive one. >> My first guess was that my provider may have a problem with the >> DHCP-server. But I connected my PC the cable modem directly for some >> days, and the problem went away. Back to m0n0wall (a new box with >> different NICs), and the problem showed up again. >> >> Here's a snapshot of the log files (an older one, before I connected >> my PC to the cablemodem directly): >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch >> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > |