Ticket #1333 (new)

Opened 3 years ago

Last modified 19 months ago

Routing issues

Reported by: RokX Owned by: RokX
Priority: normal Milestone: Naslednji mejnik
Component: projekt/slovenija Keywords:
Cc: RokX Realization state: maintenance
Related nodes: hrvatini-48a, hrvatini-48a-bb Effort: normal
Blocking: Privacy sensitive: no
Blocked by: Security sensitive: no

Description

Hi,

Based on the conversation regarding "Bridge LAN ports with wireless on nodewatcher" I figured out my issue could be connected with the subject.

The node hrvatini-48a, has a LAN port connected to the backbone node hrvatini-48a-bb and another LAN port is connected to a stationary client computer.

Could this be the reason the connection is frequently interrupted?

As I understand from the conversation LAN port should be user only for node connections or only for client connections. Is this right?

I could test this with a usb wifi dongle for the stationary computer.

Any comment is highly appreciated.

ps: I hope I am posing in the right trac.

Change History

comment:1 Changed 3 years ago by kostko

The node hrvatini-48a, has a LAN port connected to the backbone node hrvatini-48a-bb and another LAN port is connected to a stationary client computer.

So in dev:#1306 we were discussing how to handle this in version 3 by default when migrating from version 2. The best way would be to have either but not both, so for now, all imported nodes in v3 will be configured with LAN for clients but not routing. The node maintainer can of course change this after import.

Could this be the reason the connection is frequently interrupted?

No, this shouldn't be the reason.

Can you say more about what "interrupted" means? What does the routing table look like when this interruption happens (ip ro sh table 20)?

comment:2 Changed 3 years ago by RokX

But how is this done in V2? Are there any defaults?

I now checked the problem deeply at the connected nodes and the last node srebniceva-6-bb (and the only exit one) also has some interruption in its graphs. This must be the root cause.

Interrupted means, the device is always connected to the node and sometimes opening the web pages is fast and responsive, other times "Page not found" occurs. Something in the connection chain is stopping or lossing the requests.

comment:3 Changed 19 months ago by mitar

What is the status of this?

Note: See TracTickets for help on using tickets.