"Ignore LAN traffic" conflict with bridge

Started by lmpzkt

"Ignore LAN traffic" conflict with bridge   03 September 2015, 18:05

Hi...

I have very slow wireless network file transfer, my SPBM configure as follows:
ADSL modem> Cable 5e> SPBM bridge between external and internal NIC> Cable 5e> AP> Client devices

When I try to ignore LAN traffic, it gives me an error and some clients lose the connection. How I make my wireless network file transfer faster?

Thanks
SoftPerfect Support forum - Andrew avatar image

Re: "Ignore LAN traffic" conflict with bridge   03 September 2015, 19:14

File transfer from where to where? What error does it display? What version of BM are you using?

Re: Ignore lan traffic conflict with bridge   03 September 2015, 22:37

Transfer from client>client or local host<>client

Using TP-Link 150M Wireless N Access Point but my Lan speed maximum 400 Kb/s

Attached error and version.
Attachments:
open | download – error.jpg (49 KB)
open | download – license.jpg (98.5 KB)
SoftPerfect Support forum - Andrew avatar image

Re: Ignore lan traffic conflict with bridge   03 September 2015, 23:53

Client-to-client transfers should not be affected as their traffic never reaches BM, however BM-Client may be slower if their speed is shaped by your rules.

Try adding the following rule in the beginning of the ruleset:
Rate: Unlimited
Protocol: IPv4 based
Source: x.x.x.x-y.y.y.y
Destination: x.x.x.x-y.y.y.y
Interface: LAN NIC
Where x.x.x.x-y.y.y.y is your LAN IP address range. This should handle local traffic before any other rules and improve the transfer speed.

Sometimes you can get the answer faster if you try the forum search and/or have a look at the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • If possible, check your spelling and grammar.

Author:

Email:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

  *******   **    **        **  **    **  **      ** 
 **     **  **   **         **  **   **   **  **  ** 
 **         **  **          **  **  **    **  **  ** 
 ********   *****           **  *****     **  **  ** 
 **     **  **  **    **    **  **  **    **  **  ** 
 **     **  **   **   **    **  **   **   **  **  ** 
  *******   **    **   ******   **    **   ***  ***  

Message: