similar to: Samba sending broadcasts on wrong devices.

Hello list, I wish to report a problem with openvpn tunnels. Synopsis: Despite adding policies to the shorewall policy file, I have to add extra rules to allow the UDP port 5000 packets to get through. I have used no particular setup guide. I believe this problem goes away with shorewall 2.0.9, as I have implemented openvpn with that version on a different machine, and I see no UDP:5000 packet

When I add all interfaces, the internet does not work.... eth0 = interneteth1 = lan ------------------auto eth0 iface eth0 inet static address 192.168.1.254 netmask 255.255.255.0 broadcast 192.168.1.255 auto eth1 iface eth1 inet static address 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.254 auto xenbr0 iface xenbr0 inet static

Hi, I've been trying to get a couple of routers up after h/w failure. The border router is an OpenBSD firewall running NAT between the Internet and a DMZ like subnet, and in that a Linux antivirus server is running NAT to the LAN. When the client does a DNS query it reaches to the f/w where dns is running and is returned into the A/V server but never hits the 0.254 interface. (Shown by

I have an ADSL router, a linux box with two NICS connected to the router and another PC connected to the router. I installed shorewall using the two interface method. I can ping and see the webserver on the linux box from the local network, but not from the internet. Sys info as follows: [root@wilma root]# shorewall version 1.4.6b [root@wilma root]# ip addr show 1: lo: <LOOPBACK,UP> mtu

Hi all, I''m new to shorewall and have been struggling with several problems for several days now. Most of them are solved, but one still persists. The firewall is running on my server under Debian Sarge (Kernel 2.6) I''ve got three network interfaces: ppp0 (DSL Internet) eth1 (lan) ath0 (wlan) eth1 and ath0 are bridged together to br0. The problem is, that Samba (also running

Thanks for your email. Yes it does provide some insight into why I could hack a Linux DHCP server into providing enough PXE boot information for PXE 3 clients but PXE 2.1 were happy (ROMs under many circumstances need to use proxy dhcp 4011 - as documented by IBM on the link I shared earlier). It appears only the most latest Dell business systems have EFI 64 support, and the best you can expect

Spike White, Sent: Saturday, December 27, 2014 4:32 AM > > Luke, I have considerable experience with this. We use WDS at work > for PXE (MS-centric shop). I use pxelinux at home. > > I've got WDS working in our test lab w/ UEFI. As you state, it strongly > wishes to do proxyDHCP (port 4011). More on this in a bit. > > It's quite common to segregate the DHCP

Here's the output: Feb 9 15:51:26 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:2b:67:5b:a7:08:00 SRC=192.168.1.54 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=51248 DF PROTO=TCP SPT=1964 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT=

Hi everybody, I'm facing a issue with the pxelinux when trying to Boot WDS and I run PXELINUX version 4.03 2010-10-22 and trying to chain (pxechain.com is from the same syslinux package as pxelinux) the WDS (that is a windows 2008 R2). $WINDOWS-2K8-R2-IP$ = The IP address to the WDS server and this is the config in the pxelinux.cfg/default $LINUX-PXE-SERVER$ = The server that serves the

> Date: Thu, 25 Dec 2014 07:07:52 +0000 > From: Luke Ledgerd <luke.ledgerd at niteco.se> > To: "syslinux at zytor.com" <syslinux at zytor.com> > Subject: [syslinux] Chain-loading from WDS to PXELinux on a different > tftp server > Message-ID: <17ba7ad419d54b6cab685c2cedc3de95 at NI-MAILEX.niteco.se> > Content-Type: text/plain;

Dear All, First posting here... I am trying to integrate a PXELinux boot into my native-mode WDS server. I have found that making WDS boot the PXELinux is easy (see below), it is making PXELinux give control back to WDS that I have not cracked yet. -In your WDS server, copy the contents of your tftpboot folder to the Boot\x86 folder in your RemoteInstall one. -Open the Windows Deployment

On May 31, 2012 5:23 AM, "Arends, R.R." <r.r.arends at hr.nl> wrote: > > Hello Genec, > > Got a question regarding pxechn.c32 in combination with wds (2k8r2). > > We got (i)pxelinux as our main pxe system, and want to chain to wds with a vesamenu option. > > I tried the latest pxechn.c32 from git. But somehow wds still tries to contact the next-server (main

On Dec 25, 2014 2:11 AM, "Luke Ledgerd" <luke.ledgerd at niteco.se> wrote: > > Hey guys, > > We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off

Hi all. I have a NAT problem. I have read FAQs and a lot of masquerading docs, but this seems such a simple problem, that I guess noone else will consider this a problem... This is my setup: shorewall version 1.4.6.c uname -a Linux server 2.4.21-0.13mdksecure #1 SMP [root@server shorewall]# ip addr show 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00

Hey guys, We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off anything you want to including PXELinux. The stuff I was talking about before with PXELinux not working in

sorry, i''m confuse where to post my problem.. i was post to shorewall-users, but must read to support.html this''s my problem ----------- i have squid running on DMZ zone and my network using ProxyARP on eth1 and eth2 mylinuxbox slackware 9.2 my network can access to internet normal, but can''t redirect to squid server from firewall. sometimes my network can connect

Thanks for this answer. As I understood, for example if parameter bind interfaces only = yes is and interfaces = lan0 (192.168.0.254) is and if broadcast packet goes from 95.95.95.14 such packet will be dropped (in other words) ? Am I right ? And other thing. Why is 192.168.0.255 (network broadcast) opened for ? May be exact such address (network broadcast) is inbtended for receiving broadcasts

Hello all, This might have been fixed in later versions (I am using R1.7.0), r-help archive contains messages reporting similar problems but no reports of codes fixes. I have encountered a couple of problems using the silhouette function. one occurs when the clustering contains clusters composed of 1 element (Martin Maechler posted code few months ago that fixes a similar problem that occurs

Hello, We are trying to set up a configuration with pxelinux on a linux machine and WDS, allowing us to be free to boot linux netboot installers from the tftp server. We have validated that pointing our dhcp server to the wds server works perfectly. Our idea was to use pxechain.com to launch the wdsnbp.com kernel as below : label windows KERNEL pxechain.com APPEND <ip

Hmmm, I founded some at https://lists.samba.org/archive/samba-technical/2012-July/085752.html As I saw these patches was already implemented. But is it possible to receive broadcast not to 0.0.0.0 but to x.y.z.255 ? This is network broadcast either. And opened 0.0.0.0 even with checking of source net is quite insecure from net security point of view. I think so. May be is it necessary to add