Re: ipfw help needed (IP vs TCP)
From: The Other Guy (null_at_null.void)
Date: 11/26/03
- Next message: Richard Parker: "Re: ipfw help needed (IP vs TCP)"
- Previous message: Lowell Gilbert: "Re: Some more questions on FreeBsd usage"
- In reply to: Max Fine: "ipfw help needed (IP vs TCP)"
- Next in thread: Richard Parker: "Re: ipfw help needed (IP vs TCP)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 27 Nov 2003 11:18:49 +1300
"Max Fine" <max29@yahoo.com> wrote in message
news:069xb.20794$Rk5.20278@newsread1.news.atl.earthlink.net...
> I am still a newbie at this so can someone please explain the difference
> between these two ipfw commands?
>
> ipfw add 1000 allow tcp from any to any
>
>
> ipfw add 1000 allow ip from any to any
>
> When I VPN to our company server from home behind my FreeBSD-4.9 gateway I
> can't connect unless I use the second command.
>
> I know I can narrow this rule down to the exact port eventually but for
now
> I just use this temporarily to gain access. I thought TCP was the protocol
> used by VPN?
A VPN can use a variety of packet types including TCP. My own VPN uses UDP.
> Any advice would be appreciated.
TCP packets are created inside IP packets. TCP is therefore a more specific
subset of IP, as is UDP or ICMP. Rules that apply to IP will apply
irrespective of what is contained in the IP packet. TCP rules will apply
only to packets containing TCP packets.
You will sometimes see TCP referred to as TCP/IP, and UDP as UDP/IP etc.
The Other Guy
- Next message: Richard Parker: "Re: ipfw help needed (IP vs TCP)"
- Previous message: Lowell Gilbert: "Re: Some more questions on FreeBsd usage"
- In reply to: Max Fine: "ipfw help needed (IP vs TCP)"
- Next in thread: Richard Parker: "Re: ipfw help needed (IP vs TCP)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|