Re: Blocking access to a network
From: Vanguard (Vangu_at_rd.invalid)
Date: 06/03/05
- Previous message: Sunny: "Re: Windows XP VPN to Netscreen using native client and L2TP over IPSEC"
- In reply to: Duane ;-\): "Re: Blocking access to a network"
- Next in thread: Leythos: "Re: Blocking access to a network"
- Reply:(deleted message) Leythos: "Re: Blocking access to a network"
- Reply: Duane Arnold: "Re: Blocking access to a network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 3 Jun 2005 01:25:10 -0500
"Duane ;-)" <Notme@Notme.com> wrote in message
news:050ne.22995$IC6.15771@attbi_s72...
>
> "Vanguard" <Vangu@rd.invalid> wrote in message
> news:-_2dnVdhvN_NGgHfRVn-qw@comcast.com...
>> "Duane Arnold" <Notme@notme.com> wrote in message
>> news:V8%me.22716$IC6.15734@attbi_s72...
>>> A static IP is any IP on the router that is
>>> not controlled by the DHCP server on the router.
>>
>> Not entirely true. The DHCP server (in some NAT routers) can be
>> configured to always assign the same IP address to a host based on
>> its MAC address. So the host is configured for DHCP for its IP
>> assignment but the DHCP server in the router always gives that host
>> the same IP address.
>
> Yes, that information is in the DHCP table and the IP is linked to the
> MAC of the NIC.
> That Information can also be deleted out of the DHCP table too on the
> router. The Linksys routers have that ability. My Watchguard doesn't
> have this ability.
Nope, the Linksys BEFSR41 doesn't have the ability to assign static IP
address based on MAC address. Running through the screens:
Setup: Basic Setup - Nothing there regarding assigning static IP
addresses. The only settings there are: enable/disable the router's
DHCP server, decide on the starting number for dynamically assigned IP
addresses to local hosts, and how many maximum local hosts to which it
will assign dynamic IP addresses.
That is it for DCHP control. None of the other configuration screens
deal with the router's DHCP server. In fact, you have to wander off to
the Status screen to then see the DHCP assignment table (which local
host got what IP address).
Similarly, the Linksys firewall is abysmal. Nowhere can you configure a
schedule of when an IP address or MAC can have Internet access. You
cannot perform domain and URL filtering, and you cannot block specific
hosts from connecting to each other. The firewall in Linksys sucks
compared to the D-Link DI-604. Moving "up" to the Linksys BEFSR41
resulted in losing lots of features; however, I did the "privilege" of
paying twice as much for the Linksys.
The Linksys BEFSR41 was a poor replacement for the D-Link DI-604,
especially since the Linksys cost twice as much. Yeah, there might be
another higher model for Linksys with those missing features but then I
would pay twice again to get back the features in the D-Link at
one-fourth the cost. If I get another D-Link, however, I will pop out
the center tang in the vent holes and might even drill out a vent grill
on the top to keep it from running hot.
- Previous message: Sunny: "Re: Windows XP VPN to Netscreen using native client and L2TP over IPSEC"
- In reply to: Duane ;-\): "Re: Blocking access to a network"
- Next in thread: Leythos: "Re: Blocking access to a network"
- Reply:(deleted message) Leythos: "Re: Blocking access to a network"
- Reply: Duane Arnold: "Re: Blocking access to a network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
