Now leasing a dedicated server from a company, you would think they wouldn't mind telling you your connectivity information, or you might even think that it is your right to know... but get this, I asked webreseller.net about the connectivity of two of my servers with them and they refused to tell me. Here is what they had to say...

We cannot disclose this information. Our BW provider is yipes. www.yipes.com

Would anybody have any idea why this information would be so secretive? What are your opinions, would you do business with them if they wouldn't provide this information? Anybody else have similiar problems with webreseller.net?

I've heard of other issues involving them, but you'll have to do a search to find out more as I don't remember off-hand.

-- Jonathan

I'm not sure what the question was exactly, but you did find out who the bandwidth provider is. Some companies don't like to discuss the size of their pipes for 1 of two reasons, either they don't have enough or they just don't want you to figure out how big they are. Normally its because they don't want you to know how big they are. I say if you're not having a problem, don't worry too much about it. If you are, that's a whole different story...

Well the thing is, I have potential clients calling me wanting to know, and I don't know what to tell them... I don't want to lie to them.

I'm pretty sure webreseller has a Gig-E Line from Yipes.

I'm unfamiliar with the term Gig-E, could you explain?

Gigabyte Ethernet - 1000 MBPS (I think)

Well if that is their overall backbone, then I just have to find out what my connectivity is connected to my servers...

Probably 10MBPS either limited by the router or the port on your server.

Alright, sounds good... how about redundancy, do you think Yipes is their only provider?

It should be fine. Seeing as Yipes is made up of two providers, Level 3 and Genuity. Although when I was on a server that used WebReseller their network was overtaken by DOS attacks quite a bit. It looks like they have fixed that problem though.

Thanks so much inogenius...

Originally posted by webwired
Well if that is their overall backbone, then I just have to find out what my connectivity is connected to my servers...

Connect to your server with SSH or telnet, get to a shell prompt, and type:

ipconfig -a

You should get a result resembling this:

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 209.50.225.14 netmask 0xffffff00 broadcast 209.50.225.255
ether 00:90:27:73:7e:bc
media: Ethernet 100baseTX <full-duplex>
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000

The line that says media: Ethernet 100baseTX <full-duplex> means the server I'm on now has a 100 Mbps ethernet card running full-duplex. Full duplex means it can do 100Mbps ingress and 100Mbps egress simultaneously (theoretically). Half-duplex would mean you can do 100Mbps total inbound+outbound at any given time (such as 70/30, etc).

Hope that helps.

Ah, so they don't cap ya at 10MBPS like a few companies do.

Originally posted by BobFarmer
Connect to your server with SSH or telnet, get to a shell prompt, and type:

ipconfig -a

You should get a result resembling this:

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 209.50.225.14 netmask 0xffffff00 broadcast 209.50.225.255
ether 00:90:27:73:7e:bc
media: Ethernet 100baseTX <full-duplex>
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000

The line that says media: Ethernet 100baseTX <full-duplex> means the server I'm on now has a 100 Mbps ethernet card running full-duplex. Full duplex means it can do 100Mbps ingress and 100Mbps egress simultaneously (theoretically). Half-duplex would mean you can do 100Mbps total inbound+outbound at any given time (such as 70/30, etc).

Hope that helps.

I doubt his server is bsd :)

Well, technically, I don't cap me, but neither does the company I work for (ServInt customers go on 100Mbps segments, and have been known to hit 90Mbps in the past). Yeah, they're probably not on FreeBSD, but regardless the output of ifconfig is similar enough to find what they need. :)

Connect to your server with SSH or telnet, get to a shell prompt, and type:

ipconfig -a

I get a "command not found"

Webreseller just called me and gave me all the info, apparently that used to be their policy and one of the techs thought it still was and answered without thinking... Oh, well, all is good. Oh, btw, he said that the server is connected at 100 mbps.

yeah, I typoed. It should be ifconfig with an F, not ipconfig with a P. ipconfig is some lame windows command I think. :)

Good news on being 100 Mbps, btw.

That was pretty cool of them to call though, my other dedicated server provider wouldn't do that in a million years, I won't mention their name ... *cough* see eye host *cough*

Oh, and to clear that up, I'm not on freeBSD... Linux Redhat 7.2 w/ensim 3.1.6