search for: vlan4

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=40 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From laforge@netfilter.org 2003-02-03 16:49 ------- We haven't seen this

I''m trying to implement simple untagged vlans on our switch and have misconfigured something.. ISP gw is on the default vlan1 (untagged) Router eth1 is setup on the switch with default vlan1 and member of vlan4. eth0 is default vlan4 which connects to the clients that are all default members of vlan4 eth0 is x.x.x.86/28 This is what clients are connecting to as their gw.. (no nat) eth1 is x.x.x.82/26 default route is .65/26 dev eth1 If client is default vlan4, but a member of vlan1 then it all wor...

...Kernel 2.6.18, Shorewall 3.2.4, iptables 1.3.5, and iproute iproute2-ss060323. The problem is that I can''t get the GRE packets to make it through the firewall. Any time I try to pass traffic I get (on the righthand host in the diagram): Jan 4 10:53:47 slc-gw-01 Shorewall:INPUT:REJECT:IN=vlan4 OUT= MAC=00:15:c5:f5:99:be:00:b0:c2:89:af:68:08:00 SRC=67.42.31.242 DST=166.70.106.148 LEN=112 TOS=0x00 PREC=0x00 TTL=240 ID=0 DF PROTO=47 I even went as far as putting a rule (ACCEPT inet:67.42.31.242 $FW 47) instead of the entry in the tunnels file with the same result. Here are my config...

...We run dell managed switches here, so we don't have the luxury of running CDP to force the VOIP vlan. I haven't been able to get the polycom phones to talk on a manually set vlan. I have some junky sipura phones that work fine-(get dhcp, register to asterisk etc) when i manually set them to vlan4. Any advice you guys have would be greatly appreciated! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060412/09ffb869/attachment.htm

Package: xen-utils-4.17 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainers, On one of our domUs we discovered that the network interface names were wrongly assigned since recreating the domU after an upgrade to bookworm. If over 10 network interfaces are configured the mapping (dom0) vifX.10 <-> eth10 (domU) does not apply anymore. Instead the interfaces on dom0 are

Hello, I'm wondering about closing some information leaks in FreeBSD jails from the "outside world". Not that critical (depends on the application), but a simple user, with restricted devfs in the jail (devfsrules_jail for example from /etc/defaults/devfs.rules) can figure out the following: - network interfaces related data, via ifconfig, which contains everything, but the

Hello, Thanks for the great Shorewall which has replaced my hard to maintain home-made scripts. First, what works. Our local network is 10.48.X.X with multiple vlan, each on a dedicated interface. We use Shorewall 4.4.11 from Debian Squeeze. We have a 2 ISP: - isp1 : an optical fiber provider with 10 Mbps. - isp2 : a DSL provider with 15Mbits/1Mbits. We use isp2 as the default outgoing