---------- Original Message ---------------------------------- From: "RobertH" roberth@abbacomm.net Reply-To: CentOS mailing list centos@centos.org Date: Tue, 9 Sep 2008 12:32:33 -0700
I got my information about the MTU setting from doing google searches and the message boards on broadband reports as well as doing the tweak test on broad band reports.
It appears you are on Comtrash where everything is CoMtRaSHtIc.
Good for you. Dance a jig.
Stop beating the MTU horse to death and get busy finding out how to best connect to the CPE devices.
Google that stuff.
First, when testing, disable (admin down) the internal network on the second nic
Also, check to see what specific nics you have an if any recent issues with kernels and such and any updates.
Google that too.
Then Focus on the internet transit/transport infrastructure.
Find out best way to interface with the cable modem CPE infrastructure.
Meaning what speed and duplex.
Trial and error.
You will get there...
Some nics need to be played with and dealt with in terms of kernel and other things like disable ipv6 in modprobe.conf and dhcp...
You might be better off having an intermediate device between you and the cable modem if your nics don't wanna play nice with the cable modem.
Last but not least, you can always check stats and see if collisions and errors on interfaces and more.
Enjoy
- rh
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
1. Comcrap is not available in my area I am on road runner biz through bright house with 15m down and 2 up and static ip.
2. Already tested without the internal nic running
3. Tried with a router in between and the result is the same.
4. I do agree about the negotiation aspect, which I'm looking into as well.
5. Don't notice any collisions or errors on ifconfig.
________________________________________________________________ Sent via the WebMail system at mail.dsli.com
- Comcrap is not available in my area I am on road runner biz through
bright house with 15m down and 2 up and static ip.
Already tested without the internal nic running
Tried with a router in between and the result is the same.
I do agree about the negotiation aspect, which I'm looking into as
well.
- Don't notice any collisions or errors on ifconfig.
I see, when I trace the domain you are sending email from I assumed it was you on a comcast link.
Or maybe roadrunner resells comcast in your area or comcast bought roadrunner in your area?
The dlsi.com dig pointing at 0.0.0.0 was interesting.
Never ever seen dns point to 0.0.0.0
Shouldn't there be a error catch in dns server software for that situation?
It's like using dns to route? Har har he.
Or did you buy the internet?
;-)
Man, if so, I wanna be your best bud cause I need a piece of the action to sell at a good deal
;->
- rh
I see, when I trace the domain you are sending email from I assumed it was you on a comcast link.
Or maybe roadrunner resells comcast in your area or comcast bought roadrunner in your area?
The dlsi.com dig pointing at 0.0.0.0 was interesting.
Never ever seen dns point to 0.0.0.0
It just means they have tried to break their A or never had one pointing to their domain root. Their MX has valid records, so the mail will still flow.
Comcast is just shown as the netblock owner, they could have re-sold a subnet, or acquired the block from the original owner.
My netblock is now owned by Verizon, but the ARIN records still have many references to UUNet, also long gone.
Shouldn't there be a error catch in dns server software for that situation?
It's like using dns to route? Har har he.
Or did you buy the internet?
;-)
Man, if so, I wanna be your best bud cause I need a piece of the action to sell at a good deal
;->
- rh
-
David Petruzzella -
RobertH -
Scott Silva