Suggest you connect SME and only SME to your modem and test yum.
That will tell you if sme and www will work, if it does work, then the problem is your network setup.
I see you've had other issues, my guess, since I don't have info and not sitting at your network, you have a network issue.
Yum is finicky about the network working 100%.
Yum is deliberately programmed to test the packet stream to ensure it's ok, so it doesn't d/l corrupt files and save them.
Makes no sense updating with corrupted d/l files.
From the info you have given so far, your network is not setup properly.
Connect SME in gateway mode so you can admin from the internal interface and connect directly to the modem.
Once you report the results, then it's possible someone will look into a yum issue, if it still doesn't work.
Chances are it will.
As of now your lan has not been verified to be setup properly.
Need to isolate SME connected to the modem only.
Your mtu tested good source to destination firewall to firewall.
We know the yum servers are ok and it looks like the wan to you is ok.
That leaves your internal network and that has yet to be confirmed ok.
You have a packet framing issue, that is what yum is telling you, well maybe not you, certainly me.
Something on your network is the likely cause.
I use fedora with yum updates, my box is behind fortigate running 4.0, with no issues.
Well there ya go, at least fedora is setup properly.
That doesn't mean SME is.
Everyone on the internet that has the
exact same error report as you, also has a network setup issue.
Takes 10-15 min to test SME direct to the modem, a lot less time then you've spent searching the internet.
So get er done, then we'll go from there....
We're not going to fix yum for each person who has a foobar network.
Fix your network.
There are a lot of folks that use SME and yum works for them.
Kinda says it all in a nut shell.
Beside all that, nobody is going to waste their time fixing yum if it ain't broke and
they won't try unless sme is connected directly to the modem, which rules out your network setup
as the issue during the possible bug diagnosis.
If sme still still doesn't work directly connected, make sure you have a clean install and nothing else
connected to the modem.
Leave sme connected to the modem in gateway mode so you have access
from the gateway interface.
You can connect Fedora or a Win client to SME's gateway interface.
Then file a bug in the bug tracker.
Have you read
here?
Goto that thread, top right click Notify, then you'll get notification of new posts in that thread also.
Interesting new findings there, last posts, read them.
You can have packet framing issues on a network you think is perfectly set up.
Most everything will work, yum and VPN will not.
echo -e "TRACE / HTTP/1.1\nHost: mirrors.kernel.org\n\n" | nc mirrors.kernel.org 80
That line does nothing more the opens a connection to the designated server, much the same method that yum uses.
We already know you can hit the servers with yum, so that line should work ok for you.
If you made a connection with it, then the ability to connect to the servers is ok.
However it doesn't tell you that you don't have a network packet framing issue, that test simply can't.
HTH
21 Replies
3065 Views