- WLUG - wlug.mailman3.com

Mailing List with web post interface

by Michael Zarozinski

Does anyone know of a mailing list package that allows you to post via a web form along with the standard email interface?

Aug. 21, 2006

Re: [Wlug] router/printing problems

by Jared Greenwald

To my knowledge, that is the case. I had a previous configuration that involved wireless and wired. I didn't have anything to broadcast wireless other than my linksys wireless router, but I didn't want to use that as the outside-facing router, so that I could have more control than just the NAT the linksys provided. Anyway, I ended up with a strange configuration. On the router Linux box, I had three NICs: one outward facing, one that serves 192.168.1.x, and one that serves 192.168.2.x. The .1.x network is my main network on which I run a fixed-address dhcp as well as local dns and share my printers. The NIC that served the 1.x network was plugged into a switch that services the rest of the house. The 2.x network is kinda tricky. This network was only connected directly to the WAN port of the linksys - so the linksys was "thinking" that it was doing stuff (explaination follows). On the linksys, all forwarding and dhcp was turned off (dhcp is served from the Linux router). What I did was put a crossover cable from one of the switch ports on the router directly to the switch that was serving the 1.x network. This allows any client (wired or wireless) to connect directly to the 1.x network without ever having to deal with the 2.x private network and the effect is that the linksys is an access point without being an access point. It also allows me to share printers and drives across mac/windows/linux (I have all three) without crossing over subnets. (The main reason for me doing this is that its more cost effective usually since routers can usually be found on sale for $30, while access points are usually $100+.) I've recently replaced the router with a straight access point, thus eliminating the need for the 2.x network. I can furnish a diagram upon request. -Jared On 8/21/06, Bill Smith <wsmith(a)chezsmith.com> wrote: > On Sun, 20 Aug 2006 22:41:17 -0400, Bill Mills-Curran wrote: > > >I have a home network with 2 routers. > > > >My 192.168.2.x network has a couple of windows boxes (some wireless) > >behind a linkSys router. This network feeds to my 192.168.1.x network > >which connects to the internet through a second router. My linux box > >(samba print server) is on the 192.168.1.x network and has a static > >IP. I just moved to this setup when I got Verizon FIOS. (Their > >wireless router has poor range.) > > > >Problem. Since moving, I can't print to the samba-served printer from > >the windows boxes. I have modified samba to accept connections from > >the 192.168.2.x machines. Here's my samba log for the machine that > >tries to print. > > I might well be mistaken, but don't Windows systems have to be on the > same network to interact with each other? > > If that is indeed the case, then the Windows systems won't be able to > work with the Samba server very easily. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > William Smith wsmith-at-chezsmith-dot-com > Fall River, MA http://www.chezsmith.com > > "For every complex problem, there is an answer which is > short, simple and wrong." -- H.L. Mencken > * TAG! v3.2 * > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > > >

Aug. 21, 2006

Re: [Wlug] router/printing problems

by Bill Smith

On Sun, 20 Aug 2006 22:41:17 -0400, Bill Mills-Curran wrote: >I have a home network with 2 routers. > >My 192.168.2.x network has a couple of windows boxes (some wireless) >behind a linkSys router. This network feeds to my 192.168.1.x network >which connects to the internet through a second router. My linux box >(samba print server) is on the 192.168.1.x network and has a static >IP. I just moved to this setup when I got Verizon FIOS. (Their >wireless router has poor range.) > >Problem. Since moving, I can't print to the samba-served printer from >the windows boxes. I have modified samba to accept connections from >the 192.168.2.x machines. Here's my samba log for the machine that >tries to print. I might well be mistaken, but don't Windows systems have to be on the same network to interact with each other? If that is indeed the case, then the Windows systems won't be able to work with the Samba server very easily. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- William Smith wsmith-at-chezsmith-dot-com Fall River, MA http://www.chezsmith.com "For every complex problem, there is an answer which is short, simple and wrong." -- H.L. Mencken * TAG! v3.2 *

