search for: firewall_ip

...ddress. For this I am using dyndns.org alias on DI804 side. Shorewall is stopping all packets comming from DI804 whey trying to establish tunnel. Log on Shorewall machine looks like this: Jan 16 18:31:35 FIREWALL kernel: Shorewall:INT2all:DROP:IN=Internet_Interface OUT= MAC=***** SRC=DI804_IP DST=Firewall_IP LEN=116 TOS=0x00 PREC=0x00 TTL=60 ID=191 PROTO=UDP SPT=500 DPT=500 LEN=96 Multiple IPSEC tunnels are active on Shorewall machine with all kinds of equipment on other side (software and hardware VPN devices) but all of them have fixed IP on other side. This is my first attempt to setup IP tunnel to...

Greetings- I recall mention of this bug at some tim elast year, but do not know if anything yet has been done to address it or if it is in any plans... I have multiple servers behind a f/w. I have ports forwarded on the f/w which map to port 22 on the various servers. i.e. ssh -p1001 FIREWALL_IP ---> NON_ROUTEABLE:22 This is fine, but the hostkey negotiation obviously fails... Is there any sensible way to fix this, and will known_hosts include a port identity at some point in time? Any input would be greatly appreciated- P