Scripting the behaviour of Status --> Interfaces --> DHCP renew button

jly2680

[2.3.5-RELEASE][root@pfSense.local]/root: usbconfig -d ugen1.2 dump_all_config_d esc
ugen1.2: <HUAWEIMOBILE HUAWEIMOBILE> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)

Configuration index 0

bLength = 0x0009
bDescriptorType = 0x0002
wTotalLength = 0x00af
bNumInterfaces = 0x0003
bConfigurationValue = 0x0001
iConfiguration = 0x0000  <no string>
bmAttributes = 0x0080
bMaxPower = 0x0001

Interface 0
  bLength = 0x0009
  bDescriptorType = 0x0004
  bInterfaceNumber = 0x0000
  bAlternateSetting = 0x0000
  bNumEndpoints = 0x0002
  bInterfaceClass = 0x00ff  <Vendor specific>
  bInterfaceSubClass = 0x0003
  bInterfaceProtocol = 0x0012
  iInterface = 0x0000  <no string>

  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x00
   RAW dump:
   0x00 | 0x05, 0x24, 0x00, 0x10, 0x01


  Additional Descriptor

  bLength = 0x04
  bDescriptorType = 0x24
  bDescriptorSubType = 0x02
   RAW dump:
   0x00 | 0x04, 0x24, 0x02, 0x02


  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x01
   RAW dump:
   0x00 | 0x05, 0x24, 0x01, 0x00, 0x00


  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x06
   RAW dump:
   0x00 | 0x05, 0x24, 0x06, 0x00, 0x00


 Endpoint 0
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0081  <IN>
    bmAttributes = 0x0002  <BULK>
    wMaxPacketSize = 0x0200
    bInterval = 0x0000
    bRefresh = 0x0000
    bSynchAddress = 0x0000

 Endpoint 1
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0001  <OUT>
    bmAttributes = 0x0002  <BULK>
    wMaxPacketSize = 0x0200
    bInterval = 0x0000
    bRefresh = 0x0000
    bSynchAddress = 0x0000


Interface 1
  bLength = 0x0009
  bDescriptorType = 0x0004
  bInterfaceNumber = 0x0001
  bAlternateSetting = 0x0000
  bNumEndpoints = 0x0003
  bInterfaceClass = 0x00ff  <Vendor specific>
  bInterfaceSubClass = 0x0003
  bInterfaceProtocol = 0x0010
  iInterface = 0x0000  <no string>

  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x00
   RAW dump:
   0x00 | 0x05, 0x24, 0x00, 0x10, 0x01


  Additional Descriptor

  bLength = 0x04
  bDescriptorType = 0x24
  bDescriptorSubType = 0x02
   RAW dump:
   0x00 | 0x04, 0x24, 0x02, 0x02


  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x01
   RAW dump:
   0x00 | 0x05, 0x24, 0x01, 0x00, 0x01


  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x06
   RAW dump:
   0x00 | 0x05, 0x24, 0x06, 0x00, 0x00


 Endpoint 0
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0083  <IN>
    bmAttributes = 0x0003  <INTERRUPT>
    wMaxPacketSize = 0x000a
    bInterval = 0x0009
    bRefresh = 0x0000
    bSynchAddress = 0x0000

 Endpoint 1
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0082  <IN>
    bmAttributes = 0x0002  <BULK>
    wMaxPacketSize = 0x0200
    bInterval = 0x0000
    bRefresh = 0x0000
    bSynchAddress = 0x0000

 Endpoint 2
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0002  <OUT>
    bmAttributes = 0x0002  <BULK>
    wMaxPacketSize = 0x0200
    bInterval = 0x0000
    bRefresh = 0x0000
    bSynchAddress = 0x0000


Interface 2
  bLength = 0x0009
  bDescriptorType = 0x0004
  bInterfaceNumber = 0x0002
  bAlternateSetting = 0x0000
  bNumEndpoints = 0x0001
  bInterfaceClass = 0x00ff  <Vendor specific>
  bInterfaceSubClass = 0x0003
  bInterfaceProtocol = 0x0016
  iInterface = 0x0007  <NCM Network Control Model>

  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x00
   RAW dump:
   0x00 | 0x05, 0x24, 0x00, 0x10, 0x01


  Additional Descriptor

  bLength = 0x06
  bDescriptorType = 0x24
  bDescriptorSubType = 0x1a
   RAW dump:
   0x00 | 0x06, 0x24, 0x1a, 0x00, 0x01, 0x1f


  Additional Descriptor

  bLength = 0x0d
  bDescriptorType = 0x24
  bDescriptorSubType = 0x0f
   RAW dump:
   0x00 | 0x0d, 0x24, 0x0f, 0x09, 0x0f, 0x00, 0x00, 0x00,
   0x08 | 0xea, 0x05, 0x03, 0x00, 0x01


  Additional Descriptor

  bLength = 0x05
  bDescriptorType = 0x24
  bDescriptorSubType = 0x06
   RAW dump:
   0x00 | 0x05, 0x24, 0x06, 0x02, 0x02


 Endpoint 0
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0085  <IN>
    bmAttributes = 0x0003  <INTERRUPT>
    wMaxPacketSize = 0x0010
    bInterval = 0x0005
    bRefresh = 0x0000
    bSynchAddress = 0x0000


Interface 2 Alt 1
  bLength = 0x0009
  bDescriptorType = 0x0004
  bInterfaceNumber = 0x0002
  bAlternateSetting = 0x0001
  bNumEndpoints = 0x0003
  bInterfaceClass = 0x00ff  <Vendor specific>
  bInterfaceSubClass = 0x0003
  bInterfaceProtocol = 0x0016
  iInterface = 0x0008  <CDC Network Data>

 Endpoint 0
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0085  <IN>
    bmAttributes = 0x0003  <INTERRUPT>
    wMaxPacketSize = 0x0010
    bInterval = 0x0005
    bRefresh = 0x0000
    bSynchAddress = 0x0000

 Endpoint 1
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0084  <IN>
    bmAttributes = 0x0002  <BULK>
    wMaxPacketSize = 0x0200
    bInterval = 0x0000
    bRefresh = 0x0000
    bSynchAddress = 0x0000

 Endpoint 2
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0003  <OUT>
    bmAttributes = 0x0002  <BULK>
    wMaxPacketSize = 0x0200
    bInterval = 0x0000
    bRefresh = 0x0000
    bSynchAddress = 0x0000

stephenw10

Looks promising. Can you test it on something 64bit?

Or boot FreeBSD 11.3 on the ALIX maybe?

You might get it working in 2.3.5 with the right FreeBSD 10 kernel module. Really you should upgrade though. 2.3.X is unmaintained and should be considered insecure as a result.

Steve

jly2680

@stephenw10 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

Looks promising. Can you test it on something 64bit?

Or boot FreeBSD 11.3 on the ALIX maybe?

You might get it working in 2.3.5 with the right FreeBSD 10 kernel module. Really you should upgrade though. 2.3.X is unmaintained and should be considered insecure as a result.

Steve

I would prefer loading kernel module on 2.3.5,, but I dont have any links to dowload modules

stephenw10

Get them from the corresponding FreeBSD iso. 10.3 in this case.

https://docs.netgate.com/pfsense/en/latest/releases/versions-of-pfsense-and-freebsd.html

Steve

jly2680

@stephenw10 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

Looks promising. Can you test it on something 64bit?

Or boot FreeBSD 11.3 on the ALIX maybe?

You might get it working in 2.3.5 with the right FreeBSD 10 kernel module. Really you should upgrade though. 2.3.X is unmaintained and should be considered insecure as a result.

Steve

@stephenw10 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

Get them from the corresponding FreeBSD iso. 10.3 in this case.

https://docs.netgate.com/pfsense/en/latest/releases/versions-of-pfsense-and-freebsd.html

Steve

@stephenw10 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

Get them from the corresponding FreeBSD iso. 10.3 in this case.

https://docs.netgate.com/pfsense/en/latest/releases/versions-of-pfsense-and-freebsd.html

Steve

I did try it on vmware lastest pfsense , NCM and ue0 interface showed..can you guide which module are needed to load on 2.3.5??

But when I load Freebsd 10.3 also on vmware,,no ncm and ue0 int showed,,

stephenw10

@jly2680 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

But when I load Freebsd 10.3 also on vmware,,no ncm and ue0 int showed,,

That doesn't bode well. It's probably just not supported there then.

You can use kldstat to see what kernel modules are being used.

Steve

bradtpt

@jly2680 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

