more dumb vlan questions

Ok, so I'm hoping the answer to this question will complete my basic understanding of vlan setups. I have a system with the following network device configurations: - hostname.dc0: up hostname.vlan0: inet 172.17.1.1

another dumb vlan question

Lets say I'm setting up vlan devices so that 4 completely separate subnets' gateways can share same ethernet port on the router. Is it more appropriate to give the physical device itself an ip address and then create 3 vlan devices, or to give the physical device no ip address at all and

vlan vs ip aliases

Hey everyone, I've got a really stupid but really simple question. If I have an openbsd machine acting as an internal router (private IP addresses on all interfaces) for several subnets that have to share physical ethernet devices, should I use IP aliases or vlans, and in either case, would

net.inet.ip.mforwarding?

Sorry I should know this but I'm sorta green. If I enable net.inet.ip.mforwarding on all my routers, should that allow OS X things like bonjour and iTunes music sharing to work across the bridge?

Re: net.inet.ip.mforwarding?

weren't designed for anything other than small-scale home use. i'm acutely aware of that at this point. (the mac decision was someone else's) anyway, thanks for your time, ~jon Jussi Peltola wrote: Jonathan Whiteman wrote: Sorry I should know this but I'm sorta green. If I enable

Re: net.inet.ip.mforwarding?

Thank you both for your responses. I have made this diagram clearer because I sort of *am* using the same subnet on both sides of the bridge... or at least that was my intent, but obviously the address ranges have to be separate on both sides of the bridge even though the netmasks need to be the

Re: net.inet.ip.mforwarding?

Sorry just for the sake of correctness: em0 and em1 are the devices on firewall 2, not en0 and en1... thats a typo. Jonathan Whiteman wrote: Thank you both for your responses. I have made this diagram clearer because I sort of *am* using the same subnet on both sides of the bridge

Re: Strange vpn trouble

Actually I am having a similar problem with an entirely different (I think) VPN solution. Pings work for me but tcp/ip *returns* don't work. Sometimes they only fail on the first try, but for some hosts they never respond. Two questions, out of curiosity, is this VPN you've set up

Re: HTTP URL filtering?

Yes, I'd recommend pf. If you've never worked with it before, the PF section of the FAQ is an excellent starting point. http://www.openbsd.org/faq/pf/index.html Xavier Mertens wrote: Hi *, I've a problem with an Apache web server hit by f*cking spammers... I would like to filter some URLs

Re: HTTP URL filtering?

Sorry I should have read the original more carefully before replying. For some reason I thought you wanted to filter by source address. PF is not the way you'd want to go for filtering based on the HTTP GET request. Jonathan Whiteman wrote: Yes, I'd recommend pf. If you've never worked

vpn bridge misbehavior

Greetings all, Last week I described briefly a problem with *return* TCP/IP traffic only, across a LAN-to-LAN VPN network bridge, only on the first connection. I appreciate your responses and so now as you've requested I have composed a detailed network topology and configuration document in

vpn bridge misbehavior

Greetings. Is there a commonly known cause of *return* TCP/IP traffic to reach but be dropped rather than passed back across a bridge (ala bridgename.bridge0) but... get this... only on the first try? I'd like to get into a detailed explanation of the network topology I'm working with here but