|
No, a forking of the chain would lead to dilution and confusion and nothing good will come of that.
You never want to hear someone utter "Do you accept my bitcoins? Oh, no, you accept the OTHER bitcoins? Dang..."
|
|
|
|
|
Yeah, it really sounds like you are being filtered, but the fact that you can get all the way up to my ingress router is kind of strange. Can you send me your IP in a PM and I will check with the DC to see if anything is going on locally here.
|
|
|
|
|
I don't currently have any way to redirect you without using one of the IPs. It's kind of strange that it's stopping at the last hop, but I definitely am not blocking any IPs except the one I already mentioned. You are sure your outbound IP is not the one mentioned?
|
|
|
|
|
I don't know... I know some people have managed it, but I have not revisited it since. I just install Natty at present.
|
|
|
|
|
The arp cache on that box might be munged. Do you have the same problem from a different machine?
|
|
|
|
|
Something definitely wonky on your end, that IP is the same box as us1, just a different interface.
You say you were doing that from work? Are they filtering it out perhaps?
|
|
|
|
|
Petflow is the shiznit. No more lugging 50lb bags around!
|
|
|
|
|
Hmm... what happens if you traceroute to 208.110.73.247?
|
|
|
|
|
Sorry, have a problem here at work I am trying to take care of.
BinaryMage is correct, it's stopping just before the server. The next hop is the server itself.
Are you able to get to the website?
The only IP I am dropping from the server at the moment is 178.86.12.182, that's not yours is it?
|
|
|
|
|
Hmm, they respond to pings and are up right now. Can you do a traceroute to any of them?
tracert in windows
|
|
|
|
First, I have to admit that I haven't been following the threads for a while. So I really don't know what's been going on.
I've been using the us.eclipsemc.com server for several months.
Quite recently I could no longer connect. I switched over to the eu server until the us server came back up but shortly thereafter I couldn't connect to it either.
I looked at the eclipse faq and saw that I was supposed to be using us1, us2 or us3. I switched to us2 and was able to connect again.
Last night about 9:15 I lost connection again and still can't ping any of the servers but I don't see any mention of it in the forums.
I wondered if Comcast is blocking me but I don't know why they would or how I would test that.
Anyone have any idea what might be my problem? I mean besides being an idiot.
This is kind of strange. What IP addresses are you getting for us1, us2 and us3? |
|
|
|
Yeah, 40% = average shares.
Is luck the percentile? ( exp (-shares/difficulty)) If so then shares = difficulty (which is the average shares) is 36.8% luck. But 36.8% is not average luck. If you take the different luck values and calculate the average, it should be 50%. Well, 36.8% explains a lot. I was wondering why we were always hovering just below 40% . I could have sworn you posted 40% awhile back... I'll have to dig through the previous threads. Yes, I'm using (exp(-shares/diff)). I fixed the calculations and colors now. |
|
|
|
Thanks... faq updated  I guess I didn't kill enough people tonight. It was kind of a crappy night.  Yeah, 40% = average shares. |
|
|
|
|
So what's the proper command line for Diablominer to connect? I will add it to the FAQ.
Since this block is taking so long, I'm going to fire up BF3 if anyone wants to join me. Hopefully we can scare the block into submission.
|
|
|
|
|
As far as I know, you can. I've never used Diablominer, but I'm pretty sure at least a few people are.
|
|
|
|
|
I have two of these for sale as well... similar specs. One is loaded with 146 GB and one is loaded with 73 GB drives. I can't recall RAM, somewhere in the 4 GB range I think. I will ship if you pay shipping.
|
|
|
|
|
Yeah, already done. Seems to be working out just fine so far.
|
|
|
|
|
Seems there was an attack on the network. The data center mitigated it at the ingress point... I'm waiting on more details now, I guess they are/were scrambling to filter the packets. Thing should be back to normal for now.
|
|
|
|
|
Yeah, it seems there's an upstream router down near 69.30.209.1 ... seems to be going in and out. I think maybe a card on a router is going bad. I submitted a support ticket, but I'm not sure it's part of my datacenters maintenance domain.
|
|
|
|
|
Show Posts
