Re: Soekris network problems - 48 hour deadline - SOLVED!!

2006-10-14 Thread Melameth, Daniel D.
Richard P. Koett wrote: > I guess it was a stupid autonegotiation problem after all. I didn't > know that could affect traffic in only 1 direction. Live and learn :) FWIW, if you're not autonegotiating, you should make certain both sides (NIC and switch) are hard coded/not set to negotiate.

Re: Soekris network problems - 48 hour deadline

2006-10-14 Thread Bob DeBolt
On Saturday 14 October 2006 4:10 am, you wrote: Hi Richard I dealt with an ISP on behalf of a client that required a MSS of 1100 during one particular phase of troubleshooting. Funny thing (not) they forgot to notify everyone when said problem was corrected and the client ran with that MSS for

Re: Soekris network problems - 48 hour deadline

2006-10-14 Thread Stuart Henderson
On 2006/10/14 02:42, Richard P. Koett wrote: > >> I won't post a dmesg unless requested because I think this platform > >> is pretty well known. it probably won't make a difference here, but in general, the dmesg doesn't just tell about the platform, it tells about the OS you're using on it too.

Re: Soekris network problems - 48 hour deadline - SOLVED!!

2006-10-14 Thread Richard P. Koett
A huge thank you to all who offered advice on my network problem. It appears that the problem has been fixed by changing hostname.sis0 from "dhcp NONE NONE NONE" to "dhcp media 10baseT". Previous output from ifconfig showed: sis0: flags=8843 mtu 1500 media: Ethernet autoselect (100baseTX fu

Re: Soekris network problems - 48 hour deadline

2006-10-14 Thread Matt Radtke
Good morning > I tried the following variations: > > scrub out on sis0 max-mss 1440 > scrub out max-mss 1440 > scrub max-mss 1440 > scrub max-mss 1400 You should be able to figure out the problem, actually. Good ole tcpdump should show you something. I'd specifically look for icmp that you mig

Re: Soekris network problems - 48 hour deadline

2006-10-14 Thread Richard P. Koett
Stuart Henderson wrote: > On 2006/10/14 00:56, Richard P. Koett wrote: >> known. Hosts on the internal network are able to access the Internet >> but report that access seems slow. Some operations fail consistently. >> For example, users can send and receive e-mail e-mails but can't send >> e-mail

Re: Soekris network problems - 48 hour deadline

2006-10-14 Thread Richard P. Koett
Adriaan wrote: > On 10/14/06, Richard P. Koett <[EMAIL PROTECTED]> wrote: >> I'm having throughput problems using a Soekris net4801 as a firewall >> running OpenBSD 3.9. This is replacing a SonicWALL device that was >> working fine from the user's perspective. (I want to replace it >> because, amon

Re: Soekris network problems - 48 hour deadline

2006-10-14 Thread Richard P. Koett
Matthew Closson wrote: > On Sat, 14 Oct 2006, Richard P. Koett wrote: > >> I'm having throughput problems using a Soekris net4801 as a firewall >> running OpenBSD 3.9. This is replacing a SonicWALL device that was >> working fine from the user's perspective. (I want to replace it >> because, among

Re: Soekris network problems - 48 hour deadline

2006-10-14 Thread Stuart Henderson
On 2006/10/14 00:56, Richard P. Koett wrote: > known. Hosts on the internal network are able to access the Internet > but report that access seems slow. Some operations fail consistently. > For example, users can send and receive e-mail e-mails but can't send > e-mail with attachments larger than a

Re: Soekris network problems - 48 hour deadline

2006-10-14 Thread Adriaan
On 10/14/06, Richard P. Koett <[EMAIL PROTECTED]> wrote: I'm having throughput problems using a Soekris net4801 as a firewall running OpenBSD 3.9. This is replacing a SonicWALL device that was working fine from the user's perspective. (I want to replace it because, among other things, I abhor Son

Re: Soekris network problems - 48 hour deadline

2006-10-14 Thread Matthew Closson
On Sat, 14 Oct 2006, Richard P. Koett wrote: I'm having throughput problems using a Soekris net4801 as a firewall running OpenBSD 3.9. This is replacing a SonicWALL device that was working fine from the user's perspective. (I want to replace it because, among other things, I abhor SonicWALL's li