[MSN] Firewall problemen?

Pagina: 1
Acties:

  • jsiegmund
  • Registratie: Januari 2002
  • Laatst online: 14-02 11:20
Zoals ik hier: http://gathering.tweakers...ist_messages/967806///msn al schreef heb ik wat problemen met de MSN service...

Ik ben er inmiddels achter dat het probleem zich alleen lijkt voor te doen wanneer er meerdere computers op het netwerk aangemeld zijn. Ben ik alleen kan ik zonder problemen tijden online zitten. Iemand een idee waar dit aan kan liggen? Ik werk met het standaard simple-firewall script op Linux.

  • jsiegmund
  • Registratie: Januari 2002
  • Laatst online: 14-02 11:20
Shop, nog steeds geen oplossing kunnen vinden helaas.

  • Wilke
  • Registratie: December 2000
  • Laatst online: 19:25
Wat is de inhoud van 'het standaard simple-firewall' script :? Er zijn in het verleden ontzettend vele topics geweest over MSN en firewalls e.d., heb je die opgezocht, en wat heb je evt. al geprobeerd om het op te lossen?

  • jsiegmund
  • Registratie: Januari 2002
  • Laatst online: 14-02 11:20
Ik heb uiteraard gezocht, maar kwam een hele hoop topics tegen over het niet in kunnen loggen, geen spellen kunnen spelen, geen filetransfer... etc. etc.

Mijn probleem is niet terug te vinden (ik kon het althans niet) en bestaat ook niet in MSN troubleshooters.

Het simple-firewall script gebruik ik al tijden naar volle tevredenheid, en ziet er alsvolgt uit:

code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
#!/bin/sh
#
# rc.firewall-2.4
FWVER=0.75
#
#               Initial SIMPLE IP Masquerade test for 2.4.x kernels
#               using IPTABLES.  
#
#               Once IP Masquerading has been tested, with this simple 
#               ruleset, it is highly recommended to use a stronger 
#               IPTABLES ruleset either given later in this HOWTO or 
#               from another reputable resource.
#
#
#
# Log:
#       0.75 - Added more kernel modules to the comments section
#       0.74 - the ruleset now uses modprobe vs. insmod
#       0.73 - REJECT is not a legal policy yet; back to DROP
#       0.72 - Changed the default block behavior to REJECT not DROP
#       0.71 - Added clarification that PPPoE users need to use
#              "ppp0" instead of "eth0" for their external interface
#       0.70 - Added commented option for IRC nat module
#            - Added additional use of environment variables 
#            - Added additional formatting
#       0.63 - Added support for the IRC IPTABLES module
#       0.62 - Fixed a typo on the MASQ enable line that used eth0
#              instead of $EXTIF
#       0.61 - Changed the firewall to use variables for the internal
#              and external interfaces.
#       0.60 - 0.50 had a mistake where the ruleset had a rule to DROP
#              all forwarded packets but it didn't have a rule to ACCEPT
#              any packets to be forwarded either
#            - Load the ip_nat_ftp and ip_conntrack_ftp modules by default
#       0.50 - Initial draft
#

echo -e "\n\nLoading simple rc.firewall version $FWVER..\n"


# The location of the iptables and kernel module programs
#
#   If your Linux distribution came with a copy of iptables, 
#   most likely all the programs will be located in /sbin.  If 
#   you manually compiled iptables, the default location will
#   be in /usr/local/sbin
#
# ** Please use the "whereis iptables" command to figure out 
# ** where your copy is and change the path below to reflect 
# ** your setup
#
#IPTABLES=/sbin/iptables
IPTABLES=/sbin/iptables
DEPMOD=/sbin/depmod
MODPROBE=/sbin/modprobe


