Louis-Alexandre Duchesneau

I also have the issue as @jamerst. I have the same setup, Fedora Workstation, Gnome Termnial, ZSH version. I have disabled async untill the main issue is found.

Issue still persist for me

I have the same issue on x86/64 build ( PC Engines apu4 with AMD GX-412TC SOC)

So the issue was added between rc1 and rc2. Doing some basic troubleshooting by applying commit after commit, I was able to find that the issue was introduced in this...

Trying to find the root cause: Can others confirm that you are using PPPOE over VLAN ?

I have done some basic test, using a switch to untag the VLAN and configuring the PPPOE interface on openwrt without VLAN. The issue persists.

Its up to the user to implement this. I use a map and store the PDU SequenceNumber as the KeyType. When I receive a response, I just get the value...

You have access to the sequence number that will be used before you send the PDU on the connection. When you create a PDU with its New function, like [NewSubmitSm()](https://github.com/linxGnu/gosmpp/blob/master/pdu/SubmitSM.go#L26),...

You dont pass it to newSubmitSm, you change the ESM class after submitSm is created.

My two cents, the Functional Option should also be added to Transmitter bind, address_range (addr_ton, addr_npi) are allowed in the bind_transmitter body.