similar to: No connection in DomUs with network-route

Believe me, I have tried everytbing I can think of to solve this problem. I will work my tail off to resolve this but I am fresh out of ideas. Any suggestions would be GREATLY appreciated. Here are the details... problem: server can see machines/shares on clients but clients cannot see machines/shares on server workgroup/domain: golgerth no router server: rpms: kernel 2.4.18.19.8.0

Hi all, I''m running Xen-3.2 and linux-image-2.6.18 as Dom0 kernel on a VT-x processor. The problem is that broadcast arp who-has packets are not seen in Dom0 kernel. I''ve tried both precompiled debian kernel and compiled latest one from sources as described at http://lists.xensource.com/archives/html/xen-users/2008-01/msg00699.html There is no linux bridge invoked,

I have 3 machines, T60 thinkpad with e1000 NIC Dell PowerEdge 2950 with bnx2 NIC HP DL360 G4P with tg3 NIC All running xen 3.03 / 2.6.16.29-xen I have a netbootable image with 2.6.16.29-xenU. This image when it boots creates a vlan eth0.4002, and then tries to communicate on that interface to a central server. On the machines with e1000 an bnx2 NICs, this works fine. On the

Hi, I would like to run a network firewall as a VM on a KVM host. There are ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP or other things. I have the VLANs 100-180 on the host's enp1s0, the VLANs 200-280 on the host's enp2s0 and the VLANs 300-380 on the host's enp3s0. To save myself from configuring all VLANs on the KVM host, I'd like to hand the entire

Hi all: I see a lot of the errors below in /var/log/messages on my firewall: Aug 1 00:47:44 munin kernel: [109008.257109] martian source 192.168.1.5 from 127.0.0.1, on dev eth1 Aug 1 00:48:44 munin kernel: [109068.257384] martian source 192.168.1.5 from 127.0.0.1, on dev eth1 Aug 1 00:49:44 munin kernel: [109128.257509] martian source 192.168.1.5 from 127.0.0.1, on dev eth1 Aug 1 00:50:44

hi everyone, so,first it seemed a trivial question to me, but since I could not find anybody being neither able to answer this question nor giving a short config example. after a few sleepless nights and exhausting all the reading and research. here I am sharing my problem with all of you, in the hope of some possible solution/sugestion. or is it that this is impossible?? below my

Greetings! I am still struggling with the issue that after vampiring from NT4 domain to Samba 3.0.7 with ldap backend, Windows XP cannot find the domain controller. In particular, WXP is an XP Prof which signed in AB_INITIO_DOM domain. After the migration I put the Samba Server (Priscilla) and WXP in an isolated network, and started up Priscilla as PDC for the network. But WXP

Hello everybody. I could not find an answer to my problem in the archive. (But that may just be me :-) ) I have a problem with proxy arp and connection from loc (localnet) and from the firewall. Works fine from internet to dmz / proxy arp and vise versa. I have a feeling the solution is simple, but I''m no guru in Linux routing etc. The problem seems to be the routing setup. loc -

While using the linux bridge module in 2.6.10, the kernel seems to munge the source IP address of broadcast UDP packets if they come from "0.0.0.1", and sticks on an address of the linux host. I humbly submit that re-writing the source address of packets is not proper behavior for a bridge, even if those source addresses are not traditionally valid. Sure, 0.0.0.1 isn't a valid

The WoL magic packet is only scanned for the string above, and not actually parsed by a full protocol stack, it could be sent as any network- and transport-layer protocol, although it is typically sent as a UDP <https://en.m.wikipedia.org/wiki/User_Datagram_Protocol> datagram <https://en.m.wikipedia.org/wiki/Datagram> to port <https://en.m.wikipedia.org/wiki/TCP_and_UDP_port> 0,]

Hi Krishna, 1) If you want to classify according to MAC address, you could use iptables to mark the packet (using MARK target), but just source MAC is available for now. 2) Usually tc just could classify by fields of IP layer and its sublayer, so I think classify by ethertype is unavailable. 3) VLAN tag belongs to MAC layer! I''m not sure how to QoS for VLAN, can anybody give some

Hello, I am running Shorewall 2.0.2f, on SuSE 9.2 distro, kernel 2.6.8-24.11-default My ip addr show output is as follows: 1: lo: <LOOPBACK,UP> 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 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0:

----- Original Message ---- > From: Pyun YongHyeon <pyunyh@gmail.com> > To: Ian FREISLICH <ianf@clue.co.za> > Cc: FreeBSD Current <freebsd-current@freebsd.org>; Robert Backhaus <robbak@robbak.com> > Sent: Monday, March 17, 2008 8:12:03 AM > Subject: Re: Packet corruption in re0 > > On Fri, Feb 22, 2008 at 10:43:22AM +0200, Ian FREISLICH wrote: >

Hi, Although Im dutch too, Ill write this in english. I got a similar problem then the one on the helpforum. Ill paste my setup first server tincd.conf ---- ListenPort = 8089 MyOwnVPNIP = 192.168.100.1/24 #VpnMask = 255.255.255.0 TapDevice = /dev/tap0 Passphrases=/usr/local/etc/tinc/passphrases server tapdev ---- tap0 Link encap:Ethernet HWaddr FE:FD:C0:A8:6F:01 inet

Have an interesting issue that's cropped up for us. We have a switch based vpn setup with multiple endpoints, some publicly accessible, some behind hide NAT. What we've noticed is that every machine can reach each other's VPN IP's up to a certain packet size. All machines can successfully ping each other up to 297 bytes. At 298 bytes and beyond, only "forwarded"

Hi Lars, I have no experience to use tcpdump, here is the output from TCPdump for your reference. Any idea? Use my home PC to ping company PC 01:00:25.154706 ethertype IPv4, IP 192.168.1.2 > 10.0.0.2: ICMP echo request, id 1, seq 17, length 40 01:00:25.154706 IP 192.168.1.2 > 10.0.0.2: ICMP echo request, id 1, seq 17, length 40 01:00:25.154706 IP 192.168.1.2 > 10.0.0.2: ICMP echo

An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110303/0fbefee6/attachment.html

Sure, I?ll see if we can narrow it down for you. > On Jun 12, 2015, at 2:25 PM, Etienne Dechamps <etienne at edechamps.fr> wrote: > > That's interesting. I'm using a near-HEAD tinc-1.1 myself and haven't > encountered this problem, but I think that's because I'm using it in > router mode, as opposed to switch mode. > > I'm trying to narrow

Hi, I am a newbie working on tc tool, i want to know whether we have the following classifiers available (1) source MAC address. (2) destination MAC address. (3) IEEE 802.1D user priority. (4) Ethertype (IEEE 802.3, 1998 Length/Type Field). Can any one help me in finding the help for the above classifiers. Thanks in advance Krishna Chaitanya

This makes it work for us: > On Jun 12, 2015, at 5:02 PM, Chris Clements <cclements at outlook.com> wrote: > > This looks like the culprit: > > http://www.tinc-vpn.org/git/browse?p=tinc;a=commit;h=7730d5f3ed9bd7c011dced5808130ffcbd74ea6b <http://www.tinc-vpn.org/git/browse?p=tinc;a=commit;h=7730d5f3ed9bd7c011dced5808130ffcbd74ea6b> > > >> On Jun 12,