On 11/25/10 12:25 PM, Stephen Brown wrote: > Thanks Tom, here's the output of shorewall show routing:
> > Table main: > > 70.90.228.192/29 dev eth0 proto kernel scope link src 70.90.228.197 > 10.5.10.0/24 dev vlan2 proto kernel scope link src 10.5.10.1 > 10.5.1.0/24 dev eth1 proto kernel scope link src 10.5.1.1 > default via 70.90.228.198 dev eth0 > > And this is a sample of what I see in the logs: > Nov 25 15:24:36 bubastis kernel: [28104.130146] martian source 10.5.1.1 > from 10.5.10.2, on dev eth1 > Nov 25 15:24:36 bubastis kernel: [28104.130152] ll header: > d8:5d:4c:b0:70:8e:00:25:90:01:35:44:08:00 > > I kinda think I know what's going on, but not really. > > Any help appreciated :) What is happening is that packets from 10.5.10.2 are arriving on eth1 even though 10.5.10.0/24 is supposedly connected to vlan2. So your VLAN configuration seems wrong. Sorry that I can't be more specific but I have no personal experience with VLAN configuration. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
