Re: Alias in different subnet on card

From: Micheal Patterson (micheal_at_tsgincorporated.com)
Date: 03/08/04

  • Next message: Ralph M. Los: "Cisco 350 card with 128-bit WEP?"
    To: "Wayne Pascoe" <freebsd-feb@penguinpowered.org>, <freebsd-questions@freebsd.org>
    Date: Mon, 8 Mar 2004 13:53:33 -0600
    
    

    ----- Original Message -----
    From: "Wayne Pascoe" <freebsd-feb@penguinpowered.org>
    To: <freebsd-questions@freebsd.org>
    Sent: Monday, March 08, 2004 12:02 PM
    Subject: Alias in different subnet on card

    > Hi all,
    >
    > I'm running a firewall at the moment using FreeBSD 5.2.1 and IPFW. I
    > have 3 interfaces in the machine.
    >
    > I need to be able to firewall a 4th range of IP's. I have tried to do
    > this by adding an alias to xl1, but this hasn't worked. If I add the
    > alias with a mask of 255.255.255.255, no other machine can ping the
    > alias. I also see the following in /var/log/messages
    > Mar 8 18:02:13 styx-tmp kernel: arplookup 19x.xxx.xxx.196 failed: host
    > is not on local network
    >
    > The primary IP on xl 1 is currently 19x.xxx.xxx.1 and the mask on there is
    > 255.255.255.128 (/25)
    >
    > If I add the alias with a mask of 255.255.255.240 (/28) which is the
    > correct mask for this subnet, and the mask that all other machines use,
    > then I am able to ping this address. However, at this point, no
    > forwarding appears to take place for machines using this IP address as
    > their default route.
    >
    > Is there any way to use an alias to do firewalling like this or do I
    > have to get another network card? The problem with another network card
    > is that will mean a whole new machine as I'm out of slots in this one.
    >
    > Thanks in advance ?
    >
    > --
    > Wayne Pascoe
    > Microsoft complaining about the source
    > license used by Linux is like the event
    > horizon calling the kettle black - adamba on k5

    You have 3 networks in a firewall, and since we don't know the full
    topology, I'll use these network ranges for my example: 192.168.1.0,
    192.168.2.0, and 192.168.3.0. You now want to add a 4th range, let's say,
    192.168.4.0.

    ipconfig_xl1="inet 192.168.1.1 netmask 255.255.255.128"
    ipconfig_xl1_alias0="inet 192.168.2.1 netmask 255.255.255.128"
    ipconfig_xl1_alias1="inet 192.168.3.1 netmask 255.255.255.128"
    ipconfig_xl1_alias2="inet 192.168.4.1 netmask 255.255.255.128"

    The only time you would use a netmask of 255.255.255.255 is if the aliased
    IP is a member of a subnet that is already assigned on the interface.

    ipconfig_xl1_alias3="inet 192.168.1.2 netmask 255.255.255.255"

    Then you will need to add the appropriate firewall rules to allow those
    networks to either talk / no talk to the remaining network segments.

    It would help to have all of the ip information that you're using and your
    current alias maps to see just what's going on. Although, I'd guess that the
    first problem may be a subnetting issue.

    --
    Micheal Patterson
    TSG Network Administration
    405-917-0600
    Confidentiality Notice:  This e-mail message, including any attachments, is
    for the sole use of the intended recipient(s) and may contain confidential
    and privileged information. Any unauthorized review, use, disclosure or
    distribution is prohibited. If you are not the intended recipient, please
    contact the sender by reply e-mail and destroy all copies of the original
    message.
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: Ralph M. Los: "Cisco 350 card with 128-bit WEP?"

    Relevant Pages

    • RE: Secure Network Design (DMZ, LAN, etc)
      ... you'll see that their both on the same subnet. ... It has a port for the trusted network and a port ... Our firewall handles NAT. ... > servers, wouldn't it require a public IP and therefore be somewhat ...
      (Security-Basics)
    • Re: [fw-wiz] scanning...
      ... > ports are allowed through the firewall for each host... ... > cant see the port... ... > subnet and go ... > do network discovery and even seems that it will do so via whatever port you ...
      (Firewall-Wizards)
    • Re: 2nd DHCP Scope?
      ... I only have one subnet. ... As far as the router, there is an eithernet port with the IP of 172.20.4.1. ... the firewall is a Fortigate 100. ... Of course the 7 and 8 network are connected ...
      (microsoft.public.windows.server.networking)
    • Re: arpwatch question
      ... > The other subnet is remote, ... Not only is it remote, ... Doing this on someone else's network is _not_ a ... If it _is_ your net, you shouldn't need an alias, ...
      (comp.os.linux.networking)
    • Re: [fw-wiz] scanning...
      ... you can put in the IP range or subnet ... ports are allowed through the firewall for each host... ... listening because you cant see the port... ... Isn't there a "true" management network operation you can use on Cisco ...
      (Firewall-Wizards)