On 12/14/2010 3:07 PM, Arno J. Klaassen wrote:
Quite sure many 8-XXX worlds worked great on this box including reboots,
I will find the date window when things went wrong.
Merci, Arno
I am curious as to the status of the hanging reboot. I too have some
systems that has had a working reboot on
Sorry for the cross-post, but this could be either lists problem.
I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is
running ISC DHCPD 3.0.x from recent ports, and the other dhclient from
make world.
The server is refusing to answer the DISCOVER request, as it thinks the
I
Can someone please confirm or rule out my issue with dhclient sending
bad IP checksum packets. It would really suck if 7.1 was released with a
broken DHCP client.
Jonathan Feally wrote:
Sorry for the cross-post, but this could be either lists problem.
I have 2 boxes running 7-STABLE as of
ny problems lately, but none involved checksum nor the dhcpd
(btw, I assume that you are seeing bad checksum on the receiving server)
could you add a nic to your PE1750?
danny
Jonathan Feally wrote:
Sorry for the cross-post, but this could be either lists problem.
I have 2 boxes runn
Jonathan Feally wrote:
I will try another em card in that server to confirm/rule out the nic
driver. I am seeing the same checksum number on both the source
machine, the dhcp server machine, and a 3rd windows xp machine
sniffing the traffic with etherreal/wireshark. The windows xp box is
OK, so I installed a different PE1750 with BETA2 and then updated the
source via cvsup RELENG_7 from cvsup3 and all is ok now on that box.
Went back the first box and cvsup'ed the src again into an empty
directory and it compiled and worked fine. Looks like my updating of the
source along the w
Ok, I managed to cause it again.
dhclient was the problem.
My source tree was fine. Turns out that it is my make.conf CFLAGS=-O3
setting.
When compiled with -O3 it will generate packets with bad checksums.
Simply recompiling it with -O2 did not cause this issue and dhclient
works fine.
So th
Attila Nagy wrote:
Bingo, this solved the problem. The current uptime nears four days.
Previously I couldn't go further than a day.
The machine gets very light TCP load (and other machines which get work
well), so I guess it's UDP RX or TX checksum related
I also have had my network g
Sorry to cross post, but the net list didn't help a couple weeks back on
this.
names, natd, and dhcpd have all been getting stuck in zoneli (zone
limit) since I upgraded to the box to stable about a month ago. It was
running a 6.1-STABLE before with out difficulty. Very little has changed
on
1:04 -0800, Jonathan Feally <[EMAIL PROTECTED]> wrote:
Sorry to cross post, but the net list didn't help a couple weeks back on
this.
names, natd, and dhcpd have all been getting stuck in zoneli (zone
limit) since I upgraded to the box to stable about a month ago. It was
running a 6.1-S
10 matches
Mail list logo