#Setting the EXTERNAL and INTERNAL interfaces for the network
#
#  Each IP Masquerade network needs to have at least one
#  external and one internal network.  The external network
#  is where the natting will occur and the internal network
#  should preferably be addressed with a RFC1918 private address
#  scheme.
#
#  For this example, "eth0" is external and "eth1" is internal"
#
#
#  NOTE:  If this doesnt EXACTLY fit your configuration, you must 
#         change the EXTIF or INTIF variables above. For example: 
#
#            If you are a PPPoE or analog modem user:
#
#               EXTIF="ppp0" 
#
#
EXTIF="ppp0"
INTIF="eth0"
echo "   External Interface:  $EXTIF"
echo "   Internal Interface:  $INTIF"


#======================================================================
#== No editing beyond this line is required for initial MASQ testing ==


echo -en "   loading modules: "

# Need to verify that all modules have all required dependencies
#
echo "  - Verifying that all kernel modules are ok"
$DEPMOD -a

# With the new IPTABLES code, the core MASQ functionality is now either
# modular or compiled into the kernel.  This HOWTO shows ALL IPTABLES
# options as MODULES.  If your kernel is compiled correctly, there is
# NO need to load the kernel modules manually.  
#
#  NOTE: The following items are listed ONLY for informational reasons.
#        There is no reason to manual load these modules unless your
#        kernel is either mis-configured or you intentionally disabled
#        the kernel module autoloader.
#

# Upon the commands of starting up IP Masq on the server, the
# following kernel modules will be automatically loaded:
#
# NOTE:  Only load the IP MASQ modules you need.  All current IP MASQ 
#        modules are shown below but are commented out from loading.
# ===============================================================

echo "----------------------------------------------------------------------"

#Load the main body of the IPTABLES module - "iptable"
#  - Loaded automatically when the "iptables" command is invoked
#
#  - Loaded manually to clean up kernel auto-loading timing issues
#
echo -en "ip_tables, "
$MODPROBE ip_tables


#Load the IPTABLES filtering module - "iptable_filter" 
#  - Loaded automatically when filter policies are activated


#Load the stateful connection tracking framework - "ip_conntrack"
#
# The conntrack  module in itself does nothing without other specific 
# conntrack modules being loaded afterwards such as the "ip_conntrack_ftp"
# module
#
#  - This module is loaded automatically when MASQ functionality is 
#    enabled 
#
#  - Loaded manually to clean up kernel auto-loading timing issues
#
echo -en "ip_conntrack, "
$MODPROBE ip_conntrack


#Load the FTP tracking mechanism for full FTP tracking
#
# Enabled by default -- insert a "#" on the next line to deactivate
#
echo -en "ip_conntrack_ftp, "
$MODPROBE ip_conntrack_ftp


#Load the IRC tracking mechanism for full IRC tracking
#
# Enabled by default -- insert a "#" on the next line to deactivate
#
echo -en "ip_conntrack_irc, "
$MODPROBE ip_conntrack_irc


#Load the general IPTABLES NAT code - "iptable_nat"
#  - Loaded automatically when MASQ functionality is turned on
# 
#  - Loaded manually to clean up kernel auto-loading timing issues
#
echo -en "iptable_nat, "
$MODPROBE iptable_nat


#Loads the FTP NAT functionality into the core IPTABLES code
# Required to support non-PASV FTP.
#
# Enabled by default -- insert a "#" on the next line to deactivate
#
echo -en "ip_nat_ftp, "
$MODPROBE ip_nat_ftp


#Loads the IRC NAT functionality into the core IPTABLES code
# Required to support NAT of IRC DCC requests
#
# Disabled by default -- remove the "#" on the next line to activate
#
#echo -e "ip_nat_irc"
#$MODPROBE ip_nat_irc

echo "----------------------------------------------------------------------"

