Hey, yes usually you should set 10/100/g to see when the link state changes, also if the auto protocol is not working or if the cable goes bad is easier to troubleshoot, have seen this on co-los worldwide. in any case, setting 10/100 etc shouldnt affect the bandwidth. so the question here is: which Nic you are using? is it supported? do you see any network issue/crc issue, alert/errors, or something onthe logs? via the web interface check if there are any error on the interface counters. also: check with ifconfig 'interface name' for crc errors, and the advertised speeds, paste here the full output of the problematic interface.
let us know how it goes. 2016-01-11 3:23 GMT-03:00 Muhammad Yousuf Khan <sir...@gmail.com>: > I am remotely supporting one of my client who is using pfsense. i have > been using pfsense for years and never face such issue in this > experience, the Client Co-location is recommending to use 100BaseTX full > duplex setting instead of Auto. i do not know why they required that since > i am not in US i never observe this settings recommended by colo people in > my country. > > > > ------------------Server 1 > > / > colo switch-------->[WAN]pfsense[LAN]--------------+ > > \ > > -----------------Server 2 > > - iperf speed test for LAN, between is 50Mbps up and down > - but iperf test on WAN showing 10Mbps down and 5Mbps up. > - however my client is saying that assigned speed from colo is 100Mbps. > > now i can not find where is the issue. i suspect that issue is with > 100BaseTX setting. > > can anyone please guide me where i am doing wrong and what i can do to fix > this. > any help will be highly appreciated. > > Thanks, > Yousuf > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
