Leopard IP Forwarding Stopped Working

I have a virtual machine (Hercules) running on my Leopard 10.5.6 Mac Pro. It uses the Mac tun/tap driver to establish its network presence.
Under Tiger I could use "sysctl -w net.inet.ip.forwarding=1" to turn on IP forwarding and get to my virtual machine just fine. In fact, I modified /etc/sysctl.conf to turn it on. Everything worked fine. Now it doesn't work. In addition to net.inet.ip.forwarding, I've turned on net.inet.ip.fastforwarding and net.inet6.ip6.forwarding. No luck. My firewall is off, since I'm behind a firewall.
Using "route add -host nnn.nnn.nnn.nnn gw nnn.nnn.nnn.nnn" on all my other machines works, but that's lots of places to modify, instead on just 1.
Has anyone had success with ip forwarding and Leopard?

Our keyboard is working, but the 'num lock' and 'caps lock' lights are ON when they should be OFF and vice versa.
The install does not seem to have affected our 2.4GHz machine in the same way (which is 3 months old) and was upgraded to 10.5 last night from 10.4.9 (however with this unit we can't get visibility of external network drive connected via Airport Extreme, whereas with the 2.2Ghz machine with the keyboard issue we do!).
The 2.2Ghz machine listed here (with the keyboard issue) was fresh out of the box last night, so just used the install disk Apple had shoved in the box for 10.5. The 2.4Ghz machine was loaded with a single user copy of 10.5 bought off the shelf at the Apple store.

Similar Messages

Port forwarding stops working several hours after reset

I have a WRT350N (fw v. 1.03.2). It's connected to an Alcatel ADSL modem (PPPoE configuration). I've configured port forwarding to allow HTTP and SSH into a linux box on my home network (static IP). I am able to get to the linux box from outside for the first few hours after I set up the configuration, but a few hours later I am no longer able to get to it from outside - port forwarding stops working though the settings remain as I'd left them. Over the course of various attempts I've had the external connections just die (404 errors, host not found, etc) and sometimes the connection went to the router - getting the WRT350N login prompt (remote management is turned on, but on port 8080, not 80, so this was unexpected).
The only way I've found to resolve this is to reset to factory defaults and reconfigure. Then it works again for a few hours and shortly is again not forwarding. I've tried other ports (VNC, RDC, telnet, SMTP) and the forwarding stops working on all ports at the same time. My home machines are able to get out to the internet with no problems.
I thought the router had a hardware flaw so i replaced it with an identical model yesterday, and sure enough, today I'm again stuck without external access to my home website.
Any thoughts or suggestions would be welcome.
Thanks,
Nick

I was able to trace the problem to torrent downloads. It seems the router wasn't handling all the concurrent connections when handling torrents. I haven't had problems since i stopped downloading torrent files. I did add a static port mapping and configured utorrent to run on a single port on a machine with a static address but haven't had cause to download any torrent files since then, so i don't know if that will fix the problem.
That being said, i've had no issues since i stopped the torrents.
HTH
Nick

Port forward stopped working after update

i updated my software and the port forward stopped working and it will no longer allow access to my ip camera.

Hey Cab,
Yea, mine stopped working since the update to 10.8.2. It was working fine prior to the update cause I used it at work on a 50 inch Samsung. I undrstand that there was a driver update but I'm not sure why.

E2000 Port Forwarding Stops Working

I am using port forwarding for running a webserver. All is working fine. After a random number of hours or days, the port forwarding stops working. I can get in and look at the settings and they are correct. I can then change something on the port forwarding screen and resave it and it starts working again. Do I have a bad unit ?

Webserver might not be set to static IP. Try setting the webserver to static IP first, then make sure that static IP is enabled in the Port Forwarding screen of the router's web-based setup page. Also, protocol should be set to BOTH (TCP-UDP). You can also try having less firewall/AV restrictions on the web server (or none at all) and set MTU to 1400.

Ssh Port Forwarding Stopped Working

I have used ssh port forwarding in the past, and it has come in handy.
I have recently upgraded to Mavericks, but it does appear that my ssh port forwarding stopped some time before this. The last time I know it worked was 5/14/14, and feel it has worked more recently as well.
Here's what I do, from my Mac I ssh to my work jump server (port 22, let's say its IP is 11.22.33.44), and my jump server has access to work PC (lets say IP of 10.1.2.3). My work PC has RDP running on it on the common port 3389. I have verified that I can set up a working RDP session at work from another box. Also, I know that my jump server can get to my PC at work as I can ping my work IP if I just ssh straight to my jump server. And I know that there is no firewall stopping me from the jump server as I can also open a telnet session to my work PC on port 3389, without errors.
So, here's how I have done it in the past and it has worked, but now recently stopped working in Terminal app:
ssh -f [email protected] -L 3388:10.1.2.3:3389 -Nnv
The verbose logging shows that it sets up connectivity. If I then look to see if my local port is listening I can type:
netstat -an | grep 127.0
I will note that port 3387 is in fact LISTENing and waiting for connection
I then start my RDP client app, and start a session to "localhost:3387" (I could also use "127.0.0.1:3387", and have, but it does not work either). My RDP client eventually times out. I have turned my firewall off and on, neither way works.
Does anyone know why this may have stopped working?
Your input is most appreciated.
The verbose log shows the following is setup appropriately (with noted modifications to server names and actual IPs):
debug1: Authentication succeeded (keyboard-interactive).
Authenticated to somewhere.net ([11.22.33.44]:22).
debug1: Local connections to localhost:3387 forwarded to remote address 10.1.2.3:3389
debug1: Local forwarding listening on 127.0.0.1 port 3387.

