Skip to content

parodus client connection to talaria with http 400 error? #138

Description

@VicLin66

Hi,
I am testing and review CPE's parodus client coonnection with talaria, and packet capture showed http 400 error. Just wonerring if it is one of the problem with tr1d1um issue xmidt-org/tr1d1um#498

Here is the talaria log when CPE's parodus client "say hello" to talaria, seems fine.

{"key":"debug","ts":"2024-04-09T10:56:58+08:00","message":"accepted connection","serverName":"talaria","bindAddress":":6400","listenNetwork":"tcp","listenAddress":"[::]:6400","remoteAddress":"192.168.1.1:56888"}

But packet capture showed 400 error, does it matter?
image

Where 192.168.1.1 is my CPE's IP, and 192.168.1.132 is WebPA server IP (talaria+scytale+tr1d1um).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions