3G modems and Fortigates

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › 3G modems and Fortigates

Paul1977

5039 posts

Uber Geek

#136576 2-Dec-2013 13:41

I am attempting to configure a Fortinet FortiWiFi 60C to us a USB 3G modem as a redundant connection, but so far haven't been too successful. I am starting by just configuring it as a standalone interface and will configure the redundancy once that is working.

I am using a Netgear Air Card 320U (formerly Sierra). The modem is recognized by the Fortigate (although as a Sierra AC320U). I have confirmed that the modem itself works by attaching it to my PC and connecting successfully to the XT network. But when i try on the Fortigate it just sits there saying "Connecting..." but never establishes the connection.

Here is the config I have:

config system modem
    set status enable
    set auto-dial enable
    set phone1 "*99#"
    set extra-init1 "at+cgdcont=1,\"ip\",\"wap.telecom.co.nz\""
end

Anyone out there who has managed to get a 3G modem working on a Fortigate who can help me out?

Thanks

Paul1977

5039 posts

Uber Geek

#944175 2-Dec-2013 15:15

Correction to above, the Fortigate recognizes the modem as a Sierra AC313U

estebaan

15 posts

Geek

#945025 3-Dec-2013 23:07

Whilst I have no experience with fortinet I have used the Sierra card and 3G backup on another device (router).

I found that I needed to use the APN 'internet.telecom.co.nz' and it worked where 'wap.telecom.co.nz' did not. It may, or may not work but no harm in trying :)

johnr

19282 posts

Uber Geek
Inactive user

#945027 3-Dec-2013 23:08

I would not use the APN wap.telecom.co.nz

Paul1977

5039 posts

Uber Geek

#945921 5-Dec-2013 09:56

Thanks for the suggestions.

Turns out it was because since the router was recognizing it as a slightly different model than what it was it was attempting to access it using the wrong port number. Creating a custom modem definition specifying the correct port has resolved the issue.

Syntax for the APN was correct, and I have found it work with wap.telecom.co.nz and internet.telecom.co.nz. Am currently using internet.telecom.co.nz since that seems to be the consensus of the best one to use.

The issue I am now having is that the IP address that the router is reporting it has been assigned is different to what is being reported to websites (whatismyip.com, speedtest.net etc.) and I can't seem to get it to accept any unsolicited inbound traffic.

What I would like to do is use open port 25 and use DDNS on the modem interface to make it a secondary MX so if the primary connection fails.

I'm quite sure the router config is correct, are inbound pinholes possible on Telecom 3G?

Thanks

Paul

wongtop

563 posts

Ultimate Geek

#945934 5-Dec-2013 10:18

If you want inbound connections you might need to use the "direct.telecom.co.nz" APN http://www.geekzone.co.nz/forums.asp?forumid=39&topicid=32983

Paul1977

5039 posts

Uber Geek

#946050 5-Dec-2013 13:09

wongtop: If you want inbound connections you might need to use the "direct.telecom.co.nz" APN http://www.geekzone.co.nz/forums.asp?forumid=39&topicid=32983

Thanks. I've tried that and hasn't made any difference. The device is getting an external and internal address, rather than bridging the external address to the router interface, and I think this is the issue. I've created a new topic under the Telecom XT forum to see if anyone else has got inbound port forwarding to work on XT.

New topic is here.

Thanks again