search for: notice1

Hi all, I''m not able to use shorewall for manage a bridge. I get the following error: ERROR: BRIDGING=Yes is not supported by Shorewall 4.4.13.3 Same error with version 4.4.11.4 I have read many documents, but I didnt find any solution. I have test many configuration (managing hosts,interfaces,zones files), but I get always the same error. Have I to compile a new kernel? With which

...st headers are HTTP/1.0 200 OK Content-Type: audio/mpeg icy-br:128 ice-audio-info: bitrate=128 icy-description:Mixed files of all kinds icy-genre:All icy-name:Radio Ostergaard icy-pub:0 icy-url:http://radio.home.ostergaard.net/index.php Server: Icecast 2.3.1 the shoutcast ones are ICY 200 OK icy-notice1:<BR>This stream requires <a href="http://www.winamp.com/">Winamp</a><BR> icy-notice2:SHOUTcast Distributed Network Audio Server/Linux v1.9.5<BR> icy-name:Radio Ostergaard icy-genre:All icy-url:http://radio.home.ostergaard.net/index.php content-type:audio/mpe...

...($connection,"Content-Type:audio/mpeg\r\n"); //ogg is application/ogg socket_write($connection,"Cache-Control:no-cache\r\n"); socket_write($connection,"Pragma:no-cache\r\n"); socket_write($connection,"Connection:close\r\n"); socket_write($connection,"icy-notice1:test1\r\n"); socket_write($connection,"icy-notice2:test2\r\n"); socket_write($connection,"icy-name:test server\r\n"); socket_write($connection,"icy-genre:industrial\r\n"); socket_write($connection,"$fr\r\n"); socket_write($connection,"Connection:ke...

Hi, I've changed /etc/resolv.conf, rebooted, here is the output: cat /etc/resolv.conf domain rona.loc search rona.loc nameserver 192.168.19.2 ------ smbclient -L $(hostname -f) -UAdministrator%<password> -d5 INFO: Current debug levels: all: 5 tdb: 5 printdrivers: 5 lanman: 5 smb: 5 rpc_parse: 5 rpc_srv: 5 rpc_cli: 5 passdb: 5 sam: 5 auth: 5 winbind: 5 vfs: 5

...($connection,"Content-Type:audio/mpeg\r\n"); //ogg is application/ogg socket_write($connection,"Cache-Control:no-cache\r\n"); socket_write($connection,"Pragma:no-cache\r\n"); socket_write($connection,"Connection:close\r\n"); socket_write($connection,"icy-notice1:test1\r\n"); socket_write($connection,"icy-notice2:test2\r\n"); socket_write($connection,"icy-name:test server\r\n"); socket_write($connection,"icy-genre:industrial\r\n"); socket_write($connection,"$fr\r\n"); socket_write($connection,"Connection:kee...

...($connection,"Content-Type:audio/mpeg\r\n"); //ogg is application/ogg socket_write($connection,"Cache-Control:no-cache\r\n"); socket_write($connection,"Pragma:no-cache\r\n"); socket_write($connection,"Connection:close\r\n"); socket_write($connection,"icy-notice1:test1\r\n"); socket_write($connection,"icy-notice2:test2\r\n"); socket_write($connection,"icy-name:test server\r\n"); socket_write($connection,"icy-genre:industrial\r\n"); socket_write($connection,"$fr\r\n"); socket_write($connection,"Connection:ke...

On Wed, Jun 25, 2003 at 11:34:07AM +1000, Michael Smith wrote: > > > 2) Should relay icy/x-audiocast stream metadata when connecting to > > icecast1/shoutcast/etc so that this information is available to YP > > Eh? It does. I even tested that with someone's shoutcast stream. It works. > Just add >

...g could have been broken (I think this is > unlikely, though - that code hasn't been changed lately AFAIK) Or connect via telnet and see what's really going on ;-) HTTP/1.0 200 OK Content-Type: audio/mpeg icy-br: 64 icy-genre: Talk icy-metaint: 8192 icy-name: Enemy Combatant Radio icy-notice1: <BR>This stream requires Winamp<BR> icy-notice2: SHOUTcast Distributed Network Audio Server/FreeBSD4 v1.9.2<BR> icy-pub: 1 icy-url: http://sf.indymedia.org/ Server: Icecast 2.0-alpha2/cvs Yes, it copies over the icy headers exactly as-is... Now what's interesting, prehaps t...

Hi, <p>I moved this to icecast@, since none of these are icecast development related questions and issues. Macsym wrote: > I didn't know so many people in the Icecast-Dev list were running Linux PPC! Oh well, I'm neither a developer nor running Linux PPC. ;) > Anyway, I understand that you guys don't have the time to help me with that > because you wouldn't be

Hello guys, I past the last days trying to configure my shorewall 4.06 firewall to allow openvpn bridging connection. My scenario is the following: roadwarrior (openvpn client) -------------> Internet ------------> (X.Y.W.Z - eth0) Firewall/Gateway (10.x.x.254 - eth1) --------> Local Lan -------> OpenVPN Server (10.x.x.249 - br0) where 10.x.x.0-254 is my private lan X.Y.Z.W is

Hi Karl, Thanks for your help, About the "Connection:" header, you are right, it's: "Connection: close" and NOT "Connection: keep-alive". The protocol when the SERVER sends the data is http 1.0. It's http 1.1 when the browser requests the data. I don't understand the "Content-Length: 54000000" header either. Also I noticed the flash player on