In the case you mentioned previously, does ifconfig show the interface in promisc mode? I have tried further investigating whether or not the interface is in promisc mode by using ethtool, a soft tool, however unsuccessful. I also attempted to use a hub on eth0 to see if tcpdump would pick up the packets in promisc mode; the packets are successfully captured on the hub. [I did not test eth1, but I shall tomorrow morning.] Both network interfaces are the same model/brand. Listed below is a snapshot of my ifconfig and a snippet from my lspci.
This list is pretty responsive - I just wanted to say thanks to everyone for taking time to help me out. ;)
Mahalo,
Chris
eth0 Link encap:Ethernet HWaddr 00:13:72:FC:84:36
inet6 addr: fe80::213:72ff:fefc:8436/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:7792 errors:0 dropped:0 overruns:0 frame:0
TX packets:9417 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:699418 (683.0 KiB) TX bytes:1846522 (1.7 MiB)
Interrupt:169
eth1 Link encap:Ethernet HWaddr 00:13:72:FC:84:37
inet6 addr: fe80::213:72ff:fefc:8437/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:318 errors:0 dropped:0 overruns:0 frame:0
TX packets:165 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:34204 (33.4 KiB) TX bytes:10886 (10.6 KiB)
Interrupt:225
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)
Subsystem: Dell: Unknown device 01b6
Flags: bus master, fast devsel, latency 0, IRQ 169
Memory at fe6f0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
Capabilities: [d0] Express Endpoint IRQ 0
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)
Subsystem: Dell: Unknown device 01b6
Flags: bus master, fast devsel, latency 0, IRQ 225
Memory at fe4f0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
Capabilities: [d0] Express Endpoint IRQ 0
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
On 10/4/06,
Alex Zeffertt <[EMAIL PROTECTED]> wrote:
>
> Now for the PROBLEM! The bridge can access IP's outside of the subnet
> via eth0 of the bridge, ie - pinging 128.171.1.1 <http://128.171.1.1 >,
> 128.171.3.13 <http://128.171.3.13>, 64.233.167.99
> <http://64.233.167.99 >. The laptop cannot ping the previously listed
> IPs. The only thing the laptop can ping is 128.171.103.11
Hi Chris,
I have seen a problem with some ethernet drivers where the interface
does not go into promiscuous mode automatically as the interface is added
to a bridge.
It's worth trying to do this manually with "ifconfig eth0 promisc" and
likewise for eth1, then seeing if things work.
A few ethernet drivers don't support promiscuous mode at all. But it
definitely looks to me the way you describe the problem that the devices
on the bridge are not in promiscuous mode.
Regards,
Alex
_______________________________________________ Bridge mailing list [email protected] https://lists.osdl.org/mailman/listinfo/bridge