Unfortunately I don't have another device to test if RDP is working on my LAN, however, when I check out my network connections and this is what I see after setting up the ssh tunnel and prior to attempting the RDP connection (again names protected):
my-rmbp:~ me2$ netstat -an | grep 127.0
tcp4       0      0 127.0.0.1.3387         *.*                    LISTEN
Then, as it is difficult to catch in the middle of TCP 3-way handshaking, here's what happens after an attempt with the RDP client while it sits and spins:
my-rmbp:~ me2$ netstat -an | grep 127.0
tcp4       0      0 127.0.0.1.3387         127.0.0.1.50323        FIN_WAIT_2
tcp4       0      0 127.0.0.1.50323        127.0.0.1.3387         CLOSE_WAIT
tcp4       0      0 127.0.0.1.3387         *.*                    LISTEN
You can clearly see it's attempting to make a connection over the tunnel via my RDP client, but it's being shut down right away. I will obtain a WireShark packet capture and see exactly what's happening. Oh, and if I tried to RDP to a port other than the one I set up the port forwarding tunnel with, RDP would disconnect right away.
What I'm most interested in is why, without any known changes, other than OS updates, did this work a few months ago, and now it does not?
I have also tried other test ssh port forwarding, such as to www.apple.com forwarding 8080 on localhost to 80, and others, and none of those work either with web browsers, I assume this is something Apple has done to disable ssh port forwarding/tunneling. Perhaps someone else has bumped into this and found a fix? Please share!
Also, I have heard that you have to be root in order to set up port forwarding, but clearly this is not accurate, as it worked before, and also as you can see above it worked without root. But I tried both ways, and sadly neither worked.
Could it by my jump server? Possibly, but others at work do this and it works just fine for them from their Windoze PCs. So can't be that either.
Perhaps my capture will tell me, I'll report back here with what I discover. Thanks in advance!

Port Forwarding Stops Working WRT400N

Is anyone else having a problem with port forwarding on their WRT400N? I'm forwarding one service (https) and this stops working if it's not accessed after a 10 days or so. The only way to get it to work again is to reboot the router. I’m running the “latest" firmware, which is an oxymoron considering it's been over 12 MONTHS since Linksys updated the code... Which is appalling considering this appears to be their flagship wireless N router.

I tried the hard reset and still the same problem, port forwarding stops after a period of time. Sometimes 1 day, other times 10 days. I have 2 servers on the local network, each running Remote Desktop on port 3389. I have 2 ports forwarded to get to either server depending on the external port number. E.g.: The external port forward is {wan_ip_addr}:33389->{server 1}:3389 to get to server 1 and, {wan_ip_addr}:23389->{server 2}:3389 to get to server 2. Works great when it works, but then, without error, just the port forwarding stops, and all other router functions seem to continue working. Has anyone else come across this? Any fixes? Help!!!!
Thanks in advance to any help!!

Forwarding stopped working with iMS5.2

Fowarding of messages in our iMS5.2 has suddenly stopped working. It has been working up until now. Searching the directory shows
mailDeliveryOption=mailbox
mailDeliveryOption=forward
mailForwardingAddres=.........real email address here
Is there any reason why forwarding should suddenly stop working?
Thanks in advance.

I know of no reports of the ability to forward mails being removed.
When did it last work? What has changed since then?
Exactly what version of iMS 5.2 are you running? Please run
imsimta version
and post the results.
It's possible that your "reprocess" channel has stopped, that's where forwards get created. Check that you don't simply have a bunch of forwards there, use
imsimta qm sum
for a quick read of what's in all the queues.

X11 forwarding stops working

I'm not sure if this is a client or server side problem, but when I ssh (with -X) into a remote host (running debian) X11 forwarding initially works, but after some time (15 minutes?) it stops. Then I get errors like, e.g., "gv: Unable to open the display."
I never used to have this problem, so something must have changed somewhere. Anyone else experienced something similar?
Thanks!

I've been using X11 from my iMac since just before Christmas '09 talking to RedHat EL4, EL5, as well as Solaris and AIX systems.
However, I use -Y instead of -X, otherwise I've had X-Windows up for weeks on end without any problems.

My text forward stopped working and its not showing up anymore under imessage

My text forwarding used to work and it suddenly stopped working and it wont even show up under imessage. i have restart and re-did everything and it is still not showing up for me to turn it on

both emails and phone number is checked on both ipad and iphone. Thats how im still getting imessage on both device its only the text forward that stopped showing up
also even if its not connected to any device it should still show the option for text forward. at least it used to before but its not even showing that option on my iphone anymore

TS4002 Forwarding stopped working

I have iCloud mail set to forward to my gmail account. This worked perfectly but then just stopped. No settings have been changed in either account. I recall similar problems with MobileMe. Any solutions?

I have been struggling with this forwarding issue too: any email messages I try to manually forward from my iPhone just never arrive to the intended recipients. I have tested this on multiple occasions and to multiple e-mail addresses.
Using a .mac account via icloud now, I can "reply", create a new message from my iPhone and it gets right through to the target recipient. Using iCLoud on my Mac deskop, forwarding works just fine (again, using my .mac handle). So, I suspect its possible that the Mail client on the iPhone has the software glitch, seeing the Mail client from the Mac works just fine.
Would love to hear of any solutions to this issue.
iPhone 4, using iOS 5.1.1
(not going to iOS 6 til the Google maps thing gets figured out)

RV042 Port forwarding stops working when Firewall is enabled

Hey all,
I have a RV042 router on a single WAN and an internal LAN. I have configured port forwarding as follows:
HTTP[TCP/80~80]->10.0.0.6
HTTPS[TCP/443~443]->10.0.0.6
IMAP[TCP/143~143]->10.0.0.5
IMAP SSL[TCP/993~993]->10.0.0.5
SMTP SSL[TCP/587~587]->10.0.0.5
Everything works just fine when I have the firewall DISABLED. However, when I enable it the behaviour is erratic. 1 out of 10 attempts to connect to ANY port forwarded works. Almost all attempts time out.
Notice that this happens even if using only the default firewall rules (which should be bypassed by the port forwarding as I read in other posts).
My second try was to create firewall rules manually, overriding the default ones. I tried adding rules from source WAN1 (where my connection is) to ANY and to SINGLE IP's on every port. Nothing seems to work.
I don't know what I'm doing wrong, this is really bugging me. I had to turn the firewall off so we can access our servers from outside the office. This shouldn't have to be done.
Do you know anything I could try?
Best regards,
Theo
EDIT:
Just found out that my firewall is getting LOTS and LOTS of Blocked - SYN Flood entries. I think this is why we are having trouble with the firewall. Could this be the problem? I have no idea where all these SYN packets are coming from since they appear with spoofed IPs or come from different bots all over.

