开云体育

Nice!? I've added?

?x25 subscribe packetsize permit 128 4096
?x25 subscribe windowsize permit 2 15

to my configuration now and can establish in- and outbound connections.

Here is my complete configuration for reference:

version 12.3
service pad to-xot
service pad from-xot
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption

hostname netzhansa-router

boot-start-marker
boot-end-marker

enable secret 5 $1$cmGX$ZJnIqCPqDPIVgaM0VTJzS.

no aaa new-model
ip subnet-zero
no ip routing

no ip cef
ip name-server 192.168.178.2

x25 profile TELEBAHN dxe
?x25 version 1988
?x25 modulo 128
?x25 address 230001
?x25 win 15
?x25 wout 15
?x25 ips 1024
?x25 ops 1024
?x25 subscribe packetsize permit 128 4096
?x25 subscribe windowsize permit 2 15
x25 routing

xot access-group 10 profile TELEBAHN

interface FastEthernet0/0
?ip address 192.168.178.9 255.255.255.0
?no ip route-cache
?duplex half

ip default-gateway 192.168.178.3
ip classless
ip default-network 192.168.178.0
ip route 0.0.0.0 0.0.0.0 192.168.178.2
ip http server

access-list 10 permit any

x25 route 14704100 xot 193.219.181.219
x25 route ^603 xot 193.219.181.219
x25 route ^(...)(...).. xot dns \2.\
x25 host netzhansa-router 23000100

line con 0
?stopbits 1
line aux 0
?stopbits 1
line vty 0 4
?password cisco
?login

end

Am Mo., 10. Apr. 2023 um 11:33?Uhr schrieb Mantas Mikul?nas <grawity@...>:

On Mon, Apr 10, 2023 at 12:00?PM Hans Hübner <hans.huebner@...> wrote:

Hi Mantas,

this is a bit puzzling:? If I make an outbound connection to?14704100 (on?193.219.181.219), the connection is established with the default parameters:

*Apr 10 10:54:10.993: [193.219.181.219,1998/,64238]: XOT O P2 Call (22) 8 lci 1024
*Apr 10 10:54:10.993: ? From (6): 230001 To (8): 14704100
*Apr 10 10:54:10.997: ? Facilities: (6)
*Apr 10 10:54:10.997: ? ? Packet sizes: 128 128
*Apr 10 10:54:10.997: ? ? Window sizes: 2 2
*Apr 10 10:54:10.997: ? Call User Data (4): 0x01000000 (pad)
*Apr 10 10:54:11.077: [193.219.181.219,1998/,64238]: XOT I P2 Call Confirm (11) 8 lci 1024
*Apr 10 10:54:11.077: ? From (0): ?To (0):
*Apr 10 10:54:11.077: ? Facilities: (6)
*Apr 10 10:54:11.077: ? ? Packet sizes: 128 128
*Apr 10 10:54:11.077: ? ? Window sizes: 2 2

If I add the TELEBAHN profile to xot, however, the connection is refused:

*Apr 10 10:52:20.957: [193.219.181.219,1998/,35675]: XOT O P2 Call (22) 128 lci 1024
*Apr 10 10:52:20.957: ? From (6): 230001 To (8): 14704100
*Apr 10 10:52:20.957: ? Facilities: (6)
*Apr 10 10:52:20.957: ? ? Packet sizes: 1024 1024
*Apr 10 10:52:20.957: ? ? Window sizes: 15 15
*Apr 10 10:52:20.957: ? Call User Data (4): 0x01000000 (pad)
*Apr 10 10:52:21.045: [193.219.181.219,1998/,35675]: XOT I P2 Call Confirm (11) 128 lci 1024
*Apr 10 10:52:21.045: ? From (0): ?To (0):
*Apr 10 10:52:21.045: ? Facilities: (6)
*Apr 10 10:52:21.045: ? ? Packet sizes: 1024 1024
*Apr 10 10:52:21.045: ? ? Window sizes: 15 15
*Apr 10 10:52:21.045: XOT Call Confirm packet, Bad value for facility, Window size is not within permitted range
*Apr 10 10:52:21.045: [193.219.181.219,1998/,35675]: XOT O P2 Clear (5) 128 lci 1024
*Apr 10 10:52:21.045: ? Cause 3, Diag 66 (Invalid facility request/Facility parameter not allowed)

It seems that the xot listener on?192.168.178.9 is not using the TELEBAHN profile, but I'm not sure as I'm still very new to this.

I couldn't get it to work locally before either, but strangely now it works without issues between local systems. Actually, I *think* you have to unapply and re-apply the "xot access-group" configuration for it to pick up the new profile parameters (at least in my IOS version).

(Looks like "x25 subscribe windowsize permit 2 15" in the profile would allow for dynamic negotiation?)

?

I'm wondering why it was decided to have non-standard packet and window sizes in the first place?? I understand that they improve performance, but that's not really the point of TELEBAHN or is it? :)

--

Mantas Mikul?nas