i've asked to be removed countless times. here's another message that i didn't want. it's really not that hard to remove somebody is it...
This is a forwarded message From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Saturday, January 31, 2004, 8:49:05 PM Subject: Fwd: [squid-users] 802.1Q and SQUID : bug ! Don't use them together ===8<==============Original message text=============== i've asked to be removed countless times. here's another message that i didn't want. it's really not that hard to remove somebody is it... This is a forwarded message From: PINEAU Olivier <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Tuesday, January 27, 2004, 10:44:26 AM Subject: [squid-users] 802.1Q and SQUID : bug ! Don't use them together ===8<==============Original message text=============== Instinctively, my router was on eth0.3 eth0 was just ifconfig eth0 0.0.0.0 up. So, eth0.3 was on vlan 3 port tagged. But with this configuration, squid made me madness : paquet were routed to client maybe 10 minutes after the request (!!!). Problem i have solved by puting my router on eth0 on untagged port. But, like i said before, with weird issues on several websites. Note : with eth0 and eth0.3 configuration, pinging on several interface works fine Olivier ----- Original Message ----- From: "Koppen, Peter van" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 27, 2004 3:44 PM Subject: Re: [squid-users] 802.1Q and SQUID : bug ! Don't use them together > I don't have a full understanding of SQUID or of 802.1Q on Linux but what is do know > is regular .1Q configuration. > > I see that you use the real Ethernet port eth0 for VLAN 3 and use a vlan for all the > other VLAN definitions. What is know of VLAN's this wil NOT work. Either you do not > use VLAN's or you just use VLAN's So to make this work you should define a VLAN > (VLAN3) for you gateway and not use the non-tagged etho interface. > > This can be tested, the proxy itself should not be able to connect to the pages you > listed. nor be able to trace or ping beyond it's own interfaces. > > Peter > > On 21 Jan 2004 at 16:01, PINEAU Olivier wrote: > > > Hi ! > > > > I want to inform you that i have discover a bug with 802.1Q technologie and > > SQUID. > > > > 802.1Q is for VLAN's : > > the module 8021Q is use to configure a network card to be present on > > different VLAN's (tagged port). > > > > My previous installation was : > > > > VLAN 3 on eth0 > > 10.0.0.0/255.254.0.0 > > routeur SDSL (gateway) 10.0.0.1 > > > > VLAN 2 on eth0.2 (vconfig add eth0 2) > > 10.20.0.0/255.255.0.0 > > > > VLAN 1 on eth0.1 (vconfig add eth0 1) > > 10.10.0.0/255.255.0.0 > > > > With this configuration, i was ending weirds issues : i was not able to log > > in hotmail, yahoo!mail, e-bay, or perform any transaction on net. > > For exemple, with hotmail, the https transaction was done and recorded on > > log, but the following url was not recorded in log and a basic error message > > prompt on navigator (DNS error or serveur not found). > > > > By despair, I change my network conf to use a different networdk card for > > each VLAN and it's finally works. > > So, don't use 8021Q module with SQUID ! > > > > > > NOTE : I use 8021Q for my data serveur (SAMBA and netatalk) and it works > > fine > > > > > > > > > > > met vriendelijke groet, > > > -- > Peter van Koppen > > Functie : Specialist Netwerk- en systeembeheer > Organisatie : Alfa-college > E-mail : [EMAIL PROTECTED] > TelefoonNr : +31(0)50-597 3054 > GSM : +31(0)6-53223700 > > ===8<===========End of original message text=========== -- Best regards, mortbox mailto:[EMAIL PROTECTED] ===8<===========End of original message text=========== -- Best regards, mortbox mailto:[EMAIL PROTECTED]
