I do as well, as all filenames over a certain length are truncated (this has been default behavior for yum as long as I know on SME Server)
Sure will, but that's something different.
and on top of that is also the case with yum installations that do work as Charlie showed in an earlier post.
Yum works for me and everyone else, doesn't work in this case and another current case.
By no means am I saying yum is the issue, it's not.
Please stop bashing on saying that MTU header dropping would cause those symptoms,
I'm not bashing anyone or thing, and please don't don't make that accusation, it's getting old dude.
Simply understand my posts.
Yea I know that's hard, more patients/effort...
there obviously is something wrong as the user has a problem and it might be MTU settings (for all I know),
Well JFYI the OP has confirmed MTU settings and diagnostics, which appear to be alright Wan Firewall to Wan Firewall.
That still leaves what's behind each firewall doesn't it.
but I find it hard to believe that the truncation of file names would be the symptoms for such a problem.
I don't, it's a packet problem for sure and what kind of things cause packet issues.
Pick anything from the network universe as a possible cause, I won't argue with you, that's for sure.
It can be anything, I know it's not yum.
So where do you start, MTU is a good start, oh well some things look pretty good.
Did it tell us everything about everything, no...but a good start.
What do you suggest?
My next suggestion was to Gateway SME to the modem and verify SME to the world.
If SME works, then we're back to internal network packets.
And what are the chances of that.
Yea I'd say, I agree with you...
But then again it doesn't do much good looking on this (LAN) side of the fence, if the issue is on the other side (www) with SME.
Gateway Mode direct to modem....can eliminate that possibility from the universe.
If it was a bad mdsum/checksum you would get a completely different yum error message.
And how?
If you program it into the socket, but that wasn't done with yum.
Sock's is a low level raw packet transporter, how fancy depends on your programming effort.
Yum doesn't mdsum or checksum.
Raw packet transporter....yum.
Another method is you can put the mdsum into the header, the facility is there already.
Then when it's received the sock pulls it from the header and your program can automatically mdsum.
But nobody does that, you get the mdsum in a second txt file don't you.
The EL Manual mdsum procedure. My thumb is down.
I played with that mdsum in the header, works a treat, however this boy isn't to make the WWW embed the mdsum.
Work around code, d/l file.exe and sum.txt and auto mdsum. Thumb starts to go up.
What yum does do however is what it's doing here in this case.
It is detecting bad packets, and preventing the d/l.
With yum.... it's feed me good packets or forget it.
Ok that's not optimal I agree, but it works for me, I think it works for you, as well as everyone else.
Or would you rather it ate your bad packets and made a file for you anyway.
Yum works a treat at this point.
If it ain't broke don't fix it.
Fact is when was the last time you told someone to mdsum all the files in SME's update?
Never?
Na...we don't want that, do we...!!!
Would be nice if yum told you exactly what the problem was with your packets and thus your network.
However, I do think that's a few versions into the future.
OR Never is more like it.
BTW did you both goto Caio's link and read that fix?
He could have narrowed down "fix your network" somewhat though.
Please also stick to the topic in question as it doesn't help the OP. Thanks
Likewise gents.
May your packets always be good ones.....later.
40 Replies
12572 Views