i got my e3372 and switch its firmware to stick mode..but my pfsense is based on 2.3.5 running on alix 2d13..I check the dmesg when I put my modem:
ugen1.2: <HUAWEIMOBILE> at usbus1 (disconnected)
u3g0: at uhub1, port 1, addr 2 (disconnected)
ugen1.2: <HUAWEIMOBILE> at usbus1
u3g0: <HUAWEIMOBILE HUAWEIMOBILE, class 0/0, rev 2.10/1.02, addr 2> on usbus1
u3g0: Found 2 ports.
no ue0 device at /dev .. doesnt show the NCM interface..Can I load the NCM driver using 2.3.5??

Yes you can, you need to use the setport command from the AT command set for the modem to enable the NCM interface. I have another post with some details thrown in contained here: https://forum.netgate.com/topic/137637/huawei-e3372-will-not-reconnect-ppp-after-manual-disconnect-under-status-interfaces

In summary what you need to do is jump into the console and talk directly to the modem via the emulated serial port by running: cu -l /dev/cuaU0.0 or cu -l /dev/cuaU0.1 depending on which port it created and wants to talk on. Once in there run the command AT^SETPORT="FF;10,12,16" and then AT^RESET to reboot the stick. After having done this once, from herein the stick should present the NCM interface which is defined by the 16 in the command above.

PS - I can confirm this works on 2.3.x as I had a client on that version a while ago and utilized ones of these.

stephenw10

Nice!

jly2680

@bradtpt said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

@jly2680 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:
i got my e3372 and switch its firmware to stick mode..but my pfsense is based on 2.3.5 running on alix 2d13..I check the dmesg when I put my modem:
ugen1.2: <HUAWEIMOBILE> at usbus1 (disconnected)
u3g0: at uhub1, port 1, addr 2 (disconnected)
ugen1.2: <HUAWEIMOBILE> at usbus1
u3g0: <HUAWEIMOBILE HUAWEIMOBILE, class 0/0, rev 2.10/1.02, addr 2> on usbus1
u3g0: Found 2 ports.
no ue0 device at /dev .. doesnt show the NCM interface..Can I load the NCM driver using 2.3.5??
Yes you can, you need to use the setport command from the AT command set for the modem to enable the NCM interface. I have another post with some details thrown in contained here: https://forum.netgate.com/topic/137637/huawei-e3372-will-not-reconnect-ppp-after-manual-disconnect-under-status-interfaces

In summary what you need to do is jump into the console and talk directly to the modem via the emulated serial port by running: cu -l /dev/cuaU0.0 or cu -l /dev/cuaU0.1 depending on which port it created and wants to talk on. Once in there run the command AT^SETPORT="FF;10,12,16" and then AT^RESET to reboot the stick. After having done this once, from herein the stick should present the NCM interface which is defined by the 16 in the command above.

PS - I can confirm this works on 2.3.x as I had a client on that version a while ago and utilized ones of these.

[2.3.5-RELEASE][root@pfSense.local]/root: cu -l /dev/cuaU0.0
Connected

Manufacturer: huawei
Model: E3372
Revision: 21.200.07.00.805
IMEI: 866785033259671
+GCAP: +CGSM,+DS,+ES

OK

OK

OK
ugen1.2: <HUAWEIMOBILE> at usbus1 (disconnected)
u3g0: at uhub1, port 1, addr 2 (disconnected)
[2.3.5-RELEASE][root@pfSense.local]/root: ugen1.2: <HUAWEIMOBILE> at usbus1
u3g0: <HUAWEIMOBILE HUAWEIMOBILE, class 0/0, rev 2.10/1.02, addr 2> on usbus1
u3g0: Found 2 ports.

Same no ncm interface after issuing these commands..

bradtpt

Ok can you show me the output of the following:

cu -l /dev/cuaU0.0
AT^SETPORT=?
AT^SETPORT?

Unfortunately I don't have one with me to check the config directly, however have you modeswitched the device out of mass storage mode? If not, you'll need to download and install usbmodeswitch by running this (from memory 2.3.x is on FreeBSD10 so this should be the correct version):
pkg add http://pkg.freebsd.org/FreeBSD:10:amd64/release_4/All/usb_modeswitch-2.5.0.txz
and then running this:
/usr/local/sbin/usb_modeswitch -J -v0x12d1 -p0x1f01

Running that will cause the device to drop out of mass storage mode and should present the interfaces. Let us know how you go. If I had a stick with me I'd go through the motions and post it up for you but unfortunately I can only go off some notes I have here from the last one I did quite a while back.

jly2680

