IP routing/ETS problem

[domoticom]

Hi,

I'm lost. I have a Homeserver v2.4 running @ customer. Communication with KNX via IP-router. See att. for settings.
The visu works fine (can control, can see status from bus)

When I connect with ETS to iETS on HS, then I can read/write from bus (group addresses). The bus monitor works fine.
But I can't read/program any device on the bus.
Not even read info from a device in ETS.

I can't see the problem. ANyone got a clue/hint for me ?

edit: as can be seen in the attachement, the physical address in iETS settings is 1.2.65. This is actually the physical address of the IP-router. I'm not sure if that's correct !?

Thanx.

[swenga]

Hello Mike,

there might be a problem with your adress structure. Could you post your TP line adress(es), if there are line couplers in there, where the IP-Router is situated and which adress it has?

Best regards

[grudziu]

Hi,
could you show us bus transmision? (group monitor - save as - trx file open it using notepad).
Isn't your source address 0.0.0?

[domoticom]

hi, thnx for the reply.
I've attached the topology.

The IP-router has 1.2.65. The HS is connected to this interface.

There are two line couplesrs (1.1.0 & 1.2.0)
But even comunication with devices on line 2 (no line coupler in between ip-router and device) isn't working.

As mentioned communication HS with bus is ok (read & write), but programming is not.

Thanx for the help!

[swenga]

Hello Mike,

if your 2 lines are 1.1.0 and 1.2.0 i suppose you have 2 line couplers, connected via one main line, correct? then you should place the IP-router on the main line and give him 1.0.1. You have to understand that with the Routing Part the IP segment is a total new line/area! Thats why the HS should NOT get the same adress as the Router but an adress from an offside area. I would recommend 2.1.1. Adresses of IP-Router and HS must not be the same with IP/Routing!

In your case the answer packets to the HS 1.2.65 were sent adressed to the router, however the Router treats this packets as not adressed to the IP-area and therfore didn't forward these packets back to the HS.

Best regards,

[domoticom]

ok to start I will move the IP-router to the main line.

But can somebody explain why GA communications can work, but Physical communication (like programming) not ?

[swenga]

Line couplers and router will forward GAs according to the Filter tables and forwarding rules. Packets adressed to devices however will only be forwarded according to their destination. Otherwise they would storm the network!

E.G.: In one Line 1.1.0 is a Device 1.1.5. This one sends a packet to device (not GA!) 1.1.10. This packet will be received by the line coupler 1.1.0, however it wont be picked up and forwarded, because it is destined for the local line. Now 1.1.5 sends a packet to 1.2.21. This one will be forwarded by the line coupler to the main line, because the destination adress is outside the local line.

The same applies to the IP-Portion, where the IP-Segment ca be seen as "independent" line(s).

So the main difference is, if packets are transmitted on GA (normal Activity on the Bus) or if they are sent to Devices (for Programming). If your line couplers and the Router are programmed to transparent mode, they will not filter GA's, thats why this is working although the adress scheme is incorrect.

Best regards,

[domoticom]

Ok, thnx for the clear explanation. I'm trying to understand.
So shouln't I be able to program a device on the same line as the IP-router is ? (no line couplers inbetween) ?

[swenga]

So shouln't I be able to program a device on the same line as the IP-router is ? (no line couplers inbetween) ?

IMHO no, because the IP-Router IS a line coupler, it couples the TP line with the IP line(s)!