Most, if not all, modems require a break of a second or so either side
of the escape string. Without this they will ignore it, so a +++
mid-stream shouldn't have any effect.
Incorrect, this is not a standard. The guard time around the escape
sequence is patented by Hayes [1]. So other modem
[ For the confused: ICMP is the Internet Control Message Protocol, and was
originally specified in RFC 792 which can be found at
http://ds.internic.net/rfc/rfc792.txt or
http://www.kashpureff.org/nic/rfcs/700/rfc792.txt.html ]
I have been using ip_masq for several months now and but one
thing
Jason wrote:
I am setting up masquerading on a debian 1.3 box and I need to
figure out the rules I need to add. The linux gateway machine has an
assigned ip (private of 10.0.0.1) and clients will be
10.0.0.2 and .2 and
so forth. What ipfwadm rules do I need to add I was thinking the
David A. Ranch wrote:
Well, I'm worried about the big ones. For example:
[snip]
# Xwindows - Deny
/sbin/ipfwadm -O -a reject -W $extif -P tcp -S $extip/32 -D
$universe/0 6000 -o
/sbin/ipfwadm -O -a reject -W $extif -P udp -S $extip/32 -D
$universe/0 6000 -o
Shouldn't that be port range
Sean A. Walberg wrote:
On Tue, 9 Feb 1999, Fuzzy Fox wrote:
It appears, from the large number of messages which are related to
networking, but not really masquerade-related, that there
is some sort
of demand for a list which revolves, topic-wise, around the
subject of
networking,
to
the outside. If more than one machine connects to the outside then you
should write rules for both NICs.
From Lourdes A. Jones 's Email:
He help me lot to clarify this previous mechanism.
Thank you, for future reference I am a she. :)
So you mean Forward rules are Leaded by the Output
David A. Ranch wrote:
I found in writing firewall rules, its easier to do a "blanket" deny
policy, (so you get all your bases), then only do "accept" for those
services you want to allow.
Why not a blanket REJECT?
Personal preference, DENY drops the packet, REJECT sends back an ICMP
David A. Ranch wrote:
Feb 10 23:22:59 trinity2 kernel: IP fw-out deny eth0 ICMP/3
192.168.0.1 24.0.75.172 L=106 S=0xD0 I=24193 F=0x T=64
ICMP Masq is a separate kernel configuration option in
2.0.36+ and 2.2.x.
Did you enable it? If you did, did you set up a general
forwarding rule