Hi Theo, if you want to over ride the default state table, you need to first make firewall rules to block all access then make your permission rules.
Such an example would be-
Action Deny
Service All
Source interface WAN
Source IP any
Destination IP any
Save
Action Permit
Service RDP
Source interface WAN
Source IP -xx.xx.xx.xx
Destination IP - xx.xx.xx.xx
Save
As for your concern about the syn flood, it can be a likely cause of your problems. Does the logging facility of the router give any indications?
-Tom
Please mark answered for helpful posts

Why did my call forwarding stopped working with 8.2 update on my 5s?

I have tried a hard re-boot twice. I forwarded the iPhone to my home when I'm there because my LAN line gets better reception. Now that I need to leave the house I can't un-forward it. I put in the number but it keeps going back to grey and won't work. Help????

In case anyone else experiences this, I found the problem...
Apparently I had some corrupted fonts. I had installed some older Chinese language fonts that complained about errors, which I overrode.
Font Book was unresponsive, but I was able to move all my user fonts out by going to
~/Library/Fonts
I moved them all to a new folder, and the problems went away.
Now I can move them back one by one to identify/eliminate the culprit(s).

ICloud Forwarding Stopped Working?

I've had iCloud set to forward and delete my emails for quite a while now. Starting 3 May the forwarding and deleting aburuptly stopped. I've checked and the settings are the same. Also I had to change my password when logging in due to a "security problem". I guess I'll assume that these are connected. I've changed the password, checked the settings, and still no joy. New emails sent to that account do not forward and do not get deleted. Any ideas?

Nevermind. I found the following on another post
This is the website that shows the iCloud system status. There is a problem.
http://www.apple.com/support/icloud/systemstatus/

Port Forwarding not working after 7.7.1 Firmware update

I bought the new 6th generation Airport Extreme today, and after I set it up, everything worked great. I have a VoIP phone that needs to have traffic on port 5060 forwarded to it, and that worked just fine as well.
However, I then updated to the 7.7.1 firmware, and the port forwarding stopped working. I tried a hard reset of the Airport and re-entered all the settings, but it still didn't work. I spent about 30 minutes on the phone with 2 Apple support people who tried hard, but couldn't help. They also couldn't find a way to download the 7.7 firmware, so there was no way to downgrade. They suggested I go back to the store and exchange it for another one, which I did, and now it all works again.
Has anyone else had issues with port forwarding on 7.7.1? I'm just wondering how I'll ever be able to update the firmware, since failure means having to get a new Airport.

Huh,
turns out the problem went away with another restart of the Mac Mini. I'm still uneasy about it though, as I do not understand how it went from working to not-working over night in the first place. But, at least for now, the problem seems gone.
Thanks for commenting.
Cheers
Niels Olof

Ever since I installed Snow Leopard (10.6.8), masking in QuickTime 7Pro has stopped working. Has anybody experienced this? Is there a work around? Can I use FCP to add masks to video?

Ever since I installed Snow Leopard (10.6.8) a month ago, the masking function in QuickTime 7Pro (v. 7.6.6) stopped working. Masks disappeared in old videos where I had previously and successfully added a mask, and I could not longer use QT 7Pro to add a mask to a new video. When I installed Snow Leopard I also installed QT X, but I found QT 7Pro in the Utilities folder, so it is still there but the masking function is definately not working.
Has anybody else experienced this?
Is there a remedy so I can recover my older masked videos, and make new masked videos?
Can I make masked videos in Final Cut Pro?
Thanks!

Ever since I installed Snow Leopard (10.6.8) a month ago, the masking function in QuickTime 7Pro (v. 7.6.6) stopped working. Masks disappeared in old videos where I had previously and successfully added a mask, and I could not longer use QT 7Pro to add a mask to a new video. When I installed Snow Leopard I also installed QT X, but I found QT 7Pro in the Utilities folder, so it is still there but the masking function is definately not working.
Has anybody else experienced this?
Is there a remedy so I can recover my older masked videos, and make new masked videos?
Can I make masked videos in Final Cut Pro?
Thanks!

Leopard IP Forwarding Stopped Working

Similar Messages

Maybe you are looking for