Aug. 21, 2006

Re: [Wlug] router/printing problems

by Christoph

How are the networks configured? subnet mask, broadcast, routes, etc... what devices deliver dhcp, and what clients use it? How are the routers configured? Route/Bridge? My hunch... you need a static route for 192.168.2.x on the Linux box since it's default route probably points towards the internet. Or, put the static route on the main (other) router. That probably makes more sense... Just guessing though. -cfd On Sun, 2006-08-20 at 22:48 -0400, Bill Mills-Curran wrote: > On Sun, Aug 20, 2006 at 10:41:17PM -0400, Bill Mills-Curran wrote: > > Date: Sun, 20 Aug 2006 22:41:17 -0400 > > From: Bill Mills-Curran <bill(a)mills-curran.net> > > To: Worcester Linux Users Group <wlug(a)wlug.org>, BLU Discuss <discuss(a)blu.org> > > Cc: > > Subject: router/printing problems > > Precedence: list > > > > I have a home network with 2 routers. > > > > My 192.168.2.x network has a couple of windows boxes (some wireless) > > behind a linkSys router. This network feeds to my 192.168.1.x network > > which connects to the internet through a second router. My linux box > > (samba print server) is on the 192.168.1.x network and has a static > > IP. I just moved to this setup when I got Verizon FIOS. (Their > > wireless router has poor range.) > > > > Problem. Since moving, I can't print to the samba-served printer from > > the windows boxes. I have modified samba to accept connections from > > the 192.168.2.x machines. Here's my samba log for the machine that > > tries to print. > > > > [2006/08/20 04:02:21, 1] smbd/server.c:open_sockets_smbd(353) > > Reloading services after SIGHUP > > [2006/08/20 22:17:10, 0] smbd/server.c:main(798) > > smbd version 3.0.14a-2 started. > > Copyright Andrew Tridgell and the Samba Team 1992-2004 > > [2006/08/20 22:27:29, 0] tdb/tdbutil.c:tdb_log(725) > > tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 > > at offset=175296 > > [2006/08/20 22:28:09, 0] tdb/tdbutil.c:tdb_log(725) > > tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 > > at offset=175296 > > > > Any suggestions? > > > > TIA, > > Bill > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > > > _______________________________________________ > > Discuss mailing list > > Discuss(a)blu.org > > http://olduvai.blu.org/mailman/listinfo/discuss > > > The previous was the smbd.log. Here's the one for the client > 192.168.1.153.log: > > [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) > getpeername failed. Error was Transport endpoint is not connected > [2006/08/20 22:27:25, 0] lib/access.c:check_access(328) > [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) > getpeername failed. Error was Transport endpoint is not connected > Denied connection from (0.0.0.0) > [2006/08/20 22:27:25, 1] smbd/process.c:process_smb(1084) > [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) > getpeername failed. Error was Transport endpoint is not connected > Connection denied from 0.0.0.0 > [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket_data(430) > write_socket_data: write failure. Error = Connection reset by peer > [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket(455) > write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection > reset by > peer > [2006/08/20 22:27:25, 0] lib/util_sock.c:send_smb(647) > Error writing 5 bytes to client. -1. (Connection reset by peer) > [2006/08/20 22:28:32, 0] tdb/tdbutil.c:tdb_log(725) > tdb(/var/cache/samba/printing/hp.tdb): rec_free_read bad magic > 0x42424242 at offset=673736 > > Bill >

Aug. 21, 2006

Re: [Wlug] router/printing problems

by Bill Mills-Curran

On Sun, Aug 20, 2006 at 10:41:17PM -0400, Bill Mills-Curran wrote: > Date: Sun, 20 Aug 2006 22:41:17 -0400 > From: Bill Mills-Curran <bill(a)mills-curran.net> > To: Worcester Linux Users Group <wlug(a)wlug.org>, BLU Discuss <discuss(a)blu.org> > Cc: > Subject: router/printing problems > Precedence: list > > I have a home network with 2 routers. > > My 192.168.2.x network has a couple of windows boxes (some wireless) > behind a linkSys router. This network feeds to my 192.168.1.x network > which connects to the internet through a second router. My linux box > (samba print server) is on the 192.168.1.x network and has a static > IP. I just moved to this setup when I got Verizon FIOS. (Their > wireless router has poor range.) > > Problem. Since moving, I can't print to the samba-served printer from > the windows boxes. I have modified samba to accept connections from > the 192.168.2.x machines. Here's my samba log for the machine that > tries to print. > > [2006/08/20 04:02:21, 1] smbd/server.c:open_sockets_smbd(353) > Reloading services after SIGHUP > [2006/08/20 22:17:10, 0] smbd/server.c:main(798) > smbd version 3.0.14a-2 started. > Copyright Andrew Tridgell and the Samba Team 1992-2004 > [2006/08/20 22:27:29, 0] tdb/tdbutil.c:tdb_log(725) > tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 > at offset=175296 > [2006/08/20 22:28:09, 0] tdb/tdbutil.c:tdb_log(725) > tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 > at offset=175296 > > Any suggestions? > > TIA, > Bill > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > Discuss mailing list > Discuss(a)blu.org > http://olduvai.blu.org/mailman/listinfo/discuss The previous was the smbd.log. Here's the one for the client 192.168.1.153.log: [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2006/08/20 22:27:25, 0] lib/access.c:check_access(328) [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0) [2006/08/20 22:27:25, 1] smbd/process.c:process_smb(1084) [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection reset by peer [2006/08/20 22:27:25, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) [2006/08/20 22:28:32, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/printing/hp.tdb): rec_free_read bad magic 0x42424242 at offset=673736 Bill

Aug. 20, 2006

router/printing problems

by Bill Mills-Curran

I have a home network with 2 routers. My 192.168.2.x network has a couple of windows boxes (some wireless) behind a linkSys router. This network feeds to my 192.168.1.x network which connects to the internet through a second router. My linux box (samba print server) is on the 192.168.1.x network and has a static IP. I just moved to this setup when I got Verizon FIOS. (Their wireless router has poor range.) Problem. Since moving, I can't print to the samba-served printer from the windows boxes. I have modified samba to accept connections from the 192.168.2.x machines. Here's my samba log for the machine that tries to print. [2006/08/20 04:02:21, 1] smbd/server.c:open_sockets_smbd(353) Reloading services after SIGHUP [2006/08/20 22:17:10, 0] smbd/server.c:main(798) smbd version 3.0.14a-2 started. Copyright Andrew Tridgell and the Samba Team 1992-2004 [2006/08/20 22:27:29, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 at offset=175296 [2006/08/20 22:28:09, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 at offset=175296 Any suggestions? TIA, Bill

Aug. 20, 2006

Re: [Wlug] DNS and PPP

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HI everybody, Upon further investigation, it appears that the dns server is not replying when the palmtx makes its dns request. The dns server does reply to everybody else on my network. I'll have to look at the dnsmasq configuration to see why that might be happening. I turned on logging for dnsmasq, and it definitely receives the query, and it receives a reply from the upstream dns server, but it doesn't send a reply to the palmtx. I turned off the firewalling to see if it was eating the dns reply, but that doesn't seem to be happening. More news later, Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFE5SnOHl0iXDssISsRArkAAJ0cejcUErAjfMGGmnbd4IKN1IrP6gCeKv/R AAPd7HDzK2lR5W2/3REYov0= =2QZu -----END PGP SIGNATURE-----

Aug. 17, 2006

Re: [Wlug] DNS and PPP

by John Stoffel

Andy> I have a setup like this: Andy> palmtx -> computer --> firewall/dns_server Andy> The connection between the palmtx and the computer is a PPP Andy> connection (ppp0) over bluetooth, which works fine between the Andy> palmtx and the computer. More details please. IP addresses, routes, netstat -rn on the computer, etc. Also, do you have iptables turned on the computer, or any other firewalling type of software? So when the DNS response comes back, what do your NAT table logs and such say? Andy> The connection between the computer and the firewall is ethernet (eth0), Andy> and it also works fine. Andy> My problem is that I can't get the palmtx to get dns responses back from Andy> the dns server. Andy> I ran ethereal on eth0 and ppp0. I can see the DNS query go from the Andy> palmtx to the computer, and out to the firewall on eth0. The firewall Andy> responds onto eth0, but the computer doesn't seem to be sending that Andy> back to the palmtx on ppp0. Andy> On the computer, routing is enabled (or the dns server wouldn't have Andy> seen the initial request). The route table has the entry (1st in the Andy> list) for the PPP connection. Andy> iptables is set to accept everything. Andy> What did I miss? Andy> Thanks! Andy> Andy Andy> - -- Andy> Andy Stewart, Founder Andy> Worcester Linux Users' Group Andy> Worcester, MA, USA Andy> http://www.wlug.org Andy> -----BEGIN PGP SIGNATURE----- Andy> Version: GnuPG v1.2.5 (GNU/Linux) Andy> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org Andy> iD8DBQFE4+1tHl0iXDssISsRAmVEAJ4/yMPiP3Qrm8twHyLxdgJYKJEAtQCfeGmw Andy> 4J+q1cxJh9v6GyjomZPMSEg= Andy> =0wJS Andy> -----END PGP SIGNATURE----- Andy> _______________________________________________ Andy> Wlug mailing list Andy> Wlug(a)mail.wlug.org Andy> http://mail.wlug.org/mailman/listinfo/wlug Andy> !DSPAM:44e3eed4103371184020261!

Aug. 17, 2006

Re: [Wlug] DNS and PPP

by Jamie Guinan

On Thu, 17 Aug 2006, Andy Stewart wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > HI gang, > > I have a setup like this: > > palmtx -> computer --> firewall/dns_server > > The connection between the palmtx and the computer is a PPP connection > (ppp0) over bluetooth, which works fine between the palmtx and the computer. > > The connection between the computer and the firewall is ethernet (eth0), > and it also works fine. > > My problem is that I can't get the palmtx to get dns responses back from > the dns server. > > I ran ethereal on eth0 and ppp0. I can see the DNS query go from the > palmtx to the computer, and out to the firewall on eth0. The firewall > responds onto eth0, but the computer doesn't seem to be sending that > back to the palmtx on ppp0. > > On the computer, routing is enabled (or the dns server wouldn't have > seen the initial request). The route table has the entry (1st in the > list) for the PPP connection. > > iptables is set to accept everything. > > What did I miss? > > Thanks! > > Andy Hi Andy, So are you doing NAT for the palmtx via the computer? What about, $ cat /proc/sys/net/ipv4/ip_forward Is it set to "1"? -Jamie

Aug. 17, 2006

DNS and PPP

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HI gang, I have a setup like this: palmtx -> computer --> firewall/dns_server The connection between the palmtx and the computer is a PPP connection (ppp0) over bluetooth, which works fine between the palmtx and the computer. The connection between the computer and the firewall is ethernet (eth0), and it also works fine. My problem is that I can't get the palmtx to get dns responses back from the dns server. I ran ethereal on eth0 and ppp0. I can see the DNS query go from the palmtx to the computer, and out to the firewall on eth0. The firewall responds onto eth0, but the computer doesn't seem to be sending that back to the palmtx on ppp0. On the computer, routing is enabled (or the dns server wouldn't have seen the initial request). The route table has the entry (1st in the list) for the PPP connection. iptables is set to accept everything. What did I miss? Thanks! Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFE4+1tHl0iXDssISsRAmVEAJ4/yMPiP3Qrm8twHyLxdgJYKJEAtQCfeGmw 4J+q1cxJh9v6GyjomZPMSEg= =0wJS -----END PGP SIGNATURE-----

Aug. 17, 2006