[2.3.5-RELEASE][root@pfSense.local]/root: cu -l /dev/cuaU0.0
Connected

ERROR

^SETPORT:FF;10,12,16

OK

Issuing this AT^SETPORT=? command got an error answer from modem..here's the message after usbmodeswitch

[2.3.5-RELEASE][root@pfSense.local]/root: usb_modeswitch -J -v0x12d1 -p0x1506   Look for default devices ...
   product ID matched
 Found devices in default mode (1)
Access device 002 on bus 001
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 255
Error: can't use storage command in MessageContent with interface 0; interface class is 255, expected 8. Abort

echo 'AT^NDISDUP=1,1,"jawalnet.com.sa"' > /dev/cuaU0.1

this modem command gave me a solid blue light on the modem,,but no ue0 or cde interface showed up..

bradtpt

The error from usbmodeswitch makes sense now I think about it, you have the stick firmware loaded so as such the device when inserted won't present as a mass storage device. I have an e3372 with the stick firmware loaded at work, if I get a chance tomorrow I'll fire up a machine with 2.3.5 and see if I can make it work. As I'm not familiar with your Alix hardware the closest I can go to replicating your environment would be to install an archived version of pfSense-CE-memstick-2.3.3-RELEASE-amd64.img I have here on an amd machine. Is your alix similar or a totally different platform?

jly2680

@bradtpt said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

The error from usbmodeswitch makes sense now I think about it, you have the stick firmware loaded so as such the device when inserted won't present as a mass storage device. I have an e3372 with the stick firmware loaded at work, if I get a chance tomorrow I'll fire up a machine with 2.3.5 and see if I can make it work. As I'm not familiar with your Alix hardware the closest I can go to replicating your environment would be to install an archived version of pfSense-CE-memstick-2.3.3-RELEASE-amd64.img I have here on an amd machine. Is your alix similar or a totally different platform?

Oh thanks..its an old alix 2d13 i386..I think 2.3.5 doesnt work with 3372 in stick mode

bradtpt

Ahh ok, unfortunately netgate don't leave old versions online, I'll have to go digging and see if I can find a i386 installer kicking around somewhere. If you have a link or can dropbox it to me or similar let me know.
-edit- I just found this: https://mirrors.xmission.com/pfsense/downloads/pfSense-CE-2.3.5-RELEASE-i386.iso.gz and this: https://mirrors.xmission.com/pfsense/downloads/pfSense-CE-memstick-2.3.5-RELEASE-i386.img.gz so it looks like we're in luck.

stephenw10

I would be surprised if there's any difference between the 32bit and 64bit versions as far as this modem is concerned. The available tools should be identical.

Steve

jly2680

@stephenw10 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

I would be surprised if there's any difference between the 32bit and 64bit versions as far as this modem is concerned. The available tools should be identical.

Steve

I test this modem through vm pfsense 2.4 , ue0 and cdc showed up..I wonder if there is any new patch from 2.4 if_cdce.ko that was not included in 2.3.5

can you look at this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192345

stephenw10

There are many, many differences between FreeBSD 10.3 and 11.1 which is what you're comparing there.

That link is broken.

Steve

jly2680

@stephenw10 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

There are many, many differences between FreeBSD 10.3 and 11.1 which is what you're comparing there.

That link is broken.

Steve

the patch includes

head/sys/dev/usb/net/if_cdce.c
head/sys/dev/usb/serial/u3g.c
head/sys/dev/usb/serial/umodem.c

hope someone could port this patch on 2.3.5

stephenw10

Your link was actually good, the bug server was down at that exact moment I tested.

Porting that is non trivial. You would have to rebuild a whole number of things there. You cannot just load a replacement module. And even after you had done that you would still be running unsupported, unpatched, 2.3.5.

Is there some reason you cannot just replace that ALIX with something vaguely current?

Steve

jly2680

@stephenw10 said in Scripting the behaviour of Status --> Interfaces --> DHCP renew button:

Your link was actually good, the bug server was down at that exact moment I tested.

Porting that is non trivial. You would have to rebuild a whole number of things there. You cannot just load a replacement module. And even after you had done that you would still be running unsupported, unpatched, 2.3.5.

Is there some reason you cannot just replace that ALIX with something vaguely current?

Steve

This alix will be deployed on our client’s remote area maybe this end of the month.I’ll convince him if he can rather buy a new hardware..I may use openwrt with this 4g stick if he refuse to shell out some $