Lan0 & wan0 speed

[Anil Kumar H]

Hi,

is it necessary to have both Wan0 & LAN0 to be of same speed  ?

[ahenning]

It is not a requirement, e.g. it is possible to have 1 Gbps lan and 100 Mbps wan.

[Anil Kumar H]

Today I connected A.Core-B.Core but after some download network failed at B end. I did port swap but still fails after sometime.. don't know what is wrong

PC---coreswitch---WanCore----100Mbps P2P link---WanCore---coreswitch---PC

Both ends with latest 1.2.2

[ahenning]

...after some download network failed at B end

To help, some basic info is needed e.g:
What exactly happened here?
Did icmp pings drop completely?
Was the web interface up?
What did the logs say?
How did you fix it?
Is this running as a VM/ which hypervisor? (since you mentioned in another thread that you can't get the HDD image to work)
What are the hardware specs?
How much disk space is available?
Are any extra sites configured in MultiSite?
How are the tests done (tools/protocols/files)?

[RamIndia]

Hi anil

As admin said, you need to give more info to people to help
since we do not have your visibility of network.

can you produce more ping or port status from switch when you lost the connection.

Ram

[Anil Kumar H]

What exactly happened here?


this was the setup, no routers at both end, isp was directly terminated on Wan0

PC---coreswitch---WanCore ( A )----100Mbps P2P link---WanCore ( B )---coreswitch---PC


Did icmp pings drop completely?

without data transfer yes network is up, when I started data transfer after some MB downloads, CPU utilzation went High on B End & network went down. in graph I see only 35% utilized, but when we saw physically on web interface during the issue it was to the peak.

Was the web interface up?

Machine was up, but not webinterface, nor no network. we had to hard reboot to make machine up.

What did the logs say?

A End:

hu Jul 10 16:34:15 UTC 2014  : Routine : Initializing Startup Scripts
Thu Jul 10 16:34:15 UTC 2014  : Routine : Check Configs
Thu Jul 10 16:34:15 UTC 2014  : Routine : Updating Configuration
Thu Jul 10 16:34:15 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned
DropBroadcasts: dropped a packet
Queue@58 :: Queue: overflow
Peer detected on lan0:   52
Peer detected on lan0:   56
Peer detected on lan0:   52
Peer detected on lan0:   56
Peer detected on lan0:   52
Peer detected on lan0:   56

B End:

Wed Jul 16 20:08:54 UTC 2014  : Routine : Initializing Startup Scripts
Wed Jul 16 20:08:54 UTC 2014  : Routine : Set Interface Roles
Wed Jul 16 20:08:54 UTC 2014  : Routine : Setting Optional Interface driver flags if supported
Cannot set device rx csum settings: Operation not supported
Cannot set device tx csum settings: Operation not supported
Cannot set device scatter-gather settings: Operation not supported
Cannot set device tcp segmentation offload settings: Operation not supported
Wed Jul 16 20:08:55 UTC 2014  : Routine : Check Configs
Wed Jul 16 20:08:55 UTC 2014  : Routine : Updating Configuration
Wed Jul 16 20:08:55 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned
Queue@57 :: Queue: overflow
Peer detected on lan0:   64
Peer detected on lan0:   64
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56


How did you fix it?

We had to hard reboot B end machine.

Is this running as a VM/ which hypervisor? (since you mentioned in another thread that you can't get the HDD image to work)

Its Physical machine

What are the hardware specs?

A End:
Core i5
8GB RAM
500GB SATA HDD 7200RPM

B End:

Core i3
4GB RAM
320GB HDD 5400RPM



How much disk space is available?

100% free other than wanos folders, files & OS

Are any extra sites configured in MultiSite?
no

How are the tests done (tools/protocols/files)?
Started with FTP to test

Utilization during testing:

A End:

CPU:5%
Memory: 240MB
Disk I/O: 35%
Disk Usage: 35MB

B End:

CPU: 35%
Memory: 160MB
Disk I/O: 80%
Disk Usage:34MB


Later: at B End we configured similar conf machine which is of A end, but still it fails in Core--Core, Core--Edge, Edge--Edge.

[ahenning]

For starters, lets fix the lan0 and wan0 cabling. The 'Peer detected on lan0' on both ends means both are reversed.

[Anil Kumar H]

hi,

you mean to say, Change the Switch Interface Port Roles ? or physical cabling ?

[Anil Kumar H]

Hi,

On A end, I did reverse cabling. B also did same

A End results
Thu Jul 17 14:57:27 UTC 2014  : Lan0-Wan0 Interface Port Roles Switched. Restarting Wanos Service
Thu Jul 17 14:57:28 UTC 2014  : Routine : Initializing Startup Scripts
Thu Jul 17 14:57:28 UTC 2014  : Routine : Set Interface Roles
Thu Jul 17 14:57:28 UTC 2014  : Routine : Setting Optional Interface driver flags if supported
Thu Jul 17 14:57:28 UTC 2014  : Routine : Check Configs
Thu Jul 17 14:57:28 UTC 2014  : Routine : Updating Configuration
Thu Jul 17 14:57:28 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned

B End,

Did cable interchange, port swap & still I  see below error, network breaks.

Thu Jul 17 15:02:53 UTC 2014  : Routine : Initializing Startup Scripts
Thu Jul 17 15:02:53 UTC 2014  : Routine : Set Interface Roles
Thu Jul 17 15:02:53 UTC 2014  : Routine : Setting Optional Interface driver flags if supported
Cannot set device rx csum settings: Operation not supported
Cannot set device tx csum settings: Operation not supported
Cannot set device scatter-gather settings: Operation not supported
Cannot set device tcp segmentation offload settings: Operation not supported
Thu Jul 17 15:02:54 UTC 2014  : Routine : Check Configs
Thu Jul 17 15:02:54 UTC 2014  : Routine : Updating Configuration
Thu Jul 17 15:02:54 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned
Queue@57 :: Queue: overflow
Peer detected on lan0:   56
Peer detected on lan0:   64
Peer detected on lan0:   52
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56
Peer detected on lan0:   56

[ahenning]

B is still detecting the peer on lan0, which it should not. There is some reason for this. Are lan0/wan0 perhaps connected to the same switch or vlan?

[Anil Kumar H]

one more thing observed.

earlier I was downloading from B to A, this use to make B network go fail, im doing viceversa now, still B is up for time being. Need to figure out with your query on switch or vlan

vlan: 10.9.232.0/29

A--10.9.231.1 & 2  ( Vlan number 42 )
B--10.9.232.3 & 4 ( Vlan number 10 )

[ahenning]

I suspect that it is possible that both lan0 and wan0 might be in the same vlan and hence the 'peer detected on lan0'. The wanos bridge needs to separate the wan side from the lan side, either physically between the router and lan switch or using two different vlans for the wan and lan network.

[Anil Kumar H]

Hi,

In my case I don't have router here..even without wanos my P2P link setup is like this

A-Core---ISP--B-Core

at present I see this connection

A--Core ( 10.9.232.1 )--L2--WANOS ( 10.9.232.2 )---ISP---WANOS( 10.9.232.4 )--Core B( 10.9.232.3 ) ( B end L2 switch is missing, will connect to L2 & check, if this is not working, then will connect router )

Thanks for patience..

[ahenning]

Ok, a layer-2 setup is fine, there is no need for a router, but the wanos bridge needs to separate the ISP side from the lan side, either physically with the cabling or with separate inside/outside vlans.

[Anil Kumar H]

I did layer 2 setup,  but speed decreased drastically from 10Mbps to 500kbps

A End:

Thu Jul 17 19:41:46 UTC 2014  : Info : Cleared Statistics and Logs
Thu Jul 17 19:41:54 UTC 2014  : Info : Clearing the datastore
Thu Jul 17 19:41:54 UTC 2014  : Info : Reboot Requested
Thu Jul 17 19:42:18 UTC 2014  : Routine : Initializing Startup Scripts
Thu Jul 17 19:42:18 UTC 2014  : Routine : Set Interface Roles
Thu Jul 17 19:42:18 UTC 2014  : Routine : Setting Optional Interface driver flags if supported
Thu Jul 17 19:42:19 UTC 2014  : Routine : Check Configs
Thu Jul 17 19:42:19 UTC 2014  : Routine : Updating Configuration
Thu Jul 17 19:42:19 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned
ToDevice(wan0): Message too long
ToDevice(wan0): Message too long
B End:

Thu Jul 17 19:42:28 UTC 2014  : Routine : Initializing Startup Scripts
Thu Jul 17 19:42:28 UTC 2014  : Routine : Set Interface Roles
Thu Jul 17 19:42:28 UTC 2014  : Routine : Setting Optional Interface driver flags if supported
Cannot set device rx csum settings: Operation not supported
Cannot set device tx csum settings: Operation not supported
Cannot set device scatter-gather settings: Operation not supported
Cannot set device tcp segmentation offload settings: Operation not supported
Thu Jul 17 19:42:29 UTC 2014  : Routine : Check Configs
Thu Jul 17 19:42:29 UTC 2014  : Routine : Updating Configuration
Thu Jul 17 19:42:29 UTC 2014  : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
  warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
  warning: wan0: no IPv4 address assigned

any suggestions before I test with router, B End is not having stock of router, need to check how & what to do.