# Just to be complete, here is a partial list of some of the other  
# IPTABLES kernel modules and their function.  Please note that most 
# of these modules (the ipt ones) are automatically loaded by the 
# master kernel module for proper operation and don't need to be 
# manually loaded.
# --------------------------------------------------------------------
#
#    ip_nat_snmp_basic - this module allows for proper NATing of some 
#                        SNMP traffic
#
#    iptable_mangle    - this target allows for packets to be 
#                        manipulated for things like the TCPMSS 
#                        option, etc.
#
# --
#
#    ipt_mark       - this target marks a given packet for future action.
#                     This automatically loads the ipt_MARK module
#
#    ipt_tcpmss     - this target allows to manipulate the TCP MSS
#                     option for braindead remote firewalls.
#                     This automatically loads the ipt_TCPMSS module
#
#    ipt_limit      - this target allows for packets to be limited to
#                     to many hits per sec/min/hr
#
#    ipt_multiport  - this match allows for targets within a range
#                     of port numbers vs. listing each port individually
#
#    ipt_state      - this match allows to catch packets with various
#                     IP and TCP flags set/unset
#
#    ipt_unclean    - this match allows to catch packets that have invalid
#                     IP/TCP flags set
#
#    iptable_filter - this module allows for packets to be DROPped, 
#                     REJECTed, or LOGged.  This module automatically 
#                     loads the following modules:
#
#                     ipt_LOG - this target allows for packets to be 
#                               logged
#
#                     ipt_REJECT - this target DROPs the packet and returns 
#                                  a configurable ICMP packet back to the 
#                                  sender.
# 

echo -e "   Done loading modules.\n"



#CRITICAL:  Enable IP forwarding since it is disabled by default since
#
#           Redhat Users:  you may try changing the options in
#                          /etc/sysconfig/network from:
#
#                       FORWARD_IPV4=false
#                             to
#                       FORWARD_IPV4=true
#
echo "   Enabling forwarding.."
echo "1" > /proc/sys/net/ipv4/ip_forward


# Dynamic IP users:
#
#   If you get your IP address dynamically from SLIP, PPP, or DHCP, 
#   enable this following option.  This enables dynamic-address hacking
#   which makes the life with Diald and similar programs much easier.
#
echo "   Enabling DynamicAddr.."
echo "1" > /proc/sys/net/ipv4/ip_dynaddr


# Enable simple IP forwarding and Masquerading
#
#  NOTE:  In IPTABLES speak, IP Masquerading is a form of SourceNAT or SNAT.
#
#  NOTE #2:  The following is an example for an internal LAN address in the
#            192.168.0.x network with a 255.255.255.0 or a "24" bit subnet mask
#            connecting to the Internet on external interface "eth0".  This
#            example will MASQ internal traffic out to the Internet but not
#            allow non-initiated traffic into your internal network.
#
#            
#         ** Please change the above network numbers, subnet mask, and your 
#         *** Internet connection interface name to match your setup
#         


#Clearing any previous configuration
#
#  Unless specified, the defaults for INPUT and OUTPUT is ACCEPT
#    The default for FORWARD is DROP (REJECT is not a valid policy)
#
echo "   Clearing any existing rules and setting default policy.."
$IPTABLES -P INPUT ACCEPT
$IPTABLES -F INPUT 
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -F OUTPUT 
$IPTABLES -P FORWARD DROP
$IPTABLES -F FORWARD 
$IPTABLES -t nat -F

echo "   FWD: Allow all connections OUT and only existing and related ones IN"
$IPTABLES -A FORWARD -i $EXTIF -o $INTIF -m state --state ESTABLISHED,RELATED -j ACCEPT
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT
$IPTABLES -A FORWARD -j LOG

echo "   Enabling SNAT (MASQUERADE) functionality on $EXTIF"
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE



echo -e "\nDone.\n"


En wat heb ik al geprobeerd: niks. Ik gebruik dit script al langer, en voor de reinstall werkte het prima, dus ik zou niet weten wat er mis mee moet zijn. Verder heb ik niets anders gedaan dan normaal, waardoor ik geen flauw idee heb waar ik het moet zoeken. Daarom dus de vraag of jullie dat misschien wel weten.

Verwijderd

