Nmap Development mailing list archives
Issue with Multihomed Linux System and -e Option
From: "Jason Alexander" <alexander.jason.a () gmail com>
Date: Fri, 24 Aug 2007 15:58:29 -0500
Hello, I have a linux box with two network interfaces, eth0 and eth1. I have the box configured with the following settings: 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:14:22:49:5b:b3 brd ff:ff:ff:ff:ff:ff inet 129.255.13.81/23 brd 129.255.13.255 scope global eth0 3: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:e0:98:29:4d:f6 brd ff:ff:ff:ff:ff:ff inet 129.255.99.148/27 brd 129.255.99.163 scope global eth1 129.255.99.128/27 dev eth1 proto kernel scope link src 129.255.99.148 129.255.12.0/23 dev eth0 proto kernel scope link src 129.255.13.81 127.0.0.0/8 dev lo scope link default nexthop via 129.255.99.129 dev eth1 weight 1 nexthop via 129.255.12.1 dev eth0 weight 10 When I test with ping and source from eth0 or eth1 it gets sourced from the correct and travels over the correct interface. When I do the following command : nmap -e eth0 -T5 -sS -sV -p- -v 129.255.XX.XX Everything works ok. Nmap scanns from the interface and address assigned to eth0. When I do the following: nmap -e eth1 -T5 -sS -sV -p- -v 129.255.XX.XX Packets are source from the address for eth1 but are being routed out the interface for eth0. Any ideas. Thanks Jason _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Issue with Multihomed Linux System and -e Option Jason Alexander (Aug 24)
- Re: Issue with Multihomed Linux System and -e Option nano bug (Aug 25)