Firewall Issue (Network_Firewall.sh)

[archived]

I'm trying desperately to get my Packet 8 service back up and running now that I've switched to the Pluto dual-NIC configuration from my old simple Linksys Router.

The ATA adapter is getting assigned an IP from Pluto's DHCP server, so that's good.  So are my laptop and dekstop PCs.  Both PCs are able to connect to Internet sites, so I am going to assume that the ATA adapter can see it as well.

But I get no dial tone and calling my number results in a message that the ATA has been disconnected from the Internet.

So I looked in Packet 8's support site and found a firewall FAQ saying they need UDP 5060 - 65534 outgoing open, with 5060 for dial tone.  I noticed that 5060/udp outgoing is already opened, but I decided to enter in the 5060-65534 anyways.

BIG MISTAKE

When the system boots up, Network_Firewall.sh calls OpenPort() one time for every single port in the range.  It's been going for almost an hour now and it's nowhere near done.  And of course, while that script goes, the whole system isn't available (at least not the web admin).

I think it would be worthwhile to either add a more optimal method for doing ranges (especially big ranges) or at least give the user some warning that it will take a gazillion years to complete the request.

I'd add it in but I'm not yet comfortable making changes to a system I don't have up and running yet.

Two questions:

1) Anyone had any similar problems and know the solution?
2) Anyone integrated Asterisk in with Packet 8 service?  Care to share your configuration?

Thanks,
Dan

[archived]

Ok, my Packet 8 service is back up and running.  I set the ATA to a static IP and filled in all the DNS information manually.  That worked.

Any ideas why it didn't work as a DHCP device?  I simply took the info found in /etc/resolv.conf and entered it into the static fields.  It was definitely having trouble resolving the IP address of the SIP server, which was likely the cause of my missing dial tone.

Grrrr.. that means I'm waiting for the firewall to come up for nothing.  Lol.


Dan

[archived]

Outgoing connections are always allowed. The firewall only restricts incoming ones. From the firewall you can open ports into the Core or forward ports to machines/devices inside the Core's LAN.

As for the DHCP issue you have with your ATA, if your computers get their data right, I don't understand why the ATA doesn't. The syslog may hold some answers in this case.