Staat er nog wat in je logs mbt het droppen van msn connecties? Eventueel ff je log monitoren en een msn connectie opzetten. Dan weten we precies welke packets ge-denied worden op je firewall, en welke tweaks we moeten maken aan het firewall script om het te laten werken...

  • jsiegmund
  • Registratie: Januari 2002
  • Laatst online: 14-02 11:20
Welke log moet ik daarvoor hebben? IPtables?

Verwijderd

yup. Iig een logfile waarin de logregels staan van je firewall. Meestal is dit iets als /var/log/messages, wat vol moet staan met regels waar "DROP" in voorkomt

  • jsiegmund
  • Registratie: Januari 2002
  • Laatst online: 14-02 11:20
Voila, ik heb even opgelet en kom nu steeds van dit soort blokjes tegen:

code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Nov 27 16:27:33 localhost pppoe[19539]: Inactivity timeout... something wicked happened on session 49374
Nov 27 16:27:33 localhost pppoe[19539]: Sent PADT
Nov 27 16:27:33 localhost pppd[19538]: Modem hangup
Nov 27 16:27:33 localhost pppd[19538]: Connection terminated.
Nov 27 16:27:33 localhost pppd[19538]: Connect time 12.7 minutes.
Nov 27 16:27:33 localhost pppd[19538]: Sent 89239 bytes, received 538522 bytes.
Nov 27 16:27:33 localhost /etc/hotplug/net.agent: NET unregister event not supported
Nov 27 16:27:33 localhost pppd[19538]: Exit.
Nov 27 16:27:33 localhost adsl-connect: ADSL connection lost; attempting re-connection.
Nov 27 16:27:38 localhost pppd[19722]: pppd 2.4.1 started by root, uid 0
Nov 27 16:27:38 localhost pppd[19722]: Using interface ppp0
Nov 27 16:27:38 localhost pppd[19722]: Connect: ppp0 <--> /dev/pts/0
Nov 27 16:27:38 localhost /etc/hotplug/net.agent: assuming ppp0 is already up
Nov 27 16:27:38 localhost pppoe[19723]: PPP session is 50400


"something wicked happened"... juist daar heb ik wat aan inderdaad.

  • jsiegmund
  • Registratie: Januari 2002
  • Laatst online: 14-02 11:20
Nog steeds niet opgelost helaas.

  • moto-moi
  • Registratie: Juli 2001
  • Laatst online: 09-06-2011

moto-moi

Ja, ik haat jou ook :w

Je laat een logfile zien waarin pppd en pppoe meuk staat, dat heeft dus bar weinig te maken met je iptables output ;)

God, root, what is difference? | Talga Vassternich | IBM zuigt


  • jsiegmund
  • Registratie: Januari 2002
  • Laatst online: 14-02 11:20
Dit is de logfile waar om gevraagd werd volgens mij, en de foutmeldingen daarin lijken me ook niet 100% normaal... daar komt bij dat ze erin staan op de momenten dat ik problemen ondervind, dus zou het wel eens erg goed hierdoor kunnen komen :)

  • moto-moi
  • Registratie: Juli 2001
  • Laatst online: 09-06-2011

moto-moi

Ja, ik haat jou ook :w

Eh, het enige wat ik zie is dat je modem de verbinding verbreekt ? Daarna maakt 'ie weer een verbinding.
Waarom 'ie de verbinding verbreekt staat er trouwens niet bij.

God, root, what is difference? | Talga Vassternich | IBM zuigt


  • jsiegmund
  • Registratie: Januari 2002
  • Laatst online: 14-02 11:20
Precies... en het is niet dat ik daarom vraag ofzo. Ik neem aan dat MSN het niet volhoudt zonder verbinding en er dus om die rede uitknalt. Er wordt meteen weer opnieuw verbinding gemaakt, en msn logt zichzelf weer in na 10 seconden ongeveer. Nu nog erachter zien te komen waarom die verbinding er af en toe mee ophoudt... fijne melding dat "something wicked happened"
Pagina: 1