Topic: portforwarding

[Micke B]

I'm using portforwarding-0.0.1. If I get a new IP the forwarding breaks. How do I restart portforward?

Thanks in advance
Micke B

[guestHH]

Hi,

Use portforwarding-0.0.4

Regards,
guestHH

[Micke B]

I am using dmc-mitel-portforwarding-0.0.1-4.noarch.rpm

[guestHH]

Hi,

Ok the issue lies within the fact that your external IP changes. After a IP change you have to apply the portforwardig rules again. Thus delete them and apply the again.

Maybe it's time to us a dynamic IP service...

Regards,
guestHH

[Micke B]

Hi, thanks for your answers

Yes I know I can apply the rules again by deleting and adding them but I don't want that. I just want to apply the rules again.

I thougt I was using a dynamic IP service. Why would the IP change if I wasn't?

Micke B

[guestHH]

Hi,

Then maybe the automatic update isn't working. Try searching these forums for with the keyword the service you use. I know there where some issues in the past.

Regards,
guestHH

[Bill Talcott]

I think he meant "dynamic DNS", not "dynamic IP". By running a client on the SME, it will update your server's IP with the service, and you'll always have a set domain name (mysme.dyndns.org or something) that points to your server.

[guestHH]

Yeah sorry, you're right Bill. I was talking about 'dynamic DNS'

[Micke B]

There must be a way to restart the portforwarding. What is happening when I delete/add a port forwarding entry?

--Micke B

[Jay Rentmeester]

I am having the same problem. When my Cable provider forces me a new DHCP address, port forwarding on port 80 stops working. Port 21 work s ok though.

here is my configuration:

SME Server v5.5
Update blade 1
dmc-mitel-portforwarding-0.0.1-4.noarch.rpm
Time Warner Cable
dyndns.org custom dns services
dyndns client on windows server behind SME Server (web server)

Any ideas is much appreaciated.

Thanks,

Jay

[Micke B]

I guess none in this forum is skilled enough. I'll better ask someone who knows linux. This seems to be a playground for amateurs like myself

[Guck Puppy]

So yes... portforwarding and it's stoppage after an IP update (like when you have a reconnect on a dynamic IP adsl account).

I too am using dmc-mitel-portforwarding-0.0.1-4 on a 5.1.2 server...

The server is slow, old and having to recreate these port forwards every time the IP address changes (it's pacbell, it happens too much) is pain pain pain.

Is there perhaps a console command I could include that would run when the dyndns "update" occurs?

G

[Hanno Stockhausen]

Hi

Well, we had the same prob, ipforwarding stopped after an ip-change occured.

Basically the solution to this is rather simple. When you change a forwarding rule the event remoteacces-update will be signaled, which builds a new masq file under /etc/rc.d. Unfortunately the external ip in the forwarding rule is hard coded in that file. So when an ip-change occurs, the masq file will be read again, but still has the old ip in it. What you need to do is, to trigger the recreation of the masq file with your new ip address.

We accomplished that by creating a symlink in /etc/e-smith/events/ip-change to /etc/e-smith/actions/conf-masq. Make sure that this will be executed before the restart-masq script. (Or you can just copy the link from remoteaccess-update and adjust the linkname so it will be processed just before the restart-masq).

I hope, this information will be useful.

Hanno Stockhausen

[Charlie Brady]

Hanno Stockhausen wrote:

> Basically the solution to this is rather simple. When you
> change a forwarding rule the event remoteacces-update will be
> signaled, which builds a new masq file under /etc/rc.d.
> Unfortunately the external ip in the forwarding rule is hard
> coded in that file. So when an ip-change occurs, the masq
> file will be read again, but still has the old ip in it. What
> you need to do is, to trigger the recreation of the masq file
> with your new ip address.

Or don't hard code the IP address into the rules.

If you look at the masq file, you'll see that the other rules are doing a run-time lookup of the correct address, using $OUTERNET. The portforwarding contrib should be updated to do the same thing.

Charlie

[Guck Puppy]

So Darrel, the date on your rpm is 09-21, did you update your contrib to not hard code the IP address?

G